For multi-site brands & franchises

Your name is on every location. Now your standard can be too.

Brand HQ puts one status board over every member facility: walks on time, overdue work, recall exposure, incidents, and incidents per 1,000 admissions compared site by site. Status only is the default. Record-level detail exists only where a site’s agreement grants it, and each site keeps its own ledger either way.

Pricing follows the packs each location runs. The HQ portal comes with the portfolio.

Summit Air Parks × Telure · Brand HQSTATUS-ONLY VISIBILITY · GRANTED BY EACH SITE
FacilityStatusOn-time walks 30dOverdueRecallsIncidents 30dIncidents per 1,000 adm
Summit Air · ColumbusON TRACK98%00 open10.08of 12,480
Summit Air · DaytonON TRACK96%00 open00.00of 8,240
Summit Air · CincinnatiWARNINGS88%21 reviewing20.21of 9,610
Summit Air · LouisvilleACTION NEEDED71%61 new30.43of 6,900
Summit Air · LexingtonON TRACK94%00 open0n/a, no admissions feed

The demo portfolio is fictional. Thresholds and columns are configurable per brand.

The comparable number

Incidents per 1,000 admissions, across every location you carry.

A raw incident count punishes your busiest site and flatters your quietest. Telure divides by admissions wherever a facility’s waiver or booking integration reports them, so a 6,900-admission site and a 12,480-admission site sit in the same column and the ranking means something.

A site with no admissions feed shows n/a. It is never estimated and never averaged into a brand figure, and the packet lists every site that is missing a denominator by name.

Denominator: admissions reported by the site’s own waiver or booking integration, last 30 days. Telure documents your work. It is not a safety system.
Last 30 days · ranked4 of 5 sites reporting admissions
Summit Air · Louisville3 incidents · 6,900 admissions
0.43
Summit Air · Cincinnati2 incidents · 9,610 admissions
0.21
Summit Air · Columbus1 incident · 12,480 admissions
0.08
Summit Air · Dayton0 incidents · 8,240 admissions
0.00
N/ASummit Air · Lexington, no admissions feed connected yet

Status only is the default. Records are not yours by default.

Every brand starts at status only: indicators and counts. Record-level detail is a second tier that exists only where a member facility’s own agreement grants it, and it is set by Telure with a written reason, recorded permanently in your tier log. What HQ can see, HQ is expected to act on, so the tier is a liability decision rather than a toggle.

Tier 1 · Status only

DEFAULT

HQ can see: status indicators and counts

  • ·On-time completion rate for opening and closing walks, last 30 days
  • ·Count of overdue recurring tasks
  • ·Count of open recall matches
  • ·Count of incidents, last 30 days
  • ·Count of rushed checks (duration anomalies), last 7 days
  • ·Current Telure Standards version
  • ·A red, yellow or green status indicator derived from the above
  • ·Median walk duration and rushed-check rate, last 30 days
  • ·Incidents per 1,000 admissions where an integration provides admission counts
  • ·Open recall matches grouped by recall, with per-site status
  • ·Escalations for this facility and their status history

Tier 2 · Full records

ONLY IF THE SITE’S AGREEMENT SAYS SO

Everything above, plus record-level detail

  • +Recent inspection runs: dates, pass and flag counts, duration anomalies
  • +The list of overdue tasks by name and due date
  • +Open maintenance items by title and age
  • +Open recall matches with device and status detail
  • +Incident titles and dates

Still no writing, no guest names, and no export of a site’s ledger. Every member facility sees its tier in these same words and the identical metric list.

The registered packet

One portfolio document an underwriter can check

A brand admin generates the portfolio packet as a PDF. Every generation is registered permanently: the document’s digest is filed under a printed Document ID, and any recipient can confirm at floorkept.com/verify that the file they hold is the one that was registered. It can factor favorably into underwriting.

Recall exposure

One recalled part, every floor carrying it

Telure maps a recall to every location that has the equipment, and shows each site’s response status side by side. A recall closed at one site and untouched at three is visible as exactly that.

The shared standard

Publish once, and read the exceptions

Put your brand’s requirements on top of each site’s Telure Standards. Adoption stays the facility’s own decision, and where a site documents an exception, HQ reads the exception and the reason instead of a silent gap.

HQ reads status. It cannot touch the record.

Brand HQ cannot write, edit, or amend a site’s records at either tier. Each facility’s ledger stays append-only under its own roof, which is exactly what makes the portfolio worth reading: nobody upstream can polish it.

And a facility that leaves your brand takes its records with it, intact. Sites cooperate with a board they cannot be locked out of.

What HQ sees · What HQ can’t

SEESStatus, adherence rates, benchmarks, escalations, adopted-standard exceptions
CAN’TWrite or amend entries, read guest names, export a site’s ledger, adopt a standard on a site’s behalf
CAN DOAcknowledge, assign and resolve escalations, which the site sees in full

Put your standard over every floor that carries your name.

Member facilities each get the full product, priced by facility type.

For Brands · Telure