Separate the exception from the price
Ask the proposal to identify payment and appointment authorities, every interface used to verify them, the expected evidence for a mismatch, the customer communication handoff, and recovery ownership. Keep one-time implementation, recurring operation, usage or metered charges, and future change work in separate fields—even when the value is unknown. Record the currency, recurring billing period, usage unit/tier/volume assumption, comparison horizon, and tax or fee treatment before calculating a like-for-like total.
NIST's contingency-planning guide is used only for the general framing of owned recovery and testing. It does not set small-business terms, interpret a contract, or establish a payment provider's behavior.
Require an inspectable acceptance exercise
Use this blank worksheet to expose unknowns without making up money, SLAs, or provider capabilities. First freeze the comparison basis:
| Basis field | Value from proposal or buyer-owned assumption | Source / owner |
|---|---|---|
| Currency | __________ |
__________ |
| Recurring billing period | __________ |
__________ |
| Usage unit and tier | __________ |
__________ |
| Expected usage volume per billing period | __________ |
__________ |
| Comparison horizon and number of billing periods | __________ |
__________ |
| Tax and fee treatment | __________ |
__________ |
| Normalized total over the comparison horizon | __________ |
__________ |
Show the arithmetic as one-time costs, plus recurring cost per period multiplied by the periods in the comparison horizon, plus usage cost per period at the stated unit, tier, and volume multiplied by those periods, plus only the change costs and taxes or fees explicitly included in the comparison. State which taxes and fees are included, excluded, or unknown. If an input or tax/fee treatment is missing, write unknown rather than estimating it.
Then expose the responsibility and cost scope:
| Scope area | One-time cost | Recurring cost | Usage / metered cost | Change cost | Included, excluded, or ambiguous work | Buyer question and owner |
|---|---|---|---|---|---|---|
| Payment and appointment authority | __________ |
__________ |
__________ |
__________ |
__________ |
__________ |
| Verification interfaces and evidence | __________ |
__________ |
__________ |
__________ |
__________ |
__________ |
| Duplicate event or repeat report handling | __________ |
__________ |
__________ |
__________ |
__________ |
__________ |
| Customer communication and staff handoff | __________ |
__________ |
__________ |
__________ |
__________ |
__________ |
| Safe acceptance-test and recovery record | __________ |
__________ |
__________ |
__________ |
__________ |
__________ |
| Recovery, support, and monitoring | __________ |
__________ |
__________ |
__________ |
__________ |
__________ |
| Data and configuration handoff | __________ |
__________ |
__________ |
__________ |
__________ |
__________ |
| Termination responsibilities | __________ |
__________ |
__________ |
__________ |
__________ |
__________ |
Stop when recovery is invisible
Pause comparison if the proposal leaves currency, billing period, usage basis, comparison horizon, normalized total, authority, verification, duplicate-event treatment, communication, acceptance test, recovery owner, ongoing support, data handoff, or termination responsibility blank. An amount is not comparable while these obligations are unknown.
For a buyer change record, see Record a Custom-Software Change Request Before Acceptance. For a data-work acceptance record, see Accept Data Migration Work Before Final Payment. For a related appointment scope, see Review a Cross-Time-Zone Rescheduling Quote Before Approval.
Does this worksheet select a vendor or prescribe contract terms?
No. It makes a proposal inspectable. A buyer can still choose a configured product, a manual process, a narrow pilot, or no change after reviewing the completed record.