Most residential builders run one profitability review per year. They close the books in December, pull a P&L, and spend January trying to understand why the year looked different than they expected. By then, the problems are 12 months old. The decisions that caused them were made in Q1. Nothing can be done about it now.
That is not a financial review — it is a postmortem with no bearing on the future. A real profitability review cadence tells you what's happening while you can still change the outcome. It catches job cost overruns in week six instead of month eight. It surfaces pricing gaps before you bid the next similar project. It gives you the data to stop guessing and start adjusting.
Beyond the Bid has implemented this quarterly review cadence with 312+ builders. The ones who run it consistently see margin improvement of 2–4 points within two quarters. The ones who skip it tend to be the same ones who are surprised at year-end. Here is the exact structure.
Why Quarterly Is the Minimum, Not the Target
Monthly reviews feel aggressive until you do one and realize it takes 45 minutes if your data is clean. Quarterly reviews feel reasonable until a $60,000 job cost overrun surfaces in week eight of a sixteen-week project and you have already spent the margin on consumables, labor, and the next deposit.
Monthly is better. Quarterly is the minimum. Every month, you look at the four metrics below and decide whether anything needs to change before the next review. If the numbers are clean, you move on. If something is drifting, you diagnose and act. The review itself is not the work — the action coming out of it is the work.
The builders who have the most trouble with this cadence are the ones with dirty data. If your cost codes are inconsistent — the same work categorized differently across different jobs or different months — the monthly review will be frustrating instead of clarifying. The solution is to fix the cost code structure first, then run the reviews. Cleaning up cost codes is a one-time project that makes every future review faster and more useful.
The Four Metrics That Run the Entire Review
You do not need a full financial model for a monthly profitability check. You need four numbers that, looked at together, tell you whether the business is healthy. Everything else is noise.
1. Gross Margin by Project Type
Not overall gross margin — by project type. A kitchen remodel and a ground-up addition have different risk profiles, different labor mixes, and different margin targets. Blending them into a single number tells you nothing useful.
Track gross margin by project type each month: new construction, whole-house renovation, addition/ADU, kitchen or bath specialty remodel. If kitchen remodels are running 28% margin this quarter and you target 32%, that is a conversation. If additions have been running 5 points below estimate for the last two quarters, that is a pricing problem, not a execution problem — and you address it in the estimate, not in the field.
2. Job Cost Variance — Estimated vs. Actual by Category
Pull this per job and per category. Most builders know their overall job cost variance. Almost none know it by cost code category — which is where the signal lives.
The categories that matter most to track by job: labor (own crew), subcontractors, materials, permits and fees, and site conditions. If a category is running more than 10% over estimate on three consecutive jobs, that is not bad luck — that is an estimating problem. Update the number and move on.
3. Overhead Absorption Rate
Overhead absorption is the percentage of your total overhead that is covered by the markup on labor and materials — the portion of every job's margin that pays for the office, the trucks, the insurance, the admin. If you are absorbing less than 100% of overhead, you are running at a structural loss on every job before the first board is set.
Track this monthly: total overhead divided by total labor plus materials revenue. If it is running at 85%, your pricing is too low by 15% on the overhead component alone. If it is running at 110%, you are pricing with a small buffer — which is where you want to be for years when overhead creeps up.
4. Change Order Capture Rate
Change order capture rate is the percentage of initiated change orders that were written, approved, and posted before the work was done. A rate below 80% means you are doing work that is not covered by contract — work you are effectively doing for free.
Track this per job per month. If it drops below 75% on an active project, that is a process problem — something in the field is not routing change orders fast enough. The fix is usually a simple protocol: any field decision that costs money gets a change order initiated before the end of the day. Not approved yet — initiated. Approval comes after. The initiation is what protects the margin.
| Metric | What to Track | Target Threshold | Action When Off |
|---|---|---|---|
| Gross Margin by Project Type | Monthly by category (new build, renovation, ADU, specialty) | ±2 pts of estimate per project type | Revise estimating templates if consistently under; raise prices if consistently over target |
| Job Cost Variance by Category | Per job, per cost code bucket (labor, sub, materials, permits, site) | <10% variance per category on any single job | Update estimating number for that category; investigate if pattern spans 3+ jobs |
| Overhead Absorption | Total overhead ÷ (labor revenue + materials revenue) | 100–110% minimum; 115–120% target for growth phase | Reduce overhead or raise markup; both are valid — pick one and execute |
| Change Order Capture Rate | % of initiated COs written and approved before work performed | >80% per job | Implement same-day initiation protocol; assign someone to track CO pipeline weekly |
The Meeting Cadence That Makes It Happen
The review only works if it actually happens. Monthly reviews die when they are too complicated to prepare. The structure below takes 45 minutes to run with clean data — and the data only needs to be clean if you have a consistent cost code structure and a job costing workflow in your project management tool.
First Week of Each Month: Data Preparation (30 minutes)
Export from JobTread (or your project management tool): job cost report for all active jobs, change order log, and markup summary. Review the four metrics before the review meeting. Flag anything outside target threshold. Note which jobs had change orders initiated vs. approved vs. posted. This is not analysis — it is data gathering. It should take 30 minutes.
Second Week of Each Month: Review Meeting (45 minutes)
The meeting is 45 minutes, structured as follows:
- 0–10 min: Gross margin by project type — are any categories running outside threshold? This is the pricing signal.
- 10–20 min: Job cost variance by category across active jobs — where are overruns happening? This is the execution signal.
- 20–30 min: Overhead absorption rate — is the business covering its fixed costs? This is the structural signal.
- 30–40 min: Change order capture rate on active jobs — which projects need a CO process check-in? This is the margin protection signal.
- 40–45 min: Action items — one to three specific decisions coming out of the review. Not general awareness — specific actions assigned to specific people.
If the four metrics are all within target, the meeting ends at 25 minutes. That is fine. The purpose of the meeting is to catch problems — the empty meeting is not a failure, it is evidence the business is healthy.
The Most Common Failure Mode
Builders who run this review quarterly instead of monthly tend to let problems compound. A job that goes 8% over in week six looks like it might turn around. By week twelve, it is 14% over and the window for recovery is gone. Monthly reviews catch it in week five — when there is still time to change the scope, adjust the schedule, or initiate a change order that covers the overrun. Quarterly reviews catch it when the job is 60% done. Monthly reviews catch it when there is still runway to respond.
What to Do When a Metric Is Off-Target
The four metrics tell you something is wrong. They do not always tell you why. Here is the diagnostic framework for each:
Gross margin by project type is below target: Distinguish between an estimating problem and an execution problem. Pull the original estimate for the last three jobs in that category. Were the numbers wrong when you wrote them (estimating problem), or did you hit the numbers in the estimate but the estimate was too low relative to the market (pricing problem)? Execution problems fix in the field. Estimating problems fix at the computer. Pricing problems fix in the proposal — and they require you to actually believe you are worth more than you are currently charging.
Job cost variance is high in a specific category: Start with the most recent three jobs. Is it the same sub every time? The same scope of work? The same project type? If it is one sub — renegotiate or replace. If it is one project type — update the estimating unit for that work. If it is the same scope on every job — you may be under-scoping that category in every estimate, which is a drafting problem, not a field problem.
Overhead absorption is below 100%: This is almost always a pricing or volume problem. If you are pricing correctly but absorbing below 100%, you need more revenue to cover fixed costs — which means the problem is in the pipeline and close rate, not in the estimate. If the absorption rate has been falling for three consecutive quarters, it is a pricing problem — the market moved, your costs went up, and your estimates did not.
Change order capture rate is below 80%: This is a process problem, not a pricing or estimating problem. The work happened, the client directed it, and it is not written in a change order. The fix is protocol — not a better estimate, not a better contract, a different process for how change orders are initiated in the field. Assign someone to own the CO pipeline: every change order in draft, approved, posted, and aging status. Review that list in the Monday morning huddle. Keep it current.
The Data Dirty Problem
If your cost codes are inconsistent — the same type of work getting different codes on different jobs, or labor categories mixed with materials categories — the monthly review will show you noise instead of signal. The fix is not to stop running reviews. The fix is to spend one Saturday morning auditing your cost code structure and consolidating to 25–35 consistent codes that anyone on the team can apply without ambiguity. That clean structure is what makes every subsequent review 30 minutes instead of three hours. One day of cleanup. 11 months of clear data.
What You Need Before the First Review
Three prerequisites. Without them, the review will produce frustration instead of insight:
Consistent cost codes. A standardized chart of accounts that everyone on the team uses the same way, with 25–35 codes maximum. If you have 80 cost codes — most of which only one person understands — consolidate first. The Cost Code Audit Checklist covers exactly how to do this.
Job costing in your project management tool. JobTread tracks costs against budget by code. If you are not using job costing, you cannot run this review — you are working from gut feel instead of actual data. Set it up before your first review. It takes one to two days to configure and one to two months to get the data populated. Start now so the data is there when you need it.
A change order template that is fast to use. If initiating a change order requires filling out a complex form, navigating a multi-step approval workflow, or sending a series of emails, people will not do it for small changes. Build a one-page CO form that takes three minutes to complete. The process has to be faster than the impulse to just do the work and hope it works out.
The Quarterly Review That Changes Decisions
The review itself is not the goal. The goal is a business that adjusts before problems compound. A monthly review cadence gives you that — and the discipline of running it consistently will surface problems earlier than you expect, catch pricing gaps before they become year-end surprises, and build the data history you need to make better estimating decisions every year.
The first review will take longer than subsequent ones if your data is not clean yet. That is normal. The second review will be faster. By the fourth or fifth, it will be the 45-minute meeting it is supposed to be. The work is not in the meeting — the work is in the decisions that come out of it. Track those decisions. Follow up on them. The review tells you what needs to change. Following through is what actually changes it.