---
name: notion-workspace-database-designer
description: "Specifies a Notion database you can build in under an hour: exact property types, saved views with filters, relations, one automation and the properties teams regret skipping. Use when a Notion database needs designing with the right properties, views and relations for how a team works. Do not use for general Notion page layout or migrating data out of another tool. Related topics: Productivity, Notion, Planning."
---

# Notion Workspace Database Designer

Specifies a Notion database you can build in under an hour: exact property types, saved views with filters, relations, one automation and the properties teams regret skipping.

## When to use

Use this skill when a Notion database needs designing with the right properties, views and relations for how a team works. Do not use it for general Notion page layout or migrating data out of another tool.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Name the failures in the current process and decide what each property must fix.
3. List every property with its exact Notion type, fitting the count to the volume and users.
4. Define three or four views with filters, sorts and grouping.
5. Describe relations and rollups when they are on and justify each.
6. Add one automation or template button and finish with the two properties teams regret skipping.

## Inputs

- **What the database tracks** (free text, e.g. "client projects or bug reports")
- **Who uses it** (choose one: Just me, A small team, A whole company, External clients too)
- **Items added per week** (choose one: Under 10, 10 to 50, 50 to 200, 200+)
- **Tools it must work with** (choose any: Slack, Google Calendar, GitHub, Jira, Figma, Nothing else)
- **What goes wrong today** (longer free text)
- **Include relation and rollup properties** (choose one: Yes, No)

## Output

A property list with exact Notion types, three or four saved views with filter, sort and group settings, any relation setup, one automation, and two properties to add on day one.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Notion Workspace Database Designer

Design a Notion database setup I can build in under an hour.

- What the database tracks: {{What the database tracks}}
- Who uses it: {{Who uses it}}
- Items added per week: {{Items added per week}}
- Tools it must work with: {{Tools it must work with}}
- What goes wrong today: {{What goes wrong today}}
- Include relation and rollup properties: {{Include relation and rollup properties}}

Start from the pain described and keep only properties that fix it. List each property with its exact Notion type (Select, Multi-select, Person, Date, Relation, Rollup, Formula and so on), and fit the number of properties to the item volume and user group. Define three or four saved views with their filters, sorts and grouping. If relations are on, set out each relation and what the rollup calculates. Add one automation or template button that removes the most repeated work, and say how it connects to the tools named.

End with the two properties most teams add later and wish they had on day one.

## Pitfalls

- Creating dozens of properties that nobody fills in.
- Using a Text property where a Select would make filtering reliable.
- Relations and rollups for a single-user list that never needs them.
