BranchFlow

For maintenance planners

Plan the service before the fryer decides for you.

Plans generate work on a schedule or from a reading you record, so routine servicing stops competing with emergencies for attention.

What we can state plainly

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

  • Plans generate work items on schedule without creating duplicates.
  • Triggers include fixed dates, intervals, usage and meter thresholds.
  • Compliance is measured as completed on time against what was due.
  • Overdue plans escalate rather than sitting quietly.

How it works in practice

  1. 1

    Define the plan

    Pick the asset or asset type, the schedule and the procedure to follow.

  2. 2

    Work appears

    Tasks are generated ahead of the due date with an owner.

  3. 3

    Record readings

    Hours, cycles or counts trigger the next service when thresholds are hit.

  4. 4

    Prove compliance

    Report completion on time per branch and per plan.

What you get

  • Eight trigger types

    Date, interval, usage, meter and condition-based generation.

  • Trading hours

    Schedule work outside service periods where the branch requires it.

  • Meter readings

    Enter readings individually or import a batch.

  • Compliance view

    Due, completed, late and missed per branch.

The screens behind this page

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

  • /maintenanceAvailable today

    Preventive maintenance plans and meter triggers

    Available today: recurring plans that generate scheduled work.

    Data shown: Sample refrigeration and fryer plans

  • /assetsAvailable today

    Equipment register with history, downtime and failure causes

    Available today: one record per unit with its own history.

    Data shown: Sample freezers, fryers and vehicles

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

  • Plans, triggers, generated work, readings and compliance figures

Connected during setup

  • Automatic meter feeds need a connection to your own equipment or systems; readings are entered today

Common questions

Will it flood the queue with tasks?
No. Generation is controlled and repeated runs do not create duplicate tasks for the same period.
Can plans cover many branches at once?
Yes. A plan can apply to an asset type across branches you select.

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.