Separate a workflow from a line item
Ask the proposal to identify the appointment authority, controlling time zone, recurrence policy where relevant, and every interface that may display or act on the change. Separate one-time implementation and migration from ongoing support, usage, and future change work. Do not convert an unstated responsibility into an assumed inclusion.
NIST's contingency-planning guide is used here only for its general framing of owned recovery roles and testing. It does not set commercial terms for a small business, interpret a contract, or establish any provider behavior.
Require a bounded exercise and recovery owner
Before approval, request a harmless boundary exercise that shows what the parties expect to inspect when a reschedule crosses the stated time-zone policy. Record who owns an unavailable alternative, a duplicate or missing calendar record, an incorrect notification, and a post-release correction. A test item should say what will be exercised, what result will be captured, and who interprets it; “time zones tested” is not a useful acceptance statement.
Use the blank worksheet to reveal unknowns without inventing figures:
| Scope area | Included work or term | Excluded / ambiguous | Buyer question and owner |
|---|---|---|---|
| Appointment authority and service policy | __________ |
__________ |
__________ |
| Controlling time zone and recurrence rule | __________ |
__________ |
__________ |
| Booking, calendar, and message interfaces | __________ |
__________ |
__________ |
| One-time implementation and migration | __________ |
__________ |
__________ |
| DST-boundary or equivalent test exercise | __________ |
__________ |
__________ |
| Exceptions, mismatch handling, and recovery | __________ |
__________ |
__________ |
| Ongoing support, monitoring, and changes | __________ |
__________ |
__________ |
| Data, configuration, and termination handoff | __________ |
__________ |
__________ |
Stop when the handoff is invisible
Pause comparison if the proposal does not identify the policy owner, interfaces, exception owner, boundary test, ongoing support, data or configuration handoff, and termination responsibilities. An amount is not comparable while those obligations are blank.
For a general appointment-recovery scope, see Review a Custom Appointment-Recovery Quote. For assumptions that must be surfaced before award, see Record Software Proposal Assumptions.
Does this worksheet tell a buyer to choose custom software?
No. It makes a custom proposal inspectable. The buyer can still choose a configured product, a manual workflow, a narrow pilot, or no change after reviewing the completed record.