A clean scope letter before they mobilize.

Subcontractor Scope Letter is a free browser tool that turns a plain description of the job and what the sub owns into a formal pre-mobilization scope letter: in-scope, out-of-scope, mobilization requirements, and a sign-off line. The scope goes on paper before day one, not after the dispute.

Write the letter ↓See how ↓

Free · no account · we ask for an email after five runs

Good at:
Preventing the "I thought the GC was handling that" conversation on day three.
Not for:
Replacing a subcontract or establishing payment terms.

Scope letter only. Does not create a subcontract, establish liability, or define payment. Review with counsel before using on regulated or public projects.

Name, address, and a one-line description.

e.g. electrical, framing, mechanical, plumbing, drywall

Describe the scope in plain language. The more specific, the better the letter.

PDF, image, Word. Up to 3 files, 10 MB each.

The scope letter will appear here once the tool runs.

Questions people ask first

A written scope letter ready to send to a subcontractor. Project, sub trade, scope of work, start date, site contact, laid out in the format a sub recognises and a court would accept as a written record of what was agreed.

No. The output is a scope letter, useful for early-stage coordination, for confirming what was agreed verbally, and for clarifying scope before a full subcontract is signed. The substantive subcontract terms (insurance, indemnification, payment, lien provisions) belong in a subcontract a construction attorney drafts.

Early in the job, before the formal subcontract is in place. Right after a verbal handshake. When a sub starts work and you want a written record of what they're supposed to be doing. Anywhere the alternative is a text-message scope description.

Project name and location, the sub's trade, the scope of work (be specific, “electrical” isn't enough; “rough-in for first-floor receptacles and lighting per Sheet E-201” is), the start date, and your site contact.

Both. Send the letter as an email attachment with the body of the email recapping it briefly. The sub gets the letter; you get an email trail with the letter attached for the dispute file.

What it catches

01

Define it before day one

Day-one disputes are day-negative-fourteen problems. Write the scope down before mobilization, not after.

02

In scope and out of scope

Clear sections for what the sub owns and what they don't, so “I thought the GC had that” never happens.

03

Ready to sign

Mobilization requirements and a sign-off line, formatted and ready to send.

Want the whole shop read, not just one form?

An operations review reads your estimating, change orders, and field workflow cold and names where margin actually leaks. Free while in beta — will be $1,499 after. 3 review slots a week.

Start an operations review →Compare pricing →