Construction / revision workflow
Keep approved value separate from pending change-order exposure
A local-first contractor change-order ledger with running approved and pending totals, credits, days, contingency comparison, and review warnings.
Your plan
01 / INPUTSChange Ledger
Calculated from user-entered inputs. Review assumptions and limitations.
Plan summary
02 / RESULTSChange orders and contingency
Shared scale: 0 to 2,440 USD. Values may overlap; bars are comparisons, not parts of a total. Review the details below.
| ID | Description | Status | Amount | Days | Approved running | Pending running | Contract with approved |
|---|---|---|---|---|---|---|---|
| CO-01 | Relocate plumbing | approved | $1850.00 | 2 | $1850.00 | $0.00 | $49850.00 |
| CO-02 | Upgrade cabinet hardware | pending | $640.00 | 0 | $1850.00 | $640.00 | $49850.00 |
| CO-03 | Delete pantry shelving | approved | $-450.00 | -1 | $1400.00 | $640.00 | $49400.00 |
| CO-04 | Alternate tile | rejected | $1200.00 | 1 | $1400.00 | $640.00 | $49400.00 |
Pending changes are shown as exposure but are not included in the approved contract value.
Approved time impact: 1 day; pending time impact: 0 days.
- Illustrative ledger for Illustrative kitchen renovation; rows are processed in the order entered.
- Approved rows change the running contract value. Pending rows change exposure only. Rejected rows remain visible but do not change either total.
- Negative amounts are treated as credits. Date and day fields are tracking aids, not evidence of legal notice, approval, or schedule entitlement.
- Original contingency allowance is $3840.00 based on the entered 8.0% assumption.
Know the boundaries
- 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.
Examples are illustrative. Results depend on the assumptions and measurements you enter.
Method, not guesswork
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.
Read the methodology and worked examplesFrom inputs to a useful decision
All guidesSeparate approved changes from pending exposure
Use status rows and running totals to see what changes the contract value and what still needs review.
Read guidePractical guideCompare change orders with contingency and time fields
Use the ledger allowance and day totals as review prompts while keeping contract decisions in the project record.
Read guideCommon questions
Which rows change approved contract value?
Only rows with status approved are added to the base contract. Pending rows are shown as exposure and rejected rows remain visible without changing totals.
How is contingency remaining shown?
The engine multiplies base contract by the entered contingency percentage and subtracts the positive approved net change.
Are days a schedule commitment?
No. Approved and pending day totals are tracking fields for the entered rows and need review in the project’s governing process.