FlowScope Clarification5 min read

Scope clarification for trades, without the email chase

Your GC sends an email about work you need to do. The scope isn't clear enough to price or schedule yet. Flow gives you one shared intake form to close the gap with the general contractor before work starts.

Trades company and general contractor collaborating on a shared scope clarification form

Summary

Scope Clarification collects missing project details through a simple shareable intake flow. Start the intake, send it out, and receive clearer scope information before work begins. A trades company creates the form, sends it to the general contractor, and both sides collaborate on one shared record until the scope is clear enough to lock.

Try it

The email that starts it

Your general contractor sends a note: drywall repair on the fourth floor, can you take a look? You know there's work, but you don't have enough to price it or put a crew on site. Access hours aren't clear. You don't know what's in scope versus what's being handled by another trade. The photos, if there are any, are buried in the thread.

That back-and-forth usually happens over email. Someone forwards a PDF. Someone else replies with a screenshot. A third person asks for details that were already sent two days ago. By the time you have enough to move forward, you've lost a week and you're not sure which version everyone is working from.

Scope clarification is about closing that gap. Not sending a quote request. Not issuing a work order. Just getting the missing information in one place before you start the job.

What scope clarification looks like in Flow

Scope clarification intake form shared between a trades company and general contractor

Scope Clarification collects missing project details through a simple shareable intake flow. Start the intake, send it out, and receive clearer scope information before work begins.

You fill in what you already know from the GC's email, send the link back to the general contractor, and everyone works from the same form. Pick a template or build your own with the fields your crew actually uses: areas in scope, access details, photos, exclusions, whatever you need before you can price or mobilize.

The GC opens the link on their phone or laptop. No login. They update the shared form, attach files, and leave comments while the intake is still open. Your team sees the same version, not a forwarded email chain with five different attachments.

Why a shared form beats email

Email works until it doesn't. The moment more than two people are involved, you start losing track of what's current, who provided what, and whether the latest thread matches what the GC actually agreed to.

With a shared intake form, there's one record. If the GC lists the wrong area or a photo doesn't show the full scope, your team can flag it in the comments before anything gets locked.

Comments stay open while the intake is in draft, which is when most of the back-and-forth actually happens. You're not waiting for someone to reply to a buried email thread. The question sits on the form where everyone can see it.

When scope is clear enough to lock

Marking an intake complete isn't a formality. It means the information is good enough to price, schedule, or start the work.

When you mark it complete, Flow locks the shared form so nobody can slip in edits after the fact. If you need to reopen it, you can. But the lock is there so you're not rebuilding scope from a surprise email three days later.

Every change gets logged along the way. Who updated the site details. When a file was added. When the form was sent, locked, or marked complete. That history matters when the GC disputes a detail weeks later, or when your PM takes over from the estimator.

How it plays out on a real job

You get the GC's email. You open a Scope Clarification intake, add what you know, and send the link back to the general contractor. They fill in the gaps, upload site photos, and answer your questions while the form is still open.

Your team reviews it, asks follow-up questions in the comments, and marks it complete when the scope is solid enough to move forward.

From there, you can create a Flow project with the collected details already in place. Less retyping, fewer transcription errors, and the person running the job isn't starting from a blank screen.

Free to use, built for the field

You don't need a full platform rollout to try this. Scope Clarification is free, and the general contractor doesn't need an account.

For trades companies: share the intake, gather missing details, and keep scope work moving. It works on mobile, which matters when your GC contact is on site trying to upload photos. Send the link, collect what you need, and stop rebuilding scope from email every time someone new joins the job.

If the job grows into something bigger, the intake you've already collected lives in Flow's project workspace alongside tasks, documents, and team access.

Try it on your next job

Scope Clarification is free. Create the intake, send it to your GC, and get everyone working from the same information before work starts.

FAQ

Frequently asked questions

Common questions about scope clarification

Scope clarification is the step where a trades company collects missing project details before pricing, scheduling, or starting work. That usually includes site access, affected areas, photos, inclusions, and anything else the general contractor hasn't spelled out yet.