5 Key Areas to Evaluate in a Roofing Crew Performance Review

A roofing crew performance review should make the next job safer, cleaner, and easier to run. It is not a personality contest, a way to shave hours off a timecard, or a place to punish someone for calling a stop-work. A review that works is built on five areas: job-site safety, work quality and rework, communication and handoffs, schedule discipline and job readiness, and training and advancement. Score each one against documented evidence, write a real example for every rating, and end with a short development plan that has an owner and a date.

The single most important rule is this: every rating needs an example a worker could read back to you. "Missed the deck-condition photos on three jobs after the checklist was reviewed" is a fact you can coach. "Careless" is an opinion that invites an argument and, in a worst case, a discrimination complaint. If a supervisor cannot write the example, the score is not ready to be final. That one discipline removes most of the bias, most of the resentment, and most of the legal exposure from the whole process.

The second rule is just as important: separate what the crew controlled from what the company controlled. Roofing jobs run late and produce callbacks for a dozen reasons that have nothing to do with the people on the roof — missing materials, late permits, weather, bad estimates, hidden decking, slow change-order approvals. A review that blames the crew for an estimating miss teaches your best people that the system is rigged, and they leave. A review that finds the real source of the problem makes your whole operation better.

What follows is a working playbook: the five areas, the questions under each, the scorecards and scripts you can copy, and the legal guardrails — OSHA, EEOC, and the Department of Labor — that keep a review fair and defensible. None of this is legal advice. Before you change anyone's pay, classification, discipline status, or employment, run it through qualified counsel and your company's official HR process.

Why most roofing crew reviews fail

Before the five areas, it helps to know why the typical review falls apart. Three failure modes show up over and over in roofing shops.

The first is memory-based scoring. The supervisor sits down once a year and rates the crew on a gut feeling shaped mostly by the last bad job or the loudest argument. Recency and mood drive the score. The fix is a paper trail collected as the work happens — photos, callbacks, incident notes, closeout items — so the review reads the record instead of the supervisor's mood that morning.

The second is collapsing the company's problems onto the crew. Production was low, so the crew gets a low schedule score, even though materials showed up two days late on half their jobs. Callbacks were high, so the crew gets a low quality score, even though the estimator never flagged the rotten decking. When you push system failures onto people, you lose the people and you keep the system.

The third is drifting into protected territory. A supervisor writes that a worker "doesn't fit the culture," "has an attitude," or "is hard to understand," and a year later that file is sitting in front of an investigator. The U.S. Equal Employment Opportunity Commission's best practices guidance for employers is blunt about it: appraisals should rest on actual job performance, comparable performances should get comparable ratings regardless of who is doing the rating, and ratings should be neither artificially low nor artificially high. Comments about accent, national origin, age, religion, disability, or any other protected trait do not belong in a performance record.

The five-area structure below is designed to defeat all three failure modes. Each area is anchored to evidence, each separates crew-controlled from company-controlled, and each is written in plain job language that stays out of protected territory.

There is also a fourth, quieter failure: the review that never happens, or happens once a year as a rushed formality. In a trade with the labor turnover roofing carries, the crews that stay are the ones who can see a path — who know what "ready for lead" looks like and trust that the people grading them are fair. A real review process is a retention tool as much as a quality tool. The shop that coaches honestly and consistently keeps its trained people; the shop that grades on mood and favoritism trains roofers for its competitors.

What to collect before you score anyone

A review is only as good as the record behind it, and the record has to be built while the work happens, not reconstructed from memory the week the reviews are due. Decide up front what evidence each crew leaves behind on every job, and make capturing it part of the normal closeout rather than a special task. At a minimum, a reviewable job leaves:

• A before/after photo set — including deck condition before dry-in, any hidden conditions found, flashing and penetration details before they are covered, and a final cleanup shot.
• A callback log with the address, the symptom, and the root-cause classification once it is diagnosed.
• Incident and near-miss notes, including any stop-work calls and what triggered them.
• Closeout documents returned to the office — completed punch list, change orders, customer sign-off where used.
• Delay and escalation notes — when a problem was raised and to whom.

None of that is exotic. Most of it is paperwork a well-run crew already produces; the discipline is making sure it lands somewhere searchable instead of dying in a group text. When the evidence is captured per job, the review writes itself from facts, and the supervisor's memory stops being the system of record. When it is not, every review becomes a debate about who remembers what, and the loudest or most recent impression wins.

Area 1: Job-site safety practices

Safety is the first area for a reason. In roofing it is also the area with the most public law behind it, which means it has to be handled with care. The goal is to evaluate whether the crew followed the documented safety process — not to manufacture a scapegoat for a hazard the company failed to plan for.

Why roofing safety carries the most weight

Falls dominate roofing injuries, and the regulator's own numbers make the point. For the fifteenth straight year, OSHA's Top 10 Most Cited Standards for fiscal year 2025 was led by Fall Protection, general requirements (29 CFR 1926.501) with thousands of violations, and OSHA has noted that roofing contractors lead the industries cited under it. Three of the ten most-cited standards in FY2025 are fall-related: 1926.501 at number one, Ladders (1926.1053) at number three, and Fall Protection — Training Requirements (1926.503) at number seven. Every one of those is squarely a roofing-crew issue.

The baseline rule is simple to state and easy to violate. Under 29 CFR 1926.501, each employee on a walking or working surface with an unprotected side or edge six feet or more above a lower level must be protected by guardrails, safety nets, or a personal fall arrest system. Residential construction gets the same six-foot trigger. Low-slope roofing work allows certain combinations involving warning line systems, but the warning line is not a free pass — it has to be set up and used correctly, and the moment someone is at the edge the arrest system or guardrail has to be in play. OSHA's Fall Protection in Construction booklet walks through the accepted systems in plain terms and is worth keeping in the truck.

Training is its own citation category for a reason. The training rule at 29 CFR 1926.503 requires that employees who might be exposed to fall hazards be trained to recognize those hazards and to use the protective systems — and that the training be documented. If a worker was never trained, a safety failure is a company failure, full stop. You cannot review a crew member for not knowing what you never taught them.

Heat is becoming a documented hazard too

Roofing is hot work on a black surface in direct sun, and the regulatory picture is shifting. OSHA published a Notice of Proposed Rulemaking for Heat Injury and Illness Prevention in outdoor and indoor work settings, with the public hearing process running into the second half of 2025. The proposed standard would require a written heat-prevention plan, monitoring of heat conditions, and procedures for water, rest, and shade. Until a federal standard is final, OSHA's heat overview presses employers to provide water, rest, and shade as both prevention and treatment, and a heat illness can already be cited under the General Duty Clause. A modern roofing safety review should ask whether the crew followed the company's heat plan — took the breaks, kept the water on the roof, watched a new worker through the acclimatization window — and whether supervisors enabled that instead of pushing through it.

What to actually score

A fair safety review asks the crew member or lead these questions, and grounds each answer in something written down:

• Were the required fall-protection systems planned and set up before work started, not improvised after someone was already exposed?
• Did the crew recognize and report hazards instead of working around them?
• Were ladders set and tied off correctly, anchors rated and placed right, harnesses inspected, warning lines positioned to the standard?
• Were new or newly assigned workers trained before exposure, with the training documented?
• Were near misses, incidents, and stop-work decisions recorded?
• Did the crew follow the heat plan — breaks taken, water available, new workers watched?
• When a worker raised a concern or called a stop-work, did the response come without retaliation?

That last point is not optional. An unjustifiably low evaluation handed to a worker because they reported a hazard, an injury, or a wage problem can be treated as retaliation. OSHA's worker-rights pages and the EEOC both treat retaliation as a separate, serious violation. The cleanest protection is a record showing that a stop-work call was treated as the right call.

Say this, not that — safety language

The weak column starts fights and can read as bias. The strong column points to a specific behavior on a specific job, which leads to either training, a documented correction, or recognition.

Subcontracted crews and the safety record

Many roofing companies run a mix of W-2 crews and subcontracted labor, and that changes how you handle a safety review. You do not performance-review a sub the way you do an employee, but you absolutely still document safety conditions on jobs they run, because a host employer can carry exposure for hazards on its sites. Keep the same field evidence — were fall systems set before work started, were ladders tied off, was the warning line correct — and feed it into how you decide which subs get the next job. The review of a sub crew is really a decision about whether to keep working with them, and that decision should rest on the same documented safety behavior you would expect from your own people. Confusing the two — treating a sub like an employee in the paperwork — can also blur worker-classification lines, which is its own legal exposure best handled with counsel.

Where the line sits

Never turn a planning failure into a crew-quality failure. If the job started without the right anchors, the right ladder, the right training, or any schedule buffer to do it safely, that is a management problem to fix upstream. If a trained, corrected worker keeps bypassing a known requirement, document the observed behavior — what, where, when, who saw it, what correction followed — and move it into your discipline process under company policy. Keep safety incident investigation separate from the performance review; an incident has its own record and its own legal weight, and you do not want your only copy of an injury report buried inside an annual appraisal.

Area 2: Work quality and rework prevention

Quality is the area where roofers most often argue, because "good work" feels subjective until you tie it to a standard and a photo. The fix is to review quality from the job record — photos, punch lists, callbacks, manufacturer instructions, inspection notes, the customer walkthrough — and to chase the source of every callback rather than assigning blame by default.

Anchor quality to a published standard, not taste

The roofing trade has reference standards so you do not have to invent them. Manufacturer installation instructions are the first authority, because installing outside them is the fastest way to void a warranty — GAF, Owens Corning, CertainTeed, and Malarkey all publish system-specific specs for nailing patterns, starter and ridge, underlayment, and ventilation. Beyond the brand sheet, the NRCA Roofing Manual from the National Roofing Contractors Association is the trade's working reference for construction details and flashing, updated on a repeating four-year volume cycle. When a quality review can point to "the step-flashing detail doesn't match the manufacturer spec or the NRCA detail," the conversation stops being about taste and starts being about a documented standard.

A few failure modes show up again and again, and a good quality review names them specifically rather than hiding them under a generic score:

• Fastening errors — overdriven or underdriven nails, shiners, wrong nailing pattern for the wind zone. These are the quiet warranty-killers because they are invisible from the ground.
• Flashing and penetration details — reused or face-nailed step flashing, sealant used as a substitute for proper metal, pipe boots installed without counterflashing logic.
• Underlayment and dry-in — gaps, wrinkles, missing ice-and-water at eaves and valleys in cold climates, exposed felt left too long in the sun.
• Ventilation — intake and exhaust mismatched, ridge vent installed without enough soffit intake, bath fans dumping into the attic.
• Cleanup and property protection — nails in the driveway, damaged landscaping, gutters full of debris, no magnet sweep.

The quality questions that matter

• Did the crew follow the approved scope and the change-order process, or did they freelance a scope change?
• Were materials staged and installed per the job packet and the manufacturer instructions?
• Were flashing, penetrations, ventilation, underlayment, and edge details documented with photos before being covered?
• Were hidden conditions — bad decking, prior layers, structural issues — photographed and escalated before being buried?
• Were defects caught before the final walkthrough, or did the customer find them?
• For each callback: was the root cause workmanship, unclear scope, a material defect, weather, a customer change, or an office handoff miss?

That last question is the whole game. A callback is data, not a verdict. If the estimator missed rotten decking, the fix is an estimating or pre-production checklist change, not a crew quality ding. If the job packet never included the skylight detail, the fix is in pre-production. If the crew repeatedly skips a documented installation step after being shown it, that is a crew quality issue, and it earns retraining, closer supervision, or a written correction.

A rework root-cause table

Run every callback through a quick classification so patterns become visible across the whole company:

A crew that documents a hidden condition the moment they find it should gain points, not lose them — they protected the company. Photos of bad decking taken before the new shingles went on are exactly the kind of record that supports a homeowner's own insurance claim later, and that distinction matters. A roofer documents conditions and provides an estimate; the insurer decides coverage. A crew that quietly roofs over a problem to stay on schedule is the one creating risk.

Worth a clear word here, because crews and salespeople pick up bad habits from the field: documenting conditions is legal and valuable, but a roofer cannot "handle," "manage," "fight," or "maximize" a homeowner's insurance claim, cannot promise a claim will be approved, and cannot offer to waive, cover, or "eat" a homeowner's deductible. In many states those moves cross into unauthorized public adjusting or insurance fraud — the kind of line a Texas roofer ran into in a well-known 2024 enforcement matter. A crew review can reward thorough condition documentation and accurate estimates. It should never reward, or train, anyone toward promising a coverage outcome. The safe field posture is simple: show up with the facts, write what you see, and let the insurer decide.

Quality verification: who checks the work, and when

The other half of a quality review is whether the work was checked before the customer saw it. A crew that self-inspects against a closeout checklist catches its own misses; a crew that relies on the homeowner or a leak to find problems is running blind. Build the verification into the day:

• A mid-job check after dry-in and before the field is covered, so flashing and underlayment problems are visible while they are still cheap to fix.
• A final walkthrough against a punch list, ideally with photos, before the crew leaves.
• A manager or QC spot-check on a sample of jobs, weighted toward newer crews and toward the details that have generated callbacks before.

Review each crew partly on whether they caught defects versus whether someone downstream did. A crew whose punch lists are honest and whose photos show they fixed their own misses is a more reliable crew than one with a clean-looking record only because nobody inspected. The goal is not zero mistakes — that is not real on a roof — it is mistakes caught and corrected before they become callbacks.

This is also where keeping a property-level record pays off long after the job closes. Contractors who use tools like RoofPredict to keep photos, deck-condition notes, and closeout items tied to the address can pull the actual callback evidence into the review instead of arguing from memory — "here are the three jobs, here is the photo, here is the root cause, here is the next-job correction." RoofPredict does not inspect the roof or diagnose the workmanship for you; it keeps the record connected to the house so the review stays grounded in what was observed.

Area 3: Communication and handoffs

Roofing is a relay race. The baton passes from sales to estimating to production to purchasing to the crew to the homeowner and back to the office, and most jobs that go sideways do so at a handoff, not on the roof. A crew review should evaluate whether the crew kept those handoffs clear, early, and documented.

What good communication looks like in the field

Good field communication is mostly about timing. The same problem reported at 7 a.m. is a planning adjustment; reported at 4 p.m. it is a crisis. Score the crew on whether issues moved up the chain while there was still time to act on them:

• Were pre-job questions raised before the crew rolled out, not after they were standing on a roof with the wrong material?
• Were material shortages reported early enough to fix the same day?
• Were hidden conditions photographed and escalated, with a clear ask, rather than improvised?
• Were customer questions routed to the right person instead of answered with a guess?
• Were weather delays communicated before they became surprises to the office and the homeowner?
• Were cleanup, walkthrough notes, and closeout documents completed and returned?

The field should never improvise a major scope change without office approval — that is how you end up doing unbilled work or making a promise the company cannot keep. And the office should never expect a crew to resolve a pricing or coverage question they have no authority over. A clean escalation path protects both sides, and the review should check whether the crew used it.

Keep communication scoring out of protected territory

This is the area where reviews most quietly drift into bias. "Hard to understand," "doesn't communicate well," or "doesn't fit" can be a thin cover for accent, national origin, or language background — exactly the kind of judgment the EEOC's guidance on performance evaluations and discrimination complaints tells employers to watch for. The protection is to score the process, not the person's style. Did the crew document the condition? Did they notify the supervisor? Did they follow the escalation path? Those are job-related behaviors anyone can be coached on.

If language access is part of your job sites — and on most roofing crews it is — review the system, not the worker. Are safety materials translated? Is there a bilingual lead? Are checklists visual where they can be? Build the supports, and never turn someone's native language or accent into a performance criticism. A crew that escalated a hidden condition with a clear photo and a one-line note communicated perfectly, regardless of which language the note was in.

A handoff scoring snapshot

Area 4: Schedule discipline and job readiness

Schedule performance matters — slow jobs cost money and crowd the calendar — but it is the area most often scored unfairly, because so much of what drives a schedule sits outside the crew's hands. The review's job is to separate the parts of the schedule the crew actually owned from the parts the company has to fix upstream.

Score readiness, not only speed

Raw production speed is a noisy signal. A crew on a cut-up, steep, two-story tear-off with three penetrations and a chimney is not slower than a crew on a clean ranch walkable — it is doing harder work. Score job readiness and execution of the controllable sequence instead:

• Did the crew arrive with the right job packet, equipment, and task assignments?
• Were start, break, and end-of-day closeout steps recorded per company policy?
• Were delays reported early, while the office could still react?
• Did the crew protect completed work — tarps, edge protection — before leaving for the day?
• Did the crew follow the approved sequence: tear-off, dry-in, install, cleanup, final check?
• Did the lead update the office the moment a schedule assumption changed?

If a crew chronically misses production expectations, audit the inputs before blaming the people. Are materials landing on time? Are jobs scoped right? Are green workers paired with strong leads or thrown onto crews of their own? Are disposal, access, and weather buffers realistic, or does the calendar assume perfect conditions? Are change orders approved fast enough to keep the crew moving? A schedule review that skips those questions produces resentment and garbage data in equal measure.

The wage-and-hour line you cannot cross

This is where a performance review can create real legal liability if a supervisor gets careless, so it deserves a hard line. A schedule conversation is about planning and sequence. It is never a reason to shave hours, discourage accurate time reporting, or push anyone to work off the clock.

The Department of Labor's Fact Sheet #22 on hours worked under the FLSA lays out what counts as compensable time, and the traps for roofers are specific:

• Loading and prep at the shop before driving to the first job can be compensable work, depending on the facts. Telling a crew to "clock in when you get to the roof" can erase paid time they are legally owed.
• Waiting time can be hours worked when a crew is "engaged to wait" — stuck on site waiting on a delayed material drop they were told to wait for is different from being released to go home.
• Rounding is allowed only in fair increments (5, 10, 15, or 30 minutes) and only if it is not always rounded against the worker. Rounding that always lands in the company's favor is a violation.

If a review nudges anyone toward under-reporting time to make a schedule look better, you have traded a small production gain for a wage-and-hour claim. Keep the two completely separate: schedule discipline lives in the performance review; hours worked live in an accurate, honest timekeeping system.

A controllable-vs-not schedule grid

Area 5: Training, coaching, and advancement — the roofing crew development plan

The strongest reviews end looking forward, not back. The first four areas measure what happened; this one turns the findings into a roofing crew development plan with named skills, owners, and dates. Done right, the review stops being a complaint list and becomes a coaching document the worker actually wants to follow.

Tie training to the actual work

Training only sticks when it maps to the work a person really does. For roofing teams that usually means a mix of:

• Fall-hazard recognition and the company's fall-protection plan
• Ladder setup, anchor selection, and harness inspection
• Rescue planning — what happens in the first minutes after a fall arrest
• Heat illness recognition and the acclimatization plan for new workers
• Material handling and staging to cut shortage calls
• Specific installation details the crew has missed — flashing, ventilation, fastening pattern
• Photo documentation and closeout discipline
• Customer handoff and escalation scripts
• Bilingual safety communication where the crew needs it
• Crew-lead development for the people next in line

Map skills to autonomy, not to a grade

The most useful question in a training review is not "how good is this person, 1 to 5?" It is "what can this person do without close supervision, and what still needs supervised reps?" That framing is honest, it is coachable, and it builds a real ladder toward lead.

A simple competency map does this better than a number:

The X's tell you exactly what the next month of coaching should target, and they tell the worker exactly what "ready for lead" looks like.

Keep the development plan short enough to use

A plan nobody opens is not a plan. Two or three line items, each with evidence, an action, an owner, and a date:

One caution on advancement: do not promise that finishing a checklist guarantees a promotion, a raise, or a certification unless company policy actually says so and management is ready to apply it the same way to everyone. And never hand better training, better jobs, or the lead track only to favorites. The EEOC's best-practices guidance presses employers to monitor exactly these decisions — who gets developed, who gets the good assignments — for equal-opportunity problems. Uneven access to training is one of the quieter ways a company drifts into a discrimination pattern.

Regional and seasonal variation in what you score

The five areas are constant; the standard you score against shifts with climate, code, and season, and a fair review accounts for that. A crew on the Gulf Coast lives and dies by wind-zone nailing patterns and proper edge metal, because the next named storm will test every fastener. A Northern crew is judged hard on ice-and-water placement at eaves and valleys, on cold-weather sealant handling, and on whether they kept a dry-in watertight through a freeze-thaw cycle. A high-hail region weights documentation heavily, because clean before-and-after photos are what a homeowner needs to support a storm claim. A coastal crew gets scored on corrosion-aware fastener and flashing choices that an inland crew never thinks about.

Season changes the fair baseline too. The same production number means different things in July heat and in a short, wet shoulder-season week. A heat-illness near miss carries more weight in August; a slip on frost matters more in November. The review should hold the crew to the right standard for the conditions they worked in, and the company should make sure the job packet reflects the local code — wind zone, underlayment, ventilation, and permit rules vary by jurisdiction, and a crew cannot be faulted for missing a detail that was never in the packet. Local building code and the manufacturer spec set the bar; the review checks whether the crew hit it.

Build a one-page roofing crew scorecard

Keep the form short. A complicated review form guarantees rushed scores and copy-paste comments. One page for the scorecard, one page for the examples. Here is the core:

The "example required" column is the whole point. If the supervisor cannot write a specific example, the rating is reviewed before it becomes final. That single rule strips out vague criticism and surfaces upstream problems — a low schedule score whose only examples are about late materials is telling you to go fix purchasing, not to discipline the crew.

Avoid stack-ranking crews against each other unless you have a carefully reviewed policy for it. Ranking hides bias and punishes whoever drew the harder jobs, the newer crew, or the weather-cursed week. The safer default is to compare each person against the written job expectations and the evidence from their own assigned work.

Calibrate supervisors before the review cycle

If more than one supervisor rates crews, their scores will not mean the same thing until you calibrate them. One runs hot and dings every small thing; another avoids conflict and rates everyone a four. A short calibration meeting before the cycle fixes most of the drift.

Run anonymized examples past the group and agree on how each should be scored:

• A missed closeout photo set
• A correct stop-work call
• A late material-shortage report
• A customer complaint about cleanup
• A documented hidden-condition escalation
• A repeated failure to follow a corrected process

For each one, ask: what evidence is needed, which area does it belong under, and what action is fair? Calibration also keeps documentation tone consistent. "Missed three required deck-condition photos on the Oak Lane job after the checklist was reviewed" is a fact. "Careless" is an opinion. The difference is not cosmetic — performance records can resurface later in discipline, promotion, unemployment, wage, safety, or discrimination proceedings, and the fact survives scrutiny while the opinion does not.

A repeatable, fair review process

Use the same steps for every crew and every worker:

ROOFING CREW REVIEW — PROCESS CHECKLIST

[ ] 1. Pull the record: job photos, callbacks, incident notes,
       closeout notes, customer concerns, training completed.
[ ] 2. Strip out rumor and personal opinion. Evidence only.
[ ] 3. Sort blockers: company-controlled vs. crew-controlled.
[ ] 4. Score against WRITTEN job expectations — not stereotypes,
       not favorites, not other crews.
[ ] 5. Write ONE specific example per rating. No example, no score.
[ ] 6. Name themes across the five areas (safety, quality,
       communication, schedule, training).
[ ] 7. Write 2-3 next actions, each with an owner and a date.
[ ] 8. Give the worker a chance to respond/add context per policy.
[ ] 9. File it in the right place (employment file vs. job file vs.
       safety file) — do not make the review the only copy of a
       sensitive record.

A performance review is not a substitute for an incident investigation, a payroll correction, an accommodation request, a discrimination complaint, or a safety report. Each of those has its own process and its own legal handling. If a worker raises a discrimination concern about an evaluation, the EEOC's small-business guidance on internal complaints describes the corrective steps — checking whether the evaluation was consistent with the same standards and policies applied to everyone else. Consistency is the defense, and the example-per-rating rule is what makes consistency provable.

Turn individual reviews into company fixes

The best thing a review cycle produces is a list of company problems to fix. After the individual reviews, look across all of them for themes:

• Which job phases generated the most rework?
• Which checklist items got skipped most often?
• Which supervisors needed better documentation?
• Which safety topics keep coming up and need a refresher or a toolbox talk?
• Which office-to-field handoffs caused the most confusion?
• Which sales promises never made it into the job packet?

Then actually fix them — update the pre-load checklist, revise the closeout photo list, rewrite the crew-lead escalation script, schedule the toolbox talk, change how property-level tasks and records are assigned. This is the step that earns the crew's trust. People accept feedback far more easily when they can see management fixing the parts of the system management owns. A review process that only ever flows downhill loses credibility fast.

Keeping a property-level history makes the pattern-finding easier. When job photos, deck notes, callbacks, and follow-ups live tied to each address — the way a record in RoofPredict does — you can see that the same flashing detail caused three callbacks across two crews, which points at training or the job-packet template, not at one person. The tool keeps the evidence connected to the house; the management judgment is still yours.

Records, privacy, and what to keep separate

Keep enough to explain the decision, and no more in the wrong place. A review file should hold the form, the examples, the worker's response if policy allows one, the development plan, and the follow-up date. Safety incident records, payroll records, medical and accommodation information, and discrimination complaints generally need separate handling under company policy and applicable law — do not let a performance review become the catch-all folder for sensitive material.

The clean rule of thumb: operations evidence lives in the job system, employment decisions live in the HR process, safety records live in the safety process. A supervisor can reference a job photo or an incident number inside a review without copying the entire sensitive record into it. That separation makes information findable later and cuts down on careless sharing.

Common mistakes to avoid

• Importing benchmarks that don't fit your jobs. A squares-per-day target borrowed from a flat-roof commercial shop is meaningless on cut-up residential steep-slope.
• Promising outcomes from a review cadence. Do not claim a quarterly review will cut injuries or lift revenue by some figure. Run the process because it makes the work better, and let the results speak.
• Rating "attitude" without behavior. If you cannot tie it to a job-related action, it does not belong in the record.
• Punishing protected activity. A lower score because someone reported a hazard, filed for workers' comp, requested an accommodation, or took lawful leave is the textbook retaliation trap.
• Dinging people for needing training, translation, or accommodation. Those are supports to provide, not failures to score.
• Mixing review data into marketing. A crew review is an internal tool. It is not evidence for a public claim that your crews are "safer" or "faster" than competitors unless you have current, verifiable support and legal review.
• Letting the review replace real-time coaching. A surprise at the annual review is a management failure. Feedback should be continuous; the review just consolidates it.

The review conversation itself

The document is only half the job; how you deliver it decides whether it lands. A few rules from the field make the sit-down work.

Lead with the evidence, not the verdict. "Here are the three jobs and the photos" puts a fact on the table that the worker can engage with, where "your quality is slipping" just triggers defense. Walk the five areas in order, read the example for each rating, and let the worker respond — sometimes the response is the missing context that changes your read of the score, and capturing it is part of a fair process. Spend the most time on the forward plan, because that is the part the worker actually controls and the part that builds trust. Close by naming the company-side fixes you took away from the conversation, so the feedback visibly flows both directions.

Keep it free of surprises. If something in the review is the first the worker is hearing of it, that is a coaching failure that happened months earlier, and the review is the wrong place to spring it. And keep the tone in plain job language throughout — the same discipline that keeps the written record defensible keeps the conversation respectful.

A short list of questions to ask the worker, not only tell them, makes the review a two-way exchange:

• What slowed you down on these jobs that I might not see from the office?
• Which handoffs from sales, estimating, or the warehouse failed you?
• What do you want to learn next, and what is in your way?
• What would make the next job go smoother?

Those questions surface system problems and signal that the review is about getting better, not assigning blame.

A roofing crew performance review, done this way, is one of the highest-leverage hours a production manager spends. It makes the next roof safer and cleaner, it surfaces the system problems only the field can see, and it builds the next generation of leads — all while keeping the company on the right side of OSHA, the EEOC, and the Department of Labor. Tie every rating to evidence, separate what the crew controlled from what you controlled, end with a short plan, and the review will earn its place instead of being something everyone dreads.

Sources checked: June 18, 2026.

FAQ

What should a roofing crew performance review measure?

Measure five job-related areas: job-site safety practices, work quality and rework, communication and handoffs, schedule discipline and readiness, and training and advancement. Each rating should rest on real evidence from the job record — photos, callbacks, incident notes, closeout items — and carry a specific written example. Skip vague personality labels like "careless" or "bad attitude," which invite arguments and can read as bias. The strongest reviews separate what the crew actually controlled from problems the company needs to fix upstream.

How do you evaluate safety in a roofing performance review without unfairly blaming a worker?

Score whether the crew followed the documented safety process, not whether a hazard existed. If a job started without the right anchors, ladder, or training, that is a management planning failure, not a crew failure. OSHA's fall-protection rule (29 CFR 1926.501) triggers at six feet, and training is required before exposure under 1926.503. Only document a worker for bypassing a known requirement after they were trained and corrected. Never lower a score because someone called a justified stop-work — that can be illegal retaliation.

What is the OSHA fall-protection requirement for roofing crews?

Under 29 CFR 1926.501, any worker on a surface with an unprotected side or edge six feet or more above a lower level must be protected by guardrails, safety nets, or a personal fall arrest system. Residential construction uses the same six-foot trigger. Low-slope roofing allows certain warning-line combinations, but the warning line is not a substitute for protection at the edge. Fall protection was OSHA's most-cited standard for the fifteenth straight year in FY2025, with roofing contractors leading the violations.

How can a roofing crew review avoid wage-and-hour problems?

Keep schedule discipline completely separate from timekeeping. A review can discuss arrival, sequence, and delay reporting, but it must never pressure anyone to under-report hours or work off the clock. The Department of Labor's Fact Sheet #22 explains that shop loading, engaged waiting time, and similar activities can be compensable, and that time rounding must be fair and not always against the worker. Telling crews to "clock in at the roof" can erase paid time they are legally owed and create a wage claim.

How do you keep a performance review from becoming discriminatory?

Use written job expectations, a consistent form, a required example for every rating, supervisor calibration, and a chance for the worker to respond. The EEOC's guidance says comparable performances should get comparable ratings regardless of who is rating, and that appraisals should not be artificially high or low. Keep comments tied to job behaviors and out of protected territory — never score accent, national origin, age, religion, or disability. "Hard to understand" can mask language bias; review the communication process instead, such as whether the crew escalated and documented the issue.

What is a roofing crew development plan?

A development plan turns review findings into forward action: a short list of skills to build, each with the evidence behind it, a specific action, an owner, and a review date. The most useful version maps skills to autonomy — what the person can do independently, what still needs supervised repetitions, and what they could teach — rather than a single grade. Tie training to the work the person actually performs: fall-hazard recognition, specific flashing or ventilation details, closeout documentation, or crew-lead readiness. Keep it to two or three line items so it gets used.

Should productivity or squares-per-day targets be used in crew reviews?

Use them carefully, if at all. Raw speed is a noisy signal because a steep, cut-up tear-off is harder than a walkable ranch, and jobs run late for reasons the crew never controlled — late materials, permit delays, weather, hidden decking, slow change-order approval. Score job readiness and execution of the controllable sequence instead: on-time setup, following the approved work order, reporting delays early, protecting completed work. Never use a target to push inaccurate time reporting or off-the-clock work.

How often should a roofing company review its crews?

There is no single right cadence, but a formal review should never be the first time a worker hears feedback — that is a management failure. Coach continuously as jobs close, then consolidate it into a periodic formal review (many shops run quarterly or twice a year, with safety check-ins more often). What matters more than frequency is that the record is built as work happens, that supervisors are calibrated before each cycle, and that the company acts on the system-level themes the reviews surface, not only the individual scores.

How can RoofPredict support roofing crew performance reviews?

RoofPredict keeps job photos, deck-condition notes, tasks, closeout items, and follow-up actions connected to each property, so a review can pull the actual callback evidence and root cause instead of arguing from memory. That property-level history also makes it easier to spot patterns across crews — for example, the same flashing detail causing callbacks on several jobs points to training or a job-packet fix rather than one person. RoofPredict does not inspect roofs, diagnose damage, or score workmanship for you; the management judgment stays yours.