Choose the facts people need for the work
Start with terms that affect everyday delivery: dates, review windows, billing milestones, contacts, support hours or communication routes. Identify the client and project for every entry so a condition from one agreement is not reused for another.
A signed agreement, approved change, client message and internal recollection are different sources. Name the type of record and include only the information the intended readers need.
Put the source beside the summary
Keep exact wording where practical. If a clause is too long, label your entry as a summary and point to the page, section or dated message containing the original. Record the person who checked it and when.
Use statuses such as confirmed in source, superseded and needs owner review. If two records conflict, keep both references and ask the responsible owner to resolve the issue.
- Choose a client and project.
- Record one operational term and its scope.
- Add the exact source, reviewer and current status.
Two projects with different answers
In the fictional register, Northwind Studio's signed addendum gives a five-business-day review window for its website refresh. That entry is limited to the website project. A second Northwind project has two messages with different proposed start dates, so its date needs owner review.
A separate fictional Morrow Workshop retainer uses the support inbox named in its approved onboarding note. The original worksheet keeps the three sample rows and source references.
Keep the reference current and appropriately shared
Review an entry when its agreement changes or someone finds a mismatch. A check date tells readers when it was last reviewed, not that nothing has changed since. Give access only to people who need the information and keep restricted files in their existing location.
If the wording raises a legal question, return to the agreement and the person qualified to interpret it. Leave the question visible instead of inserting an unapproved conclusion.
Prepare a source-linked summary with Areinum
Areinum Assistant can help organize the terms and source references you provide by client and project. Review the wording and scope against the original documents before the team relies on the summary.
See the example
Client terms source register
All clients, terms, dates, and source records in the worked example are fictional.
| Client and project | Topic | Recorded wording or summary | Applies to | Source reference | Checked by and date | Status |
|---|---|---|---|---|---|---|
| Fictional Northwind Studio, Website refresh | Draft review window | Signed addendum says the client reviews the first draft within five business days | Website refresh only | Fictional signed addendum, section 3 | Fictional project owner, 2026-06-01 | Confirmed in source |
| Fictional Morrow Workshop, Retainer | Request channel | Approved onboarding note names the client support inbox | Retainer support only | Fictional approved onboarding email, 2026-05-18 | Fictional account lead, 2026-05-20 | Confirmed in source |
| Fictional Northwind Studio, second project | Start date | Two messages show different proposed dates | Second project only | Fictional email threads C and D | Fictional account lead, 2026-06-03 | Needs owner review |
- Create one row for each fact the team needs to retrieve. Name the client and project so a term is not reused elsewhere.
- Preserve exact wording where practical. Label paraphrases as summaries and keep the source reference beside them.
- Status describes the record, not a legal conclusion. Mark conflicts for owner review and retain each original source.
- All examples are fictional. Replace them with reviewed facts and limit access according to source sensitivity.
Limits of this method
- The source documents a search feature, while this page proposes a manual reference workflow. Their connection is an adjacent-evidence hypothesis, not a measured result.
- A reference can point to a source and record its scope. It cannot establish legal meaning or resolve conflicting documents without review.
Questions you may have
Should I copy every clause into the reference?
No. Include the operating details the intended readers need, and point to the original for full context.
What if two terms appear to conflict?
Keep both references, mark the entry for owner review and avoid choosing one solely because its file is newer.
Does the reference replace the agreement?
No. It is a way to find and summarize the relevant source; questions about legal meaning belong with the appropriate adviser.
Sources and further reading
- Enterprise Search in Notion, Notion Help Center
Notion describes search answers that cite workspace or connected-app sources. The manual terms register applies the related idea of pointing readers back to a source.
A citation does not establish accuracy or the legal meaning of a term.
Notion documents Enterprise Search answers that cite workspace or connected-app sources so readers can return to them.
This vendor documentation does not benchmark answer accuracy or measure demand. A citation does not confirm a term’s meaning, and the described search feature is adjacent evidence for the manual reference proposed here.
2026-10-18
The demo is in English. Access may need to be arranged.
Explore the demo