Quick answer
A service business workflow is the complete path a job follows from the first customer request to operational completion. A practical workflow for small and medium service teams can use eight stages: New, Confirmed, Scheduled, Arrived, In Progress, Finishing, Ready and Completed. Each stage should describe a real condition, identify the next required action and be visible to everyone involved. Payment must be tracked separately because a job can be completed and unpaid, or paid before work begins.
What a service business workflow controls
A process describes how to perform one activity. A workflow connects several activities and handoffs into one operational path. Quoting is a process. Scheduling is a process. Completing a work order is a process. The workflow shows how a customer request moves through all of them without losing information or responsibility.
This difference matters because many service companies improve individual tasks while the overall job still breaks between them. The office may create an accurate quote, but nobody schedules the approved work. A technician may complete the service, but the photos and final notes never reach the person preparing the invoice. Each person performed a task, yet the job did not move cleanly.
A well-defined workflow makes the state of every job visible. It tells the team what has already happened, what must happen next and who is responsible. Managers can focus on exceptions because normal work follows a repeatable path.
Why eight stages work for service teams
Too few statuses hide important differences, such as a new enquiry versus confirmed work waiting to be scheduled. Too many statuses create hesitation and fragmented reporting because several labels appear to mean the same thing.
Eight stages provide enough detail for businesses with multiple handoffs while remaining understandable to office staff, drivers, technicians and owners. The stages can support on-site services, workshop services, pickup and delivery operations, cleaning companies, maintenance teams and other job-based businesses.
The wording may be translated or adjusted for a specific industry. The underlying condition of each stage should remain stable.
Stage 1 New
New means that a request or potential job has entered the business but has not yet been fully agreed.
The record should capture enough information to continue the conversation: customer identity, contact details, service address, requested work, source of the enquiry and any important notes or photos. The job does not need a final date, team or price at this stage.
The next action must be clear. Someone may need to call the customer, inspect the site, prepare a quote or ask for missing information. A new job without an owner or next action becomes a forgotten lead.
Stage 2 Confirmed
Confirmed means that the customer and the company have agreed on the service or on the next committed step. The scope, price or pricing method and relevant conditions should be sufficiently clear to reserve capacity.
For a simple residential service, confirmation may happen during a telephone call. A commercial job may require an approved quote, deposit or signed agreement. The workflow can support different confirmation requirements without changing the meaning of the status.
Stage 3 Scheduled
Scheduled means that the job has a working date, time or route position and the necessary people know about it.
Scheduling should connect the customer commitment with internal capacity. A date in a calendar is not enough if the assigned team cannot see the address, instructions or required equipment. Before moving the job to Scheduled, verify that the time is realistic, responsibility is assigned and essential job information is available.
Stage 4 Arrived
Arrived records the moment when the team reaches the customer location or when an item reaches the workshop. It separates travel and waiting from actual service time.
This stage is useful even when the company does not track detailed time. It gives the office a factual answer when a customer asks whether the team has arrived. It can also trigger the next internal step, such as intake inspection, condition photos or customer signature.
Stage 5 In Progress
In Progress means that the agreed work has started. The assigned team now owns the active execution of the job.
Employees should have access to the current scope, customer notes, site information, relevant history and any documents required to perform the work. Changes discovered during the job should be recorded before they disappear into a phone call or private message.
Managers should use this stage to identify exceptions, not to interrupt employees for constant updates. A job that remains In Progress beyond its expected duration may need attention. A job progressing normally should not require separate reporting.
Stage 6 Finishing
Finishing means that the main service has been performed but the job is not ready for final handoff. This stage covers the work that companies often forget to model: inspection, testing, drying, packaging, documentation, supervisor approval or correction of small defects.
Without a Finishing stage, teams face pressure to mark work Completed too early. That makes dashboards look clean while unfinished obligations remain hidden in memory or messages.
Stage 7 Ready
Ready means that the service is operationally complete and waiting for the customer or final logistics step.
For on-site work, Ready may represent customer review or signature. For workshop work, it can mean ready for collection. For a cleaning or restoration company, it may mean ready for delivery. This stage gives the office a clear queue of work that can now be handed over but has not yet left the company’s responsibility.
Stage 8 Completed
Completed closes the operational lifecycle. The service has been delivered, required handoff has occurred and the record contains the information the company needs to preserve.
Completion should not be used to hide work that still requires action. If a missing document, unresolved complaint or delivery remains, the job is not operationally complete. A clear closeout rule protects both the customer experience and internal reporting.
Completed jobs form the customer’s service history. That history improves future quoting, reduces repeated questions and gives new employees useful context.
Keep Paid and Unpaid outside the job stages
Payment status is related to the job but does not belong inside the operational sequence. The two dimensions answer different questions.
The job status answers where the work stands. Payment status answers whether the financial obligation has been settled. A customer may pay a deposit before the job becomes Scheduled. Another customer may pay an invoice thirty days after the job is Completed. Neither situation should distort the operational workflow.
Use separate fields for payment status, invoice status and, when required, payment method. This allows the owner to filter Completed and Unpaid jobs without changing them back to an operational status. It also prevents employees from assuming that Paid means the service is finished.
Define roles at the handoffs
Statuses become useful only when responsibility is clear. Each transition should have an owner and a minimum set of conditions.
An office manager may move New work to Confirmed after agreement with the customer. A scheduler may assign the date and team. A field employee can record Arrived and In Progress. A supervisor may control Finishing and Ready. The job manager can close the job after final handoff.
Small companies do not need a different person for every transition. One person may perform several roles. The value comes from defining responsibility, not from creating job titles.
Permissions should follow the same principle. Employees need enough access to complete their work, but they may not need to see unrelated customers, company-wide financial data or administrative settings.
Create rules for exceptions
Real work does not always move forward in a straight line. Customers postpone appointments, teams discover additional work and quality control may return a job from Finishing to In Progress.
Allow necessary backward movement, but record why it happened. Repeated backward transitions reveal problems in quoting, intake or execution. A cancelled job should use a clear cancellation field or outcome instead of disappearing from the system. A job placed on hold should include a reason and next review date.
Do not create a new status for every exception. Use notes, reasons, tasks or flags when the core operational condition has not changed. Status lists remain useful only while every team member understands them.
Implement the workflow in one working week
On the first day, map several recent jobs from enquiry to completion. Identify the real handoffs and the information that employees needed at each point.
On the second day, agree on the eight status definitions and the minimum conditions for each transition. Write one sentence for every status. If the team cannot explain the difference between two labels, simplify them.
On the third day, configure roles and job fields. Keep the first version small. Customer, location, service, assignment, date, notes and status are more important than advanced automation.
On the fourth day, test the workflow with realistic jobs on desktop and mobile. Include a postponed appointment, a change in scope and a completed but unpaid job.
On the fifth day, train the team using the same examples. Start using the workflow for new work and active jobs. Review problems after one week of real use before adding more fields or rules.
Measure whether the workflow works
A good workflow should reduce questions and make delays visible. Track practical indicators such as confirmed jobs waiting for schedules, jobs that remain In Progress beyond expectation, work waiting in Finishing, Ready jobs awaiting handoff and Completed jobs that remain unpaid.
The numbers do not need to become a complicated performance system. Their purpose is to show where work stops moving. When the same bottleneck appears repeatedly, change the underlying process or capacity instead of adding another status.
Soroby uses this eight-stage model to keep operational progress understandable across managers, office staff and field teams. The model is detailed enough to reflect real work while remaining simple enough to use every day.
Frequently asked questions
What is a service business workflow
A service business workflow is the connected sequence that moves a customer job from the initial request through confirmation, scheduling, execution, final preparation and completion.
How many job statuses should a service business use
Use enough statuses to represent meaningful handoffs without creating duplicate labels. Eight stages work well for many service companies, but a very simple business may use fewer if no important operational condition is lost.
Should invoiced and paid be job statuses
No. Invoicing and payment describe the financial state of a job, while operational statuses describe the work. Keep them connected to the job but track them separately.
Who should update a job status
The person closest to the relevant event should record it. Office staff may confirm and schedule work, while field employees record arrival and progress. A manager or responsible employee should control final completion.
Can a job move backwards in the workflow
Yes, when real work requires it. Record the reason so the company can distinguish normal exceptions from repeated process failures.