Freelance Client Intake Form: Questions to Ask Before Every Project

Most project scope disputes trace back to a question no one asked before the work started. The client assumed the budget included revisions; you assumed the deadline was flexible; neither of you confirmed who had final sign-off. A client intake form closes those gaps before they become problems.

The goal is not to quiz prospects — it is to gather the information you need to write an accurate proposal and scope, and to spot red flags before you invest time in a discovery call. A good form takes the client ten minutes to fill out and takes you ten minutes to build.

The complete intake form

Project scope

• What is the project? Describe it in a few sentences.
• What problem are you trying to solve, or what does success look like once this is done?
• Do you have existing assets — brand guidelines, previous versions, reference examples — I should review?
• Is this a standalone project or part of a larger ongoing effort?
• Has this project been attempted before, either internally or with another freelancer?

Timeline and deadlines

• When do you need the final deliverable?
• Is that deadline fixed (tied to a launch or event) or flexible?
• Are there intermediate milestones — an internal review, a presentation date, a soft launch — I should plan around?
• How quickly can you typically turn around feedback on a draft?

Budget

• Do you have a budget in mind for this project? Even a ballpark helps me scope something realistic rather than miss your range entirely.
• Is that budget fixed, or is there flexibility if the scope requires it?
• Have you hired someone for something similar before? If so, roughly what did you pay?

Approvals and communication

• Who is my main point of contact?
• Who else has input or sign-off authority — a manager, a partner, a legal team, a board?
• How do you prefer to communicate: email, Slack, video calls, or a mix?
• How often would you like check-ins or progress updates?
• Are there known preferences or constraints I should be aware of — things previous collaborators ran into?

Deliverables and format

• What file formats do you need for final delivery?
• Are there technical constraints — platform, software, brand standards — I need to work within?
• How many rounds of revisions are you expecting?

Add one project-type question that reveals whether the engagement is scoped realistically: for design work, ask whether copy is included in scope; for development, whether designs exist; for writing, whether you are expected to define the topic and angle; for consulting, what a successful outcome looks like in six months. These questions surface hidden scope before you quote.

How to send it and what to do with the answers

• A Google Form or Typeform is cleaner than questions pasted into an email body. Build it once and reuse it on every project.
• Keep it to fifteen questions maximum. Longer forms get abandoned.
• Collect responses before your first call, not instead of it. Read the answers first so your questions during the call are sharper.
• If a prospect skips the form and pushes directly to a call, ask the six most important questions verbally — then request the completed form afterward. Written answers on file before a project starts give you a reference point if scope shifts later.
• Save every completed form. When a client says the brief changed, you can point back to what they described on day one.

A client intake form is not a screening device — it is a project insurance policy. The ten minutes it takes to fill out is worth several hours of mid-project clarification later.