BranchFlow

For field-service teams

The job finishes where there is no signal.

Technicians complete work offline, with photos, and it syncs when they are back in coverage. Scheduling shows workload and skills before you commit to a time.

What we can state plainly

The product is the same in every industry. Only the examples change, and nothing here is industry-specific marketing.

  • Reports and checklists complete offline and sync with duplicate protection.
  • Suggestions consider skills, workload and availability, but a person assigns.
  • Parts consumption is recorded as a permanent stock movement.
  • Proof of work is captured at the site and verified afterwards.

How a typical problem runs

  1. 1

    Job created

    From a customer request, a plan or a failed check.

  2. 2

    Scheduled

    Skills, availability and existing workload are visible before assigning.

  3. 3

    Completed on site

    Steps, readings and photos recorded, with or without a signal.

  4. 4

    Verified

    A second authorised person accepts the completed work.

What you use most

  • Offline completion

    Queued records with compressed photos that upload after reconnection.

  • Skills and availability

    Per-person skills and working availability kept up to date.

  • Van stock

    Parts held per location with transfers and consumption recorded.

  • Dependencies

    Mark work that cannot start before another job finishes.

The screens behind this page

Every entry names a real screen in the application and its state today.

  • /offlineAvailable today

    Field mode with queued reports and checklist completions

    Available today: work continues without a signal and syncs later.

    Data shown: Sample queued records

  • /scheduleAvailable today

    Workload, skills and availability used for assignment suggestions

    Available today: suggestions only. A person still makes the assignment.

    Data shown: Sample week of planned work

  • /inventoryAvailable today

    Stock levels, counts, waste, transfers and purchase requests

    Available today: stock movement is kept as a permanent record.

    Data shown: Sample branch stock and movements

  • /queueAvailable today

    Shared queue with priority, owner and response clock

    Available today: one queue with owners and response clocks.

    Data shown: Sample work queue

What's included

What you get on day one, and what we connect to your own systems during onboarding.

Included

  • Offline completion with photos, scheduling suggestions, parts movement and verified closure

Connected during setup

  • Live vehicle tracking and route optimisation are not built and are not claimed
  • Customer notifications need your own messaging accounts

Common questions

Do customers get a tracking link?
No. That is not built. Job status stays inside your organisation today.
Is there a ready-made template for our industry?
They are configured for you. The procedures, issue types and wording are configured during setup. Restaurant routines are the only ones we have built out in advance.
Can each site see only its own work?
Yes. Site-level access is enforced in the database, and it applies to reports and exports too.

How access and records are handled

Each organisation's records are separated in the database, and people only see the branches they are assigned to. Status changes, approvals, rejections and verifications are recorded with who did them and when. We do not claim any external certification or audit at this stage; if you need a formal security review, ask us and we will tell you exactly what exists today.

Bring one real problem to the demonstration.

The workspace is loaded with clearly labelled sample sites and records, so you can run your own scenario before deciding anything.