To make a project request form in Notion, create a database for requests, add a Form view to it, and turn each property you need into a question: the problem, the sponsor, the deadline. Share the link with your team. Every submission becomes a page with a Status you can move from Requested to Approved or Declined.
What a project request form should ask
A project request form should collect enough to decide yes, no or later without a meeting. One university IT office says its form exists to give “a good understanding of what the project is and why it should be done”, which is a fair test for every question you add.
One university’s intake form collects the title, sponsor, requester, business driver, proposed dates, the problem and proposed solution, a priority level, risks, staffing needs and funding status. Another requires only goals, strategic alignment and a sponsor at the idea stage, and leaves resources, timeline and budget optional “if known”.
That second approach suits a small team: require little and leave the rest optional.
| Property | Notion type | On the form? |
|---|---|---|
| Project name | Title | Yes, required |
| Problem to solve | Text (long answer) | Yes, required |
| Outcome you want | Text (long answer) | Yes, required |
| Sponsor | Person or Text | Yes, required |
| Needed by | Date | Yes |
| Team | Select | Yes |
| Rough budget | Number | Optional |
| Requester | Person | Auto, via Respondent |
| Status | Status | No, set by reviewer |
| Owner | Person | No, set by reviewer |
The sponsor question is what separates a request from a wish. A sponsor, in one IT department’s definition, is a leader who can assign people or funds to the project and is responsible for its success. If nobody will put their name there, you have your answer.
How to build the project request form in Notion
A project request form in Notion is a Form view on a database, and Notion’s forms help page says all members on all plans can create one. Build it on desktop or the web; the form builder isn’t available on mobile.
- Create a database called Project Requests with the properties from the table.
- Select + next to the existing views and pick Form. You need Full access to the database.
- Choose which properties become questions. Leave Status and Owner out.
- Open each question’s menu. Mark it Required, add a Description, and turn on Long answer for the problem and outcome.
- Turn off Sync with property name where a question reads better than a column name. “What breaks if we don’t do this?” beats “Problem to solve”.
- In Form settings, edit the confirmation text so people know when they’ll hear back, and turn on the email copy of each submission.
A Date question fills a Date property, and a Select gives you clean values to group by later.
Who can submit, and how you see who asked
Requests from inside the company should use the Anyone at your workspace with link option under Who can fill out. With anonymous responses off, you know who sent each one. A form built from scratch gets a Respondent property; on an existing database, add a Created by property instead. The respondent guide explains the difference.
Workspace-only forms also let you set Access to submission. Pick “Can view” and requesters can open their own request to check its status instead of messaging you “any update?”.
Guests can only submit if they have access to the database. For clients or other outsiders, choose Anyone on the web with link and add name and email questions. A client intake form is the better pattern there.
One database or two for requests and projects
Use one database when you approve most requests, and two when you decline most of them. Top-ranking templates skip this choice, and it decides how tidy your project list stays.
One database: build the form on your Projects database and add a “Requested” status. Approved requests move to the next status. Notion’s own forms guide describes building a form from an existing database’s properties, and you can link more than one form to the same database.
Two databases: keep Project Requests separate, and add an automation on it. When Status is set to Approved, the Add page to action creates a page in Projects and fills its properties. Declined ideas never touch the project list.
My take: start with one database. Split only when declined requests outnumber live projects in your default view.
Assign and notify when a request arrives
Database automations can set an owner and alert a reviewer as each request lands. Click the lightning bolt at the top of the database, choose a trigger such as Page added or a property set to a value, then add actions. The automations help page lists Edit property, Send notification to, Send mail to and Send Slack notification to.
A useful pair:
- Route by team: when Team is set to Marketing, set Owner to the marketing lead.
- Close the loop: when Status is edited to Approved or Declined, notify the person in Requester.
The limitation: automations need a paid Notion plan. Free Plan users can build Slack notification automations and nothing else. On Free, rely on the email copy and a view filtered to Status “Requested”. The form automation guide and the post on assigning form responses go further.
A screening rule, and a worked example
A screening rule tells people when a request form is required at all. One university PMO asks for a request only when a project needs more than 80 hours of effort or a budget over $10,000, and promises a reply within 10 business days. Write your own threshold and reply time into the form’s description, and small asks stay in chat.
A sales lead wants a customer referral page. She opens the pinned form, names the project, writes the problem (“referrals arrive by email and get lost”), names her director as sponsor and picks a date. The page lands as Requested. The Team rule sets the web lead as Owner. At the weekly review, he marks it Approved, and she gets a notification.
When the native form runs short
Native Notion forms show every question to everyone unless you’re on Business or Enterprise, the only plans with conditional logic. A design request and a software request then share one long form.
Two workarounds: build a separate form per team on the same database, or use a form builder that writes to Notion. nDBForms reads your database properties and generates matching fields, and its show/hide rules on Pro work with any Notion plan. Pro also accepts file uploads up to 10 MB, saved to your Google Drive, for briefs or mockups. The conditional logic guide compares both routes.
FAQ
Does Notion have a project request form template?
You don’t need one. Add a Form view to a database and Notion creates a question for each property you pick, so your own Requests database becomes the template.
Can people outside my workspace submit a project request?
Yes. Set Who can fill out to Anyone on the web with link. People who don’t use Notion can then submit, but you lose the Respondent name, so ask for a name and email.
Should project requests go into my Projects database?
For a small team, yes: one database with a Requested status is less to maintain. Use a separate Requests database when most requests get declined or the form is public.
Can a Notion form assign a project request to someone automatically?
The form can’t, but a database automation can. Trigger on a property value and set the owner property. Automations other than Slack notifications need a paid plan.
Sources
- Forms, Notion Help Center
- Use forms to collect, organize and act on responses, Notion guide
- Database automations, Notion Help Center
- Project Intake Request, University of Delaware IT
- IT Project Request Process, Grand Valley State University
- Project Request Form, Fresno State PMO
- Submit a Project, UMBC DoIT PMO