Skip to content

How to collect and organize client requirements

By The Onbo team · Updated

Short answer

Collect requirements once, in a structured questionnaire sent after the agreement is accepted, rather than across emails and calls. Group the answers into goals, scope, content, constraints and approvals, keep them with the client's agreement and files, and turn them into a one-page brief your team works from.

Most requirement problems aren’t caused by clients changing their minds. They’re caused by requirements living in six places: an email thread, two sets of call notes, a voice message, a shared document and the account manager’s memory. When it’s time to build, someone has to reconstruct the brief, and something always slips through.

Why do client requirements get lost?

  • They arrive in pieces. A goal in the sales call, a deadline in an email, a “must have” in a voice note.
  • Nobody owns the brief. Sales assumes delivery will collect it; delivery assumes sales already did.
  • Questions get asked twice. The client answers in the proposal stage and again at kickoff, slightly differently.
  • Answers aren’t tied to the agreement. When scope is questioned later, nobody can show what was agreed.

The fix is to collect once, in one structure, at the right moment.

When should you collect requirements?

Split collection into two moments:

  1. Before the proposal: a short intake of three to five questions, enough to scope and price the work.
  2. After the agreement and deposit: the full questionnaire. The client is committed, and you can ask for real detail.

Asking for detailed requirements before the client has signed tends to produce rushed answers. Asking after kickoff means the first weeks are spent waiting.

How do you structure the questions?

Group questions by the decision each one informs. A structure that works for most service projects:

Section What you learn Example questions
Goals Why the project exists and what success looks like What should change once this is done? How will you measure it?
Scope What’s included and what isn’t Which deliverables do you expect? Is anything out of scope?
Audience Who the work is for Who are your main customers? What do they need to know?
Content and assets What the client supplies What copy, images and files will you provide, and when?
Constraints Limits to work within Deadlines, budget, technical systems, legal requirements
Approvals Who decides Who gives feedback? Who has the final say?

Mark nice-to-know questions as optional. Let clients answer one section at a time, save as they go and say “not sure yet”. Those answers become your kickoff agenda.

How do you organize the answers?

Keep everything for one client together: the accepted agreement, payment status, questionnaire answers and files. Then turn the answers into a one-page brief:

  1. One-sentence summary of the project.
  2. Goals and success measures, in the client’s words.
  3. Deliverables and scope, matching the agreement.
  4. Inputs: content and assets, who supplies them and by when.
  5. Constraints: dates, budget limits, systems.
  6. Decision makers and how feedback works.
  7. Open questions for the kickoff call.

For example, a five-person marketing agency might keep the full answers in the client’s record but share only the one-page brief in the project channel, so designers and writers work from the same version.

Who should own the brief?

Give one named person responsibility for the brief from signature to kickoff. In a small agency that’s often the project lead; for a freelancer, it’s you. Their job is simple: make sure the questionnaire goes out after signing, chase only through the agreed reminders, write the one-page brief and confirm it with the client before work starts. When the project moves to delivery, the brief moves with it, and any later change is added to it rather than to a new email thread. A single owner removes the “I thought you asked them” gap between sales and delivery.

A requirements checklist

  • Short intake form used before the proposal
  • Full questionnaire sent after the agreement and deposit
  • Questions grouped by goals, scope, audience, content, constraints and approvals
  • Optional questions clearly marked
  • Answers saved as the client types
  • “Not sure yet” answers collected as kickoff topics
  • Answers stored with the agreement and files for that client
  • One-page brief written for the team
  • Brief checked against the agreed scope
  • Changes after kickoff recorded against the original brief

For a ready-made set of website questions, see the web design client questionnaire. If files are the slow part, our guide on how to stop chasing clients for files covers that step.

For agencies, the brief is one step in a wider agency project kickoff workflow.

Where Onbo fits

Onbo collects requirements at the right moment by design: your questionnaire unlocks after the client has accepted the agreement and paid. Clients answer one section at a time with autosave, and the answers sit with the agreement, invoices and files in the client’s record. When onboarding finishes, Onbo produces a Markdown hand-off brief you can share with your team or paste into the tools you already use.

Questions

How can agencies collect client requirements?

Send a structured questionnaire after the agreement is accepted, grouped by topic, with autosave so clients can finish it in more than one sitting. Use the kickoff call for open questions rather than for basic information.

What should a requirements brief include?

Goals and success measures, scope and deliverables, content and assets, constraints such as deadlines and budget, and who approves the work.

What if requirements change after kickoff?

Record the change against the original brief and agree in writing whether it changes the scope, timeline or price.

Start your next client relationship with everything in place.

Collect the first steps in one link. Try Onbo free for 30 days, no card required.

Start free