Just a moment
Customers

Client notes worth keeping, and ones that will get you in trouble

Good notes make a client feel remembered. Bad ones are a data protection problem sitting in your system waiting for somebody to ask for a copy.

The Youzse team19 June 20264 min read

Client notes are the difference between a business that remembers you and one that asks the same three questions every visit. They are also, in a lot of businesses, an unreviewed pile of personal data that nobody has read in five years.

Both things are true at once, and the fix for the second does not require giving up the first.

The test that settles most arguments

Assume the client will read it. They are entitled to. Anybody can ask for a copy of what you hold about them and you have a month to provide it, so every note you write should be one you would be comfortable reading aloud to the person it describes.

That single test removes almost every problematic note ever written, and it removes none of the useful ones.

Notes that earn their place

  • What you actually did. Products, quantities, timings, settings, colours, parts, torque figures. This is the professional record and it is the reason notes exist.
  • Preferences and constraints. Prefers the quieter chair, cannot do mornings, always parks round the back, does not want the beard trimmed.
  • What went well and what did not. If the last one was a shade too dark, that is the most useful sentence in the file.
  • Safety and clinical information where it is relevant to the work. Allergies, medication that affects treatment, previous reactions.
  • Consent and what they agreed to. The waiver, the patch test date, the photo permission.

Notes that will cause you a problem

  • Opinions about the person. Difficult, rude, a nightmare, cheap. If it describes them rather than the work, it does not belong in a system.
  • Anything about their appearance, weight, relationships or personal circumstances that has nothing to do with the service.
  • Third party information. What they told you about their sister is her personal data, not theirs, and it should not be in either file.
  • Payment resentment. "Never tips" is a note that has ended more than one business relationship at the moment it was disclosed.
  • Speculation about health. Recording what somebody told you is a record. Guessing a diagnosis is not, and it is a category of data that carries much stricter obligations.

Special category data deserves more care

Health information, and anything revealing it, is treated differently under UK GDPR and needs a stronger basis than "it is useful to know". Clinics, tattoo studios, aesthetics practitioners and anybody taking a medical history are already handling it, whether or not they have thought about it in those terms.

Where you do hold it, keep it in a field designed for it rather than in a free text box, restrict who can see it and be able to say why you have it. A junior on reception does not need to read anybody's medical history to take a payment.

Practical habits

  • Write the note at the end of the appointment, not at the end of the week. A note written on Friday about Tuesday is half invented.
  • Keep it factual and short. Two lines of specifics beats a paragraph of impressions.
  • Never use a client record as a message board between staff. Anything you would not want on a screen while the client is standing next to it should not be there.
  • Review and delete. Notes on somebody who has not been near you in years are a liability with no upside. A retention rule that runs automatically is worth more than good intentions.
  • Restrict access by role. Not everybody needs to see everything, and that is as true in a five person salon as in a hospital.

None of this is legal advice. It is the practical version of a simple rule, which is that a note should be about the work, useful next time and fit to be read by the person it is about.

Topics

CrmGdprClient notes

We value your privacy

Cookies keep Youzse running, improve the platform and help deliver relevant content. Read our privacy policy and cookie policy.