Home / Writing

How Notion Relations for Clients and Projects Stop Retyping

A relation is not a text field

The Projects list looks fine until you group it by client and find the same company spelled three ways. You typed the name into each row because that was faster than learning Notion relations for clients and projects. Then the client rebrands, you update one row, and the other eleven keep the old spelling forever.

A relation is a property that points at a row in another database instead of holding text. Change the client's name once and every linked project shows the new name, because there is only one copy of it. That is the whole idea, and it is worth four minutes of setup.

What a two-way relation actually does

When you create a relation from Projects to Clients and turn on the two-way option, Notion adds a matching property to the Clients database automatically. Linking a project to a client puts that project inside the client's row. Nothing is copied. Deleting the project removes the cell, not the client.

The auto-created property is easy to miss because it appears on the other database while you are looking at the first one. It is also the property you will use later for rollups, so it deserves a real name rather than a default.

Converting an existing text column is not a migration project. Create the relation, link the rows one by one for an afternoon, then hide the text column. A workspace with a hundred projects takes an hour; the first ten take most of it, because you are deciding on the names.

Set the relation on the many side

Create the property on the database where rows are many, not on the database where rows are one. A client has many projects, so the Client relation belongs on Projects. A project has many tasks, so the Project relation belongs on Tasks. Point three invoices at one client and the relationship stays understandable, because the link lives where the many rows are.

If your version of Notion offers a limit so a project can point at only one client, use it. If it does not, the restriction is naming plus habit rather than a setting, and the habit is worth building either way.

The four Notion relations for clients and projects worth building

Create onPropertyPoints toReverse propertyCardinality
ProjectsClientClientsProjectsmany projects to one client
TasksProjectProjectsTasksmany tasks to one project
FinancesClientClientsInvoicesmany invoices to one client
ContentProjectProjectsContentmany posts to one project

Name the relation singular on the many side and plural on the one side: Client on Projects, Projects on Clients. This sounds like a naming detail until a formula breaks because someone renamed the property. Keep the names stable, because prop("Client") reads that exact string.

What linking buys you

The link itself does not calculate anything. It enables rollups, which do the counting and totaling that make the system worth opening. On Clients, a Projects rollup counts that client's projects. On Projects, two rollups named Tasks Total and Tasks Done feed the progress formula:

`` if(prop("Tasks Total") == 0, 0, prop("Tasks Done") / prop("Tasks Total")) ``

The flag a rollup needs

Notion rollups count or sum every linked row; they do not filter which rows count. To count only finished tasks, add a formula property on Tasks:

`` if(prop("Status") == "Done", 1, 0) ``

Call it Done, hide it once the rollup works, and let the Tasks Done rollup sum it. This 1/0 flag is the standard workaround and it also sets up a weighted version later if you decide task counts are too crude. The details are in rollups that compute progress and rate.

Three ways the links drift

  1. Two rows for one client. Someone creates a new client row instead of linking the existing one, and now the client has four projects under one row and two under another. Pick one row, relink the strays, and delete the duplicate. Do not merge by retyping the name.
  2. Text plus relation. A Client name text column is added "for convenience", gets filled during a busy week, and the relation stops being updated. Hide or delete the text column once the relation is reliable.
  3. Many-to-many by accident. A task linked to two projects counts in both progress numbers, so both projects look further along than they are. Split the task if the work is genuinely two pieces, and link each half once.

The pattern behind all three is the same: the relation is only trustworthy if it is the only place the fact is stored.

The five-table version

If you are starting from a workspace full of loose pages rather than three tidy databases, the five Notion databases for freelancers is the build order this article assumes. Relations are step two of five, and they are the step that decides whether the rest of the system works.

Do this today

  1. Open Projects, add the Client relation pointing at Clients, and link every existing row before you add a new one.
  2. Rename the auto-created reverse property to Projects and repeat the naming pattern on Tasks, Finances, and Content.
  3. Add the Done flag on Tasks and the progress formula on Projects, then open a client row and confirm the rollup numbers match what you expect.