The anatomy of a change order

A change order is drafted to alter one statement of work without reopening the master services agreement above it. It is short by design, and the brevity is the point: everything it does not mention stays as it was. OctoDoc, the signing system of record, treats a change order as a file in its own right — its own document, its own marks, its own sealed state — carrying a stored reference to the parent it modifies. What follows describes the structure this class of instrument usually carries. It is a general description of a document type and not a substitute for the advice of an attorney.

Two things separate a change order from an amendment. A change order operates inside machinery the parent already defines: the statement of work anticipates that scope will move, names a process for moving it, and the change order is the artifact that process produces. An amendment edits the terms of the agreement itself, and nothing in the agreement has to have anticipated it. Common Paper's Professional Services Agreement builds the approval test into its definition, describing a Change Order as a document that "identifies the SOW being changed, describes what the parties are changing, and is approved by an authorized representative of each party". Routing follows from that definition rather than from the seniority of whoever drafted the change.

The clause doing the most work in the least space is the residual one: a statement that all other terms of the statement of work and the parent agreement stay unchanged. Without it, a change order that re-states three of eleven deliverables invites the reading that the other eight were dropped. With it, the change order is additive to a stack rather than a replacement for it.

A statement of work plus its change orders is a stack, not a document. Working out the operative scope on a given date means reading the parent and then every change order that preceded that date, in order, applying each in turn. The sequence number is what makes "in order" a fact rather than an inference.

An unnumbered change order is what turns that stack into guesswork. Three failure shapes recur. Two changes drafted in the same week and signed on the same day leave no ordering at all. A change order that supersedes an earlier one — restoring a deliverable a previous change removed — then reads as a contradiction rather than a correction. And fee arithmetic compounds: where one change re-prices a workstream and a later change applies a percentage to that workstream, the total depends on which came first.

The discipline is cheap. A monotonic integer per parent statement of work, printed in the header, in the file name and in the reference line, with the fee clause showing a running total rather than a delta alone. Federal procurement reaches the same answer from the other direction. FAR 4.1602(a)(5) directs agencies to "identify a supplementary PIID for the modification in conjunction with the PIID for the contract, order, or agreement being modified" — the modification gets its own identifier, bound to the identifier of the instrument it modifies. FAR 43.301(a)(1) then routes modifications onto one numbered form, Standard Form 30, "Amendment of Solicitation/Modification of Contract", and the list it applies to includes "Change orders issued under the Changes clause of the contract". The routing is not universal: the same paragraph carves out "except for the options stated in 43.301(a)(2) or actions processed under part 15", and 43.301(a)(2) makes the form optional for petroleum economic-price-adjustment modifications, for termination notices, and for purchase order modifications as specified in 13.302-3.

Where the discipline is kept or lost is the record. A change order sealed as an unlinked PDF is a document with a number printed on it. A change order sealed with a reference to the parent file and an ordinal within that parent is a chain that can be walked from either end.

Common Paper's Professional Services Agreement states the mechanism in three sentences: "Provider or Customer may amend any SOW by entering a Change Order. If a party requests a Change Order, the other party will review and consider the proposed changes in good faith and respond to the Change Order request within a reasonable timeframe. However, a Change Order will not be binding until Provider and Customer agree in writing on the Change Order." Three things are packed into that clause — either party may start the process, the other owes good-faith review, and nothing takes effect until both have agreed in writing. Common Paper Professional Services Agreement (Version 1.1) free to use under CC BY 4.0.

Federal procurement words the same instrument as a contract modification. FAR 52.243-1, the Changes—Fixed-Price clause, opens: "The Contracting Officer may at any time, by written order, and without notice to the sureties, if any, make changes within the general scope of this contract in any one or more of the following:". Its second paragraph is the fee-and-schedule half of a commercial change order written as a term of the contract: "If any such change causes an increase or decrease in the cost of, or the time required for, performance of any part of the work under this contract, whether or not changed by the order, the Contracting Officer shall make an equitable adjustment in the contract price, the delivery schedule, or both, and shall modify the contract."

FAR Part 43 also carries a distinction worth borrowing for the description clause. FAR 43.101 provides: "Administrative change means a unilateral (see 43.103(b)) contract change, in writing, that does not affect the substantive rights of the parties (e.g., a change in the paying office or the appropriation data)." The commercial analogue is a change order that only corrects a project code or a billing address. Keeping that kind of change visibly separate from a substantive one is what keeps a numbered stack readable years later.

Three dates in the clause order are frequently conflated and are worth keeping apart in the record: the date the last party signs, the effective date of the change, and the date the changed work begins. They are often different, and only the first is produced by the act of signing.

The authority clause is the other field the record answers for. Common Paper's definition already ties a Change Order to approval by "an authorized representative of each party", which makes the identity and title of each signer part of what the document has to show on its face. Naming the authority in the clause, and giving each signature block a printed name and title alongside the signature, is what lets the sealed file answer that question without a witness.

A post-v1.0 read link over a change order is designed to produce a reading log: which parties opened it, which pages they dwelled on, and whether the fee clause was reached before the signature block. On a two-page document with the arithmetic on page one, that would be a usefully small signal. A planned proof file would then record the sequence — parent reference, ordinal, mark set, and the sealed state of each party's marks — as one artifact a third party could check with no account.

Nobody wants to read the contract. OctoDoc is being built so you do not have to: write a document from a prompt, ask plain-language questions about the one you were sent, and keep every one of them in a single place instead of four accounts and an inbox.

Anyone can check a sealed file with no account.

Unlimited human sends on the paid tier.