How do I make a meeting agenda request form in Notion?

Build a Notion meeting agenda request form: an agenda items database, a form view with a meeting picker, and a review view that sorts topics before a call.

Nookesh KarriNovember 16, 20267 min read
Light cover card with the title 'How do I make a meeting agenda request form in Notion?' in dark text and a blue accent bar

To make a meeting agenda request form in Notion, create an Agenda items database with a topic, details, time needed and a status, link it to a Meetings database with a relation, and add a Form view. People pick the meeting, describe their topic, and each request lands on that meeting’s page. Before the call, a filtered view shows what to discuss and what to park.

Setup takes about fifteen minutes. The part most templates skip is the link to a specific meeting, and that’s what keeps topics from piling up in one long list.

What a Notion meeting agenda request form should ask

A Notion meeting agenda request form should ask for what the organizer needs to decide whether a topic makes the cut: which meeting, the topic phrased as a question, why it matters, and how long it needs. Anything more slows people down and they go back to dropping topics in chat.

Phrasing matters. One guide to agendas says to write agenda items as questions and give each one a timeframe. “Should we move the launch to March?” is easier to plan around than “Launch”.

Notion’s forms help page says a question’s type is the equivalent of a property type. So plan the database first:

Form question Question type Property in the database
Which meeting? Relation Relation to Meetings
Topic, as a question Short text Title
Why it matters / what you need Long text Text
Time needed Multiple choice Select (Quick, Short, Long)
Type Multiple choice Select (Decision, Discussion, FYI)
Pre-read link URL URL

The Type question helps the organizer more than any other. FYI items can often go in a written update instead of taking meeting time.

Step 1: create the Meetings and Agenda items databases

Two databases keep requests attached to the right call. A Meetings database holds one page per meeting, and an Agenda items database holds one page per requested topic.

  1. Create a Meetings database with a Name, a Date and a Type (Weekly team, 1:1, Board).
  2. Create an Agenda items database with the properties from the table above.
  3. In Agenda items, add a Relation property and pick Meetings. Notion’s relations help page says relations are one-way by default, so switch on Show on to make it two-way. Every meeting page then lists its agenda items.
  4. Add the properties only the organizer fills in: Status (Requested, On agenda, Parked, Done), Created by, and Owner as a Person property for follow-up.

Keep Status off the form. People shouldn’t put their own topic on the agenda.

Step 2: add the form view and share it

The form view is what your team fills in. In the Agenda items database, select + next to your views, choose Form, and add a question for each property in the table. You need Full access to the database, and Notion says forms can only be built on desktop and web, not on your phone.

For the meeting question, set the relation question to allow one selection. The forms page says relation questions can limit the number of selections per response, which stops someone from tagging every meeting at once.

Then pick who can fill it out:

  • Anyone at your workspace with link: members submit, and with Anonymous responses off their names are saved in Created by.
  • Anyone on the web with link: clients or board members without Notion can submit, but responses are automatically anonymous. Add a name question.
  • No access closes the form.

For an internal team meeting, use the workspace option. Set Access to submission to Can view so each person can open their request and see whether it made the agenda.

Step 3: add a cutoff and a review view

A review view turns raw requests into an agenda. Ask in the form description for topics by a set time, then review only what came in before then.

Notion’s views page says filters and sorts can be saved for everyone, and you can group by a property and hide empty groups. Build a view called Next meeting:

  1. Filter: Status is Requested, and the Meetings relation contains the next meeting.
  2. Group by Type, so decisions sit at the top.
  3. Sort by Time needed, ascending, so quick items go first.

Go through the list and move each item to On agenda or Parked. Parked items keep their page and their history, so you can move them to a later meeting by changing the relation.

To see how full a meeting is, add a rollup to Meetings with Count all on the agenda items. If the count is high for a short call, something has to wait.

Step 4: send the agenda before the meeting

The agenda is only useful if people see it early. A UC Berkeley meeting guide says to send the agenda to all participants 24-48 hours in advance. For a weekly call, set the request cutoff at least a day earlier.

On each meeting page, add a linked view of Agenda items filtered to Status is On agenda. Share that page link in the invite or in your team channel. The same guide says to record action items with an owner and a deadline, so add Owner and Due date to Agenda items and fill them in during the call.

If you want to know the moment a topic arrives, the form’s submit screen can email you a copy of each submission. Notion’s database automations page also lists a Page added trigger with a Slack action, though most automations need a paid plan.

Example: a weekly team meeting

Here’s how it runs for a five-person product team that meets on Tuesdays.

  • The lead creates next Tuesday’s page in Meetings from a template on Thursday.
  • Midweek, a designer submits “Should we drop the dark mode toggle from v2?”, picks Tuesday’s meeting, chooses Decision and Short, and links a Figma file.
  • Friday afternoon, the lead opens Next meeting, puts four items on the agenda and parks two FYIs for the weekly written update.
  • The meeting page with its linked agenda view goes out in Slack on Monday.

Where a native Notion agenda form falls short

The native form covers most internal meetings, but it has gaps.

  • Branching, such as asking for a decision deadline only when Type is Decision, needs conditional logic. Notion offers it only on Business and Enterprise plans, and only on multiple choice questions.
  • Outside contributors on the web link are anonymous and can’t track their own requests.
  • The relation question shows every page in Meetings, including old ones. Archive past meetings into a separate database or name pages with the date so people pick the right one.

My take: for a weekly team call, the native form plus one review view is enough. Reach for more only when outsiders, like clients or a board, need to send topics with their names attached.

If you need named submissions from people outside Notion or branching on a cheaper plan, nDBForms writes each response to your Notion database and has logic rules on Pro. For related set-ups, see how to create a form in Notion, Notion form automation, and Slack notifications for Notion forms.

FAQ

Can people outside my workspace submit agenda items?

Yes, if you share the form with Anyone on the web with link. Those responses are automatically anonymous, so add a short text question for the person’s name.

How do I attach an agenda item to a specific meeting?

Add a relation property from the agenda items database to a Meetings database and include it as a question on the form. Limit it to one selection so each topic lands on one meeting.

Can I get a notification when someone adds an agenda topic?

Yes. The form’s submit screen can email you a copy of each submission, and form automations can post to Slack.

Can I edit the agenda request form on my phone?

No. Notion says creating and customizing forms works only on desktop and web, so build it on a computer.

Sources