1. Build a change order log
A spreadsheet can work for a small job if someone owns it and keeps it current. Give each change a unique reference and use it on the proposal, photos, emails, approvals, and pay application backup.
- Job name, subcontract reference, change number, and short scope description.
- Request date, requester, instruction or drawing reference, and location.
- Notice deadline and required recipient, taken from your actual subcontract.
- Proposal submission date, revision number, proposed addition or credit, and requested time adjustment.
- Current approval status, reviewer, next action, and follow-up date.
- Approved amount and time adjustment, authorized signer, approval date, and final change order number.
- Links to photos, cost backup, correspondence, signatures, and billing records.
Do not overwrite the history when a price changes. Preserve earlier submissions and identify which version is current.
2. Separate approval status from billing status
Draft, submitted, approved, and rejected tell you where authorization stands. Unbilled, billed, and paid tell you where the money stands. A change can be approved without being billed, and billed without being paid.
Keep proposed and approved totals separate. Treat credits consistently and do not count rejected proposals as approved revenue. If only part of a change is accepted, record exactly which scope and amount were approved rather than marking the whole proposal as accepted.
Also distinguish a signed field acknowledgment from the formal subcontract amendment where the project requires both. Keep the documents linked, but do not treat two references to the same work as two separate changes.
3. Use a repeatable review routine
- Record the field event promptly. Capture the instruction and condition photos while the facts are fresh; meet the contract’s notice requirements.
- Assign one next action. Name who needs to price, submit, review, revise, or follow up, and record a target date.
- Review open items regularly. Sort by notice deadline, age since submission, and next action rather than only by dollar amount.
- Reconcile before billing. Match approved changes to the subcontract total and the GC’s pay application requirements. Confirm the approved version is attached.
- Close the loop. Record the billing reference and later payment separately. Keep disputed or incomplete items visible.
A practical weekly review can bring the foreman and office together around the same list. Increase the review frequency when deadlines or changing site conditions require it.
4. Sample entries: what needs attention?
Fictional entries for illustration, not customer records or price guidance.
- CD-001 · Added receptacles · Pending · $1,850 proposed
- Next action: ask the authorized reviewer for a decision. Do not include this in the approved total.
- CD-002 · Revised pipe route · Approved · $2,400
- Next action: check the required subcontract amendment and include the approved backup with the next eligible billing.
- CD-003 · Deleted finish work · Approved credit · $600
- Next action: deduct the credit when reconciling the approved change total. In this example, the net approved adjustment is $1,800.
5. What you can track in FieldCO
FieldCO keeps field change directives by job, date, dollar amount, and Draft, Pending Approval, Approved, or Rejected status. Capture photos, a scope description, and a lump-sum price, then collect on-screen sign-off or remote approval by text on eligible plans.
Export the signed packet for pay application backup. Keep formal subcontract amendments, detailed cost breakdowns, notice deadlines, and billed or paid tracking in your office records where needed. FieldCO is not a full accounting system.

Sources and contract note
General information, not legal advice. Follow your project’s contract, required notices, approval authority, and scheduling requirements.
More field notes
Put the extra work in writing
Use the free printable change directive form to record scope, price, schedule impact, and signatures. Or use FieldCO to capture photos, enter a lump-sum price, and request sign-off on site or by text.