# Client notes scattered across tools: why a new notes app will not gather them

Client notes scattered across tools stay scattered because each note gets written wherever the person happened to be standing, and a new app only adds one more place. The fix is one record per client, built from what the work already writes, with each note carrying its date and source, so nobody has to file anything later.

Date: 2026-11-06
Reading time: 3 min
Author: OCTYN
No. 24

The note that says a hotel kitchen will not accept a substitute on its cream was written in a van, on an account manager's phone, two winters ago. The wholesaler in this story is made up, and so is the hotel. One morning the dairy line comes up short, somebody on the customer service desk swaps in another brand, and at half past six the chef sends the crate back with the driver. The driver knew about the cream. It had come up several times, and the driver had passed it on to the drivers' group, which the desk is not in.

Somebody senior then asks everyone to put their client notes in the customer file by Friday. **What arrives on Friday is whatever people can still remember**, in tidier words, and the cream is not in it.

## Where the notes actually are

At a wholesaler with a few hundred clients, the useful notes tend to sit wherever the person writing them was standing.

| The note | Where it got written | Who needed it |
|---|---|---|
| No substitutes on the cream | An account manager's phone | The customer service desk |
| The loading bay is shared after seven | The drivers' group | The new route planner |
| Head chef leaves in March, talk to the owner | A slide in a review deck | Whoever rings in February |

Whoever wrote each one used whatever was already open. **A new notes app adds one more place to look**, and it comes with a request to copy things across later. Copying is a second job. In a busy week it gets done last, then not at all.

## Notes stay current when the next step needs them

OCTYN ran into this on its own work. Brain, the planning system it runs its portfolio on, sits over a workspace that held 141 markdown notes across 15 subprojects when audited on 24 July 2026, and the [case study](/casestudies/octyn-brain) says the progress log gets written because the next session needs it. The project list stays accurate for a plainer reason: an inaccurate one is felt within a day. **A note survives when the next piece of work depends on reading it.**

Brain is a long way from a wholesaler's desk. It assumes one reader at a time, and the write up says more than one would mean a rebuild. It also has **no measured retrieval accuracy**, since there is no fixed set of questions to test it against. Anyone building the version for a desk should write that set first.

## One record per client, fed by what people already write

The thing worth building reads the places notes already land, the drivers' group, say, or the account manager's voice memos, and keeps [one record per client](/systems/company-brain) with every line dated and tied to whoever said it. **The cream line should appear on the desk's screen at the moment somebody goes to swap the brand.** A search box cannot do that part, because nobody searches for a note they do not know exists. Whether to ring the chef or send the order short stays with [the person on the desk](/glossary/human-in-the-loop).

Before building any of it, run the sum on your own numbers. On made up ones, three hundred clients with two contacts each a week, at four minutes per contact finding out what is known about that client, comes to **forty hours a week spent looking things up**. The [page on what a system gives back](/what-it-costs) takes your real figures.



Back at the made up wholesaler, the chef has started writing no substitutes across the top of every order, which makes a fourth place to look.

## Related

**Systems this bears on**

- [Company Brain](https://octyn.co/systems/company-brain)

**Case studies cited**

- [Brain](https://octyn.co/casestudies/octyn-brain)

**Terms used here**

- [Human in the loop](https://octyn.co/glossary/human-in-the-loop)

**The longer argument**

- [Doing it by hand, or building a system](https://octyn.co/compare/doing-it-by-hand-vs-a-system)

**Read next**

- [How to hand off a client without losing context starts before anyone resigns](https://octyn.co/blog/how-to-hand-off-a-client-without-losing-context-starts-before-anyone-resigns)
- [Care coordinator workload: count the minutes spent catching up before each contact](https://octyn.co/blog/care-coordinator-workload-count-the-minutes-spent-catching-up-before-each-contac)
- [A company knowledge base that answers questions, and the answer it must never give](https://octyn.co/blog/a-company-knowledge-base-that-answers-questions-and-the-answer-it-must-never-giv)
- [Why a CRM does not fix client context, even when everyone fills it in](https://octyn.co/blog/why-a-crm-does-not-fix-client-context-even-when-everyone-fills-it-in)

More on client context: [Client context](https://octyn.co/blog/topic/client-context)

Canonical: https://octyn.co/blog/client-notes-scattered-across-tools-why-a-new-notes-app-will-not-gather-them