Scope and change
Most disputes about a project start with a scope that both sides read differently. These guides show how to write a scope of work a client understands: deliverables you can count, what is out of scope, the assumptions behind the price and how acceptance works. They also cover what to do when the client asks for more, so a change request becomes extra paid work instead of an argument. Start with the scope of work guide, then use the others when a project starts to grow.
- Start here
How to write a scope of work clients understand
The parts of a clear scope of work, how to make every deliverable countable, and how to handle change requests without arguments.
6 min read
-
Scope creep: how to handle it without losing the client
A decision table for every extra request, a priced change request worked through in euros, and four replies to copy.
8 min read
Related pages
Proposals your clients actually say yes to
Propozit is free to start, with no card needed. Create your account today and see the plans on the pricing page.