How should a lash and brow studio keep patch-test records?
Keep patch-test dates, recorded results and product notes useful across lash and brow appointments, without treating a software status as safety clearance.
On this page
Before a brow tint appointment, the artist opens the client’s history. There is a note saying “patch test done”, but no clear product name or recorded result. The artist who entered it is not working today.
The problem is not finding the note. It is knowing what the note refers to.
Keep patch-test records with the client, with the date the test took place, the recorded result, who performed it and enough product context for another authorised artist to understand it. Review that information against the planned appointment. A software status records information; it does not decide whether a service is safe to perform.
Record what happened, not what someone might assume#
A useful record separates the event from its interpretation. The date someone entered the information may be different from the date the test took place. A product description such as “usual tint” may be clear to one artist and meaningless to another.
In OpenChair, the patch-test record includes a title, test date and recorded status, with optional performing-staff and notes fields. Use the title to identify the test clearly. Put relevant product details and observations in the notes rather than expecting the title alone to carry the whole record.
| Record detail | What to make clear |
|---|---|
| Test title | What the studio is recording, rather than a label such as “done”. |
| Test date | When the test took place, not when someone later typed the record. |
| Recorded result | The outcome entered by the studio, including when it is still pending. |
| Performing artist | Who carried out the test, where that information is known. |
| Notes | The product used and relevant observations or follow-up information. |
This is a record-keeping structure, not a testing procedure. It does not specify how to carry out a test, which products require one or how long to wait. Those decisions need the applicable product instructions and the studio’s professional guidance.
Do not fill a missing detail with an assumption. If the product is unknown or the result has not been recorded, keep that uncertainty visible until the studio can resolve it.
Check that the record relates to the planned appointment#
A recent date does not tell the next artist which product was involved. Nor does a completed record for one service establish that it answers every question about another.
Before the appointment, review the record’s title, notes, date and recorded outcome together. Check them against the service the client has booked and the products the studio intends to use. Use the record as something to review, rather than treating its presence as confirmation that it covers the planned products.
For example, consider a client who usually books a brow tint with Mia but has chosen Amara for the next visit. Amara should be able to understand the saved record without asking Mia to reconstruct it from memory. A recognisable test title and product note give her something specific to review.
If the note is unclear, the next task is to clarify the record. Changing the label to make the booking look ready would not resolve the missing information.
Treat status and expiry as record information#
OpenChair displays recorded patch-test outcomes and expiry information. That makes the information easier to find, but a badge should not replace reading the underlying record.
A “Passed” label describes the outcome entered in the system. It is not an instruction to proceed with every lash or brow service. An expiry date is part of the software’s record handling, not a universal recommendation about when a particular product should be tested again.
The same distinction matters when a record is pending, missing or expired. The studio needs to review what is recorded and decide what action is appropriate. Do not rewrite a date or result merely to remove a warning.
Where a service is configured to require a valid patch-test record, OpenChair’s booking workflow can warn when one is missing or expired. The warning helps draw attention to the record. It does not complete the studio’s review for it.
Make artist handover part of the routine#
Decide who reviews the record before an appointment and who follows up when information is missing. Otherwise, reception may assume the artist has checked it while the artist assumes reception has already resolved it.
The handover can be brief. It should identify the appointment, the record to review and the specific question still outstanding. “Please check which tint this record refers to” gives the next person a clearer task than “please check client”.
Record relevant follow-up with the client information rather than relying on a private staff message. The aim is for the next authorised artist to find the same context, even if the usual artist is away.
Access also matters. OpenChair’s dedicated shared workstation does not expose private patch-test records. Reviewing them requires a personal account with appropriate access. A reception iPad and an artist’s signed-in device may therefore serve different jobs.
Keep consultation answers and patch-test records distinct#
A client saying they have had a patch test is useful information to review. It is not the same as the studio holding a record of the test, product and outcome.
Likewise, a signed consultation form does not replace the patch-test record. Keep each item in its proper place so the artist can distinguish what the client has reported from what the studio has recorded.
On Pro, OpenChair’s Consultation Forms & Waivers can keep submitted client information with the relevant client workflow. Patch-test records provide a separate record of the test information the studio enters.
Private photos are another separate form of context. Saving a photo for the working record does not authorise its publication on an artist’s profile or the studio’s social accounts. The broader lash and brow client-record guide covers that distinction.
Test whether another artist can use the record#
Use a fictional client when checking your setup. Enter a clearly identified test record, then open the client from another appropriately authorised artist’s account. Check that the second artist can identify what was recorded, when it happened and anything still requiring review.
Also test a missing record and a pending result. Staff should understand what the screen is telling them without interpreting every status as permission to perform the service.
The useful result is a record another artist can read and act on responsibly, with gaps left visible rather than hidden behind a completed label. See how OpenChair for Lash & Brow studios keeps that recorded context connected to the client and appointment.