Construction Change Order Log.
A running log of every PCO and CO with cost impact, days added, and approval status.
About this template
A data-entry register for change orders: number, description, cost impact, schedule days, and status from pending through approved or rejected. The revised contract sum recalculates as COs are approved, and an aging view surfaces PCOs that have sat unsigned for weeks. The single source of truth when the owner asks why the contract grew.
The live demo ships with sample data: Two active commercial jobs with 25 change orders between them: a mix of owner-directed changes, unforeseen conditions, and rejected claims, with realistic dollar amounts, day impacts, and approval dates.
The prompt behind this template
This is the exact description the Prized agent built it from. Yours can be one sentence: the agent fills in the rest, and you refine from there.
Show the full prompt
Build a change order log for Calloway Construction, a commercial general contractor, used by project engineers as the single source of truth when the owner asks why the contract grew. Three regions. Top: a segmented switcher between the two active jobs, Riverbend Clinic Interior Buildout and Eastgate Warehouse Shell, above five summary cards for the selected job: Original Contract Sum, Approved Changes, Revised Contract Sum, Pending Exposure, and Days Added. For Riverbend show $2,450,000 original, about $96,000 approved, and about $118,000 pending. Middle: the register itself, a dense table ordered by change order number with columns for number in PCO-014 style, date submitted, description, type as Owner Directed, Unforeseen Condition, or Claim, cost impact, days added, a status pill with Pending amber, Approved green, and Rejected red, approval date, and, for pending rows only, days outstanding shown red past 30. Bottom: two side by side visuals: a step style line chart of the revised contract sum over the last six months as approvals land, and an aging list of pending change orders sorted by days outstanding descending, each with number, amount, and days waiting. Seed 25 change orders, 14 on Riverbend and 11 on Eastgate, dated across the last six months with amounts from $1,900 to $64,000 and a couple of negative credits such as deleted casework at minus $4,300. Mix owner directed changes like a kitchen finish upgrade at $18,200 adding 3 days, unforeseen conditions like an unmarked utility line at $24,700 adding 6 days, and two rejected claims including a $31,000 weather delay. Give Eastgate an original sum of $6,800,000. Plant the insight: on Riverbend Clinic, three unforeseen condition change orders totaling $86,400 have sat unsigned for more than 30 days, so the aging list glows red at the top while Eastgate looks healthy. Behavior: revised contract sum equals original plus approved cost impacts only, pending exposure sums pending amounts, the Days Added card sums approved change orders only, and days outstanding counts from the submission date; all four are computed, never entered. An Add Change Order button opens a dialog capturing job, an auto suggested next number, description, type, cost impact, days added, status, and dates. Default to the Riverbend job so visitors land on the story without touching anything. Use a slate blue accent for primary actions, status emphasis, and the selected job on a clean light neutral base, with the meticulous feel of a contract file that holds up in a dispute.
More like this
All templatesConstruction Job Costing Dashboard
See budget vs actual by cost code before a job goes over, not after closeout.
Construction Bid Pipeline Tracker
Track every invitation to bid from takeoff to award and know your real hit rate.
Construction Crew Scheduling Board
A week grid showing which crew is on which job site, with double-bookings flagged.