Freelance Scope Prompts: Deliverables, Boundaries and Handover
Turn a client brief into clear deliverables, inputs, review rounds and acceptance checks. Eight original prompts help you explain a scope before you commit to the work.
By LifestyleGlide · Published · 6 min read
A scope becomes useful when two people can read it and describe the same piece of work. “Website content” may mean three pages to you and every page, upload and revision to a client. Name the deliverables and the things that remain outside them before estimating effort.
Use these prompts to prepare a commercial discussion and a plain-language project brief. Confirm prices, dates and terms with the client through your normal process. The examples are planning documents, not a substitute for an agreement or specialist contract advice.
Start with this workflow.
Clarify the request
Identify the audience, deliverable, inputs and unanswered questions before promising a package.
Set the boundaries
Name quantities, formats, review rounds, exclusions and what would count as completion.
Check dependencies
Separate your working time from waiting for materials, access, approvals or consolidated feedback.
WORKED EXAMPLE
“A few graphics” becomes a reviewable brief
Illustrative example: a client asks for launch graphics. They have supplied three approved messages but have not agreed sizes or revision rounds.
STARTING POINTAll launch graphics, unlimited revisions, delivered next week.
AFTER CHECKINGProposed: three static graphics using the supplied approved messages. Platform sizes and one consolidated review round still need confirmation. New messages, animated versions and ongoing posting would require a separate scope discussion. A delivery date can be proposed after the inputs are confirmed.
What changed The scope names the current material, unresolved decisions and boundaries. It avoids accepting an undefined workload.
Make your own working brief.
Desired result:
Deliverables and quantities:
Formats:
Client inputs:
Exclusions:
Review process to confirm:
Acceptance checks to confirm:
Dependencies:
Handover items:
Choose a task from this guide, add your details and check the answer before using it.
Browse the prompts below.
Freelance scope ↗
Find ambiguity in a brief
Find ambiguity in a briefOpen the prompt +
INPUTS
Client brief, service description and known constraints
PROMPT
Review this client brief [brief] for my service [service]. Constraints: [constraints]. List vague deliverables, missing quantities, unclear inputs and assumptions that could change the workload. For each, write a neutral clarification question. Do not add services or assume that a larger project is needed.
INPUTS
Confirmed request, quantities, formats and audience
PROMPT
Turn [confirmed request] into a deliverable list. Agreed quantities: [quantities]. Formats: [formats]. Audience: [audience]. Give each item a short description, supplied input, output format and completion check. Label missing details to confirm. Do not invent fees, ownership terms or technical implementation promises.
Explain exclusions without sounding defensiveOpen the prompt +
INPUTS
Included work, common assumptions and client goals
PROMPT
Write a plain-language included and not-included section for [project]. Included: [items]. Common assumptions: [assumptions]. Client goal: [goal]. Explain exclusions by describing the boundary and where a separate decision would be needed. Avoid hostile wording or invented penalties. Do not state that the client has accepted the boundary.
INPUTS
Deliverables, workflow and known client materials
PROMPT
For these deliverables [deliverables] and workflow [workflow], list the inputs I need from the client. Known materials: [materials]. Give input, reason, format, person to confirm and dependency. Keep dates unfilled unless supplied. Identify what I can begin before all inputs arrive.
INPUTS
Deliverable, stakeholders and proposed review process
PROMPT
Help me describe a proposed review round for [deliverable]. Stakeholders: [roles]. Proposed process: [process]. Explain what is reviewed, how feedback is consolidated, what a revision covers and what would need a new scope discussion. Keep these as proposals until the client agrees. Do not draft legal clauses.
Write observable acceptance checksOpen the prompt +
INPUTS
Deliverable description, brief and quality expectations
PROMPT
Suggest acceptance checks for [deliverable] using [brief] and [quality expectations]. Each check should be observable in the actual output. Separate objective checks from subjective preferences requiring agreement. Avoid guarantees about sales, rankings or audience response. Do not present proposed checks as accepted criteria.
INPUTS
Original scope, new request, effort estimate and options
PROMPT
Draft a response to [new request]. Original scope: [scope]. Estimated impact from my own assessment: [impact]. Explain the difference, then offer either replacing an existing item or reviewing an additional estimate. Ask for a decision before starting extra work. Do not invent pricing or imply acceptance.
Make the final handover checklistOpen the prompt +
INPUTS
Agreed deliverables, delivered files and open issues
PROMPT
Prepare a handover checklist from [agreed deliverables], [delivered files] and [open issues]. Include where the files are, usage notes, checks performed, client review needed and confirmed next steps. Separate complete, awaiting review and unresolved items. Do not include passwords or say an unresolved item is finished.
These are original, editable starting points. A prompt does not complete an action outside the conversation. Use approved inputs and review facts, source material and commitments before using a result.
