Lue suomeksi →

A good barber gradually learns what works for your particular hair. When you change barbers, that knowledge usually does not come with you, and the explaining starts again. One possibility would be a haircut prescription that travels with the customer: a map recording the instructions for a successful cut and the particular features of their head. You could show it to a new barber much as you would take an eyeglass prescription to a new optician.

Concept draft: this proposes an open description format, not a completed standard or a tested service.

A photograph shows the result; a prescription also explains how

“A little shorter on the sides, leave more on top.” It is a familiar request, but much remains open to interpretation. How much is a little? Where does the transition from short to long begin? What happens around the cowlick?

A photograph would still help. The prescription would complement it by describing lengths, transitions between areas, cutting techniques, and the spots where this particular customer’s hair needs attention. A photograph of a successful result and instructions for achieving it would belong in the same package.

The idea is not to replace professional skill with millimetre measurements. The prescription would be a shared memory for the customer and barber. It could record failures too: no more thinning here; leave more length there next time.

The first version could be a single page

Initially, front, side, back, and top views of the head and a few clear annotations would suffice. The target length on top might be 55 millimetres, for example, with 6 millimetres on the sides. The cowlick area would carry a note to leave more length and preserve the natural growth direction.

These would be instructions for one imaginary haircut, not a universal recommendation. The purpose would be to describe something that works for a particular person. The meaning of the annotations would also need agreement: for instance, the target length after cutting must not be confused with the clipper guard used to achieve it.

After the appointment, the barber and customer could update the prescription. The next version might specify eight millimetres more on top, a slightly lower fade, and no thinning at the right front. “The same as last time” would become something that could be checked.

A shared format would give customers more choice

The core would be an open file format. Customers could keep their prescriptions and take them to another service or show them on paper. Barbers would not need to read software code: an application would present the information as an understandable map and text.

A small common core would describe areas, lengths, transitions, and additional instructions. More detailed systems could add a three-dimensional head model, growth directions, or haircut history. An application should also say when it cannot display an important extension, so an incomplete instruction does not appear complete.

The standard would therefore not define everyone’s head as identical. It would provide shared names for areas and a way to describe individual differences. Professionals could still adapt the instructions and discuss what is possible.

For people first, machines later

The first experiment could be a shared paper or file template used by a few barbers and customers. The key question would be whether another barber could use the instructions without a lengthy additional explanation. Only then would it make sense to increase technical precision.

Later, the same format could provide input for robotic haircutting. A prescription intended for humans would not, however, constitute safe machine instructions on its own: a device would need its own interpretation, measurements, and safety limits. A common description could connect systems even when their implementations differed.

An open prescription would still leave room for paid tools

The basic prescription format and a reference reader could be published openly. Paid editors, salon customer systems, or services converting different systems’ annotations into the common format could still be built around it. Customers would not be buying permission to use their own haircut; professionals would pay for tools that made their work easier.

An experiment would therefore not need to begin with an agreement across the entire industry. One salon could issue prescriptions that customers could show elsewhere. The common format would become more useful as others learned to read and update it. It would nevertheless have to earn its usefulness in practice: if filling out a prescription takes longer than interviewing a new customer, openness alone will not make it attractive.

Novelty (October 2026)

A personal haircut prescription is not a new idea. For example, the GRÜM concept describes a portable haircut passport with a recipe, while the HairCut History product page describes measurements by area and sharing with another barber. The former presents a concept under development and the latter describes a product; their effectiveness has not been tested here.

This article adds a distinction between the prescription and an individual application: could a haircut be described in an open, interoperable format that different services and eventually devices could read? The sources checked did not describe precisely such a shared standard.

Scale of the problem and potential of the solution

Even without a new standard, customer records, photographs, and AI-organized notes could make cuts easier to repeat. The additional benefit of an open format would be keeping the information usable when changing services, barbers, and potentially equipment manufacturers.

It could reduce explaining and uncertainty and make trying a new barber easier. Schools and software developers could also build different tools on the same foundation. The first measure of success would nevertheless be ordinary: did the new barber understand the prescription, and did it help produce the haircut the customer meant?

Revision history

  • v3 (Oct 19, 2026): Dated the novelty assessment and removed an unnecessary closing qualification.
  • v2 (Oct 19, 2026): Reframed the idea as a possibility for consideration and condensed the assessment of the article’s contribution.

All changes line by line on GitHub