Team form
Service, scope and agreed feeYour team supplies the project details.
A form collects the details your document needs. Connect each question to the wording, use conditions to skip irrelevant questions, and give different people their own part to complete.
Open the practical guideLet’s make
it yours.
A few details to get things growing.
A service agreement may need information from both your team and the client. Separate forms keep those responsibilities clear.
Your team supplies the project details.
The client supplies their own information.
Shown when ongoing support is selected.
One answer supplies each connected occurrence.
Illustrative setup. You supply your own wording, questions and rules.
Open a step for the details, or follow the full guide alongside your builder.
Follow the full guideList the details that genuinely change between clients. Turn each missing detail into a clear question.
Use descriptive labels and short help text. Choose a suitable field type and make an answer required only when you need it.
Use pages for longer forms. Add headings and context so people understand what you need and why. Use conditions for questions that apply to only some answers.
Try realistic answers, including long names and optional fields. Preview the form at a narrow width and check the document those answers produce.
Yes. Create separate forms for different people or stages and assign recipients during request preparation. Keep dependencies in order so later conditions can use answers already collected.
No. Form colours, typography, corners and progress display are separate from the document’s printed layout. Preview both experiences.
Builder test answers are for checking the form and preview. They do not submit a real client request. Use the cloud workspace when you are ready to prepare and send one.
Start with a document you already use.
Create your free workspace No card needed. A little room to get growing.