Templates turn vague briefs into verifiable deliverable lists.
8 min readCore sections every template needs
| Section | Purpose |
|---|---|
| Project summary | One paragraph on goal |
| Deliverables | Numbered list of what you will produce |
| Out of scope | Explicit exclusions |
| Timeline and milestones | Dates and dependencies |
| Revision limit | How many feedback rounds included |
| Communication | Channels, response times |
| Payment terms | Amount, schedule, method |
| Acceptance criteria | How client signs off |
Sample deliverables block (VA project)
Included:
- Weekly inbox management, max 20 hours
- CRM update for new leads within 24 hours
- Friday status report email
Not included:
- Cold calling
- Graphic design
- Weekend coverage unless booked as add-on
How to use the template
- Send blank template after discovery call.
- Co-fill with client on a call or async comments.
- Resolve blanks before deposit or start date.
- Both parties confirm via email or e-sign.
- Attach template to every change order for comparison.
Common mistakes
- Template too long nobody reads. Keep it scannable.
- Missing out-of-scope section. Most disputes live here.
- Deliverables use jargon the client cannot verify.
- Never updating the template after lessons from bad projects.
Final thoughts
Scope templates are not red tape. They are the map. Clients and VAs who share the same map finish projects with less stress.
How Salag helps
- Agreement Builder. Build scope sections into a client-ready agreement.
- Rate Calculator. Price the deliverables you list in the template.
- Scope Creep Detector. Check new asks against your signed template.
Move safer. Not faster.
In short
A project scope template turns a vague brief into a list of deliverables, timelines, revision limits, and out-of-scope items. Fill it with the client before work starts. Templates save time and stop the "I thought that was included" conversation later.
Common questions
A project scope template turns a vague brief into a list of deliverables, timelines, revision limits, and out-of-scope items. Fill it with the client before work starts. Templates save time and stop the "I thought that was included" conversation later.
Write down what you agreed on and what changed. Do not start new work on vague terms.
Use plain English, confirm in writing, and set clear hours. Clients hire you for reliability, not cheap labor.
Put the basics in your agreement or a recap email before billable work starts. Bigger projects need fuller terms.
Stay warm but firm. Offer options inside a clear process, like a change order or a short written recap.
ALIGN means: capture facts, compare to your agreement, name tradeoffs, confirm in writing, and save the decision for next time.
Escalate when the same problem repeats: unpaid extras, late approvals plus new asks, or refusal to confirm in writing.
Yes. A clear email with tasks, dates, price, and limits beats a verbal yes every time.
Salag gives you tools and templates so you can set boundaries before small problems grow.
Use written recaps, scope trackers, and Salag tools like agreement builders and scope detectors.
Most recaps take five minutes after a call. That small step saves hours of arguing later.
Yes. Retainers need weekly change logs. Projects need milestone gates. Always compare new asks to written terms.
Pause billable work on unclear items. Send a narrow summary of what you will do. Save their reply either way.