Tidy CRM notes while keeping the original
Tidying a year of scruffy CRM notes sounds like an afternoon well spent, right up until someone asks what the note said before you tidied it.
What you'll make
one readable, checked summary added beside an existing CRM note, labelled so it can be found and linked to the original, which stays exactly as it was.
What you'll need
a ChatGPT, Claude, Gemini or Copilot chat in your work account that you’re allowed to use for the note, permission to add a note or comment to the record, your records policy, and about thirty minutes. Adding beside the original keeps your edit separate from the source, but it isn’t a tamper-proof audit trail: both notes may still be editable or deletable.
Example result.
CHECKED SUMMARY — A. Shah, 6 October 2026
Based on: Calderstone call note, A. Shah, 14 August 2026.
Prepared with ChatGPT; checked against the original by A. Shah. Original left unchanged.
Context: Dev wants consolidated invoicing; says invoice matching takes too long. An earlier supplier review is recorded, with no reason it stopped.
Decisions: None recorded.
Commitments: A. Shah said they'd send the invoicing one-pager. No date recorded.
Open questions: Dev thinks renewal is around March; no date or year recorded. Notice period to be checked with the contracts team; no agreed action. A possible 15% volume increase is unconfirmed.1. Find out what your CRM keeps
Before you tidy anything, find out whether you could get the old text back. On a test record your administrator has agreed you can use, add a note containing a unique marker such as ZZORIGINAL-20261010. Save it, edit the marker to something else, then look for the original: in the activity’s history, the record’s history, an export and the activity search.
In HubSpot, View property history on a record shows the history of its property values, with the change source and timestamp; it isn’t a history of note text. Restore activity brings back engagements deleted in the last 90 days, which is a deletion safety net, not edit history. And the AI-generated summary on a call record isn’t editable: HubSpot says to use the Notes box below it.
If the old text can’t be retrieved, never edit. Only add.
Why this works: five minutes on a test record tells you whether editing is reversible, before a real note depends on the answer.
What you should see: a clear yes or no on whether edited note text can be recovered, and from where.
2. Choose one note and record where it came from
Start with an ordinary, low-risk note that a colleague would use if it were easier to read. Note its account, author, date and direct link. Read it all, and leave out anything that doesn’t belong in your AI account or the summary. Removing names may not make an identifiable situation safe.
Why this works: the author and date are what let a summary say who promised what, instead of guessing.
What you should see: one note, with its author, date and link written down.
3. Ask for structure that keeps the uncertainty
Open a new chat and paste:
Restructure this CRM note into Context, Decisions, Commitments and Open questions. Use only the note and the metadata. Do not update any record or send anything.
Keep uncertain wording, conditions and the difference between what the customer said and what was verified. Do not infer an owner, date, year, deal stage or approval. Write "not recorded" where needed. Do not turn a need to check something into a promise to do it.
After the draft, list each material item with its original wording, then list anything relevant you left out and why.
METADATA: [author, date, account and link]
NOTE: [original note text][author, date, account and link] comes from step 2, and [original note text] is the note itself.
Why this works: the mapping list shows what moved and what was dropped. Metadata matters: if the note says “I’ll send it”, the assistant can only name the owner if you’ve given it the author.
What you should see: four short sections, then a list pairing each item with the original words.
4. Check the draft in both directions
Read every draft item against the original: look for firmer dates, new owners, new numbers and a customer’s claim presented as fact. Then read the original against the draft, checking that no condition, question or stated need has gone missing. Reorganising can lose information even when every remaining sentence is true. Compare the actual text, not the assistant’s account of what it kept.
Keep attribution neutral. “Customer said invoice matching takes too long” records a statement; a label about the customer adds a judgement nobody asked for.
Why this works: each direction catches a different failure: additions one way, omissions the other.
What you should see: a short list of lines to fix, or none.
5. Add the checked summary beside the original
Add it as a separate note, or in HubSpot as a comment on the activity: open the record, click the Activities tab, find the activity and click Add comment. Use this every time:
CHECKED SUMMARY — [reviewer], [date]
Based on: [original activity title or link], by [author], dated [date].
Prepared with [tool]; checked against the original by [person]. Original left unchanged.
Context:
Decisions:
Commitments:
Open questions:CRM search is literal. HubSpot’s activity search covers note bodies, so the same label every time lets you find every tidied note in one search. Then reopen the record and check that the original is unchanged, the summary sits on the right record and the link works.
Why this works: the label and provenance line make the summary’s status plain: a reviewed reading of the note, not the record itself.
What you should see: the original and the labelled summary side by side on the record.
Check the result
- Every item in the summary traces to words in the original note.
- Hedged words (“thinks”, “maybe”, “not confirmed”) are still hedged.
- Nothing from the original is missing, including reasons and needs.
- The original note is unchanged.
The usual failure: tidying hardens the note. “March-ish” becomes a date, “maybe 15%” becomes a figure, “needs to check” becomes an action with a deadline, and a reason quietly disappears because it didn’t fit a heading. Spot it in step 4’s first direction. Then:
Correct [draft sentence] against [original wording]. Keep the uncertainty and attribution. Do not turn [need, question or estimate] into an agreed action or confirmed fact. Restore [omitted item]. Return the revised draft and its updated mapping only.Fill each bracket with the exact text from the draft and the note. If the note itself is ambiguous, leave the point open and ask the author.
Worked example: keep “March-ish” uncertain
Fictional example. A. Shah’s note on the Calderstone account, 14 August 2026:
call w/ Dev 14/8 - renewal is march-ish he thinks, needs to check
notice with contracts team. volumes up maybe 15%? not confirmed.
wants consolidated invoicing, says invoice matching takes too long.
looked at another supplier last year, no reason recorded for stopping.
I said I'd send the invoicing one-pager. no date given.The first draft said: “Renewal: 1 March 2027. Volumes up 15%. Dev to check notice with contracts by Friday. A. Shah to send one-pager.” Its mapping list claimed nothing material was omitted.
- The failure. Three hardenings (a date and year, a confirmed figure, an action with a deadline nobody gave) and one omission: the invoice-matching reason vanished while the mapping said it was kept.
- The repair. Two correction prompts, one for the renewal line and one restoring the invoicing reason, gave the example result. “Dev thinks… around March” and “unconfirmed” are back, and the notice check is an open question, not Dev’s task.
- What stayed right. The author metadata supports naming A. Shah for the one-pager. Without it, “the note’s author” would be safer than a guessed name.
Task kit for this job: Download (ZIP) · Reusable instructions
Go deeper
Optional training: When not to tidy a note at all
Don’t use this on a record under legal hold, an open dispute or complaint, or a note that feeds financial reporting, without the responsible owner’s direction. Don’t tidy a colleague’s note without telling them: even an addition changes how their record reads. And don’t start with a bulk project. One note teaches you whether the method suits your team; three hundred teach you how long a rollback takes.
Optional training: Decide whether a bulk tidy is worth it
Try a small agreed sample first. Record whether colleagues found the summaries useful, which uncertainties were lost and how much checking each took. Because every addition carries the same label, you can find and remove them all without touching the originals.
A bulk rewrite is a records-change project, however quick the assistant makes it look. It needs an owner, checking and a recovery plan, and automated enrichment or task-creation features should be assessed separately from this read-and-add method. For writing a new summary straight after a call, see Write a CRM call summary the next person can actually use.