Normalize the scope before the price

Use this fill-in register for the same categories across each proposal and configured alternative. Leave an amount blank when the proposal does not state it. Included is not a usable answer unless it identifies the artifact, operating responsibility, condition, and exclusion.

At minimum, ask what covers:

  • discovery of appointment authority and exception policy;
  • message templates, consent handling, and delivery ownership;
  • calendar or scheduling connection setup and ongoing usage;
  • cancellation, waitlist, and conflicting-acceptance cases;
  • an approved recovery exercise and its retained record;
  • support, change requests, incidents, data export, and termination.
Category Included work / term One-time amount Recurring amount Usage or metered amount Owner Ambiguity or exclusion
Discovery and policy map __________ __________ __________ __________ __________ __________
Appointment record boundary __________ __________ __________ __________ __________ __________
Reminder / offer message path __________ __________ __________ __________ __________ __________
Calendar or scheduling integration __________ __________ __________ __________ __________ __________
Cancellation and waitlist exceptions __________ __________ __________ __________ __________ __________
Recovery exercise and records __________ __________ __________ __________ __________ __________
Support, changes, and incident route __________ __________ __________ __________ __________ __________
Data export, handoff, and termination __________ __________ __________ __________ __________ __________

Name the recovery work explicitly

NIST's SP 800-34 Rev. 1 describes recovery roles and validation before normal operation resumes. That is useful framing for asking who owns recovery and validation in a proposed workflow; it does not create a contract term, prescribe an appropriate service level, or show that a vendor provides one.

Ask the supplier to distinguish an implementation demonstration from a recovery exercise. A workflow can send a fixture message while still having no named response to mismatched appointment records, an expired offer, a failed calendar update, or a staff member who cannot access the service.

Hold ambiguous proposals

Do not compare total price until the buyer can identify appointment-record authority, all messages and calendar boundaries, exception owner, recovery validation, recurring support, and exit data. A configured or assisted alternative may be the smaller credible option when the proposed custom layer has unresolved operations.

For ongoing maintenance scope, see What a Software Maintenance Retainer Should Reserve, Exclude, and Report. For a pre-award ambiguity record, see Record Software Proposal Assumptions Before You Commit.

Does this worksheet choose the cheaper option?

No. It makes categories comparable. A buyer still needs authorised proposals, actual rates, operating constraints, and appropriate commercial and legal review for the final decision.