Skip to content
Platform · Information Routing

A Measurement Is Not Information Until It Reaches the Right Person

Every measurement has a named destination, a trigger, a channel and a person who confirmed it arrived.

Get a DemoBack to Platform
Mapped to your teams
Triggered, not polled
Scoped per audience
Confirmed on arrival
The problem with a dashboard

A Login Is Not a Delivery

A dashboard asks someone to remember to open it. A report asks someone to remember to read it. Neither survives a bad week on site, which is exactly the week the information was worth having. So we route it instead: every measurement leaves with a destination on it.

Named, not broadcast

Every route ends at a role and the person holding it this week, not at a distribution list nobody owns. When the roster changes, the route follows the role.

Triggered, not scheduled by default

A gate opening at 2am does not wait for the Monday digest. A claim pack does not arrive at 2am. Each route runs on the trigger that suits the thing it carries.

Scoped, not shared wholesale

A sponsor sees their own activation. A trade sees one position for one window. The superintendent sees what you chose to grant, and you can withdraw it.

On a build

The departments a project acquires, in the order it acquires them

A builder starts with the crew who can act in the next ten minutes and ends with a director carrying eight sites at once. Each one needs a different thing, at a different speed, in a different format.

Site crew and supervisors

The people on the ground who can do something about it in the next ten minutes.

  • Gate and after-hours movement alerts with the frame attached
  • Dust and noise readings against the limit set for that site, on the hour they matter
  • A node that has stopped reporting, before anyone downstream notices a gap
  • The live view and the last frame from every position, on a phone, on site

When

When something happens · When a reading crosses a line

How

Push to the crew app · SMS · A screen on the wall

Their site only, current and last 30 days. Advisory: presence, count and reading, never identity, and none of it is a safety system.

Project management

Project managers, site managers and foremen running the programme.

  • The daily site note: what changed, what arrived, what stopped, written from the day’s frames
  • Weather on the same timeline as the frames, so a lost day carries its own evidence
  • Progress compared between any two dates on the programme, from the same position and framing
  • The monthly coverage report: frames captured against frames expected, with every gap explained

When

On a schedule · At a milestone · When somebody asks

How

The site dashboard · Email, scheduled · A signed document

Every position on their projects, the full archive, and the export.

Commercial and contract administration

Quantity surveyors and contract administrators building claims, variations and delay notices.

  • A claim pack on your claim cycle: the period’s frames, the weather record and the coverage statement in one document
  • Rainfall, gust and temperature by day, exportable for a wet-weather or EOT submission
  • Any date pulled from the archive as a dated, referenced frame rather than a recollection
  • The delivery and plant record at the marked gates, by date

When

On a schedule · When somebody asks

How

A signed document · Email, scheduled · Into your own system

The archive and the weather record, with export. No alerting: this audience is a reporting route, not a response route.

Health, safety and environment

WHS managers and safety advisers holding the environmental and site-conduct obligations.

  • Dust and noise against the limit for that site, with the exceedance duration and the conditions at the time
  • Tilt and vibration on hoarding, scaffold or a neighbouring structure, with the alert threshold you set
  • After-hours movement and gate events, for the incident record rather than for response
  • A monthly environmental summary with every exceedance, its duration and the frame beside it

When

When a reading crosses a line · When something happens · On a schedule

How

Push to the crew app · Email, scheduled · A signed document

Environmental and structural readings plus the frame at the time. Advisory only, never a substitute for a monitoring regime a consent requires.

The client and the superintendent

The principal’s representative, the superintendent and the end client.

  • A read-only view of the site, scoped to the positions you choose to share
  • A monthly progress note with the period’s comparison frames
  • The milestone frames as they happen: the pour, the lift, the topping out

When

On a schedule · At a milestone

How

The site dashboard · Email, scheduled

A view you grant and can withdraw, position by position. No alerting, no sensor detail, no coverage report unless you choose to include it.

Marketing and communications

The people who need the build to look like the build.

  • The curated daily frame, one a day, taken nearest midday so the light holds across the programme
  • The completion film rendered at 4K from the full sequence
  • Milestone stills at full resolution, cleared for use, with the date on them

When

At a milestone · When somebody asks · On a schedule

How

The site dashboard · Email, scheduled

Imagery and film only. No sensor data, no alerts, no coverage reporting.

Executive and portfolio

The general manager or director who carries more than one site at a time.

  • One view across every live site: which positions are reporting, which are not, and since when
  • Coverage across the portfolio in a single figure, per site and in total
  • Weather-affected days by site, for the month and for the year to date
  • Nodes in service, nodes on the shelf and nodes due back from a finished job

When

On a schedule

How

The site dashboard · Email, scheduled · A screen on the wall

Every site in the programme, summarised. Drill-through to any site’s own view.

Your security provider

The licensed provider who responds after hours.

  • The after-hours alert with the clip, the position and the site address attached
  • An escalation if the first alert is not acknowledged inside the window you set
  • A monthly log of every alert sent and every response recorded against it

When

When something happens

How

Push to the crew app · SMS · Into your own system

Alerts and clips on the hours you set, nothing else. We are the technology and they are the licensed responder; monitoring and patrol are their work, not ours.

Subcontractors and trades

A trade that needs one position, one zone or one window and nothing else.

  • A single position or zone, for a date range that expires on its own
  • The frames covering their own works, for their own records and claims

When

When somebody asks

How

The site dashboard · Email, scheduled

One position, one window, time-limited. Granted by your project manager and revoked automatically at the end date.

On an event

The same model, on an event clock

A festival compresses the whole organisation into a weekend. The controller needs the site live, the gate supervisor needs one number, the producer needs the acquittal, and the licensee needs the condition they are held to.

The control room

The event controller and the operations manager holding the whole site.

  • Occupancy by zone against the limit, live, with the rate of change beside it
  • Gate throughput and the queue building at each entry
  • Every zone threshold crossing, on the board and in the log, with the time it cleared
  • The incident timeline as it is written, so the debrief starts already built

When

When a reading crosses a line · When something happens · On a schedule

How

A screen on the wall · The site dashboard · Push to the crew app

The whole site, live, plus the full timeline for the debrief.

Gate and door crews

The supervisors on the entries who can open a lane or hold a queue.

  • The count at their own door against the limit the venue sets
  • A call to open or hold, from the controller, with the number that prompted it
  • The barrier and queue state at their gate and the one either side of it

When

When a reading crosses a line · When something happens

How

Push to the crew app

Their gate and its neighbours. Counts and states, never identity.

Safety and medical

The crowd-safety officer and the medical lead.

  • Density by zone, read the way a safety case reads it, against the thresholds in the plan
  • The zones building fastest, ranked, so a crew is moved before the call
  • An alert on every threshold crossing, with the zone and the time

When

When a reading crosses a line · When something happens

How

Push to the crew app · A screen on the wall · The site dashboard

Density and occupancy by zone. Advisory: it informs a decision your safety officer makes, and it is not a safety system.

The producer

Whoever holds the budget and answers to sponsors, investors or the board.

  • Attendance: unique visitors and entries, by day and across the run
  • Dwell at the places you sold: the sponsor activation, the bar, the stage
  • Whether the site plan worked, zone by zone, against last year where there is a last year
  • The post-event report, written and dated, for the acquittal and the sponsor pack

When

On a schedule · At a milestone · When somebody asks

How

The site dashboard · A signed document · Email, scheduled

Every measure, during and after. No alerting: this is the reporting route.

Sponsors and rights holders

The partners who bought a position and need to see what it delivered.

  • Dwell and reach at their own activation, for their own dates
  • A one-page result they can put in front of their own board

When

On a schedule · When somebody asks

How

A signed document · Email, scheduled

Their own activation only, for their own dates. Nothing else on the site is visible to them.

The venue or the council

The landowner, licensee or authority the licence conditions sit with.

  • Occupancy against the licensed capacity, for the licensed hours
  • Noise at the boundary against the condition, with the time and the duration
  • A compliance summary for the period, dated and exportable

When

When a reading crosses a line · On a schedule

How

The site dashboard · A signed document

The conditions they hold you to, and nothing beyond them.

Channels

Seven Ways Something Can Reach You

A route is the pairing of a thing worth knowing with the way that particular person actually works.

The site dashboard

A browser, no install, one login per person. Live frames, the sensor timeline and the archive, scoped to the sites that person is on.

Push to the crew app

The alert on the phone of whoever holds that role this week, with the frame attached. Acknowledged in one tap, and the acknowledgement is logged.

Email, scheduled

A digest to a named address or a distribution list, on the day and hour you set. Renders on a phone, and the archive link inside it is permanent.

SMS

For the one or two routes that must survive a phone with no data and no app. Short, with a link, and only on the triggers you mark critical.

A signed document

The monthly coverage report and the claim pack as a PDF with dates, references and the frames embedded. Built to be attached to a claim or a variation without being re-typed.

Into your own system

A webhook or scheduled export into the project management, document control or reporting tool your teams already open. JSON or CSV, your field names, your folder structure.

A screen on the wall

A standing view in the site office or the operations room that never needs a login and never needs a person to refresh it.

Triggers

And Five Reasons One Fires

Set once with you, changed from the dashboard afterwards, and different per site, per hour and per day of the week.

On a schedule

Daily, weekly, monthly or on your claim cycle. Set once at the routing session and changed from the dashboard afterwards.

When a reading crosses a line

Dust, noise, gust, rainfall, temperature or tilt past a number you set. The number is yours, and it can differ by site, by hour and by day of the week.

When something happens

A gate opening after hours, movement in a zone outside working hours, a node that stops reporting, a delivery arriving at a marked gate.

At a milestone

A pour, a lift, a topping out, practical completion. Marked in the dashboard or picked up from the programme dates you give us.

When somebody asks

A question put to the archive, a date range pulled for a claim, a clip cut for a variation. Self-served, and we pick up the ones nobody wants to drive.

When nobody acts on it

One ladder, on every route. The windows differ, because a gate alert is not a coverage report.

  1. 1

    Sent · Immediately

    The route fires to the people holding that role right now, on every channel that route carries.

  2. 2

    Acknowledged · One tap

    The first person to acknowledge takes it, and everyone else on the route sees that it is taken. The acknowledgement and the name are logged.

  3. 3

    Re-routed · On the window you set

    Unacknowledged inside the window, it goes to the next name on that route. Windows are per route: a gate alert is not a coverage report.

  4. 4

    Escalated · On the second window

    It reaches the escalation contact for that site, and the fact that the first two steps did not land appears in the monthly report.

How the map gets built

Ninety Minutes, Then Tested Until Somebody Confirms It

The routing map is a document you keep, not a setting inside our product. It is built with you before commissioning and reviewed every month against what actually got read.

  1. 01

    The routing session

    We put your departments, teams and crews on one page with the people who hold each role, and agree what each one needs to know and how fast. You keep: the routing map: every audience, every trigger, every channel, on one sheet.

  2. 02

    Thresholds and windows

    We set the numbers: dust and noise limits for that site, gust and rainfall, working hours, and how long a route waits before it re-routes. You keep: the threshold schedule, per site, with the hours each one applies.

  3. 03

    Wiring

    Accounts created, distribution lists connected, webhooks pointed at your own systems and the field names matched to yours. You keep: every route live and addressed to a real person or a real system.

  4. 04

    Tested end to end

    We fire a real trigger on every route and confirm a real person received it and acknowledged it. A route nobody confirmed is not commissioned. You keep: the routing section of the commissioning ITP, signed.

  5. 05

    Reviewed

    Routes that fired, routes that were acknowledged, and routes nobody read. A route nobody reads is changed or switched off. You keep: the routing line in the monthly report, and the changes made that month.

What we will not do

Advisory, and Never Identity

Every route carries presence, count, reading, frame and state. No facial recognition, no biometric matching, no per-worker tracking, and an unassessable frame reports as not assessable rather than as a clearance.

Monitoring and patrol response are licensed security work and we are a technology provider. Where a route ends at a security provider, they respond and we make sure the alert reached them.

How we handle data

Map Your Teams to What They Need to Know

See live occupancy, queues and crowd flow — and how they’d work on your site.

Talk to Our Team
CrowdSense analytics dashboard