Patch tests, consent and the booking your app should refuse
Every beauty trade has a booking that should not happen.
A lash lift for someone with no patch test on file. A color service for a client whose last test was long enough ago that your product's instructions say to test again. A brow tint for someone who reacted last time. A PMU appointment where the consent form was never signed. A tattoo where the client has not confirmed their age.
You know these rules. You probably enforce them every day. The question is where they live.
Where the rules live now
For most pros, the rules live in your head, and the booking app has no idea they exist.
Look at how lash and brow businesses handle patch tests today and you see the same workarounds again and again. The patch test becomes its own five-minute "service" so it shows up on the calendar. The booking page carries a paragraph asking clients to book it first. A form asks the client to type in the date of their test. And then, on the day, someone checks by hand whether that date actually makes sense.
None of that is wrong. It is just a lot of careful people doing a job that a computer is very good at, using tools that were never told the rule. The booking app will happily take the lash lift. It is up to you to notice.
When you work alone, there is no front desk to catch it either. The check happens when you remember, which is usually fine, until the one busy day when it is not.
A rule is something an app can hold
Here is the shift that owning your app makes possible. "Patch test first" is not a feeling or a habit. It is a rule, and rules are exactly what software is good at:
- This service needs a patch test on file before it can be booked.
- The test counts for as long as you say it counts.
- After a reaction, the client cannot book this service until you clear them.
- No appointment is confirmed until the consent form for that service is signed.
A generic booking app cannot hold rules like these for every trade at once, because they differ for every trade. Lashes, color, PMU and tattoo each have their own. When the app is yours, it only has to hold yours.
And the rule moves from the moment you remember to check to the moment the client tries to book. That is the moment it matters.
You decide the rule, not the app
One thing I want to be very clear about. The app does not decide what is safe. You do.
How long a patch test counts, which services need one, what a reaction means for the next booking, which forms a client must sign: those come from your training, your product manufacturer's instructions, your insurer and your state board. They are not something a blog post, or an AI, should decide for you. If a rule is unclear, the answer is to ask the people who set it, not to guess.
What the app does is make sure the rule you chose is followed every time, including on the days you are tired.
The real work is describing the rule precisely
This is where people expect the hard part to be code. It is not. AI writes the code now, and that part is genuinely solved. The hard part is saying exactly what you mean.
"Make sure clients have a patch test" is not a rule an app can follow. It leaves too much open. Compare it with this:
A client cannot book a lash lift unless they have a patch test recorded within the window I set for that service. If they do not, show them a button to book the patch test instead.
That second version answers the questions the first one skips. Which service. What counts. How long. What the client sees instead. Writing that kind of sentence, and then trying it as a client would, is where the real work is. None of it is technical.
I wrote more about this skill in how to describe what you want built. It is the same skill you already use when you explain a service to a new client, just written down carefully.
Then you test it like a client would
Once a rule exists, try to break it. Book the lash lift with no test on file. Book it with an old test. Book it as a client who reacted last time. Sign the consent form halfway and close the page. Each one should do exactly what you decided, and nothing else.
You do not need to read code to do this. You need to be the person who knows what should happen, and then check that it does.
The checks belong where the booking happens
The reason this matters so much in beauty is that the checks protect people. A patch test, a consent form, an age confirmation: these are not admin, they are part of doing the work properly. When they live only in your head, they depend on your memory on your busiest day. When they live in your app, they are there every time.
I wrote about the wider version of this, all the trade-specific details generic apps skip, in your booking app was built for every salon.
If you want to see what your own app could look like, shaped around your services and your rules, the free starter walks you through building a clickable demo of it first, before you decide anything.
This post is not medical or legal advice. Check your rules with your product manufacturer, your insurer and your state board.