Revenue Per Crew Day: The Roofing Metric to Track Now

Revenue per crew day is the dollar amount of recognized job revenue divided by the number of crew days it took to produce. One install crew, on one production roof, for one day, generating one slice of revenue. Track it across enough jobs and it tells you something a profit-and-loss statement never will: whether the most expensive, most constrained resource you own, a trained crew on a roof, is being fed the right work in the right order.

Here is the formula, and it is deliberately simple:

Revenue per crew day = recognized job revenue / crew days assigned to the job

That is the easy part. The hard part is defining what counts as recognized revenue, what counts as a crew day, and what you do when the number moves. A high number can mean a clean replacement with tight staging and a crew that hit its rhythm. It can also mean you forgot to subtract a credit, never logged the return trip, or have not yet eaten the callback that is coming next week. A low number can mean sloppy planning. It can also mean a steep 10/12 with three skylights, a half-day weather hold, hidden decking, or a crew you are deliberately training. The number is a question, not a verdict.

Use it the right way and revenue per crew day becomes the single most honest lens you have on production. It exposes the bottleneck that average job size hides, the territory that quietly bleeds drive time, the handoff that keeps stranding crews on the roof waiting for a decision. Use it the wrong way, as a club to beat speed out of crews, and you will train your best people to skip documentation, hide hazards, and lie about hours. This is the full method: how to define it, how to measure it without fooling yourself, how to segment it so you are comparing like with like, and how to turn it into a short action list instead of a long blame meeting.

Why revenue per crew day beats the metrics roofers usually watch

Most roofing owners can recite their revenue, their close rate, and maybe their average job size. Those are real numbers. They are also lagging, blended, and easy to feel good about while the production engine grinds.

Average job size tells you how big your sales are. It says nothing about whether you can build them efficiently. You can raise average job size by selling more full replacements and still lose ground if every one of those jobs ties up a crew for an extra half-day because the packets show up incomplete. Total revenue tells you how much work moved. It hides the fact that you hit the number by running crews into overtime and weekend work that crushed your margin.

Revenue per crew day is different because it puts the scarce resource in the denominator. In residential roofing, the bottleneck is almost never leads and almost never sales capacity for a healthy company. The bottleneck is crew-days: trained, equipped, safe people on roofs, multiplied by the days the weather and the schedule actually let them produce. That number is fixed in the short run. You cannot conjure a seasoned tear-off crew in a week. So the question that decides your year is not "how many leads can we generate," it is "is every crew-day we own pointed at the most valuable work we can build well?"

That is the question revenue per crew day answers. It is a roofing production KPI in the truest sense, a ratio of output to your constraining input. When it drifts, something in the chain between sales, estimating, the warehouse, dispatch, and the roof is leaking capacity. The metric will not tell you which link. It will tell you to go look, and the good ones go look.

What it is not

Before going deeper, three things this metric is not, because confusing them causes real damage.

It is not profit. Revenue per crew day is a top-line capacity measure. A job can post a gorgeous revenue-per-day number and lose money on materials, comebacks, or a botched supplement. Keep these in separate columns.

It is not a benchmark you owe the internet. You will find blogs quoting tidy targets, nine to eleven squares per crew per day, this many thousand dollars per crew-day for "top-quartile" roofers. Treat those as directional folklore unless they cite a real, audited dataset, and almost none do. Your steep-roof, freeze-thaw, two-story market in the upper Midwest will never run the squares-per-day of a single-story tract market in Texas, and it should not try to.

It is not a stick. The fastest way to poison this metric is to tie it to crew pay without guardrails and watch your people optimize the number instead of the business.

The two definitions that decide everything: revenue and the crew day

If two of your managers calculate this metric two different ways, you do not have a KPI, you have a standing argument. Write the definitions down once and make them the law.

What counts as a crew day

A crew day is one crew, assigned to one job, for one production day. That is the unit most operators should use because it maps to how you actually schedule and dispatch. A two-day tear-off-and-install with one crew is two crew days. If you send two crews to knock out a big cut-up roof in a single day, that is two crew days, not one.

The alternative is the worker-day, where you count each person separately. Worker-days are more precise for labor analysis but harder to schedule against and easy to game by quietly resizing crews. Pick one. The most common mistake is switching between them mid-analysis to make a job look better, which is just lying to yourself with a denominator.

Now the judgment calls. Decide, in writing, how you treat:

• Partial days. A crew that finishes a small repair by 11 a.m. and goes home: half a crew day, or one? Most operators count it as one if it consumed a dispatch slot, because the cost of the day, the truck, the mobilization, the lost opportunity, was real. Be consistent.
• Return trips and punch-list visits. A crew that comes back to fix a leak detail or finish a section it ran short on is another crew day charged to the same job. This is where rushed jobs hide. If you do not count the comeback, a crew can manufacture a great Tuesday by leaving Wednesday's work for a return trip that never gets attributed.
• Travel-heavy days. A job ninety minutes out that costs the crew three hours of windshield time is still one crew day, but the drive time is exactly the kind of friction this metric should surface when you segment by territory.
• Multi-crew days. Two crews, one roof, one day equals two crew days. The roof's revenue gets divided by two.

What counts as recognized revenue

Harder, and more important. You have at least four candidate numbers for any job:

For a weekly production dashboard, contract plus approved change orders is the practical choice, as long as your change-order discipline is real. For monthly and quarterly review, where you make decisions about pricing, staffing, and job mix, use recognized revenue from closed jobs. Closed jobs have stopped lying to you: the change orders are in, the credits are posted, the punch-list returns have happened, and the callback window has mostly elapsed.

Whatever you choose, write the adjustment rules: how you handle credits, cancellations, warranty rework, supplements on insurance jobs, and customer-driven scope changes. A supplement that gets approved three weeks after the crew left still belongs to that job's revenue. A credit you issued because the crew damaged a gutter still belongs against it.

A worked example

Consider a hypothetical to make the formula concrete. Say a crew completes a full asphalt replacement.

• Contract: 28 squares of architectural shingle, signed at $19,400.
• During tear-off the crew finds rotten decking; an approved change order adds $1,100 for sheathing replacement.
• The job took the crew two production days, plus a half-day return trip to redo a valley detail that leaked in a test.

If you count the return as a third crew day (the conservative, honest approach), recognized revenue is $20,500 and crew days are 3, giving roughly $6,833 per crew day. If you had ignored the return trip, you would have reported $10,250 per crew day, a 50 percent overstatement that hides the exact problem, the valley detail, you most need to fix. The honest number is the useful number.

Squares per crew day: the physical twin of the dollar metric

Dollars per crew day is the business view. Squares per crew day is the physical view, and you want both, because dollars can move for reasons that have nothing to do with production (you raised prices, you sold more accessories) and squares cannot lie about how much roof actually got covered.

Field rules of thumb, widely cited across the trade, put a four-person asphalt crew somewhere around 15 to 25 squares of tear-off-and-install per day on a standard-pitch roof, with smaller three-person crews landing nearer 15 to 20 on simple work. Treat those as ranges, not gospel, and understand what collapses them. The NRCA Roofing Manual: Steep-slope Roof Systems is the trade's reference for steep-slope assemblies and the conditions that govern them, and the conditions are what move the number.

Production per crew day falls hard with:

• Pitch. Once you cross into 8/12 and steeper, crews need toe boards, more anchorage, and slower movement. It is normal to lose a meaningful share of daily output, and the labor cost per square climbs with it.
• Layers. A tear-off of two or three existing layers is a different job than a one-layer strip. The dump trips alone can eat a chunk of the day.
• Cut-up complexity. Hips, valleys, dormers, skylights, chimneys, and dead valleys multiply detail work. A simple gable goes fast; a roof with eight penetrations and four valleys does not.
• Access. A two-story walkout over a deck, tight side-yards, landscaping you must protect, a steep driveway, no place to stage the dumpster: every one of these bleeds time before a single shingle moves.
• Decking surprises. Hidden rot, plank decking that needs re-sheathing, or spaced sheathing under old wood shake turns a strip-and-go into a carpentry job.

The point of tracking squares per crew day alongside dollars is to separate "this crew is slow" from "this roof is hard." If squares per day are normal but dollars per day are low, you have a pricing or scope problem, not a production problem. If both crater on the same job, look at the roof, not the crew.

Crew utilization: the metric behind the metric

Revenue per crew day quietly assumes a crew that is actually on a roof producing. The brutal truth of roofing is that crews spend a lot of paid time not producing: weather holds, waiting on materials, waiting on a customer decision, driving, standing around because the next job's permit did not clear. That is the roofing crew capacity metric most owners never measure, and it is where the easiest gains hide.

Utilization is the share of available crew-days that turn into productive production-days. If a crew is on payroll five days a week for four weeks, that is 20 available crew-days. If weather, dispatch gaps, and rain-outs mean they only produced on 15 of them, utilization is 75 percent, and your revenue-per-available-crew-day is a quarter lower than your revenue-per-production-crew-day. Both numbers are real. They answer different questions.

• Revenue per production crew day asks: when a crew is on a roof, are we feeding them valuable, well-staged work?
• Revenue per available crew day asks: are we keeping crews on roofs at all, or are scheduling and weather eating our capacity?

A company can have excellent production-day economics and terrible available-day economics, which usually means a sales-to-production pipeline that runs dry, a dispatch process that cannot keep the next job ready, or a backlog management problem. Track both, label them clearly, and never quote one when you mean the other.

How to segment so you stop comparing roofs to repairs

One dashboard for every job is worse than no dashboard, because it will confidently tell you the wrong thing. A repair crew clearing five service calls a day will post lower recognized revenue per crew day than a replacement crew, and that does not make the repair crew bad, it makes the comparison meaningless. Segment before you conclude.

At minimum, split the metric by:

Give each segment its own context notes. A training crew should look slower for a quarter, on purpose, because you are building capacity you will need next storm season. A commercial service job moves to a different cadence because of tenant coordination, roof access, and approval chains. A repair crew protects relationships and warranty obligations that the dollar metric does not capture. None of that shows up unless you have segmented, and a manager who skips this step ends up blaming a crew for a problem that lives in scheduling, sales, or the warehouse.

Segmenting also turns the dashboard into a diagnostic. Once the data is grouped, the useful questions get sharp:

• Are certain job types consistently mis-scoped, so the crew always runs over the estimated days?
• Is one territory adding so much drive time that its per-crew-day economics never compete?
• Are change orders in one segment getting approved late, so crews idle waiting on a decision?
• Are callbacks concentrated around a single handoff, one estimator, one crew, one product?

What actually moves the number: the leak map

When similar jobs in the same segment produce very different revenue per crew day, the cause is almost always a handoff, not a lazy crew. Roofing is a relay race, and you drop the baton between functions, not within them. Here is where capacity leaks, roughly in the order it bites.

Sales-to-estimating handoff

The job sold on a number that did not match the roof. Wrong square count, missed second layer, ignored steep section, no line item for the decking everyone could see was soft. The crew inherits an estimate that was never buildable in the days allotted, and the per-crew-day number takes the hit for a sin committed weeks earlier at the kitchen table.

Estimating-to-production handoff

The packet is incomplete. No clear scope notes, no photos of the access constraints, no measurements the crew can trust, no flag on the skylights. The crew arrives, discovers the roof, and burns an hour figuring out what they were sent to do. Multiply by every crew, every day.

Warehouse and material readiness

The single most common, most fixable leak. Material delivered late, delivered short, delivered to the wrong spot, or the wrong color and the crew cannot start. A crew standing in a driveway at 7:30 a.m. waiting on a delivery has already lost a slice of the day you will never get back. Stage materials the day before, verified.

The decision bottleneck

Crew finds hidden decking, or the homeowner wants to change the ridge vent, and there is no fast change-order path. The crew stops, the office is slow to approve, and a half-day evaporates while everyone waits. The fix is a documented, pre-authorized change-order process the crew can trigger from the roof.

Crew-to-roof mismatch

A newer crew sent to a steep, complex cut-up they are not ready for, or a veteran crew burning their skill on a simple strip a trainee should be cutting their teeth on. Match the crew to the roof.

Closeout and the comeback

The job looked great until the punch-list return, the leak callback, the missed flashing detail. Every return trip is a crew day this metric should charge back to the original job. If your closeout misses things, your revenue per crew day will look better than reality right up until the comeback, then quietly degrade it on a different report where nobody connects the two.

The reason to find these leaks with data rather than gut is that the gut blames the visible person, the crew on the roof, instead of the invisible process, the packet that shipped incomplete. Contractors who keep job context connected, the property notes, the access photos, the inspection findings, the change orders, and the closeout items tied to the job record, can actually answer "what happened on this one" when the number moves. Tools like RoofPredict exist partly to keep that field evidence attached to the job so the review looks at what happened on the roof instead of arguing about a single ratio. Without the evidence, every review devolves into opinion, and opinion always blames the crew.

Reading the number: high, low, and the traps in each direction

Managers want a number to mean one thing. This one does not, and learning to read it in both directions is what separates a useful review from a witch hunt.

A high revenue per crew day can be exactly what it looks like: a clean, well-staged replacement, materials on site the night before, a packet the crew could trust, a roof that matched the estimate, and a crew in rhythm. That is the result you are trying to manufacture, and when you see it, the right response is to ask what made it work and how to repeat it. But a high number can also be an illusion built from omissions. You forgot to subtract the gutter credit. You never logged the half-day return trip. The supplement that should have raised the denominator's job is sitting unapproved, so the revenue is understated and the ratio is flattered. The callback has not happened yet. A suspiciously high number on a job you remember as messy deserves the same scrutiny as a low one, because it is usually hiding an unrecorded cost or an uncounted crew day.

A low revenue per crew day is where the witch hunts start, and where most of them are wrong. Before anyone blames the crew, walk the honest list of reasons a number drops: a steep or heavily cut-up roof that always takes longer, a multi-layer tear-off with extra dump trips, hidden decking that turned a strip into carpentry, a weather hold, a safety hold, late materials that cost the morning, a homeowner decision the office was slow to approve, a training assignment you made on purpose, or simply a job that was mis-priced at the kitchen table and never had enough days in it to begin with. In a healthy company, most low numbers trace to one of those, and exactly none of them are fixed by telling a crew to hurry. The discipline is to attribute first and judge second. Pull the notes, look at the photos, check the change-order log, then decide what to change, and the thing you change is usually a process, not a person.

The pattern matters more than any single job. One low number is weather. The same crew low three weeks running is a coaching or matching question. The same territory low every month is a drive-time and staging question. The same estimator's jobs running a day over, again and again, is a packet-quality question. The job-level number starts the inquiry; the trend tells you where to spend your attention.

Keep the labor records honest, because the law requires it

This metric tempts managers to lean on timekeeping, and that is a line you do not cross. The denominator is crew days, but the inputs to your labor cost, and to any incentive you build, are hours worked, and those are regulated.

Under the Fair Labor Standards Act, employers must keep accurate records of hours worked and wages for non-exempt employees. The Department of Labor lays out exactly what those records must contain in Fact Sheet 21: Recordkeeping Requirements under the FLSA, including hours worked each day, total hours each workweek, and the basis of pay. Separately, Fact Sheet 22: Hours Worked under the FLSA explains that compensable time includes work the employer suffers or permits, which for roofing can pull in mobilization, certain travel, and paid meetings depending on the facts. You do not get to leave that time off the books to make a crew-day look efficient.

So keep the systems in separate lanes and never let one corrupt another:

• Payroll records track compensable time and pay. They follow the law, full stop.
• Production reports explain job flow and crew days.
• Job-cost reports compare planned versus actual cost.
• Revenue per crew day summarizes capacity use.
• Performance reviews discuss documented behavior, training, and safety, not raw ratios.

A crew-day metric built on hours someone shaved off the clock is not efficiency, it is a wage violation wearing a dashboard. It also poisons your estimating, because the "efficient" jobs were never real, and you will bid the next ten jobs against a fantasy.

Keep the underlying job records traceable too. The IRS recordkeeping guidance for small businesses makes the basic point that you keep records that substantiate income and expenses. For revenue per crew day, that means every number in the calculation should trace to something: a contract, an invoice, a logged change order, a time record, a disposal ticket, a return-trip note. If you cannot trace it, do not make a pricing, staffing, or discipline decision on it.

Never let the number reward an unsafe shortcut

This is the guardrail that protects lives, and it is non-negotiable. Revenue per crew day creates pressure to go faster, and on a roof, "faster" too often means "skip the fall protection." That trade is illegal and it kills people.

Fall protection is required by law. Under OSHA's construction fall-protection standard, 29 CFR 1926.501, employees engaged in residential construction six feet or more above a lower level must be protected by guardrails, safety nets, or a personal fall arrest system, with documented site-specific plans only where conventional protection is genuinely infeasible. OSHA's broader employer responsibilities do not pause because your schedule is tight. A crew-day that hit its number by skipping a harness is not a good day, it is an incident waiting on a date.

So build the rule into how you read the metric:

• A safety hold is never counted as a crew failure. If a crew lost production time because a hazard was identified and corrected, that is the system working. Document the hazard and the fix, and move on.
• Weather delays, hidden conditions, and office handoff failures are not crew failures either. Attribute them honestly.
• Time spent photographing hidden decking, protecting landscaping, or documenting a change order is often time that prevents a far larger dispute later. The review asks whether the documentation was necessary and handled efficiently, never whether it dented the day's ratio.

If you ever find yourself tempted to praise a high number that you suspect came from cut corners, stop. You are about to train your whole company to hide hazards from you.

Pair every number with a reason: the crew-day notes field

A number without a note is an argument. Fix that by making the closeout require one. Add a single mandatory field at job completion:

"What affected crew days on this job?"

With controlled choices so you can filter and trend it, plus a short free-text line:

WHAT AFFECTED CREW DAYS ON THIS JOB? (select all that apply)
[ ] Weather hold
[ ] Safety hold / hazard correction
[ ] Hidden condition (decking, structure, etc.)
[ ] Customer-requested scope change
[ ] Office / packet handoff issue
[ ] Late or short material delivery
[ ] Access constraint (height, staging, landscaping)
[ ] Crew skill / training assignment
[ ] Equipment issue
[ ] Rework / callback / punch-list return
[ ] Nothing unusual

Notes (one or two lines): ________________________________

Now the metric has memory. If six jobs this month flag late material, the leak is in the warehouse or the supplier, not the crews, and you go fix purchasing. If four jobs flag hidden conditions, estimating and inspection documentation need tightening so the surprises stop being surprises. If three flag rework, training or quality control is the lever. The controlled field is what lets you go from "the number was low" to "the number was low for this specific, fixable reason, three times."

The loop only closes if a flag can become an action. A closeout note that says "late material, third time this month" should spawn a task for the warehouse manager with a due date, not sit in a report everyone glances at and nobody owns. Connecting closeout findings to assignable tasks, the kind of follow-up loop a job system like RoofPredict is built to hold, is the difference between a dashboard that informs and a dashboard that improves the next job.

Review it on a cadence, and keep the meetings short

Different time horizons answer different questions. Reviewing this metric daily for strategy is noise; reviewing it only quarterly for blockers is negligence. Match the cadence to the decision.

Keep the weekly meeting brutally tight. Pull the five jobs with the largest variance between estimated and actual crew days. For each, ask three questions: what happened, is the reason documented in the notes field, and what one process change prevents it next time. The output is a short action list with owners and dates. If the only conclusion anyone reaches is "work faster," the review was too shallow and you wasted the meeting.

The monthly is where the money is. With a month of segmented data, you can see that the southwest territory is running 20 percent below the rest on revenue per crew day and trace it to drive time, or that the newer crew has closed most of the gap to the veterans and is ready for harder roofs, or that one estimator's jobs consistently run a day long because the packets ship thin. Those are decisions, and they are the whole point.

A closeout review template you can use this week

After every closed job, run a short, calm review. Not a tribunal, a tune-up.

If a job triggers more than one or two action items, you have found a real process gap worth chasing. If most jobs sail through clean, your handoffs are healthy and you can spend the meeting on the genuine outliers.

Keep revenue and profit in separate columns

Worth repeating because it is the error that does the most damage: revenue per crew day is not profit per crew day, and the day you forget that is the day you start celebrating jobs that lost money.

Revenue per crew day tells you how much top-line work moved through your scarce capacity. Profit depends on labor cost, material cost, sub cost, equipment, fuel, disposal, insurance, overhead, commissions, rework, warranty exposure, and collections. A job can run a high revenue-per-day number and bleed margin through material waste, a blown supplement, or a callback you have not absorbed yet.

The specialty-trade context matters here. Industry financial benchmarking, including the CFMA Construction Financial Benchmarker program, consistently shows that specialty trade contractors run higher gross margins but compress to slim net margins after overhead, insurance, and rework. Roofing in particular carries real warranty and weather exposure that does not show up anywhere in a revenue-per-crew-day figure. So pair the capacity metric with the money metrics:

• gross margin by job and by segment
• labor variance, estimated versus actual
• material variance and waste percentage
• callback and warranty-return count
• days from start to closeout
• cash collection status

Use revenue per crew day to ask operating questions, was the crew matched to the job, were materials ready, did the crew idle on a decision, are return trips being charged back. Use job-costing and accounting to answer the profit questions. Never tell a crew a high-revenue job was profitable unless the cost records say so, and never tell sales a low-revenue job was bad until you have looked at its margin, its service value, and its relationship value. One KPI should never run a company.

Mining the metric to feed crews the right work

The highest use of this metric is forward-looking. Beyond grading jobs after the fact, it points crew capacity at the best available work before the season fills up. When you know your revenue per crew day by segment, you know which work earns its place on the calendar.

This is where production data meets targeting. If your replacement crews run far better per-crew-day economics than your repair crews, and your backlog is tight, the operating question is how to keep replacement crews on replacement roofs and route repairs to the right resource. That is a sales and lead-targeting problem as much as a scheduling one. Roofers who sharpen their outbound, mailing the right neighborhoods, re-engaging an old CRM of past estimates, giving a canvasser a real per-home reason to knock, fill the calendar with the work that builds well instead of whatever walked in. The point of knowing which roofs are actually due for work, by age range and storm exposure, is to keep your scarce, expensive crew-days pointed at jobs worth building, and tools like RoofPredict are aimed squarely at that targeting problem: which houses, in what order, before anyone climbs a ladder. It does not inspect roofs, diagnose damage, or certify remaining life, and roof age is a planning range, not an exact date. What it does is help you stop spending crew-days chasing brand-new roofs and start spending them where the work is real.

That closes the loop. Production data tells you which work builds efficiently. Targeting tells you how to go find more of it. The metric in the middle, revenue per crew day, is what connects the two.

Regional and seasonal reality: the baseline is not portable

A roofing company in Minneapolis and one in Phoenix can run identically tight operations and post revenue-per-crew-day numbers that look nothing alike, and neither is doing anything wrong. The metric is local. Borrowing a baseline from a different climate or a different roof stock is one of the surest ways to draw a false conclusion.

Climate drives the production half of the ratio. In freeze-thaw markets across the upper Midwest and Northeast, frozen shingles do not seal, brittle laminates crack in the cold, and crews lose mornings waiting for the roof to warm. Asphalt sealing strips need real warmth to bond, so a January install on a borderline day is slower and riskier than the same roof in May. In the Sun Belt, the constraint flips: triple-digit afternoons soften shingles, slow crews, and force early starts, while monsoon and hurricane seasons stack weather holds into the schedule. Coastal markets add salt-air corrosion concerns to fasteners and flashing detail, and high-wind zones along the Gulf and Atlantic carry code-driven nailing and underlayment requirements that add real time per square. None of that is inefficiency. It is the roof and the sky setting the pace.

The housing stock matters as much as the weather. A market dominated by single-story ranches with simple gables will out-produce a market of two-story homes with steep, cut-up roofs, multiple dormers, and tight lot lines, every single day, with equally good crews. Steep-slope work, the kind detailed in the NRCA steep-slope guidance, demands toe boards, more anchorage, and slower deliberate movement, and the labor cost per square climbs with the pitch. A company whose territory skews steep and complex should expect a structurally lower squares-per-day baseline and should price for it, not flog crews against a flatland number they can never hit safely.

Season then moves the baseline within a single market across the year:

The practical rule that falls out of all this: build your own seasonal and segment baselines from your own history, and compare each job to the right baseline. A November job in Buffalo judged against an October baseline will look like a failure when it was simply November. Hold the comparison fair and the metric stays honest.

A short glossary so everyone speaks the same language

Before you roll this out, align the vocabulary. Most arguments about this metric are really arguments about definitions, and a one-page glossary kills them before they start.

Hand this to every estimator, dispatcher, and production lead. When someone says the number, everyone now knows precisely which number, on which basis, for which jobs. That shared language is worth more than any single calculation, because it is what lets a whole team trust the metric enough to act on it.

Common mistakes that wreck the metric

The failure modes are predictable. Avoid these and you are ahead of most.

• Treating an internet benchmark as your target. Your market, pitch profile, and job mix set your realistic range. Compare against your own similar jobs first.
• Comparing unlike jobs. A repair, a steep tear-off, and a commercial service call are different products. Segment or stay silent.
• Calling revenue profit. Covered above, and worth the repetition.
• Hiding the comeback. Return trips and punch-list visits are crew days. Charge them back or the metric flatters your worst jobs.
• Switching the denominator mid-analysis. Pick crew days or worker-days and hold the line.
• Pressuring timekeeping. Illegal, and it corrupts your estimating. Hours worked are hours worked.
• Punishing safety holds, weather, hidden conditions, or office failures. Attribute honestly or your crews stop telling you the truth.
• Tying it to pay without guardrails. An incentive on a raw ratio trains people to skip documentation, rush cleanup, and resist needed return trips.
• Using it as a marketing claim. It is an internal management number. The FTC's advertising basics are a reminder that customer-facing claims must be truthful and substantiated, and a per-crew-day figure tells a homeowner nothing about quality, safety, or warranty service. Keep it on your dashboard, not your yard sign.
• Material-waste deductions that break wage law. If waste is high, investigate measurement, ordering, cutting patterns, and supervision. The fix is usually a checklist, not a payroll deduction.

Putting it together: a 30-day rollout

If you are starting from nothing, you do not need a data platform to begin. You need definitions and discipline.

WEEK 1 - DEFINE
- Write the crew-day definition (crew-day vs. worker-day; pick one).
- Write the revenue definition (contract + approved COs for weekly;
  recognized revenue for monthly).
- Write the rules for return trips, partial days, credits, supplements.
- Get every manager to agree in writing.

WEEK 2 - INSTRUMENT
- Add the "What affected crew days?" field to job closeout.
- Decide your segments (job type, complexity, crew, territory at minimum).
- Start logging crew days against jobs, including return trips.

WEEK 3 - REVIEW SMALL
- Run your first weekly review on last week's closed jobs.
- Pull the 5 biggest expected-vs-actual gaps. Ask what happened.
- Confirm the notes field is being filled honestly.

WEEK 4 - ACT
- Hold the first monthly. Compare your segments.
- Identify ONE handoff to fix (usually material readiness or packet quality).
- Assign it an owner and a date. Re-measure next month.

The goal in month one is not a perfect dashboard. It is a shared definition, an honest notes field, and one fixed handoff. Do that four times and you will have rebuilt the most leak-prone parts of your production engine, with the metric showing you exactly where to dig each time.

Revenue per crew day will never be a magic number, and any source promising you a universal target is selling something. What it is, used honestly, is the clearest signal you have that the scarce thing you own, trained people on roofs, is being fed the right work in the right order, built safely, and charged back honestly. Track it, segment it, attach a reason to every figure, and turn each review into one fixed handoff. The number will follow.

Sources checked: June 18, 2026.

FAQ

What is revenue per crew day in roofing?

It is an internal production metric that divides recognized job revenue by the number of crew days it took to build the job. One crew, on one roof, for one production day, is one crew day. It measures how well your scarcest resource, trained crews on roofs, is being used. The company has to define recognized revenue and the crew day in writing before comparing jobs, or every manager will calculate it differently and the number becomes useless.

How do you calculate revenue per crew day?

Divide recognized job revenue by crew days assigned to that job. Recognized revenue should include approved change orders and supplements and subtract credits; for the cleanest read, use closed jobs. Crew days should count every production day, including return trips and punch-list visits charged back to the original job. For example, a job earning 20,500 dollars that took two install days plus a half-day comeback counted as a third crew day works out to roughly 6,833 dollars per crew day.

What is a good revenue per crew day for a roofing company?

There is no universal target, and any blog quoting one without an audited source is guessing. The right comparison is against your own similar jobs, segmented by job type, roof complexity, crew, season, and territory. A steep, cut-up, two-story market will never match a single-story tract market, and it should not try to. Use the metric to see whether your own numbers improve over time and where they diverge between segments, not to chase someone else's headline figure.

How many squares can a roofing crew install per day?

Field rules of thumb put a four-person asphalt crew around 15 to 25 squares of tear-off and install per day on standard-pitch roofs, with three-person crews nearer 15 to 20 on simple work. Those ranges collapse with steep pitch, multiple layers, complex cut-up roofs, hard access, and hidden decking. Track squares per crew day alongside dollars so you can tell whether a low number means a slow crew or a genuinely hard roof, which are very different problems.

Is revenue per crew day the same as profit?

No, and confusing the two is the most damaging mistake with this metric. Revenue per crew day measures top-line work moving through crew capacity. Profit depends on labor, material, subcontractor, equipment, disposal, overhead, commissions, rework, warranty exposure, and collections. A job can post a great revenue-per-day number and still lose money through material waste or a callback. Always pair the capacity metric with gross margin by job, labor and material variance, and callback counts from your job-costing records.

Can revenue per crew day be used in crew performance reviews?

It can inform a conversation but should never stand alone. A low number often reflects a hard roof, weather, hidden decking, a thin job packet, late materials, or a safety hold, none of which are crew failures. Pair it with documented behavior, safety, quality, training level, and accurate time records. Tying raw ratios to crew pay without guardrails trains people to skip documentation, rush cleanup, and hide hazards, which costs far more than any speed gain is worth.

Why does my revenue per crew day vary so much between similar jobs?

Usually a handoff is leaking capacity, not a lazy crew. Common causes are a sale priced on the wrong square count, an incomplete estimating packet, late or short material delivery, a slow change-order approval that idles the crew on a discovery, a crew mismatched to the roof, or an uncounted return trip. Add a required closeout field asking what affected crew days, with controlled choices, so you can filter the metric and find which handoff is actually responsible.

Should roofing contractors advertise their revenue per crew day?

No. It is an internal management metric, and a homeowner cannot verify it or learn anything from it about your quality, safety, or warranty service. The FTC requires advertising claims to be truthful and substantiated, so a per-crew-day figure on marketing material is both meaningless to customers and a compliance risk. Keep it on your production dashboard where it helps you choose work, stage jobs, and coach handoffs, not on your yard sign or website.

How often should I review revenue per crew day?

Match the cadence to the decision. Use a daily glance only for dispatch, blockers, weather, and missing materials, never for conclusions. Run a weekly review of the closed jobs with the biggest gap between expected and actual crew days while memory is fresh. Use monthly review to compare segments, crews, and territories and adjust estimating. Use quarterly review for staffing, training pipeline, service mix, and pricing. Keep every meeting short and output a small action list with owners and dates.