Agree the work before it starts.
Write down what is included, what is not and what gets delivered. Everyone reads the same page, so “I thought that was covered” stops being a conversation.
Inclusions · Exclusions · Deliverables
A statement of work the client can follow.
Break a job into phases and tasks, with quantities and amounts you supply, and watch the totals add up on their own. Send it, get a yes, and start.
Phases · Tasks · Running totals
Every line, with its photos.
Nest lines inside lines, from a whole build down to a single task, and attach the photos that show what you mean. Changes after the yes are recorded, not argued about.
Breakdowns · Photos · Change record
From a rough idea to an agreed job
Four steps, each one visible to everyone involved.
Start a scope
Give the job a name and it gets its own number, like SOW-0001, that people can say, write down and search for.
Break it down
Add phases and tasks, nested as deep as you need, with quantities, units and photos. Say clearly what is in and what is out.
Send it for a yes
Move it from draft to review to proposed. When the client accepts, the date and the person are on the record.
Run it to done
Start, pause, resume and complete the work. If plans change, a new version replaces the old one and the old one stays on file.
Built for jobs that change
Plain enough to send to a client. Careful enough to settle a disagreement.
A record of every step
Each move, who made it and why is written down. Two people editing at once get a clear message with the current state, never a silent overwrite.
Totals that add themselves
Amounts roll up from the smallest task to the whole job. You supply the figures; Scopes does the adding and never invents a price.
Tied to the rest of the job
Link a scope to the estimate it came from, the invoice that bills it and the project that carries it out, so nothing gets re-typed.
Scopes, answered.
No. You enter the amounts, and Scopes adds them up from each task to the whole job. It never sets a price for you.
While it is a draft or in review, yes. Once it has been proposed, you pull it back to change it, or replace it with a new version. The earlier one stays on file, so there is always a clear record of what was agreed.
Every scope gets a short number, like SOW-0001, counted separately for each organization. You can change the prefix to suit you, and numbers already issued never change.
Yes. Inclusions, exclusions and boundary notes sit right alongside the work, so the limits are as visible as the deliverables.
You can link a scope to the estimate it came from, the invoice that bills it, the project that does the work and any payments, so the paperwork stays connected.