Who it is for
- Agencies qualifying new client projects
- Consultants collecting scope before discovery calls
- Service teams routing requests to the right workspace
Form template
Client intake form template
Collect client contact details, project goals, budget, timeline, qualification notes, and any private files required before the first call.
Fields included
- Client name and contact details
- Company, website, and project type
- Goals, timeline, budget range, and preferred contact method
- Conditional private brief or asset attachments, existing asset inventory, and stakeholder notes
Conditional logic examples
- If project type is Website, show launch date and content readiness fields.
- If budget is above a threshold, require procurement or approval notes.
- If preferred contact is Video call, show availability windows.
Validation and review workflow
- Require email and project type before submission.
- Validate budget range and timeline fields before review.
- Require a private brief attachment when the client says assets are ready and storage is available for the team's tier.
Problem
The workflow problem
A useful template has to capture the right details, guide respondents away from irrelevant fields, and leave reviewers with enough context to make the next decision.
How the KinoForms template is structured
The template outline combines field groups, conditional logic examples, validation checks, review handoff notes, and related pages so teams can adapt it without starting from a blank form.
- Client name and contact details
- Company, website, and project type
- Goals, timeline, budget range, and preferred contact method
- Conditional private brief or asset attachments, existing asset inventory, and stakeholder notes
Use cases
Where this page fits
These examples keep the page focused on narrow form-workflow intent instead of broad form-builder copy.
Agencies qualifying new client projects
Consultants collecting scope before discovery calls
Service teams routing requests to the right workspace
Workflow steps
How the workflow moves
Use KinoForms to adapt the fields, logic, validation, access, and review steps for the workspace that owns this process.
1
Collect the common fields first
Start with identity, contact, request, or eligibility fields that every respondent should complete.
2
Branch into conditional sections
Show extra fields only when an answer makes them relevant, such as approvals, availability, or budget detail.
3
Validate before review
Use required fields, option constraints, dates, and review-ready labels before the response reaches the team.
Concrete examples
What this looks like in a form
Discovery-ready intake
A client can submit requirements and budget context so the first call starts with concrete scope.
Qualified request routing
Conditional budget and timeline fields help teams route high-priority or low-fit requests before review.
Asset-readiness branch
If a client says assets are ready, the template can request a private brief attachment and collect stakeholder notes before the call.
Related pages
Follow the connected form workflow
form builder
Build the intake fields, sections, and validation rules.
conditional logic form builder
Branch project details based on service type, budget, and timeline.
controlled form submissions
Review submitted client details in the owning workspace.
form submission validation
Validate required intake details before the first-call review queue.
FAQ
Common questions
What fields should a client intake form include?
Start with contact details, project type, goals, timeline, budget, an asset inventory, and stakeholder notes.
Where should conditional logic appear in client intake?
Use logic around project type, budget threshold, preferred contact method, asset readiness, and timeline urgency.
Can respondents upload client files during early access?
Yes, when private attachment storage is configured and the team tier is allowed to use it. The Free tier includes no file storage.
Next step
Build this template as a controlled workflow
Use KinoForms to adapt the fields, logic, validation, access, and review steps for the workspace that owns this process.