Freelancer Client Brief Checklist: What to Ask Before Starting a Project
A project can go off track when the client and freelancer have different expectations. A clear client brief helps both sides agree on the goal, what is included, what is not included, when work is due and how approval will happen.
A practical HoxTools guide for creators, students, website owners and independent professionals.
1. Understand the Client's Goal
Start with the reason behind the project. The client may ask for a website, poster, application or social media design, but the real goal could be to generate enquiries, explain a service, improve an existing process or launch a product.
- What problem should this project solve?
- What result would make the project successful?
- Why is the work needed now?
- Is this a new project or an update to an existing one?
2. Identify the Audience and Users
Ask who will use or see the final work. A design for university students may need a different tone from a business dashboard for staff. Audience details help guide language, layout, accessibility and technical decisions.
- Who is the primary audience?
- What do they need to understand or do?
- Are there different user roles or customer groups?
- Which languages, devices or accessibility needs should be considered?
3. Define the Scope of Work
Scope describes the work you are agreeing to deliver. Be specific. For a website, scope might include a certain number of pages, a contact form, mobile-responsive layouts and basic content entry. It should also identify exclusions, such as copywriting, paid hosting, domain registration, premium plugins or ongoing maintenance if these are not included.
Scope questions
- What exact tasks and features are required?
- How many pages, screens, designs or items are included?
- What is explicitly outside the project?
- Are integrations, data migration or third-party services needed?
- Who will provide text, images, logos and other assets?
- What happens if the client requests additional work?
4. Agree on Deliverables and File Formats
Write down what the client will receive at the end. “A complete design” can mean different things to different people. Specify the final files, source files, access credentials, documentation, deployment or handover items that are included.
| Project type | Possible deliverables to define |
|---|---|
| Website | Live pages, responsive layouts, source files, admin access, backup and handover notes. |
| Graphic design | Final PNG/JPG/PDF exports, dimensions, and editable source file if agreed. |
| Software | Working features, setup instructions, database or deployment notes, and agreed source code. |
| Content | Number of pieces, word range, file format, research level and revision process. |
5. Confirm Timeline, Milestones and Dependencies
Ask for the required launch or delivery date, but also identify what must happen before work can progress. A freelancer cannot reliably promise a deadline if essential content, approvals or access are delayed.
- What is the target completion date?
- Are there fixed launch dates or intermediate milestones?
- When will the client provide content, feedback and access?
- Who is responsible for reviewing each milestone?
- How will delays or changed priorities affect the schedule?
6. Discuss Budget and Payment Terms
Confirm the project price and what it covers before starting. If the project is split into milestones, define the amount and payment trigger for each stage. Also clarify third-party costs such as hosting, domain names, stock assets, subscriptions, transaction fees or paid software.
Put the payment schedule, accepted payment methods, invoice details and any deposit arrangement in writing. Do not assume that a verbal conversation has resolved every financial detail.
7. Set Revision and Approval Rules
Revisions are easier to manage when both sides know how feedback works. State how many revision rounds are included, what counts as a revision and what would be treated as a new feature or change in scope.
8. Confirm Communication and Decision-Making
Identify the main contact person and where project decisions will be recorded. If several people provide feedback, ask the client to combine it into one approved response. This reduces conflicting instructions and repeated rework.
- Who is the primary point of contact?
- Which channel will be used for project communication?
- What is a reasonable response time for questions and approvals?
- Who has final approval authority?
- How will important decisions and change requests be documented?
9. Cover Access, Ownership and Handover
Some projects require access to hosting, a domain, analytics, a content management system or an existing code repository. Use secure access methods and request only the permissions needed. Do not ask clients to send passwords in plain text chat if a safer invitation or access-sharing method is available.
Clarify who owns the final deliverables, when ownership or usage rights transfer, whether third-party assets have separate licences and whether source files are included. For software and websites, agree how backups, credentials, deployment and future maintenance will be handled.
10. Copy-and-Use Client Brief Checklist
Project intake checklist
- Client name and business/contact details recorded.
- Project goal and success criteria written down.
- Target audience and users identified.
- Scope, included features and exclusions confirmed.
- Deliverables and file formats listed.
- Required content, assets and access identified.
- Timeline, milestones and approval dates agreed.
- Price, payment schedule and third-party costs documented.
- Revision rounds and change-request process defined.
- Main contact and final approver identified.
- Ownership, licences, security and handover discussed.
- Client has reviewed and approved the brief.
Frequently Asked Questions
Do small freelance projects need a written brief?
Yes. It can be short, but even a one-page brief helps confirm the task, deadline, price and expected result.
What if a client does not know exactly what they need?
Ask about the problem and desired outcome first. You can propose options, explain trade-offs and document the selected approach before estimating the full work.
Should I start work before the client approves the brief?
For paid project work, it is safer to confirm the scope, price, timeline and payment arrangement in writing before beginning substantial work.
How do I handle new requests after the project starts?
Record the request, assess its impact on time and cost, and send an updated estimate or change note for approval before proceeding.
Final Thoughts
A clear brief protects the working relationship. It helps the freelancer estimate accurately and gives the client a realistic picture of what will be delivered. Take time to ask the right questions, write down the agreement and get approval before moving into production.
This checklist is general business guidance, not legal or accounting advice. For high-value or complex engagements, consider having a suitable professional review your contract and payment terms.
Published by HoxTools. Review the linked official documentation for the latest product-specific requirements.