Register field
Assumption
What must be true for the written price and service plan to apply?
Proposal assumptions
Put the assumptions behind the provider's price in one place.
Copy each material assumption from the proposal, clarification message, or draft agreement. Record who must confirm it, what evidence supports it, and what may happen to price or service if it changes.
This is a planning and procurement record, not legal advice or a substitute for reviewing the provider's written agreement. It does not create, accept, or amend terms. Keep legal, tax, privacy, security, finance, and regulatory decisions with qualified owners.
Ten fields
Record what must stay true for the offer to work.
Use the provider's wording. If the written offer does not explain an effect, mark it for clarification rather than completing it from memory.
Register field
Source
Where did the provider state it? Name the document, section, version, and date.
Register field
Owner
Who must confirm or maintain it?
Register field
Evidence
Which dated record can both sides inspect?
Register field
Dependency
Which input, access, decision, or earlier step does the work need?
Register field
Pricing effect
What provider-confirmed price effect applies if it changes?
Register field
Service effect
What provider-confirmed effect on coverage, timing, staffing, or output applies?
Register field
Review date
When will this row be checked again?
Register field
Change trigger
Which event requires an earlier review?
Register field
Review status
What is the review status, who recorded it, and when?
Fictional support example
A written price can depend on volume, buyer inputs, and coverage.
Every company, date, volume, and effect below is fictional. These are examples, not benchmarks. On smaller screens, scroll the table horizontally to see all ten fields.
| Assumption | Source | Owner | Evidence | Dependency | Pricing effect | Service effect | Review date | Change trigger | Review status |
|---|---|---|---|---|---|---|---|---|---|
| Up to 600 order-status tickets each week | Fictional proposal v3, scope note 2, dated 2026-08-01 | Buyer support manager | Weekly help-desk volume report | Buyer gives read-only order-status access before launch | Provider says higher volume needs a written price review | Extra tickets may move to the next agreed coverage window | 2026-09-01 | Two weeks above 600 tickets | Clarify the over-volume rule; buyer owner, 2026-08-05 |
| Approved reply rules and examples are ready before training | Fictional clarification email, item 4, dated 2026-08-02 | Buyer support manager | Approved reply guide and version record | Buyer approves the guide and names an exception owner | None stated; clarify before signing | Training and live-start dates move until the guide is approved | 2026-08-12 | Reply policy or product rules change | Buyer reviewed; provider confirmation open, 2026-08-05 |
| Coverage is weekdays from 9:00 a.m. to 5:00 p.m. in the named timezone | Fictional proposal v3, coverage table, dated 2026-08-01 | Provider service lead | Approved staffing schedule and weekly coverage report | Both sides confirm holidays and the timezone in writing | Weekend or extended coverage needs a separate written quote | Requests outside the window wait for the next covered period | 2026-10-01 | New weekend, holiday, or extended-hour request | Both sides reviewed the written window, 2026-08-05 |
Copy-ready register
Start with the provider's written record.
Use safe references to approved files. Do not paste credentials, customer records, payment details, or full confidential terms into the register.
PROVIDER CONTRACT ASSUMPTIONS REGISTER REGISTER CONTROL Provider: Service or work lane: Proposal or agreement version and date: Buyer owner: Provider contact: Register review date: [YYYY-MM-DD] ASSUMPTION SOURCE OWNER EVIDENCE DEPENDENCY PRICING EFFECT SERVICE EFFECT REVIEW DATE CHANGE TRIGGER REVIEW STATUS [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] REVIEW NOTES Open clarifications: Qualified legal, finance, security, privacy, tax, or regulatory review needed: Next review owner and date: Use safe document or evidence references rather than credentials, customer records, payment details, or full confidential terms. This planning record does not create, accept, or amend contract terms. The provider's written proposal or agreement and review by authorized owners control.
The full register stays visible and selectable. Nothing is uploaded or saved.
Review flow
Confirm the gaps instead of filling them in.
One row should hold one assumption. That makes a missing owner, source, or effect easier to spot.
- Collect the quote brief, proposal, clarification messages, pricing notes, and draft agreement.
- Copy one material assumption into each row without changing its meaning.
- Add the exact source, dated evidence, dependency, and owner.
- Mark a missing price or service effect as clarify instead of estimating it.
- Ask the named owners to review the row and record the status and date.
- Check the row again on its review date or when its change trigger occurs.
Clarify before relying
Pause when the record asks you to guess.
The register makes missing or conflicting assumptions easier to spot. It does not decide whether a term is fair or legally sufficient.
- The assumption came from a call but does not appear in a dated written record.
- Words such as normal volume, business hours, or standard access are not defined.
- A buyer dependency has no owner or evidence.
- The buyer estimated a price or service effect that the provider has not confirmed.
- Several unrelated assumptions are bundled into one row.
- The review status has no name or date.
Next provider step
Take the written assumptions into the next review.
If the scope is still loose, rebuild the same brief for every provider. If proposals are already in hand, compare them before anyone relies on an unstated term.