“Can you add this?” leaves several decisions open. Use five fields to compare a request with the existing scope and follow the agreement’s change procedure. A request, a quote and an authorized change are different records.
Read the existing procedure first
Keep all five fields on the same version
Work
Identify the original deliverable and clause or SOW version. Describe what is added, removed or replaced, including quantities, formats, inputs and acceptance criteria. Distinguish a missing original input from a new deliverable.
Amount
Separate the existing amount, the proposed adjustment and the proposed revised total. Record currency, fixed or estimated basis, expenses, tax treatment and any invoicing change. An unpriced request is unknown, not free.
Timing
Find the affected milestone, proposed date or day number, dependencies and when the adjustment starts. State which dates remain unchanged. Do not silently turn an extra task into an automatic extension.
Authorization
Find who may approve, the required form and any notice or signature conditions in the actual agreement. Record pending decisions separately from completed approvals. A person requesting work may not be the person authorized to change the contract.
Record
Use a change identifier, version and date; link the original scope, proposal, approval evidence and effective version. Check that any approval refers to this exact scope, amount and timing, rather than an earlier quote.
Fictional teaching example · Not replacement contract wording
One extra report, three decisions still open
Assume an invented private project has a fixed USD 5,000 fee for one English research report due on project day 10. On day 4, a client contact requests a Spanish report as well. For this illustration only, the existing agreement requires written approval by both named project signatories before a scope change takes effect.
CO-01 · Version 2 · Proposed, not approved
Work
Add one Spanish report using client-supplied Spanish source material. The English report remains in scope. Translation is excluded from this proposal; acceptance would use the original report checklist plus the agreed language requirement.
Amount
Existing fee: USD 5,000. Proposed addition: USD 600 fixed. Proposed total: USD 5,600 (5,000 + 600). Assume no additional expenses or taxes solely to keep this invented arithmetic simple; those fields need their own answer in a real record.
Timing
Proposed completion: day 12 for both reports, two project days later than day 10, conditional on source material arriving by day 5. The day-10 obligation has not been amended by this proposal.
Authorization
The request came from a client contact. Neither of the two required signatories has approved version 2. Scope, additional fee and revised timing remain proposed; the request alone does not satisfy the assumed procedure.
Record
Link SOW version 1, the day-4 request and CO-01 version 2. Leave the approval date and effective version marked pending. If the quote changes again, keep the earlier version and seek approval against the matching new record.
Question to take back: “Does the approval identify this version, the USD 600 adjustment and the day-12 milestone, and does it meet the existing change procedure?” This checklist does not instruct either party to start, stop or withhold performance.
Follow the record from request to effective version
Request: preserve what was asked for and who asked. Avoid labelling the request “approved” because it appears in an email thread.
Proposal: keep the five fields together. If one is missing, name the open question rather than carrying forward a guessed answer.
Authorization: compare the actual approval evidence with the agreement’s procedure and the proposal version. A statement that approves cost alone may leave timing or scope unresolved.
Effective record: once the applicable procedure is satisfied, identify the resulting version and effective date. Cross-reference the delivery and invoice records so they do not silently use different versions.
Start with the statement of work guide when the original deliverable or dependency is unclear. The payment schedule guide covers the separate question of when work becomes invoiceable and payment becomes due.
Primary-source context · U.S. federal procurement only
FAR 43.103 distinguishes two modification types
The Federal Acquisition Regulation is a specific federal procurement framework. Section 43.103 illustrates why the kind of modification and its authorization matter; it does not prescribe a universal private-project approval rule.
Bilateral · paragraph (a)
A bilateral modification, or supplemental agreement, is signed by the contractor and contracting officer. Listed uses include negotiated equitable adjustments resulting from a change order and other agreements modifying contract terms.
Unilateral · paragraph (b)
A unilateral modification is signed only by the contracting officer. Listed examples include administrative changes, issuing change orders, changes authorized by other clauses and termination notices.
Do not merge the two: issuing a change order and negotiating an adjustment resulting from it are different listed uses. Section 43.103 alone does not establish that a particular change is authorized, settle its price or timing, or let a private client impose extra work.
Source: Acquisition.gov, FAR 43.103(a)–(b), consulted November 16, 2026. The page displayed FAC 2026-01, effective March 13, 2026. Geography and scope: U.S. federal procurement, subject to the applicable contract and rules. These are source classifications, not market data or TermsHuman prices. Recheck the current provision and applicable contract before relying on it.
Sources and limits
A reading record, not a universal change-order form
The five-field checklist and CO-01 record are original teaching aids. All project amounts, dates, deliverables, signatory requirements and arithmetic in the example are invented; none is attributed to FAR. No recommended fee, jurisdiction-wide signature rule, legal enforceability conclusion or measured business outcome is supplied. The page does not amend an agreement or draft a clause.
TermsHuman explains common contract language and risk patterns for education only. It is not a law firm, does not provide legal advice, and cannot tell you whether to sign. For material obligations, ask qualified counsel in your jurisdiction.