BranchFlow

For campus and estates teams

Fix the classroom before the next lesson, not next term.

Teaching staff report faults in seconds, the estates team works one prioritised queue, and holiday servicing is planned instead of remembered.

What we can state plainly

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

  • Faults carry the room, the impact on teaching and a photo.
  • Priorities and response expectations are configured by you.
  • Planned servicing can be scheduled outside teaching hours.
  • Closure requires a second authorised person.

How a typical problem runs

  1. 1

    Staff report

    A teacher or site officer raises the fault from a phone.

  2. 2

    Prioritised

    Safety and teaching impact drive the response clock.

  3. 3

    Planned or fixed

    Urgent work now; routine work into the servicing plan.

  4. 4

    Verified

    Someone else confirms before it is closed.

What you use most

  • Site readiness

    One figure per site from open work and overdue checks.

  • Trading-hours scheduling

    Plan work outside lesson times or during holidays.

  • Safety checks

    Versioned procedures with evidence and corrective work.

  • Asset records

    Boilers, kitchens, IT equipment and grounds equipment.

The screens behind this page

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

  • /reportAvailable today

    Frontline reporting with photos and customer impact

    Available today: the report a branch team member fills in.

    Data shown: Sample branch report

  • /maintenanceAvailable today

    Preventive maintenance plans and meter triggers

    Available today: recurring plans that generate scheduled work.

    Data shown: Sample refrigeration and fryer plans

  • /checklistsAvailable today

    Opening, closing, temperature and sanitation procedures

    Available today: published procedures with evidence and corrective actions.

    Data shown: Sample opening and temperature checks

  • /overviewAvailable today

    Leadership overview of open work and branch readiness

    Available today in the demonstration workspace.

    Data shown: Sample multi-branch group

What's included

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

Included

  • Staff reporting, prioritisation, planned servicing outside teaching hours, checks and verified closure

Connected during setup

  • WhatsApp, SMS and email alerts need your own accounts and approved templates
  • Connections to your existing systems need your credentials and a test in your workspace

Common questions

Is there anything specific for safeguarding records?
No. BranchFlow handles estates and operational work only. Safeguarding must stay in the system designed for it.
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.