States, not reminders
The difference between a useful checklist and a list of good intentions is verifiability. «Check the requirements» isn't an item: «requested the requirements list from the state board, received on date X» is, because it has an outcome someone can check without interpreting.
Organising by area — person, space, business, fit-out, launch — lets you see where the project is stuck. An area with several blocked items signals a sequencing problem or a dependency on third parties that needs managing, and it signals it in time.
The checklist should be reviewed weekly, not consulted when you remember it. It's a working document: if it hasn't changed state for weeks, the project is stalled even when daily activity suggests otherwise.
Where blockages concentrate
The chart is qualitative and shows how much each area tends to produce blocked items in an opening project.
The areas and the items that can't be missing
The table gathers, for each area, the items whose outcome determines whether you can open.
| Area | Critical items | Verifiable outcome |
|---|---|---|
| Person | Licence or named licensee | Documentation obtained |
| Space | Permitted use, suitability, compliance | Certifications received |
| Business | Registrations, tax and payroll accounts | Filings completed |
| Launch | Price list, protocols, dress rehearsal | Documents existing and tested |
How to keep it alive
Write outcomes, not actions
Each item needs a verifiable result.
Organise by area
Person, space, business, fit-out, launch.
Note who unblocks
A name next to every stuck item.
Review weekly
Same day, same time, thirty minutes.
How to use it
- Write each item with a verifiable outcome, not a generic action.
- Review it weekly, at the same time.
- Flag blocked items with the name of whoever can unblock them.
Attaching to each blocked item the name of the person or authority who can unblock it turns the checklist into a chasing tool. Without that detail, blocked items stay stuck because nobody knows who the next step depends on.
A weekly review at a fixed time is what stops the checklist becoming a dead document. Thirty minutes at the same moment each week is enough to keep the project moving even in periods when attention is elsewhere.
The service to include in the new salon
Saloria slots into the opening project as a consultation tool, not as management software. A new salon can use it to guide the first visit, analyse the face, build the look plan, and generate a protocol useful to the team. That way, technology isn't an accessory: it becomes part of positioning and of professional selling.
To consult before deciding
Federal and state board guidance gives the general structure of the checklist; the specific items for your address come from your local authority.
Frequently asked questions
What makes a checklist useful?
That every item has a verifiable outcome rather than a generic action: someone has to be able to say whether it's done without interpreting.
How should it be organised?
By area — person, space, business, fit-out, launch — so you can see immediately where the project is stuck.
How often should you review it?
Weekly, at the same time. If it hasn't changed state for weeks, the project is stalled.