You see “Prepare proposal” on a project page and again on your weekly dashboard. That does not necessarily mean you have two tasks to maintain.
First establish whether both cards open the same page. A linked view can display an existing task in another place without creating a second record.
Start with identity, not the title
| What you find | Likely explanation | Next check |
|---|---|---|
| Both cards open the same task page | One record displayed in two places | Source and view settings |
| Cards open different task pages with the same title | Separate records | Purpose and creation history |
| Two weekly routine pages share a title | Possibly intentional occurrences | Occurrence date and work performed |
The title is a label. Two separate tasks can legitimately share it, while one page can appear in several views.
1. Open each card as a page
- Open the first task from its view.
- Copy its page link, rather than a link to the database view.
- Repeat for the second card.
- Open both page links and inspect the destination page identity.
- Compare the task source, project and page content.
Page links can have different display text or view parameters. Do not treat a differently formatted URL alone as proof of a separate page; check the page identifier and destination.
2. Confirm the source behind each view
Inspect the data sources for the project view and weekly view. If both use the same task source and open the same page, there is no duplicate task to remove.
Notion’s linked database guide explains how existing content can appear across pages. The linked view versus relation guide separates display from record connections.
3. Use a fictional rename test if needed
For a fictional test task only, rename it Prepare proposal — identity check in the first view. Inspect the second view and the original source.
If both cards refer to that same page, the underlying task title is the same wherever it is displayed. Restore the original title after checking.
This is a diagnostic check, not a reason to rename live work. If the result is unclear, retain both references and inspect the source more closely.
4. If there are two pages, check whether they serve different jobs
Read both records before choosing one to keep. Compare their project relations, dates, completion state, notes and outputs.
A weekly review on one date and the following week’s review can be separate, intentional occurrences. A recurring template creates new pages; shared titles are not by themselves an error.
For recurring work, use the repeating task guide to review the creation process.
5. Reconcile accidental duplicates before removal
If two pages truly represent the same action, identify the intended continuing record. Preserve useful notes and source references, then update any project connections or dashboard references that depended on the other record.
Do not assume deleting one page merges its content or transfers its relationships. Confirm the retained page has the information needed before removing an accidental duplicate through your normal cleanup process.
6. Prevent the duplicate creation path
Review how both pages were created. Possibilities include manual recreation of a filtered-out task, repeated imports or more than one repeating setup for the same routine.
If a task appeared to vanish before someone recreated it, check the task visibility guide. Correcting that cause is more useful than repeatedly deleting copies.
Common mistakes
- Deleting a task because it appears on two dashboards.
- Using the title alone to identify duplicates.
- Removing legitimate recurring occurrences.
- Discarding notes or relations before comparing separate records.
Frequently asked questions
Can one task appear in several views?
Yes. Several views can display the same underlying task page without creating independent task records.
Do matching titles prove duplication?
No. Compare the page identity, source and purpose.
Should I compare page links or view links?
Use links to the individual task pages. A database view link identifies a display context rather than the task itself.
Are weekly tasks with the same title always duplicates?
No. They may be intentional recurring occurrences. Check their dates and work history.
Does deleting a duplicate merge its notes into the retained task?
Do not assume so. Preserve relevant content and check relationships before removing an accidental duplicate.
Explore the wider workflow
You can build this with your existing records. For a broader client and project workspace, explore Freelancer CRM and compare its structure with your workflow.