Home · Solutions · Operations & quality
Solution · Operations & qualityThe client fills in the declarations on his sofa at home, not on his knee in the lobby
Lane bookings and declarations before entry
A robot ties a lane booking to the complete formalities: after booking it sends the rules and declarations to fill in, reminds, and on the day staff see a list of who is ready to enter. The slot starts on time, because the paperwork happened earlier.
Executive summary
Bookings arrive by phone, email and social media, and the formalities happen at the door: declarations on knees, rules read in a hurry, the queue grows, the slots slip.
After booking, the client gets a link: the rules, the required declarations and the entrants’ details are completed before the visit; the robot reminds, and shows staff who is ready and who is missing.
Slots start on time, staff run the shooting instead of the paperwork, each visit’s documents live in one place, and the owner sees lane utilisation in numbers.
the booking calendar (Microsoft Bookings); declaration forms (Microsoft Forms); a visit register in SharePoint; the entry list in Microsoft Teams
Business problem
Paperwork in the lobby
A range sells lane time, and lane time is indivisible: a slot that started twenty minutes late will not give those minutes back in the evening. Yet the entry procedure, right and necessary, because safety comes first here, happens at the worst possible moment: when the client is already in the door and his slot is already running.
Declarations filled in on site are not just a delay. They are also quality: fields completed in a rush come out illegible or empty, and with a corporate group of eight the range officer turns into a clerk for a quarter of an hour. The declarations binder swells, and finding the documents of one visit from six months ago is an hour’s work.
Bookings come from everywhere: a phone call during a session, a message on the social profile, an email. Some never reach the calendar, some reach it twice. Then there is staffing: which instructor is qualified to run which kind of session, and whether he is free at all, gets checked in someone’s head, at the last minute.
At month end the owner knows what came in, but not how the lanes worked: which hours stand empty, which burst at the seams, how many slots started late and how much of that time was even sellable. The price list and opening hours are set by feel.
How it works today
Below is what the work looks like before anything is automated.
- PersonBookings arrive by phone, email and social media; someone retypes them into a calendar, sometimes twice
- WaitingFormalities begin when the client is in the door and his paid slot is already running
- PersonThe range officer hands out pens and explains the rules instead of watching the lanes
- Risk of errorDeclarations filled in a hurry come out illegible or incomplete; it surfaces after the fact
- PersonInstructor staffing against qualifications is checked in someone’s head, at the last minute
- Risk of errorNobody counts delays or utilisation; prices and hours are set by feel
Why the current process costs more than it appears
The bill that never shows up in a budget.
- Twenty minutes of slot delay is a third of its value handed to paperwork; on a full evening that is a real, daily cost.
- A range officer working as a clerk is the most expensive possible use of a qualified person.
- An incomplete declaration comes to light exactly when it is needed, which is too late.
- Bookings from four channels without one calendar end in an empty lane or a double-sold slot; both variants cost.
Cost of inaction
The first row counts staff time alone: the minutes a qualified person spends handing out forms instead of running sessions. The second is cautious and counts only delays that genuinely shortened sold lane time at peak hours.
The model does not price the risk of incomplete declarations, because that cost appears rarely and abruptly. It prices order: each visit’s complete documents in one place, findable in a minute.
A model organisation with realistic proportions – the numbers exist so you can run the same maths on your own data; they are not a client result.
A sports shooting range: six lanes, three instructors on shifts, an accessories shop, bookings by phone and social media, Microsoft 365.
Around 380 booked slots and 950 entries a month; evenings and weekends full, mornings empty.
Declarations and rules at the door, on paper; corporate groups take 20-30 minutes to enter; documents in binders by year.
Instructor staffing arranged in someone’s head; a slot without a properly qualified person happens.
After every booking the robot sends a link with the rules and declarations for all entrants, reminds a day before, and on the day staff see the entry list in Teams: ready, missing, notes; the visit’s documents land in the register; the instructor rota is checked against qualifications at every booking.
In the modelled case, paperwork at the door falls to a minute per person, delays all but vanish, and the owner gets weekly lane utilisation per hour. Model numbers, not the range’s records.
Proposed solution
We start with your entry procedure: which declarations are required for which kind of session, what every entrant must complete and what suffices once a year, how a corporate group enters, and who may run which sessions. We write it down once; from then on the system keeps it, not memory.
A booking, whatever the channel, lands in one calendar. The client gets a message with a link: rules to read, declarations to fill in, entrants’ details to complete. The robot reminds those who have not finished, and shows a group’s organiser which of his people are still behind. On the day, staff see a simple list: who is ready, who is not, what remains to collect on site.
Each visit’s documents are stored in a register tied to the booking: a year later they surface in a minute, not in a binder. Instructor staffing is checked against qualifications automatically at every booking, and the owner receives weekly lane utilisation per hour and day, the basis for pricing and opening-hours decisions.
UiPath Orchestrator: a booking queue, reminder schedules, retries and an audit trail; UiPath Integration Service connectors for Microsoft Teams, Outlook 365 and SharePoint; Microsoft Bookings and Forms
A versioned entry procedure, the declaration set per session type, reminders, the staff entry list, staffing qualification checks and a weekly utilisation report
The booking calendar in Microsoft Bookings; forms in Microsoft Forms; the visit and document register in SharePoint; an SMS gateway via API where email is not enough
How the automated process works
- SystemA booking from any channel lands in one calendar with session type and headcount
- AutomationThe client gets a link: rules, declarations, entrants’ details; the robot reminds the unfinished
- AutomationA group’s organiser sees which of his people are behind; nudges go out by themselves
- PersonOn the day staff see the entry list: ready, missing, notes to collect on site
- SystemThe visit’s documents land in a register tied to the booking; findable in a minute
- PersonThe owner gets weekly lane utilisation per hour and day
Human-in-the-loop model
Automation handles
- The complete pre-visit formalities: sending, reminders, per-person completeness checks
- The staff entry list and the document register of every visit
- Staffing checks against qualifications and the weekly lane utilisation report
People decide
- The entry procedure: which declarations, for whom, how often; the rules and their changes
- The shooting itself: supervision, safety and every decision on the firing line stay entirely with people
- Pricing and commercial decisions built on the utilisation reports
Before and after
Systems and integrations
The stack is short on purpose: one engine, one execution layer, one place where a person decides.
Inputs
- the booking calendar (Bookings)
- declaration forms (Forms)
- entry procedure rules and instructor qualifications
- group and entrant details
Automation layer
- UiPath Orchestrator
- UiPath Robots
- UiPath Integration Service
- UiPath Action Center
Target systems
- complete document sets per visit in the register
- the staff entry list in Microsoft Teams
- the weekly utilisation report for the owner
Human touchpoints: the entry list in Microsoft Teams; a weekly utilisation report; an entry procedure review at every rules change
Technologies used
the booking queue, reminders, retries, a record of every document set
Athe entry list, nudges, register writes
Aone lane booking calendar with a native API inside Microsoft 365
Adeclarations and entrant details completed before the visit
Areminders where email does not work; we use your gateway
BIllustrative economic model
Numbers you can check against your own data.
The model assumes the formalities do not vanish but move ahead of the visit; exceptions remain on site. Volumes and rates belong to the scenario; your own numbers go into the calculator alongside. Safety rules and supervision on the firing line remain entirely in human hands.
Run the maths on your data
An illustrative estimate based on your inputs. It models freed capacity, not promised savings.
Business benefits
- Slots start on time; the client shoots during the time he paid for
- Instructors run sessions instead of handing out pens
- Each visit’s complete documents live in one place, findable in a minute
- Corporate groups enter smoothly, which you hear later in the referrals
- The owner sees lane utilisation in numbers and prices on top of them
The management view
- The entry procedure stops depending on staff reflexes; it is the same every Tuesday and every Saturday
- Visit documentation is complete and ordered before anyone asks for it
- Capacity grows without building lanes: the same hours sell more fully
Board-level KPIs
slot start delays · group entry time · document sets complete before the visit · lane utilisation per hour · time to find a visit’s documents
Security and governance
The automation has exactly the permissions it needs. Not one more.
- The robot works on a minimal data scope: name, contact, booking and formality status; the declarations’ scope is set by your procedure
- Visit documents live in a register with permissions; staff have access, not everyone
- Every send and reminder has a record: what, when, to whom
- Forms and rules are versioned; only an authorised person changes them
- Data stays in your Microsoft 365 tenant; the robots run in the EU region of UiPath Automation Cloud
Why now
Recreational shooting is growing, and the first-time client compares you with every other pastime where he books and signs online.
Corporate groups are the most valuable segment and the most sensitive to entry friction; word of mouth works both ways.
The cost of a qualified person’s hour keeps rising; spending it on paperwork has stopped adding up.
Relevant executive roles
Lanes sell more fully, and pricing and hours decisions finally have numbers underneath
Runs the shooting and the safety, not the forms and the pens
Sees a list of ready entries instead of a queue holding a stack of paper
Common questions and objections
He does, and he gets it, only shorter: the briefing and supervision remain whole, what disappears is copying out details and reading the rules in the lobby. Formalities done at home cut the entry from a quarter of an hour to minutes, and the instructor starts with shooting, not with a binder.
And they still can. Walk-ins get a short on-site path: a tablet with the same form instead of a sheet of paper. The register still gets a complete set, and the entry list simply grows by a row.
If you decide so, or your procedure requires it, paper stays: the pre-visit form collects the data and confirmations, and on site the client signs a ready, printed document instead of filling it in from scratch. That alone cuts entry time severalfold, and the register ties the scan to the visit.
When this is not the right solution
- A club range with a handful of regulars and no commercial traffic: a calendar and a folder suffice
- No agreement to any electronic calendar: first one booking book, then automation
- Expecting automation of the shooting itself: supervision, safety and firing-line decisions stay with people
A question for the next management meeting
How many minutes of paid lane time did we hand to doorway paperwork last month?
Implementation approach
Scope without ambiguity, before anything is signed.
We deliver
- A written, versioned entry procedure: declarations per session and entrant type
- Bookings in one calendar and formalities completed before the visit
- The staff entry list and the document register of every visit
- Instructor staffing checks against qualifications
- A weekly lane utilisation report and two weeks of parallel running
We need from you
- Your rules and declaration templates in their current shape
- The instructor list with qualifications per session type
- A decision which formalities can go online and which stay on paper
Stages
Discovery
The entry procedure today: documents, timings, delays, booking channels
Rules
Declarations per session type, the group path, the walk-in path, qualifications
Build
Bookings, forms, reminders, the entry list, the register, the utilisation report
Parallel run
Two weeks: the system works, paper runs alongside, we compare entry times
Go-live
Full traffic with a numbers review after the first month
A quick win. Everything runs on the Microsoft 365 you already have; the only new element is an optional SMS gateway for reminders.
Friday, 6 p.m.: eight people from one firm in the lobby, one pen, and lane three stands paid for and empty.
Describe your entry to us: how many slots a month, how long a group takes to get in, where last year’s declarations live. We return the arithmetic of the minutes and a draft of an entry procedure without the queue.
Count your slot delaysThe neighbouring process usually has the same problem
Only one person can read the notebook at the counter, and questions about stock arrive unannounced.
See the solution Legal & complianceMember licences and certificates under controlThe licence expired in March, and the member shot in April. Who was supposed to catch that?
See the solution Management & planningUtilisation of lanes, rooms and studios, weeklyEvenings burst at the seams, mornings stand empty, and the price list has been one for years.
See the solutionIndustries where we deploy this most oftenSmall business & services