Back to concept work

Concept project · Field service

One connected view
from request to
ready for review.

FICTIONAL SCENARIO · PROPOSED SOLUTION

A product concept exploring how a field service business could coordinate customer requests, technician visits, operational review, and invoice preparation.

Designed for
Service desk, coordinators, technicians, operations, and accounts
Core idea
Keep every handoff attached to one job record
THE WORKING PRINCIPLE

Software should make the state of the work clear—especially when something needs a person’s attention.

The situation

The real problem is rarely
one missing feature.

01

Requests arrive in different places

Email, calls, and messages create separate starting points and repeated data entry.

02

Ownership is difficult to see

Coordinators need a reliable view of who owns the next action and what is holding it up.

03

Visit details become disconnected

Notes, materials, and customer context can be separated from the original request.

04

Billing waits for missing context

Accounts cannot prepare an accurate draft until completed work has been reviewed.

These are working assumptions for the concept. A real engagement would begin by observing the actual workflow.

Proposed workflow

Six handoffs.
One shared record.

  1. 01

    Capture

    Create one job record from the incoming request.

    Service desk
  2. 02

    Assign

    Choose an owner with the right skill and availability.

    Coordinator
  3. 03

    Schedule

    Confirm a visit and keep the customer informed.

    Coordinator
  4. 04

    Complete

    Record work, materials, and exceptions at the site.

    Technician
  5. 05

    Review

    Check the completed record before preparing billing.

    Operations
  6. 06

    Prepare

    Create an invoice draft for human approval.

    Accounts

Product direction

Show the next decision,
with the context to make it.

Three representative views demonstrate the system’s hierarchy. They are interface concepts, not screenshots of a released product.

OperationsCONCEPT VIEW · FICTIONAL DATA
Tuesday, 14 May

Work needing attention

3 active exceptions
Visits today086 confirmed
Awaiting assignment03Oldest: 42 min
Ready for review05Before billing
Priority queueOwnerStatus
Visit needs a new timeJOB-1042 · North district
Maya K.Review
Technician assignment missingJOB-1048 · Equipment repair
DispatchAssign
Completion notes readyJOB-1039 · Annual service
OperationsCheck
01 · OPERATIONS OVERVIEW

Exceptions appear before general activity so coordinators know where intervention is needed.

JOB-1042

Equipment maintenance

Visit in progress
Alex Morgan North district Tue, 10:30
  1. Request capturedService desk · 09:12
  2. Technician assignedMaya K. · 09:26
  3. 03
    Site visitWork notes pending
  4. 04
    Operational reviewAvailable after completion
Current responsibility
MK
Maya KhanField technician
Next expected actionAdd completion notes and materials used.
02 · CONNECTED JOB RECORD

Ownership, visit state, and the next expected action remain visible in one place.

Draft invoice

Prepared from reviewed work

DRAFT · NOT SENT
Source: JOB-1042Completion record reviewed by operations
Maintenance visit1 × £—
Replacement component1 × £—
TravelIncluded

Requires accounts approval before sending.

Review draft
03 · CONTROLLED HANDOFF

Reviewed work can prepare a draft while financial approval remains with a person.

Design decisions

Clarity is part of
the operating model.

Each decision reduces ambiguity around the record, the owner, or the next action.

  1. 01

    One job record

    Customer details, ownership, appointments, notes, and billing context stay attached to the same piece of work.

  2. 02

    Visible responsibility

    Every stage names the person or team expected to move the job forward.

  3. 03

    Exceptions before averages

    The operational view prioritises work that is blocked, late, or waiting for a decision.

  4. 04

    Human approval stays explicit

    The system prepares an invoice draft. It does not send financial documents without review.

Expected value

What this direction
could improve.

These are intended operational benefits, not measured client results. Validation would require real workflow data and user testing.

Start with the workflow

Have an operation
that feels disconnected?

Tell us where work slows down, gets repeated, or loses ownership. We’ll start by understanding how it works today.

Discuss your workflow hello@visionxsystems.com