A task can have a clear title and a deadline while nobody is responsible for moving it forward. An unassigned-work view makes that gap visible.
This guide uses an existing Tasks database. It creates a review queue; it does not automatically assign people or establish that someone has accepted the work.
1. Identify the responsibility property
Use your existing Person property if it represents responsibility. This recipe calls it Owner.
Created by identifies who created the record. It is not necessarily the person responsible for completing the work. A separate Follow-up Owner may also describe a different responsibility.
Notion’s property documentation explains Person properties. Select an available workspace person rather than typing a name into an unrelated text field.
2. Define what unfinished means
The example uses a Done checkbox. If your database already uses Status, preserve it and exclude the statuses your workflow treats as complete.
Decide separately how cancelled work is closed. Do not keep cancelled tasks in an active queue simply because they were never delivered.
3. Create the assignment review
- Add a Table view called Unassigned open tasks.
- Filter Owner is empty.
- Add Done is unchecked using AND.
- Show Task, Owner, Project and Due Date if you use them.
- Sort Due Date ascending, but inspect undated tasks too.
Do not add a current-user filter to this view. Its purpose is to find empty responsibility, rather than tasks already assigned to you. Use the AND and OR filter guide if unrelated tasks appear.
4. Test the queue
| Task | Owner | Done | In review queue? |
|---|---|---|---|
| Prepare first draft | Empty | Unchecked | Yes |
| Review approved copy | Selected workspace person | Unchecked | No |
| Send completed handover | Empty | Checked | No |
| Clarify missing brief | Empty | Unchecked | Yes, even without a deadline |
Assign an available workspace person to Prepare first draft. Confirm it leaves the queue, then locate the original record in an unfiltered view. Its disappearance should mean the filter no longer matches, not that it was deleted.
5. Review responsibility before assigning
For each real task, check the intended outcome, project and next action. Agree who will take responsibility through your normal working process before treating the assignment as accepted.
Adding a person is a recorded assignment. It is not proof that they have reviewed the brief, have capacity or have agreed to the deadline.
For a task blocked by client input, responsibility still matters: someone needs to check the response. The waiting-on-client guide separates the blocker and the follow-up action.
6. Keep solo work simple
In a workspace used only by you, an Owner property may add little value. Do not add team administration merely to satisfy this recipe.
If your database mixes personal and team work, use an existing field that identifies that distinction. You can narrow the review to team work, but keep unclassified records visible in a separate check.
Do not mark everything as personal merely to empty the queue.
7. Check why new tasks keep arriving unassigned
Review the creation template and the normal intake process. A blank Owner can be intentional for requests awaiting triage; the important part is who reviews that queue and when.
Keep project assignment separate. A task can have an owner while still being disconnected from its project. Use tasks without a project for that review.
Common mistakes
- Using Created by as an automatic substitute for responsibility.
- Filtering to Me while trying to find empty assignments.
- Assigning someone without checking the task context.
- Ignoring undated work because it falls below the dated tasks.
Frequently asked questions
Is Created by the same as Owner?
No. The creator and the person responsible for the work may be different people.
Should completed tasks appear?
Not in this operational queue. Use a separate historical review if you need to check older assignments.
What if I work alone?
An Owner property may be unnecessary. Use the queue only if explicit assignment serves your workflow.
Does selecting a person prove they accepted the task?
No. Confirm acceptance and capacity through your normal working process.
Why does a task disappear after I assign someone?
Owner is no longer empty, so the task stops matching the review filter. Check the same record in an unfiltered view.
Explore the wider workflow
You can build this in your existing database. For a broader client and project workspace, explore Freelancer CRM and compare its structure with your workflow.