This original review helps a small team find owed actions and missing associations. It does not infer sales, customer acceptance or completed work from a contact row.
Four linked record types
Fictional Cedar Studio review, October 13, 2026, using date-only local-calendar comparisons. No actual customer details or reminders are included.
| Company ID | Fictional name | Associated contact IDs |
|---|---|---|
| A01 | Alder | C01, C02 |
| A02 | Brook | C03 |
There are two companies and three contacts. A01 appears beside two contact records, but remains one company.
I01 records a discussion with C01 on October 10. It is a completed interaction record, not evidence that a later follow-up task was completed. Store its ID, contact/company association, date and supplied discussion notes separately from planned work.
HubSpot's task documentation describes associations with records such as contacts and companies, along with assignee, due date and notes. It also explains that tasks can exist without an associated record. Its CRM spreadsheet description separates organizations, contacts and interactions. This example uses an original portable record design; no vendor workbook was downloaded or system connected.
Five task records, four still open
| Task | Association | Owner | Due date | State and supplied work |
|---|---|---|---|---|
| T01 | A01 / C01 | Mia | October 12 | Open: send revised brief |
| T02 | A01 / C02 | Mia | October 13 | Open: confirm required file format |
| T03 | A02 / C03 | Leo | Missing | Open: collect missing deadline |
| T04 | A02 / C03 | Leo | October 11 | Closed; completed October 11 |
| T05 | Missing | Missing | October 14 | Open: identify account for imported note |
The ledger has five unique tasks. Excluding closed T04 leaves four open tasks: T01, T02, T03 and T05.
Of those, three open tasks are associated with companies: T01/T02 with A01 and T03 with A02. They touch two unique companies, not three. T05 remains an unassociated open review task; it does not create a third company by itself.
The phrase “imported note” is the fictional task's description, not evidence that this review imported anything. Keep T05 in a separate queue until the actual account and owner are supplied.
Classify dates from the fixed snapshot
For an open task with a supplied date, compare that date with October 13:
- Overdue: T01, due October 12; one task.
- Due today: T02, due October 13; one task.
- Future: T05, due October 14; one task.
- Due date unknown: T03; one task.
These mutually exclusive categories sum to four open tasks. T04's older due date does not make it overdue because it is closed. T03's blank date does not mean zero elapsed days, today or overdue; obtain the missing deadline before classifying it.
State the date basis beside the result. This review has no due-time, business-hours or SLA inputs, so it cannot report an hourly delay or an owner's performance score.
Keep the filters aligned with entity counts
Selecting A01 should reveal C01/C02, the I01 interaction and T01/T02, without doubling the company total. The two open tasks are owed work; I01 does not clear either automatically.
An owner Mia view has two open tasks and one associated company. An owner Leo view has one open task and one associated company; closed T04 remains available in a closed-work view rather than inflating Leo's open count. T05's blank owner stays visible in a separate unassigned view.
Count tasks by unique task ID and companies by unique company ID. Do not count the rows of a joined company/contact/task table as every entity's total. Recompute the included IDs and caption when the scope changes.
Require evidence for a completion change
If someone proposes closing T01, obtain the actual internal evidence for sending the revised brief through the maintained workflow. A discussion with C01, a checkbox in a mock review or the passage of its due date does not supply that evidence.
Even confirmed internal task completion would not automatically establish customer acceptance. Record the relevant event and outcome separately when supplied. Do not generate a reminder, notify a customer or imply a source record was saved merely because the review state changed.
Maintain company, contact, interaction and task sheets—or equivalent CRM records—with stable IDs and explicit associations. Keep missing associations, owners and dates visible for correction in that source workflow.
Copy a relationship-and-follow-up dashboard brief
Prepare a CRM dashboard specification in US English.
Maintained workbook/CSV or CRM and required format: [enter]
Company IDs, contact IDs and confirmed associations: [paste sanitized records]
Completed interaction IDs/dates and supplied notes: [paste]
Unique task IDs, association, owner, due date, status and completion evidence: [paste]
Snapshot date and date/time classification basis: [enter]
Keep company/contact/interaction/task identities separate. Count companies
by unique company ID and tasks by unique task ID, not joined-row count.
Separate open from completed tasks and associated from unassociated work.
Classify open dated tasks as overdue/today/future from the fixed snapshot;
missing dates remain unknown. Keep blank owners and associations visible.
Filter company/owner and recompute included IDs, counts and captions together.
Logged discussion is not task completion; closing a task requires actual
internal evidence and does not imply customer acceptance or notification.
Return the portable source-sheet design, checked counts and dated state matrix.
If requested, specify a sanitized HTML review copy with local association views.
No CRM sync, imports, sending reminders, customer actions or saved editing.
Keep authoritative relationship and task records in the spreadsheet or CRM. Review T01's overdue action and T03/T05's missing inputs there before assigning a new status or promising a customer follow-up.
Optional association review with NOS
NOS can save and display a prepared HTML review copy of the fictional relationships and dated task matrix. Use it to inspect matching IDs and counts; it does not sync the CRM, send reminders or prove that a customer's action occurred.