Operational design
From Enquiry to Completed Job: Where Trade Business Admin Actually Builds Up
A step by step breakdown of a typical service job showing where information gets copied, chased, lost or disconnected.
A single job can look simple from the outside. The customer asks for work, receives a price, books a date and the job gets done. Inside the business, the same job can pass through a surprising number of separate steps.
The problem is not that each step is difficult. It is that information often gets recreated at every stage.
Step 1: the enquiry arrives
The customer sends a form, email, WhatsApp message or phone call. Somebody records the name, address, contact details and job description. If that information is later typed into another system, duplication has already started.
Step 2: the job is qualified
The business checks location, job type, timing and whether more information is needed. Photographs may arrive separately. Notes may remain in an inbox or on a phone rather than following the job.
Step 3: the quotation is created
Customer details and job information are copied into a quotation. Prices are added. Terms and optional items may be included. The quote is sent and somebody has to remember whether it has been viewed, queried or approved.
Step 4: approval becomes a booking
Once approved, the same address, job description and customer details may be copied into a diary, job management system or spreadsheet. The customer gets another confirmation.
Step 5: the field team needs the job information
Engineers or installers need the latest scope, access notes, contact details, documents and dates. If that information is assembled manually before every visit, the office becomes the connection between systems.
Step 6: information comes back from site
Photographs, notes, measurements, forms and changes are created during the job. If they return through different channels, somebody has to match them back to the correct customer and project.
Step 7: completion creates another admin chain
The business may need to send completion documents, update the customer, trigger invoicing, archive photographs, request a review or schedule follow up work.
Where the admin actually builds up
The biggest burden usually appears at the handoffs. Enquiry to quote. Quote to booking. Office to field. Field back to office. Completion to accounts. Every handoff is a chance for information to be copied, delayed or lost.
The goal is not one enormous system
A connected system does not have to replace everything. It may simply make sure customer and job information can move between the parts that already work. An API, data feed, integration or small bespoke tool can sometimes remove more friction than replacing an entire software stack.
Map the real process before buying software
The useful starting point is to write down what actually happens from first enquiry to completed job, including the awkward workarounds people have stopped noticing. Once the process is visible, it becomes much easier to decide what should stay manual and what could be connected.