Roofing contractor service standards: documenting them

Q: Who should write them?

The [person who does the work](/roofing-contractor-pay-rates-and-labor-costs-in-2027) best, edited by whoever writes clearly. Standards written entirely by an owner who has not been on a roof recently read as instructions from a distance.

What to take away

A standard nobody reads is worse than none, because it creates the belief that the question was settled.
One page per standard, written for the person doing the work, in the order they meet the decisions.
Never restate the manufacturer's instructions or the building code in your own words. Point at them, because your paraphrase will drift and theirs will not.
Every standard needs a version, a date, an owner and a way to report that it conflicts with reality.

This guide shows how to document roofing contractor service standards for recurring job decisions. Technical content belongs to the system manufacturer and your building department.

What a standard is for

A standard exists to make one decision the same way twice, by two different people, when nobody senior is watching.

That test rules out most of what gets written. A document describing your commitment to excellence settles nothing. A document saying who inspects the deck, what quantity triggers a change order, and who signs it, settles something every week.

Before writing anything, name the decision. If you cannot name it, you are writing a policy nobody needs.

The one-page format

Title, version, date, owner.
When this applies, in one sentence.
Who does it, by role.
The steps, in order, short enough to read on a roof.
What is recorded, and where it goes.
What to do when this does not fit the situation, and who to call.
What this document does not cover, with a pointer to what does.

Item six is the one that gets skipped and the one that decides whether a standard survives contact with an unusual roof. Without it, a crew facing something the document did not anticipate either freezes or improvises, and neither is what you wanted.

One-page standard format

Title, version, date, owner
When this applies, one sentence
Who does it, by role
Steps in order, roof-readable
What is recorded, and where
What to do when it does not fit
What this document does not cover

What belongs in yours

For a roofing firm, the standards worth writing first are the ones covering decisions that repeat and cost money when they go differently.

Site preparation and delivery:Assign who confirms access, protects the property, checks material delivery, and records any preexisting damage.
Deck inspection and concealed conditions:State who inspects the exposed deck, what condition or measurement is recorded, and when work pauses for a supervisor's decision. Photograph and document the condition before it is covered.
Change orders:Define the quantity or condition that triggers a change-order review. Record the discovered condition, quantity, scope, and price, and identify the customer and company roles authorized to approve and sign before extra work begins.
Installation hold points:Identify who checks the work at required stages, including before work is covered, and where the current manufacturer instructions, adopted code, and permit requirements are checked. Record the inspection and any correction.
Fall protection and stop-work decisions:Assign who checks that the site's fall-protection plan is in place, who can stop work, and who must be contacted when conditions change.
Cleanup and final walkthrough:Assign who checks for debris and stray fasteners, protects the property during cleanup, and records the final walkthrough or any remaining work.
Job records and closeout:List the job photos, inspection records, approved change orders, customer handoff documents, and other records the crew must send to the job file, and name who checks that the file is complete.

First seven roofing standards

Site arrival and protection
Deck inspection and change order trigger
Photograph protocol, fixed order
Stop rule and who holds authority
Handling a discovered condition
Handover and documentation pack
Handling an on-site complaint

Seven documents, one page each. That is a complete first system, and it is achievable in a fortnight.

Point, do not paraphrase

The temptation is to summarize the manufacturer's fastening requirements or the local code into your own document so everything is in one place.

Resist it. Your summary will be wrong the moment either source is updated, and a crew following your outdated paraphrase is following you rather than the instruction. Reference the source, say where the current copy lives, and make it somebody's job to check that the link still resolves.

For construction fall protection, OSHA's requirements are in 29 CFR Part 1926, Subpart M, including § 1926.501. The standard should point crews to the applicable requirements rather than paraphrase them.

Your standard states what your firm does, who decides, and who may stop work, and it does not restate a requirement as if you were its source. Build its program with a qualified adviser.

Document control that a small firm can run

One place where the current version lives, and everyone knows where.
A version number and a date on every page, so a printed copy in a truck can be checked against the current one.
One named owner per document.
Superseded versions removed from circulation, not archived on the same shelf.
A standing instruction that anybody who finds a conflict between the document and real work reports it, and that reporting it is welcomed rather than treated as a complaint.

That last rule is what keeps documents alive. Firms where nobody reports a conflict do not have accurate documents, they have quiet ones.

Document control for small firms

One place holds the current version
Version number and date on every page
One named owner per document
Superseded versions removed from circulation
Anyone finding a conflict reports it

Testing a standard before it is released

Give the draft to three people and watch.

Test the draft with three people

The doer walks a real job from the page
A new person answers step four
The filer traces the record to the file
Fix what they find, then release
Set a review date

The person who will do it. Ask them to walk through a real job using only this page. Every time they hesitate, something is missing.
Somebody new. Ask them what they would do at step four. If they invent an answer, the step is ambiguous.
The person who has to file the record. Ask how the record reaches the job file. If the answer involves remembering, add the step.

Fix what those three find. Then release it and set a review date.

Standards and what the customer is told

A standard is internal, and what you publish about it is an advertising claim. Saying your firm follows a documented process is supportable if it does. Saying it is more thorough than a competitor is not. The FTC's Endorsement Guides, 16 CFR Part 255, address endorsements, including customer reviews; the FTC guidance on soliciting and paying for online reviews covers the related question of how customer feedback may be gathered and used.

Ask every customer for a review at the same point with the same wording. A standard that tells the team to ask only the happy ones is a standard that puts the firm on the wrong side of that guidance.

Where standards connect to everything else

For a shingle job, practical hold points include recording the deck condition before covering it, obtaining approval before work outside the original scope begins, and documenting the final cleanup and walkthrough. These are operating controls, not substitutes for the roofing contractor quality assurance checklist; the roofing contractor service quality guide for owners describes the three meanings of quality those controls serve.

Retain business records made by a standard using the IRS's recordkeeping guidance in Publication 583.

Any standard touching permits or inspections must match the requirements of the local building department or other authority having jurisdiction, the locally adopted building code, and the permit. The roofing contractor licensing and compliance guide covers related obligations.

New people meet these documents in their first week, so write them for that reader. How the induction is structured is covered in how to hire reliable staff for a roofing contractor business, and what a documented process lets you honestly say to customers belongs with the roofing contractor marketing and growth guide.

Common questions

How long should each standard be?

One page. If it needs two, it is probably two standards, and splitting it makes both more likely to be followed.

Who should write them?

The person who does the work best, edited by whoever writes clearly. Standards written entirely by an owner who has not been on a roof recently read as instructions from a distance.

How often should they be reviewed?

Annually, and immediately when a manufacturer changes an instruction, a code changes, or the same conflict is reported twice.

What if the crew ignores a standard?

Find out whether it is unrealistic before you treat it as a discipline problem. Ignored standards are usually badly written ones, and the crew is telling you something you asked them to tell you.