BranchFlow

For facilities managers

One queue for every building you are responsible for.

Requests arrive from occupants, planned servicing arrives from the schedule, and contractors see only the job you share with them.

What we can state plainly

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

  • Requests are reviewed and approved before becoming work.
  • Planned servicing generates work on schedule for each building.
  • Contractors participate through a private link with no account needed.
  • Compliance checks keep their evidence and their version history.

How a typical problem runs

  1. 1

    Request received

    An occupant or site contact raises the need.

  2. 2

    Approved

    An authorised person approves or declines with a reason and within limits.

  3. 3

    Assigned

    Internal team or contractor, with workload and coverage visible.

  4. 4

    Evidenced and closed

    Photos and notes recorded, then verified by a second person.

What you use most

  • Portfolio view

    Every building compared on the same definitions.

  • Contractor coverage

    Which contractor serves which building and category.

  • Compliance records

    Versioned procedures with evidence kept for audit.

  • Cost visibility

    Work, supplies and spend totals by site.

The screens behind this page

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

  • /workAvailable today

    Branch requests with approval, decline and template-based work creation

    Available today: requests are reviewed before any work is created.

    Data shown: Sample requests awaiting a decision

  • /vendorsAvailable today

    Vendor records, coverage, contracts and shared jobs

    Available today: vendor coverage and the work shared with each vendor.

    Data shown: Sample refrigeration and cleaning vendors

  • /checklistsAvailable today

    Opening, closing, temperature and sanitation procedures

    Available today: published procedures with evidence and corrective actions.

    Data shown: Sample opening and temperature checks

  • /leadershipAvailable today

    Branches, staff, vehicles and supply costs with totals

    Available today, with sample figures labelled as sample figures.

    Data shown: Sample multi-branch group with sample costs

What's included

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

Included

  • Request approval, planned servicing, contractor links, compliance evidence and portfolio reporting

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

Can tenants raise requests themselves?
Today requests come from your own users. A public tenant request portal is not built, and we will not pretend otherwise.
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.