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

    Replace scattered requests with a useful service portal

    A service portal should make a request easier to submit and easier to handle. That requires more than putting an existing paper form online. The useful starting point is the full journey: what someone asks for, what staff need to review and how the result is communicated.

    • 23 September 2026
    • 3 min read
    Custom business portals and workflow software: understand the task, then design the journey, then check it with people.
    An example approach for a team reviewing applications.

    Side by side

    Design a request process people can follow

    A planning example for a team reviewing applications.

    Scattered requests

    • Documents arriving in separate inboxes
    • Unclear responsibility for the next step
    • Exceptions handled outside the shared record

    A coherent workspace

    • An application record with the relevant documents
    • Visible stages, responsibilities and deadlines
    • Ordinary and exceptional cases included in testing

    Prototype the smallest useful journey with the staff doing the work, then agree acceptance tests and an operating guide.

    Map one request from beginning to end

    Choose a common request and follow it through the current process. Note what information is collected, who checks it and where work waits. Include the emails, documents and informal clarifications that do not appear in the official process description.

    For example, an application may look complete to the person submitting it but still require a missing attachment before review can begin. That gap belongs in the design. A process map should show both the public experience and the staff work required to reach a decision.

    Define the record before the screens

    Agree what needs to be kept together for each request: the form, supporting material, responsible team, current stage and relevant correspondence. Decide which details can change and who is responsible for keeping them accurate.

    Then design screens around the decisions people make. A reviewer needs to understand what is ready, what is missing and what to do next. An applicant needs a clear explanation of the request and its status. Those views serve different purposes even when they refer to the same underlying matter.

    Make responsibilities and exceptions visible

    Most processes have a straightforward path and several ordinary exceptions. A request may be withdrawn, returned for clarification or moved to another reviewer. Design those situations deliberately instead of treating them as unusual problems to solve after launch.

    Use status labels that staff and applicants understand. A deadline view can help a team manage work, but the responsibility for interpreting any legal or policy requirement remains with the appropriate officer. The portal should support that judgement with clear information and a record of the action taken.

    Test with realistic cases

    A demonstration often shows a perfectly completed request. User testing should also include missing information, a duplicate, an amended document and a request that needs another team’s input. Ask staff to complete real tasks rather than simply comment on the appearance of the screens.

    Record the problems and decide which must be resolved before wider use. Check the public journey on a phone and the staff journey under normal working conditions. The aim is to find where the process remains confusing, even when the software appears to function correctly.

    Handover the working process

    A useful delivery pack includes the process map, accepted screen behaviour, staff guidance and a support arrangement. Explain how changes will be considered as the service develops. A new form field, for instance, may affect review steps and reporting as well as the public screen.

    Start with a manageable service where the team can test the complete journey. A successful pilot provides evidence about the next stage: which elements can be reused, which need adjustment and what support people need to work confidently with the portal.

    Explore our Custom business portals and workflow software, related services and Design bookings and visits around the whole service.

    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.

    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.