A project can look complete in your project list while being absent from the client’s workspace. One possible reason is simple: its Client relation is empty.
This guide builds an assignment review queue. It also keeps internal projects from being mistaken for errors. Use your existing Projects and Clients databases rather than copying records into a new tracker.
1. Check what your Client property actually stores
Open a project and inspect Client. This recipe requires a Relation property connected to your Clients database. A text label containing a client’s name is not the same connection.
If you have not built that connection, start with how to connect two databases. Preserve any existing client-name text while you establish and check the relation; it can help identify the correct client.
2. Create an empty-relation view
- Open the original Projects database.
- Add a Table view named Client assignment review.
- Filter Client is empty.
- Show the project name, Client, project status and responsible person if you already track one.
- Keep an unfiltered All projects view available for checking the original records.
Begin with all projects, including older work. If you later exclude archived or completed work, make that choice explicit: your queue will then check active assignments rather than your entire history.
3. Test three contrasting projects
| Project | Client relation | In review? | Action |
|---|---|---|---|
| Client A website | Empty | Yes | Confirm client and link existing record |
| Client B proposal | Client B | No | Verify the selected page if ownership is uncertain |
| Studio portfolio refresh | Empty | Yes | Identify as intentional internal work |
The view detects an empty connection. It cannot determine whether a project should have a client. That second decision needs context.
4. Repair the assignment without creating duplicates
For a client project, check the project brief or intake record. Open Client, search for the existing client page and select it. Open the selected page to confirm its identity before considering the record repaired.
If several client pages have similar names, use their existing details to distinguish them. Do not create a new client merely because the first search result is ambiguous.
After linking the project, it should leave the empty-relation queue. Confirm it still exists in All projects. Leaving the view is the expected result of meeting its assignment requirement.
If the relation points to the wrong Clients database, inspect the configuration before changing it. An isolated wrong assignment and a property connected to the wrong source are different problems.
5. Separate intentional internal work
For a mixed studio database, optionally add a Select property called Project Type with Client work and Internal work. Review existing records before using this field to exclude anything.
You can then filter the assignment queue to Client is empty AND Project Type is Client work. Keep a separate view for Project Type is empty so unclassified work cannot silently bypass review. These are properties you create, not built-in project classifications.
Do not assign a real client’s page to internal work merely to empty the queue. Keep the relation meaningful.
6. Add a small weekly check
Review unclassified projects first, then client projects missing a relation. Assign the correct client or record who must clarify the assignment. A clean queue should mean you checked the records, rather than simply hid the ambiguous ones.
For filter grouping, use the AND and OR guide. For the difference between displaying a source and connecting records, read linked databases versus relations.
Common mistakes
- Checking a text field instead of the relation. A written name can coexist with an empty connection.
- Excluding unclassified projects too early. They need their own review queue.
- Creating another client record during cleanup. Find and verify the existing page first.
- Expecting a relation to grant access. Review sharing separately from record assignment.
Frequently asked questions
Does an empty Client relation mean the project is broken?
No. Internal work may intentionally have no client. Review its purpose before assigning a client record.
Why does the client name appear but the project is still in this view?
The name may be stored in a separate text property. This view checks the Client relation, so inspect that specific property.
Should I create an Internal client record?
Only if it deliberately fits your data model. A Project Type label can distinguish internal work without treating it as a real client relationship.
Why does a repaired project disappear from the review queue?
The queue displays empty Client relations. Assigning a client makes the project ineligible; check All projects to find the original.
Does this view catch projects linked to the wrong client?
No. A non-empty relation passes this test even when its selected page is wrong. Check the linked page when assignment accuracy is uncertain.
Want this already built?
This guide shows you how to check and maintain the connections yourself. For a broader client and project workspace, explore Freelancer CRM and compare its structure with your workflow.
Reference: Notion relation and rollup documentation.