Live work queue
Every booking request, trial and event day sorted by time, venue and status, so nothing sits unassigned.
A makeup studio with several artists often runs on a shared calendar, a group chat and a manager's memory. This manager oversight app for makeup artists puts the work queue, staff assignments and reporting in one view, so the general manager can see the whole day before it starts.
A makeup business with several artists usually runs on a shared calendar, a group text for same-day changes, and a manager who carries the rest in her head. A bridal party of six may need a lead artist at a hotel suite at seven and two assistants at a separate venue by eight. Each booking is correct on its own, but the day only works if someone checks travel and the kit list before the van leaves.
Breakdowns cluster around three moments. The first is a request that arrives in a direct message late in the evening and is not logged until the next morning. The second is the reassignment: when an artist is sick, the replacement learns about the job from a forwarded screenshot. The third is the end of the day, when hours, products used and any overtime are typed up from memory.
None of these are rare. They are the ordinary friction of a team that grew out of one artist with a phone. A useful first step is to list every place the day's jobs are recorded today, then mark which of those places the manager actually checks each morning.
Clients rarely interview the whole team. They look at the lead artist's portfolio, check that the studio replies quickly, and ask whether a specific date is open. For a wedding, the bride's family often wants one named contact who can answer questions about call times and who is coming to the venue.
That makes the manager the face of the business during booking, even when an assistant does the hands-on work. A clear view of who is confirmed for each date, and what was promised about travel and kit, lets her answer in one message instead of checking three calendars. The app should therefore focus on confirmed jobs and open requests rather than a public booking page.
For this project, the decision rule is simple: what does the manager need to see before she says yes? We would design the screens around that answer and keep client-facing features limited to confirmations and changes.
Picture a general manager who oversees four artists and a rotating pool of assistants. She opens the app before seven and sees the day's work queue sorted by call time. Two bridal parties are confirmed, and one prom request is marked as waiting for an answer, so she knows what needs her attention first.
She drags an assistant onto the second bridal party after checking that the assistant's previous job ends with enough travel time. A notice goes to the team, and the client confirmation is sent automatically. Later, an artist texts that she is running late. The manager moves the job to the reserve artist in one step, and the client receives the new arrival window without a phone call.
Every booking request, trial and event day sorted by time, venue and status, so nothing sits unassigned.
Match each lead artist and assistant to a bridal party or event based on availability and travel time from the last job.
When an artist is ill or delayed, move the job and notify the client without re-entering any details.
Track foundation shade counts, lash supplies and touch-up kit restocks, with low-stock prompts before a busy weekend.
A weekly view of bookings, cancellations and hours per artist, exported for payroll or your accountant.
Owners, managers and assistants each see only the jobs and client notes their role needs.
Many makeup businesses already use a beauty booking tool such as Vagaro, Fresha or Booksy, and many keep payroll and invoices in QuickBooks or a payroll service. We would first confirm which of these your team relies on each day. The real question is whether the oversight app should read from that calendar, sit beside it, or replace parts of it. The answer changes the build, so it is settled in the scoping call.
Teams that do not use a booking product often keep one shared Google Calendar or Outlook calendar. Portfolio photos usually live in a cloud folder or on individual phones, which makes file access rules as important as the screens. We would list each data source in the scope document so there is no guesswork about where information comes from.
Client skin notes, allergy flags and photos of faces are sensitive details, even though a makeup studio is not a medical practice. We would limit who sees those notes, log who opened them, and keep photos behind a per-client consent flag. Your own counsel should confirm which state privacy rules apply to your client base.
Payments need the same care. The app should not store full card numbers. Deposits and final payments go through a processor such as Stripe or the payment tool you already use. If artists are freelancers, job logs should be exportable for your accountant without exposing any client notes.
Before the build starts, we need a current list of artists and assistants with their roles, plus the rules that decide who can confirm a job. We also need sample bookings from the last two months, including at least one that went wrong, so the reassignment screen reflects how the team really works. Kit lists, standard looks and travel-time rules help too, even when they are rough.
On the access side, we need an admin account for setup, login details for any booking calendar if an integration is in scope, and one named person who approves the wording of client messages. We prefer access to be granted inside the app and removed when someone leaves the team, rather than passed around by email.
Each booking records its venue, call time and expected finish. The assignment board checks each artist's existing jobs and the travel time from the previous venue, and flags conflicts before anyone is confirmed. We agree on the travel-time rule during the scoping call.
The first release focuses on scheduling, work queues and reporting. Payments and contractor forms stay in the payroll or accounting software you already use, and we would connect to it only if the written scope includes that link.
Your business owns the records. Access is granted per user and removed when someone leaves the team. We would confirm the export steps in writing during the build, so the data can move with you.
Decide which jobs the manager must approve and which the lead artist can assign alone. That one rule shapes most of the screens, so it is settled before any design work starts.
A free scoping call maps your team's current workflow first, and the written scope and price follow after that.