A project brief form is the intake step for work someone wants done: what the project is for, who it is aimed at, what it has to include, what it can cost and when it has to land. Its job is to stop the same nine questions being asked across nine emails.
Not a stock template. Build it in a few minutes from a blank form, or describe it and let AI draft the questions on a paid plan.
The reason briefs come back thin is that a blank document is intimidating and a long form is worse. Ask a short common set, then branch on the project type so a website brief and a print brief are genuinely different forms rather than one form with everything on it.
A starting point, not a rulebook: every question below is a real Questionful question type, and all of them are editable once the form is in your account.
| Question | Question type |
|---|---|
| What is the project, in one sentence? Forces a summary before the detail | Short answer |
| What has to be true for this to have worked? The objective, stated as an outcome rather than a deliverable | Paragraph |
| What type of project is this? Website, brand, campaign, content, development, other, the question the form branches on | Dropdown |
| Who is it for? Audience, in their words | Paragraph |
| What is in scope, and what is explicitly out? The two halves that prevent the argument later | Paragraph |
| What is the budget band? Bands rather than a number, people answer a band and refuse a number | Multiple choice |
| When does it have to be live? Ask for the fixed date, then ask what is driving it | Date |
| What is driving that date? A launch, an event, a contract. This is what tells you whether the date moves | Short answer |
| Who signs it off? One name. The most valuable question on the form | Short answer |
| Reference material or existing assets Paid plans only, 25 MB per file, 2 GB of storage on Standard | File upload |
| Anything we should know that we have not asked? | Paragraph |
Section one asks the questions every project needs: summary, objective, budget band, date, sign-off. Then branch on the project type dropdown so each kind of work gets its own section of specific questions.
Budget as multiple choice bands gets answered where an open number does not. The date question is a real date picker, so what arrives is a date rather than "end of Q3ish".
A file upload question collects logos, brand guidelines and existing copy with the submission instead of in a follow-up email. Uploads need a paid plan: 25 MB per file, 2 GB of storage on Standard and 5 GB on Teams.
Connect Google Drive and each submission is filed to a folder as a PDF, which is the form of a brief people actually want to read and attach to a proposal.
Send the response to Zapier, Make, or your own endpoint as JSON to open a task or a deal automatically. Add a signing secret and each delivery carries an HMAC-SHA256 signature you can verify. Delivery is attempted twice, inline with the submission, and is not retried later, so treat the emailed notification as the backstop.
A one-sentence summary, the objective as an outcome, the audience, what is in and out of scope, a budget band, the fixed date and what is driving it, the person who signs off, and reference files. Then whatever your particular type of project needs, on a branch of its own.
Yes. Ask the project type as a dropdown or multiple choice and route each option to its own section. Branching is set per answer choice, so a website brief and a print brief share the common section and nothing else.
Yes, on a paid plan. A file upload question takes up to 25 MB per file, with 2 GB of storage on Standard and 5 GB on Teams. The free plan does not accept respondent uploads.
Yes. Connect Google Drive and every response is filed to a folder as a PDF, one per submission. You can also export all responses to CSV.
This page is a guide rather than a stock template, so the CTA opens a blank form, or the AI generator on a paid plan. The free plan gives unlimited forms and 100 responses a month with no card, though file uploads need Standard or Teams.
Route each answer choice to its own section, so people only see what applies.
Feature19 types, including specialist ones most builders skip.
FeatureEvery response POSTed as JSON to any endpoint, signed if you want it.
TemplateEverything you need before the first call, asked once.
TemplateStructured intake for internal or client work, routed by request type.
TemplateAsk the budget, timeline, and fit questions before the first call.
Use caseTurn recurring internal requests (time off, IT tickets, purchase approvals) into structured forms with a real audit trail.
Use caseQualify enquiries while they are being filled in, and hand every submission straight to the tool your sales process already runs on.
Unlimited forms and 100 responses a month, free. Paid plans from €19.
No credit card required.
Choose which cookies you allow. Strictly necessary cookies are always on because the site cannot function without them.
Required for core features such as security, load balancing and remembering this cookie choice. These set no tracking cookies.
Google Analytics, used to understand traffic and improve the site. Loaded only if you allow it.
