Notion AI Templates: Reusable Prompts for Everyday Work

Notion AI templates are reusable instructions that produce a consistent output when you run them on similar tasks. A meeting note template, for example, always asks for the same sections: decisions, actions, open questions. A project brief template always asks Notion AI to confirm scope before it writes a summary. A tool like fenbs stores your team's tested templates outside Notion so any connected assistant can access them, not just the person who saved the original page.

Each template below uses bracketed placeholders for the details that change between uses. Fill them in before you run the prompt. The brackets are also a useful reminder to anyone picking up the template for the first time about which inputs it needs.

Meeting note template

Summarize the notes or transcript on this page as a formal meeting record.
Include these sections:
- Date: [date of meeting]
- Attendees: [list from the notes]
- Decisions made: numbered list, one decision per line
- Actions assigned: person, action, due date
- Open questions: anything raised but not resolved
Use neutral language. Include only what is in the notes. Do not infer decisions that were not recorded.

This template works well when someone has taken rough notes during a call and wants a clean record for the project log. The instruction to include only what is in the notes prevents Notion AI from adding context it has invented, which is common when notes are sparse.

If your meeting covered multiple topics, add a line to the template: "Group decisions and actions by topic." Without it, Notion AI may produce a flat list that mixes items from unrelated agenda points.

Project brief template

Write a project brief using the notes on this page.
Include these sections:
1. Goal: one sentence describing what this project will achieve
2. Scope: what is included and what is not
3. Key decisions made so far: numbered list
4. Open questions: what still needs to be resolved before work starts
5. Next steps: the first two or three actions, each with an owner if known
Keep the output to one page. Avoid jargon. Flag any section where the notes do not give enough information.

The instruction to flag gaps is important. Without it, Notion AI will fill in missing sections with plausible-sounding but invented content. When it flags a gap instead, you know exactly what still needs a decision before the document can be shared.

The scope section is worth spending time on when you first run this template. A project scope that names what is not included is more useful than one that only names what is included. "This covers the sign-in flow, not the account settings page" is harder to misread than "This covers the sign-in flow."

Client update template

Write a client update for [project name] using the task notes on this page.
Audience: [client name or role].
Include:
- What was completed since [last update date]
- What is in progress now
- What decisions or approvals are needed from the client
- What comes next
Keep the update under 200 words. Use plain language. Do not include internal notes or cost details.

The instruction to exclude internal notes matters for teams that keep candid working notes alongside client-facing summaries on the same Notion page. Be specific about what to leave out when your page holds both kinds of content.

When project progress and decisions live in fenbs, ask your AI to read the current context before running this template. The latest task states and Where we left off note give it more accurate inputs than a Notion page that may not have been updated since last week.

Weekly review template

Write a weekly review using the tasks and notes on this page.
Sections:
- Completed this week: 3-5 bullet points
- Still in progress: 2-3 bullet points with current status
- Blocked or waiting: what is stuck and who needs to unblock it
- Priority for next week: the single most important thing
- Lessons: one thing that went well and one thing to do differently
Keep each bullet point to one sentence. Use only the information on this page.

A weekly review template makes a useful addition to a shared prompt library because different people on a team often write reviews in different formats, making them hard to compare. A shared template creates a consistent record without requiring everyone to coordinate.

The "lessons" section at the end is easy to skip when the week was uneventful, but it is most useful on those weeks. A small note about what to do differently next time, written when the context is fresh, is more accurate than a retrospective written a month later.

Adapting templates for your team

Templates work best when they match the decisions your team has already made about how to communicate. If your client updates always include a risk section, add it to the template. If your meeting notes never include attendee titles, remove that field. A template that fits your team's habits is one people will actually use.

When you change a template, keep a brief note about what you changed and why. "Added the risk section after the October project review" tells the next person who picks up the template why it looks the way it does and whether the reason still applies to their situation.

Test a template on three or four real tasks before sharing it as the team version. Output that looks good on the first run may produce worse results on different inputs. Testing across a variety of examples finds the edge cases before they become problems in production use.

Keeping templates current

• Test a template on three or four real tasks before saving it as the team version. A template that works on one document may need adjustments for others.
• Version your templates. When you change a template, note what changed and why. Knowing that "added the scope section after the March launch confusion" helps the next person understand why the template is shaped the way it is.
• Review templates every few months. A template written for a quarterly report may not fit a monthly one. Short reviews catch drift before it causes problems.
• Keep templates specific to one use case. A combined "write everything" template is harder to maintain and produces less consistent output than separate templates for separate tasks.

For a comparison of Notion AI with connecting Notion over MCP, Notion MCP vs Notion AI explains when each approach is the better fit. For project management prompts that work across tools, prompts for project management AI has a focused set.

How to do this with fenbs

Once you have tested these templates and found the versions that work for your team, move them to a shared record so they are available to every connected assistant.

1. Create a free account. Use a personal kanban board first to test the workflow. Add a team board when colleagues need access.
2. Open your project in fenbs and go to Skills and prompts. Add each template as its own entry with a short name and a note on what task it is for.
3. Connect your AI apps at Integrations. Follow the MCP setup guide for the app you use. Once connected, the assistant can list and read your templates before it starts a task.
4. Update the shared version when you improve a template. Edit the entry in fenbs so everyone gets the updated version automatically, without needing to track down old Notion pages.