Freelance Client Intake Form: 9 Questions That Reveal Who Approves the Work
How-To & Tutorials
Freelance Client Intake Form: 9 Questions That Reveal Who Approves the Work

A strong freelance client intake form does more than collect a project brief. It reveals who can approve the work, how feedback reaches you, and what could quietly delay delivery. These nine questions help freelancers uncover that decision path before they set a price or promise a deadline.
In this guide
Why a normal intake form misses the expensive risk
A freelance client intake form is usually built to collect the brief: what the client wants, when they need it, and what they can spend. Those are useful questions, but they do not reveal the person who can approve the work, the person who will give feedback, or what happens when those people disagree. That gap is where “quick revisions” turn into a second project.
The overlooked question is not only what are we making? It is who has the authority to decide that it is finished? Before quoting, map the decision path as carefully as the deliverable. This is especially useful for agency clients, startups, and remote teams where the person booking you may not own the budget or final sign-off.
The 9 questions to add before you quote
Use these questions in a discovery form or a short kickoff call. Ask for names or roles, not just broad descriptions. The goal is to make approval visible without making the client feel interrogated.
| # | Question | What it uncovers |
|---|---|---|
| 1 | Who owns the business outcome? | Name and role of the person accountable for the result. |
| 2 | Who is the day-to-day contact? | One person to answer routine questions and consolidate updates. |
| 3 | Who gives final approval? | The person authorized to accept the deliverable and release sign-off. |
| 4 | Who else must review it? | Legal, compliance, brand, IT, or other required reviewers. |
| 5 | How will conflicting feedback be resolved? | One client-side decision owner, not a vote left to the freelancer. |
| 6 | What does “done” mean? | A measurable acceptance condition tied to the brief. |
| 7 | How many review rounds are expected? | State the included rounds and what counts as a new round. |
| 8 | How quickly can reviewers respond? | Set a realistic business-day response window. |
| 9 | What happens if approval is delayed? | Agree how a missed decision date affects delivery and availability. |

A practical approval map for small projects
Once answers arrive, reduce them to a simple approval map. Do not build a complicated RACI chart for a one-page website. Record one accountable approver, one day-to-day contact, and any specialists whose feedback is required. If there are several approvers, ask the client to collect one consolidated set of comments before sending them to you.
For example, a brand refresh might have a marketing manager as the daily contact, a founder as final approver, and legal reviewing claims. Legal can flag compliance, but the founder still owns the final creative decision. That distinction keeps you from treating every opinion as a new approval gate.
Here is a compact map to capture after intake:
| Role | One clear responsibility | Write down |
|---|---|---|
| Project contact | Coordinates everyday questions and client-side updates | Name, preferred channel, usual response time |
| Final approver | Accepts the deliverable and makes trade-off decisions | Name, approval criteria, sign-off date |
| Required reviewers | Flag specialist requirements before approval | Reviewer, what they review, deadline |
| Feedback coordinator | Combines comments into one actionable response | Name and process for resolving conflicts |
How the answers should change your estimate
A brief with one approver and a fixed review date is not the same risk as a brief with four departments and an undefined launch date. Price the actual decision path, not just the number of design screens or writing hours. Add explicit time for coordination when the client needs it, or narrow the included review rounds when the budget cannot support open-ended feedback.
Do not charge a surprise “stakeholder fee” after the client has signed. Instead, name the assumptions in the proposal: number of review rounds, who consolidates feedback, turnaround time, and what triggers a change request. If the project scope later changes, use a clear process such as the one in our freelance change-request pricing guide.

A lightweight intake workflow that clients will finish
Long forms lose good clients. Keep the first form to questions that affect fit, scope, schedule, and approval. Make sensitive or detailed questions conditional, then discuss the answers during a call. Give the client a realistic completion time, save progress where possible, and explain why you ask for each detail.
After they submit it, send a concise recap: your understanding of the goal, the named approver, the review dates, and the assumptions that still need confirmation. That recap becomes the bridge between intake and proposal. For handoff structure after the project is approved, see this async client handoff brief.
What to do when nobody can name the approver
Treat “we’ll figure it out later” as an unresolved project dependency, not as permission to start. Offer a short paid discovery phase or a limited first milestone that ends with a named decision-maker and agreed approval process. Keep the initial commitment small; do not produce the full deliverable while authority is still unclear.
Sometimes the client genuinely has shared authority. In that case, ask them to choose one person to reconcile comments and send a single decision. If they cannot, make the review rounds and schedule consequences explicit in writing. This protects the relationship as much as your calendar.
The intake checklist you can reuse
Before sending a quote, check that the following are written down: the business outcome, deliverables and exclusions, day-to-day contact, final approver, required reviewers, how feedback is consolidated, review-round count, client response window, and what happens if a decision is late. If any of these remain blank, either resolve them or label the assumption clearly in the proposal.
FAQ: freelance client intake forms
Should I ask a client who approves the work before quoting?
Yes. The answer affects schedule and revision risk, so ask during intake. If they cannot name one approver yet, make that an explicit prerequisite or quote a small discovery phase first.
How many questions should a freelance intake form include?
There is no magic count. A short first-stage form of roughly 8–12 focused questions is usually easier to complete than a full project questionnaire. Add conditional questions only when the project needs them.
What if the client says the whole team will approve?
Ask who will collect and reconcile the team’s comments, then have that person send one consolidated response. If everyone can send separate feedback, define how conflicting opinions and extra rounds will be handled.
Should the intake form ask for the client’s budget?
It can, but frame it as a range or investment band and explain that it helps you recommend a realistic scope. Do not use budget as a substitute for understanding deliverables, authority, and deadlines.
Is a discovery call better than a form?
They do different jobs. A form captures consistent baseline facts; a call surfaces nuance and lets you test assumptions. For complex work, use a short form before the call, then confirm decisions in writing afterward.
Can I start work while final approval is still being decided?
Only on a clearly limited discovery or setup phase with its own deliverables and fee. Avoid beginning the full production scope until the client has confirmed who can approve it.

