Project intake form
A project intake form is the formal entry point for new work requests — it separates idea from commitment by documenting the requester, scope, deadline and priority before a project manager schedules or plans. Use this when a request comes in via email, Slack, or conversation.
The form beside this text is live. Fill it in and submit it — it validates exactly as it would for a real respondent, and saves nothing.
Deadline is a required date field, not a text field
A date input prevents ambiguous formats like "end of Q4" or "ASAP" and lets you sort requests by actual due date.
Priority is a dropdown, not free text
Standardizing priority to fixed options (low/medium/high/urgent) makes it easier to sort and triage a backlog.
This one uses file uploads, which is a paid feature — you can build and edit it on the free plan, but saving it needs an upgrade.
No card required.
Project Intake Form
Live previewHow to build this form
8 steps in the editor.
- Add a text field for the requester's name and an email field.
- Add a text field for the department, team, or company making the request.
- Add a text field for the project name.
- Add a required textarea for the project description (what is the business goal?).
- Add a required date field for the desired deadline.
- Add a required dropdown for priority: low, medium, high, urgent.
- Add an optional text field for budget range or comments.
- Add an optional file upload for relevant documents, requirements or brand assets.
Fields in this form
9 fields, using 6 of the 19 field types available.
| Question | Field type | Required |
|---|---|---|
| Your name | Short text | Yes |
| Your email address | Yes | |
| Department, team, or company | Short text | Optional |
| Project name | Short text | Yes |
| Project description | Long text | Yes |
| Desired deadline | Date | Yes |
| Priority | Dropdown | Yes |
| Budget range or comments (optional) | Short text | Optional |
| Attach files (optional) | File upload | Optional |
What goes wrong with this form
Specific to a project intake form, not general advice about forms.
Making the budget field required when it is often unknown
Leave budget optional; scoping should inform budget, not the reverse. A required budget field will just collect guesses.
Asking for too much detail before the project is scoped
Keep intake simple: name, description, deadline, priority. Deep technical requirements or resource lists belong in the scope, not intake.
Skipping the file upload option
Many requests come with supporting docs — requirements, wireframes, brand guidelines. A file upload keeps everything in one place.
Questions about this form
What is the difference between project intake and client onboarding?
Project intake captures a new request before work is scoped — it's about what needs to be done. Client onboarding gathers details after a client has signed on — it's about who they are and what they want.
Who should fill out this form?
Anyone requesting new work — an internal stakeholder, a client, a department manager, or a sales rep on behalf of a client.
What happens after the form is submitted?
You export the responses and assign the project to a PM for scoping and scheduling. The form itself does not route requests or create a ticket.
This one uses file uploads, which is a paid feature — you can build and edit it on the free plan, but saving it needs an upgrade.