BranchFlow

For dispatchers and schedulers

Assign the run, then prove it arrived.

Dispatch shows what needs to move, who is available, and records proof at the branch so deliveries are not disputed a week later.

What we can state plainly

Each line here is something the running system does today, not an ambition.

  • Vehicle and driver assignment is recorded against the delivery.
  • Proof of delivery, including partial delivery, is captured at the branch.
  • Suggestions use workload, skills and availability, but never assign on their own.
  • Scheduling shows conflicts and dependencies before you commit.

How it works in practice

  1. 1

    See the demand

    Approved supply requests and scheduled jobs in one board.

  2. 2

    Check capacity

    Workload, skills and availability for the day.

  3. 3

    Assign

    A person takes the decision; the system records it.

  4. 4

    Confirm

    Delivery or completion is confirmed with proof at the branch.

What you get

  • Delivery states

    Assigned, in transit, delivered, partially delivered, failed.

  • Fleet records

    Vehicles, drivers and availability kept per organisation.

  • Availability

    Staff skills and working availability used for suggestions.

  • Proof capture

    Photos and receipt confirmation stored against the run.

The screens behind this page

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

  • /dispatchAvailable today

    Vehicle assignment and delivery proof

    Available today: assign a vehicle and record proof of delivery.

    Data shown: Sample delivery run

  • /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

  • /suppliesAvailable today

    Supply requests, approval and receipt confirmation

    Available today: request, approve, dispatch, confirm receipt.

    Data shown: Sample packaging and parts requests

What's included

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

Included

  • Vehicle assignment, delivery states, proof of delivery and scheduling suggestions

Connected during setup

  • Live vehicle tracking and route optimisation are not built and are not claimed

Common questions

Do you optimise routes?
No. There is no route optimisation or live tracking. Assignment is a human decision with visible workload.
What if only part of a delivery arrives?
Partial delivery is recorded with the shortfall, and stock reflects what actually arrived.

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.

Walk this part of the system yourself.

The demonstration workspace is loaded with clearly labelled sample branches and records, so you can test this workflow end to end before deciding anything.