By Ryan Kramer, founder of Wisegrid. Last updated July 2026.
A construction project runs on a small stack of documents: a cost-coded budget that tracks committed and actual against estimate, a schedule the field can actually read, a contract checklist that keeps the paperwork defensible, estimates that win work without losing money, and a dashboard that tells the owner and the office the same story. This guide gives you the working structure for all five, with the columns, the math, and worked examples inline, so you can build the set in a spreadsheet or grid tool this afternoon.
It is written for the small-to-mid GC, remodeler, or specialty contractor running projects out of spreadsheets, not for the enterprise ERP crowd.
Key takeaways – The budget’s job is variance, not record-keeping. Estimate vs committed vs actual, by cost code, with the overrun visible while it is still a decision. – Two schedules, not one: a milestone-level master schedule and a rolling three-week look-ahead. The look-ahead is the one the field uses. – The contract checklist is cheap insurance. Most construction payment disputes trace to a missing clause, not a missing skill. – Estimates need a line-item structure (the roofing example below shows the shape) so the quote, the budget, and the actuals speak the same language. – One source of data. If the budget, schedule, and dashboard are maintained separately, they will disagree by mid-project. Every template here is designed to feed the next.
The construction template stack
| Template | Job it does | Reviewed |
|---|---|---|
| Project budget | Estimate vs committed vs actual by cost code; catches overruns early | Weekly |
| Master schedule + look-ahead | Sequences trades; tells the field what happens in the next three weeks | Weekly (look-ahead), monthly (master) |
| Contract checklist | Ensures every agreement covers scope, money, time, and risk before signature | Per contract |
| Estimate structure | Prices work by line item so quotes reconcile to budgets and actuals | Per bid |
| Project dashboard | One live view of money, schedule, and open items for owner and office | Continuous |
The stack works as a system because the rows share a spine: the cost codes in the estimate become the budget rows, the budget feeds the dashboard, and the schedule’s milestones are the dashboard’s other axis.
Construction project budget template
One row per cost code, five money columns, and the discipline of entering commitments when they are signed, not when they are invoiced.
| Column | What goes in it |
|---|---|
| Cost code | Your numbering, or CSI MasterFormat divisions if you work with larger GCs |
| Description | Sitework, concrete, framing, electrical… |
| Original estimate | The budget as sold, frozen at contract |
| Approved changes | Net of approved change orders for this code |
| Revised budget | Estimate + approved changes |
| Committed | Signed subcontracts and POs against this code |
| Actual to date | Invoiced/paid to date |
| Projected final | The honest forecast: committed + estimate-to-complete |
| Variance | Revised budget – projected final; negative means overrun |
A worked slice of a residential remodel budget:
| Code | Description | Revised budget | Committed | Actual | Projected final | Variance |
|---|---|---|---|---|---|---|
| 03 | Concrete | $18,500 | $17,900 | $9,200 | $17,900 | +$600 |
| 06 | Framing | $42,000 | $44,300 | $31,000 | $44,300 | -$2,300 |
| 16 | Electrical | $28,000 | $26,500 | $8,100 | $27,700 | +$300 |
| Contingency | $12,000 | $9,700 | (absorbs 06) |
The framing overrun is visible the day the sub’s contract came in over estimate, months before the invoices land, because the committed column exists. That is the entire point of this template: most budget templates track only actuals, which report overruns after the money is spent. Two habits make it work: no commitment goes unentered past Friday, and change orders touch the budget only when approved (pending COs live on their own list, on the dashboard).
Construction schedule template
Run two levels:
Master schedule. One row per phase or trade package: mobilization, sitework, foundation, framing, rough-ins, inspections, finishes, punch, closeout. Columns: start, finish, duration, predecessor, responsible sub, and status. Keep it at 30 to 60 rows; the master schedule’s audience is the owner, the bank, and your own sequencing logic, not the daily crew. Milestone rows (permit issued, dry-in, final inspection) get dates the dashboard will track.
Three-week look-ahead. The schedule the field actually uses, rebuilt every week: rows for each crew or sub, columns for the next 15 working days, cells naming the task and location. Its real function is surfacing constraints before they hit the field: material not ordered, inspection not booked, prior trade not finished, RFI unanswered. A look-ahead line without its constraints cleared is a wish.
The weekly rhythm: update the look-ahead against reality on the same day each week, push any slip into the master schedule, and read the new critical sequence: which slips move the end date and which just eat float.
A note on construction scheduling software
Searches for construction scheduling software usually mean one of two things. Enterprise CPM tools (Primavera-class) are built for schedulers on large commercial jobs and are overkill for a small GC. General-purpose grid tools with a Gantt view cover the actual need for most builders: the master schedule as rows with dates and dependencies, drawn as a timeline, with the look-ahead as a filtered view of the same data. That is the honest tier this guide targets; if your projects have claims consultants and a full-time scheduler, you are shopping in a different aisle.
What to require from whatever you pick: dependencies between rows (so a slip ripples), a critical-path view (so you know which slips matter), the ability to filter by sub, and the schedule living next to the budget rather than in a separate silo.
Construction contract checklist
This is a checklist for assembling and reviewing contracts, not legal advice; construction contract law is state-specific, and your standard contract deserves one real review by a construction attorney. What the checklist ensures is that nothing on the money-and-risk list is silently absent:
Scope and documents
- Scope of work described by reference to specific drawings and specs, with revision dates
- Exclusions stated (the assumed-included items: permits, utilities, dumpsters, final clean)
- Allowances listed with dollar amounts and what happens on overage
Money
- Contract sum and pricing basis (fixed price, cost-plus with fee, time and materials with cap)
- Payment schedule tied to milestones or monthly progress, with invoicing and payment terms
- Retainage percentage and release conditions
- Change order process: written, priced, and signed before the work proceeds
- Payment protection per your state (lien rights and notice deadlines; prompt-payment terms)
Time
- Start date, substantial completion date, and what counts as excusable delay
- Weather-day handling
- Any liquidated damages, read twice
Risk and closeout
- Insurance requirements both directions (GL, workers’ comp, builder’s risk, additional insured)
- Warranty scope and duration
- Dispute resolution method and venue
- Termination rights and payment on termination
- Punch list and final acceptance process
Run the same checklist on subcontracts you issue, from the other side of the table: the protections in your prime contract need to flow down.
Roofing estimate template
Roofing is the cleanest example of the estimate structure every trade needs, because it prices from one measurable base: the square (100 sq ft of roof area). The template shape:
| Line item | Qty basis | Notes |
|---|---|---|
| Tear-off (per layer) | Squares x layers | Disposal priced separately below |
| Deck repair | Per sheet allowance | Set an allowance + unit price for overage; you cannot see the deck until tear-off |
| Underlayment | Squares | Ice-and-water shield lineal feet at eaves/valleys as its own line |
| Shingles/covering | Squares + waste % | Waste 10% simple gable, 15%+ hips/valleys |
| Flashing (drip edge, step, chimney, pipe boots) | Lineal ft / each | The line most shortcuts hide in |
| Ridge cap + ventilation | Lineal ft | Ridge vent, boxes, or both |
| Labor | Squares x rate, adjusted for pitch and stories | Steep/high adders explicit, not buried |
| Dumpster + disposal | Per container | Tied to tear-off tonnage |
| Permit + inspection | Each | Municipality-specific |
| Overhead + profit | % on the above | Kept as its own line internally, whatever the customer-facing quote shows |
Two rules that generalize to every trade’s estimates. Price the unseen with allowances plus unit overage pricing (deck repair here; rot, rock, or asbestos elsewhere) so surprises become change orders instead of margin loss. And keep the estimate’s line items aligned with your budget’s cost codes, so when the job runs you can see which line item won or lost money, and your next bid learns from it.
Construction project dashboard
The dashboard is where the other four templates report. One screen, five widgets, readable by the owner without a walkthrough:
- Budget health: revised budget vs projected final, total and by division, with the variance number unmissable.
- Schedule milestones: the master schedule’s milestone rows with baseline vs current dates, and days of slip.
- Change orders: approved total (already in the budget) and pending total (the risk number), with a count of items awaiting owner signature.
- Open items: RFIs and submittals past their needed-by dates, punch items open; each with an owner.
- This week: the look-ahead’s headline: crews on site, inspections booked, deliveries due.
The failure mode to design against is the Friday-afternoon dashboard, assembled by hand from three spreadsheets that already disagree. A dashboard is only worth having if its widgets read live from the budget and schedule sheets themselves; the moment it is a separate artifact, it is a weekly chore that reports last week.
Run the whole stack in one place
Everything above works in plain spreadsheets. The upgrade is running the set as connected sheets: in Wisegrid, the budget, master schedule, look-ahead, CO log, and RFI list are sheets in one project; the schedule draws as a Gantt with dependencies (critical path on the Business tier); date-triggered automations chase overdue RFIs and unsigned change orders, with a run history that proves the nudge went out; and the dashboard widgets, including budget metrics and milestone tables, read live from those sheets, so the owner view is always current and never hand-assembled. Photos and documents attach directly to rows, so the deck-repair change order carries its own evidence.
The construction-specific tour, with the template set and how each piece connects, is at Wisegrid for construction.
FAQ
What templates does a construction project need?
Five cover most small-to-mid operations: a cost-coded budget (estimate vs committed vs actual), a master schedule plus three-week look-ahead, a contract checklist, a line-item estimate structure, and a project dashboard reading from the first two.
What should a construction project budget template include?
One row per cost code with original estimate, approved changes, revised budget, committed costs, actuals to date, projected final, and variance. The committed column is the one that catches overruns early; a budget that tracks only actuals reports problems after the money is gone.
What is a three-week look-ahead schedule?
A rolling field-level schedule covering the next three weeks, rebuilt weekly, showing each crew’s tasks by day and, critically, the constraints (materials, inspections, prior trades, RFIs) that must clear before each task can happen.
How do you calculate a roofing square?
One square is 100 square feet of roof area. Measure the roof’s plane areas (or take footprint x a pitch multiplier), divide by 100, then add a waste factor: around 10 percent for simple gables, 15 percent or more for cut-up roofs with hips and valleys.
Do I need construction scheduling software?
At small-GC scale, you need dependencies, a Gantt/timeline view, a critical path, and a schedule that lives next to your budget. General-purpose grid tools with those features cover it; dedicated CPM suites earn their cost on large commercial work with full-time schedulers.
What goes on a construction project dashboard?
Budget variance (projected final vs revised budget), milestone dates with slip, approved and pending change order totals, overdue RFIs and submittals, and the current week’s field plan. All of it read live from the underlying sheets, not retyped weekly.
Build the stack once, run it on every job
Budget, schedule, CO log, and an owner dashboard as connected sheets, with the chasing automated. Free to start.
Start free → · Wisegrid for construction → · Risk register template →
About the author Ryan Kramer is the founder of Wisegrid, a higher-capacity Smartsheet alternative with Gantt scheduling, date-triggered automations with run history, row attachments, and live dashboards included in the normal $9 and $19 tiers. He writes about the documents that keep jobs on budget. More from Ryan →