Chair and stylist board
Every chair, the stylist booked into it and the next open slot, on one screen.
A hair salon management app gives the owner or general manager one view of chair use, stylist schedules, open front-desk tasks and the day's takings. SIZ Group designs and builds it for iOS and Android, reading from the same booking data the salon already keeps.
On day one the screen has to answer four questions: which chair is in use, which stylist is free next, which front-desk tasks remain, and how the takings are running. A simple takings line gives the owner a reason to open it every evening.
Staff scheduling tools, payroll, retail stock counts and multi-location comparisons can wait for a later phase. Adding them too early makes the first view harder to trust, and stylists will stop using it before the owner has the figures they need.
Most salons already own a booking product and a card terminal, and the oversight view should borrow data from both instead of keeping its own copies. Reports and tax routines stay where the owner keeps them, and the new view only makes the day easier to read. Each feed is tested against one real day of bookings before go-live.
Where the booking product offers an export or an interface, the view can pull the day's bookings directly. Where it does not, a scheduled export can fill the gap for a while. We confirm that path in writing first, because some vendors restrict what third-party tools can read.
Salons operate under state cosmetology board rules, and the oversight view should not hide or change any of them. The records that matter are sanitation logs, license dates for each stylist and patch test records for color products. Those should be easy to find during an inspection, without exposing client details to every user.
The owner should decide who sees guest histories, who can change a service price and who can view takings. Card data stays with the processor, and reports should show totals rather than individual card details. Staff who leave should lose access on the same day.
Every chair, the stylist booked into it and the next open slot, on one screen.
Calls to return, color tests to confirm and late cancellations to fill, each with an owner and a due time.
Sales, tips and bookings for the day, with a clear note when a payment is still pending.
A warning when a chair or stylist is double-booked, before the client arrives.
Breaks, days off and booked hours for each stylist, visible to the owner and to that stylist only.
An end-of-day summary the owner can review in a few minutes and share with the manager.
Hair salons peak around prom, wedding season and the holidays, and the calendar can fill in a single afternoon. The oversight view should flag chairs that are overbooked, stylists with no break in the afternoon and gaps that appear after a cancellation. A manager needs that information while the day is still open.
Quiet stretches after the holidays and during bad weather call for a different response. The view can show which services are underbooked and which stylists have room for new guests, so the manager can adjust promotions and the front-desk plan together rather than guessing.
Charts are the wrong place to begin. A takings graph built from duplicate bookings or unrecorded no-shows looks plausible and misleads the owner, so the booking data gets cleaned first.
The second is treating every role the same. Stylists need their own schedule and tips, the front desk needs the task list, and the owner needs the full picture. A view that shows all of it to everyone creates friction, and a view that shows too little hides problems.
Start with one location or one shift, and ask the front-desk lead to run the new view beside the usual whiteboard for a set period. When the day's figures match what the owner already knows, the rest of the team can switch over with confidence.
Train the owner and the lead receptionist first, using a real busy Saturday rather than a demo. Guests do not need to see the oversight view at all, but faster check-in and fewer missed callbacks will show up in their experience. Post-launch support can refine the layout once the owner has used it for a few shifts.
It often is, because a single owner usually carries the schedule, the books and the front desk in the same head. A daily view can replace a stack of notes and the end-of-day guesswork. The scoping call will show which views to build first so the owner gets value quickly.
Only with your permission. By default a stylist sees her own bookings and tips, and the owner sees the full salon view. The roles are written down before the build.
Bookings stay in the product the front desk already uses during an outage. The view marks its last successful sync, and entries made on a stylist's phone wait on the device until the link comes back.
Probably, because most point-of-sale products offer exports or an interface for sales data. We confirm the exact path during the scoping call before any design work starts. Where a connection is not practical, a daily export can carry the numbers for now.
A list of your stylists and chairs, the services you offer, the reports you already run and the day-to-day problems you want solved. A recent example of a busy day that went wrong helps us design the views. Scope and price come back in writing.
The first step is a free scoping call, and you keep the written scope and price afterwards.