Project brief forms
Turn a rough request into a workable brief with deliverables, timeline, dependencies, and an explicit list of what is out of scope.
Define the deliverable, not the effort
Ask what will actually be handed over: a document, a design file, a deployed site, a report. “Help with marketing” is not a deliverable. If the output is a set of items, add a field that lets the requester list them one by one.
Make the boundaries explicit
Include fields for deadline, dependencies, and what the requester will provide. Add an optional “What is explicitly not part of this?” question, because naming exclusions at intake removes the most common source of disagreement later.
Record the agreement
Send the submitted brief back for confirmation before work starts. Keep both the original answers and any agreed changes, since the brief is the reference point when a request grows beyond what was originally described.
Explore form editing in FormPico
Early preview · Form data is currently stored in your browser.
Explore the builder