Start with a shared definition of the work
Scoping is the first of five connected stages. Clarify the outcome before price, timing, and contract language harden around different assumptions.
Scroll to see all five stages
- 01ScopeScoping & ProposalsTurn the work, timing, and responsibilities into a shared plan.Current stage
- 02AgreeContracts & TermsUnderstand the wording, tradeoffs, and questions before signing.
- 03DeliverScope & CommunicationCompare new requests with the agreement and respond clearly.
- 04InvoiceInvoicing & PaymentCheck the figures and follow up without unnecessary friction.
- 05ResolveDisputes & Wind-downOrganize the facts and consider proportionate next steps.
Lucy’s Scoping & Proposals tool
Scoping & Proposals
Review a draft or turn rough notes into the questions and wording needed for a shared, concrete understanding.
Your perspective
What Lucy checks
- Deliverables and exclusions
- Responsibilities and dependencies
- Milestones and deadlines
- Revision limits
- Acceptance criteria
- Fees and payment timing
Streamed as it is written
Lucy’s response
Lucy will organize the response into useful sections such as:
- What is already clear
- Gaps and ambiguities
- Dependencies and assumptions
- Questions to resolve
- Suggested wording
Worked example
A five-page website with two very different gaps
Situation
The draft lists Home, About, Services, Work, and Contact pages. It says the fee includes “reasonable revisions” and does not mention who supplies photography.
What stands out
Photography is missing: the draft says nothing about it. Revisions are ambiguous: they are mentioned, but “reasonable” gives neither side a shared way to count or close them.
Useful next step
Name who sources and licenses images, then replace “reasonable revisions” with a review process, number of rounds, and a route for work that changes the approved direction.
Define the result before the task list
A useful scope connects the outcome to deliverables someone can identify and review. Activity alone—design, strategy, development—does not tell either side what will be handed over.
- Name each output, quantity, format, and meaningful exclusion.
- State the client inputs, access, decisions, and deadlines the schedule depends on.
- Connect milestones to observable work rather than percentages or dates alone.
Give feedback and sign-off a shape
Revision and acceptance terms do not need to be long, but they should describe a process both sides can recognize while the project is moving.
- Identify the approver and ask for consolidated feedback.
- Distinguish corrections and in-scope revisions from a new deliverable or direction.
- State the review window, acceptance method, fee timing, and what happens when an input is late.
What this tool cannot decide
Lucy can identify missing or unclear scope language, but she cannot know an unstated budget, internal approval process, technical dependency, or local legal requirement.
When human expertise matters
Consider specialist advice when the work involves regulated data, safety-critical outcomes, employment classification, unusual insurance requirements, or substantial intellectual property.
Continue with the record
Common questions
What should a freelance project scope include?
A useful scope usually names the deliverables, exclusions, responsibilities, timing, revision limits, dependencies, fees, and acceptance criteria. Lucy can flag gaps and turn them into neutral questions for both sides.
Can Lucy write a proposal from my notes?
Lucy can help organize your notes and draft concrete proposal language. You should still confirm that the final wording reflects the actual commercial agreement before sending or accepting it.
Does the scoping tool decide whether a price is fair?
No. Pricing depends on context Lucy may not have. She can identify what the price appears to cover, explain assumptions, and highlight questions that could affect cost or timing.