Methodology / worked examples
Change Ledger guide
A change-order conversation is easier to review when approved value, pending exposure, credits, and time impact remain separate. Enter rows in the order they were received or logged; the running columns make the point-in-time ledger visible.
1. Classify each revision
Approved rows alter the contract value, pending rows show potential exposure, and rejected rows stay visible without changing either total. Negative amounts represent credits or deletions.
Approved contract = base contract + cumulative approved amount
2. Compare funding
The original contingency percentage is shown as a planning allowance. Approved net changes consume that allowance for review, but the tool does not decide whether a contract permits a contingency or how it must be documented.
Remaining allowance = base × contingency % − max(approved net, 0)
3. Treat days as a conversation starter
Days are summed for approved and pending rows independently. They are not a critical-path calculation, entitlement, or schedule promise. Confirm notice, authorization, and schedule consequences using the governing contract.
With a $48,000 base, +$1,850 approved, and −$450 approved credit, the approved contract is $49,400 while a $640 pending row makes exposure $50,040.
Limits and assumptions
- This worksheet is not a contract form, legal notice, signature system, lien record, or jurisdiction-specific compliance tool.
- Approval status is user-entered and not independently verified. Keep signed records in the process required by the project contract.
- Running totals reflect the row order and only the three supported statuses; taxes, retainage, financing, and schedule logic are outside scope.