Prompts / Productivity & Planning

Claude prompts for Notion

This prompt produces a usable Notion workspace plan, not a vague list of pages. Use it when you need a system for projects, notes, clients, content, or personal planning.

PromptOpen ChatGPTOpen Claude
I want you to design a Notion workspace for [WORKFLOW OR GOAL]. It will be used by [USERS], who currently work with [CURRENT TOOLS OR PROCESS]. My non-negotiable constraints are [CONSTRAINTS], and the information I need to track is [KEY INFORMATION].

First, identify the smallest workable system. Do not create separate databases when a relation, select property, filtered view, or template would do the job.

Produce the following:
1. A workspace map showing the home page and every database or major page.
2. A database specification for each database: purpose, properties, property type, required fields, relations, rollups, formulas, and one example record. Use names a non-technical user can understand.
3. The exact views to create, including filter, sort, grouping, and when each view is used. Include an Inbox or capture path if information arrives before it is categorized.
4. Templates for recurring records, with the fields or checklist each template should contain.
5. A weekly operating routine: what gets captured, reviewed, archived, and surfaced.
6. Setup instructions in the order I should build it.

Design around actual decisions, not decoration. Avoid redundant status fields, formula-heavy dashboards that duplicate a view, and relations without a clear reporting or workflow purpose. If dates matter, distinguish a hard deadline from a planned date. If tasks are involved, show how a task connects to its project or area without requiring duplicate entry.

Before answering, check that every database supports a named workflow and that every requested piece of information has one clear home. Flag any feature Notion cannot do natively or any assumption you made. Ask up to 3 clarifying questions only if a required input is missing.

Fill in

PlaceholderWhat to enterExample
[WORKFLOW OR GOAL]Describe the work or life process the Notion system should support.Run a freelance design practice from lead intake through final invoice
[USERS]State who will use the workspace and their roles.One designer and a part-time bookkeeper who only needs invoice status
[CURRENT TOOLS OR PROCESS]Describe how the work is currently tracked, including spreadsheets, notes, or apps.Leads in Gmail, project notes in Apple Notes, and invoices in a spreadsheet
[CONSTRAINTS]List limits such as time available, required tools, privacy needs, or team size.Buildable in one afternoon; no paid integrations; client notes must stay private
[KEY INFORMATION]List the records, fields, and decisions the system must track.Leads, clients, proposals, projects, tasks, meeting notes, invoices, payment dates

How to use

  1. Replace each bracket with details from your current process, including what regularly falls through the cracks.
  2. Paste the prompt into Claude and save its database specification before building anything.
  3. Check that each property has a real use and that a task is not entered in two places.
  4. Follow up with: “Turn the project database specification into exact Notion property names and types I can create manually.”

Variations

Project tracker

Use when you only need a project-and-task system.

Variation
Design a lean Notion project tracker for [TEAM OR PERSON] managing [PROJECT TYPES]. We need to see [REPORTING NEEDS] and currently lose track of [FAILURE POINT]. Specify one Projects database and, only if necessary, one Tasks database. List exact properties, relations, statuses, views, and templates. Include an active-work view, an overdue view, and an archive rule. Do not add a dashboard unless it answers a stated decision. Flag fields that would create duplicate maintenance. Ask up to 3 questions only if required information is absent.

Content calendar

Use when planning, producing, and publishing content.

Variation
Build a Notion content operating system for [CHANNELS] serving [AUDIENCE]. Our publishing cadence is [CADENCE], and content moves through [WORKFLOW STAGES]. Define the content database properties, status definitions, editorial calendar views, production checklist template, and a way to connect one idea to multiple channel adaptations without copying records. Include ownership, publish date, source material, approval status, and performance-review fields only where they drive a decision. Check that no status overlaps another. Ask up to 3 questions only if needed.

Personal knowledge hub

Use when organizing notes, sources, and ideas for later retrieval.

Variation
Design a personal Notion knowledge hub for [TOPICS OR PURPOSE]. I capture material from [SOURCES] and want to retrieve it when [USE CASES]. Specify the smallest set of databases or pages, exact metadata properties, capture templates, saved views, and a weekly review routine. Separate fleeting notes from durable reference material only if that changes how I use them. Include a method for linking a source to my own takeaway and next action. Do not recommend elaborate tagging systems without a retrieval use. Ask up to 3 questions only if inputs are missing.

Tips

  • Start with the decisions you need to make each week, then add only the fields needed to make them.
  • Use a select property for a controlled category and a relation only when records genuinely need to connect.
  • Keep status definitions mutually exclusive; “Waiting,” “In progress,” and “Blocked” should each trigger a different action.
  • Build with ten real records before adding formulas, charts, or a polished home page.

FAQ

Can Claude create the Notion workspace for me?

It can design the structure and give step-by-step setup instructions, but you will normally create the databases and views in Notion yourself.

Should every Notion system use linked databases?

No. Linked views help when the same records need different working contexts; they add little value for a small, single-purpose list.

How many properties should a Notion database have?

Use the fewest that support a real decision, filter, report, or template. Fields that are rarely filled in usually make the system harder to maintain.

Related prompts

All Productivity & Planning prompts →

Get a few prompts like this every week

Something Big is a free AI newsletter read by 70,000+ professionals. About three short emails a week with prompts and tools that work, plus what changed in AI and what to do about it.