Operations
Part of From signed franchise agreement to controlled daily operation
A franchise operating workflow from opening checks to close
Build a franchise operating workflow from opening checks to close, with clear handovers, exception routes, evidence records and review triggers.
An operating workflow should tell a new site manager what starts each task, who owns it, what proves completion and when normal work must stop. Begin with one complete trading day rather than copying headings from a franchise manual. The manual supplies brand requirements; the local design must also reflect the English premises, permissions, staff and systems.
What to take away
- Put risk controls inside routine and non-routine steps, including deliveries, maintenance and cleaning.
- Limit independent work until the relevant tasks have been witnessed and approved.
- Rehearse missing staff, rejected payments, unavailable products and system loss before they happen.
Prepare the workflow card
Choose one transaction or service and record its beginning and end. For a booked service, that might run from confirmed appointment to payment, customer record and follow-up. List the inputs needed at each stage: trained person, stock, equipment, customer information, system access and authorisation.
Six fields beside every step
- Ownerwho is accountable
- Backupwho covers absence
- Time or triggerwhen it starts
- Expected outputwhat good looks like
- Evidencewhat is recorded
- Exception routewho decides deviations
Beside every step, add six fields: owner, backup, time or trigger, expected output, evidence and exception route. Confirm external permissions through the GOV.UK Find a licence service, then contact the issuing council or regulator about conditions and renewals. The search service warns that its list may be incomplete, so a blank result is not an approval to operate.
For typical franchise sectors in England, the local council is the licensing authority: environmental health for food businesses, licensing for alcohol and late night refreshment, and trading standards for age-restricted sales.
A worked card for a booked service shows how the fields read in practice. This is an illustrative example.
Field / Entry
- Owner
- Duty stylist
- Backup
- Senior stylist on shift
- Time or trigger
- 09:55, five minutes before the appointment
- Expected output
- Customer confirmed, chair and tools ready
- Evidence
- Appointment record updated; shift log entry for any change
- Exception route
- If the customer has not arrived by 10:10, call the booking number and log the outcome
Walk the day in sequence
- Accept the handover.The duty manager reads open incidents, unavailable items, staffing gaps and restricted equipment before taking control. Anything affecting safe or lawful service gets a named decision.
- Open the site.Check access, critical equipment, emergency arrangements, cleanliness, stock exceptions and system connections. Each failed item should point to a pre-agreed response, such as isolating equipment or limiting the service.
- Control the live queue.State how work is prioritised, who can approve deviations and how the customer is informed. Record exceptions at the moment they occur in an exception register instead of reconstructing them at close.
- Complete and reconcile.Match the customer request, delivery, payment and required network record. Corrections need a reason and author rather than a silent overwrite.
- Close and transfer.Reconcile controlled stock or capacity, payments, unresolved complaints, safety events and system faults. Give each carry-over an owner and due time; the next shift explicitly accepts it.
Put risk controls inside the steps
HSE's risk-management sequence covers hazards, assessment, controls, written findings and review. Use it on routine and non-routine work, including deliveries, maintenance and cleaning. If a control depends on a person noticing something, describe what they look for and what they do next.
Ask frontline staff to walk through the draft. They often see collisions between the written order and the actual layout. Observe a rehearsal, record where people hesitate or create workarounds, then amend the step or provide the missing resource. A signed sheet is weak evidence if the process cannot be demonstrated.
Connect competence and system access
Acas explains that induction gives a worker the information needed to understand the role and is separate from probation. Turn that purpose into role-specific observation: show, practise, observe, approve. Limit independent work until the relevant tasks have been witnessed.
Issue unique accounts only after the access level is approved. The NCSC's small-business cyber guidance covers protected accounts, devices and backups. Prepare a paper or offline route for approved tasks during an outage, and name the activities that cannot safely continue.
Test the exceptions
Rehearse a missing employee, rejected payment, unavailable product and loss of a key system. Time the contact route, verify who may pause trading and confirm what record is preserved.
Worked exception, declined card payment. At 14:05 a card payment is declined. The supervisor calls the customer within 10 minutes, offers an alternative payment method and records the decline, call time and outcome in the exception register.
That entry reads: 14:05 payment declined; 14:15 customer called; outcome alternative payment agreed. The transaction record and terminal receipt are kept with the shift log.
Review the workflow after any incident, near miss, material promotion or equipment change. The finished procedure is the shortest reliable path through real work, including when the normal path fails.
Before you act
- Choose one transaction and record its beginning and end.
- Confirm external permissions with the issuing council or regulator.
- Walk frontline staff through the draft and observe a rehearsal.
- Issue unique accounts only after the access level is approved.
- Review the workflow after any incident, near miss or equipment change.
Common questions
How should a manager start writing an operating workflow?
Pick one transaction or service and map it end to end. The brand manual sets the standard, while the local card records the site permissions, staff and systems that shape each step.
What should be recorded beside every step of the workflow?
Each step needs an owner, a backup, a start signal, a finished output, a record and a route for when the step fails. A single table or card keeps those entries together.
How should a site test its exception routes?
Run a short rehearsal for a missing worker, a declined payment, an out-of-stock item and a system outage. Time the escalation, confirm who can pause work and check that the record survives.
