Skip to main content
    Proof
    Impress Blinds — cost per recorded Google Ads conversion down 62.63%SLS Solicitors — cost per recorded Google Ads conversion down 58.48%FixCare Property — cost per enquiry down 56.36%Rubbish Removal WA — cost per enquiry down 53.18%Floral Cakery — cost per enquiry down 49.82%ILLUMINATE Laser Emporium — cost per enquiry down 48.54%Aussie Plumbing — cost per enquiry down 41.96%Sydney Fence Painting — cost per enquiry down 33.68%Alliance Plumbing — cost per enquiry down 29.6%Gridless Build Solutions — cost per enquiry down 29.16%FacilityWorx — cost per enquiry down 23.62%Cornerstone Roofing — cost per enquiry down 20.47%Council finance — budgeting and workforce designCouncil planning — clearer approvals and reportingCultural audiences — media strategy and creative conceptsCommunity participation — surveys, maps and project pagesPublic-sector research — survey design and analysisPublic art — site studies and visual conceptsRegional identity — visitor guides and wayfinding conceptsCouncil systems — integration and migration planningA pressure washing business — service-led search campaignsA pressure washing business — a clear enquiry journeyA carpet cleaner — Google Ads built around cleaning servicesA roofing company — campaigns for repairs and restorationA CCTV installer — campaigns for security enquiriesA fence painter — search campaigns for specific surfacesA maintenance business — live in 8 weeks, 3 stacks gone41 numbered clauses, published in full5.0 across every Google review$120M+ in media under management250+ active engagements across five countries
    SoudCoh
    Government & Public Sector

    Design bookings and visits around the whole service

    A booking, visit or delivery is a sequence of practical tasks. Someone requests the service, staff prepare for it and both sides need to handle changes. Designing those steps together gives an operational system a clear purpose and helps reveal where a simple screen hides a complicated process.

    • 23 September 2026
    • 3 min read
    Booking, visitor and service operations: understand the task, then design the journey, then check it with people.
    An example approach for a community meal service.

    The steps

    Follow the service beyond the booking screen

    A practical sequence for a community meal service.

    RequestUnderstand the ordering journeyPrepareConnect the staff tasksCompleteInclude changes and exceptions

    Request

    Map how people choose, submit and change an order. Agree the information staff need before work begins.

    Ready for the next stepA defined public request

    Prepare

    Work through preparation, purchasing and delivery requirements with the responsible team. Food and nutrition rules need approval from the relevant specialists.

    Ready for the next stepA practical staff workflow

    Complete

    Test service confirmations, delivery changes and unresolved requests with a small group. Plan the staff guidance and review needed before wider use.

    Ready for the next stepA pilot and training plan

    Look beyond the initial request

    Follow the service through preparation, arrival or delivery, completion and any follow-up. A booking may require equipment and staff time. A visit may need host confirmation. A meal order may affect preparation quantities and a delivery run.

    Use one ordinary example to expose those dependencies. Ask the people doing the work what changes during the day and which information they need before they can proceed. The result should explain how the service operates, not merely reproduce the fields from the current booking form.

    Put service rules into plain language

    Write down the rules that affect the experience. These may include notice periods, availability, required documents, delivery windows or who can approve a change. Confirm them with the responsible team before using them to design software behaviour.

    Separate a firm rule from a local habit. A process may exist because an old system could not support a better option. Conversely, a rule that looks inconvenient may protect an important service obligation. Understanding the reason helps the team decide what should remain, change or receive specialist review.

    Design for the staff working in the field

    The person at a desk may have time and a large screen. A driver or visiting staff member may need a short, clear task view on a phone. Show the information needed at that stage, such as the next stop, relevant instructions and how to record a problem.

    Consider changes as well as completion. Staff may need to report an unavailable recipient, an incorrect address or a task that cannot proceed. The design should make that information useful to the person who must decide what happens next.

    Keep professional decisions with specialists

    Some operational settings involve food, nutrition, workplace safety or site access. The software can organise information and support an agreed process, but the organisation’s responsible specialists need to validate the rules and content.

    For a community meal service, the design might connect ordering, production reports and delivery information. Nutrition advice, allergen decisions and service eligibility require the appropriate professional review. Make those responsibilities explicit in the project brief so a convenient interface is not mistaken for independent assurance about the underlying service.

    Pilot a complete service journey

    Choose a small operational scope and test it from the customer’s request through to completion. Include a change, a cancellation and a failed task. Check whether staff can explain the current state without reconstructing it from several messages.

    The useful outputs are a service map, public and staff screen designs, practical operational reports and a training plan. Review the pilot with the team before expanding it. The findings should show whether the proposed process fits real work and which details need further attention.

    Explore our Booking, visitor and service operations, related services and Replace scattered requests with a useful service portal.

    What to do next

    Talk to SoudCoh about the service question, the people involved and the outputs your team needs.
    Talk to SoudCoh
    Read next

    Three more from the index.

    Filed under the same desk first. The full index is searchable and filters by reader.

    If you would rather we just did it.

    The briefing above is the reasoning. These are the pages that describe what it looks like as a piece of paid work, including what it costs and what gets reported.

    • Booking, visitor and service operations — Design the whole operational journey around a visit, booking or delivered service. Public-facing steps are connected to the staff tasks behind them, including preparation, changes and completion. Practical service rules, clear information and exception handling guide the design before a full rollout.

    • Explore Booking, visitor and service operations — Explore the people, scope and practical outputs involved.

    All 86 briefings

    Apply it to your account

    Reading it is the easy half. Thirty minutes with someone who runs accounts and you leave with a written list of what is leaking on yours — yours to keep either way.

    Get that list for your accountSee real client wins

    No pitch deck. No upsell. A real conversation and a written list of leaks.