Every site you have access to, side by side — health at a glance, plus everything overdue or due soon across all of them together.

Same idea as your Dashboard's own list, combined across every site — the 15 most urgent items.

Statutory items referenced against NBC 2016 and central Acts — verify local variations with your municipal corporation.

Critical assets with warranty, AMC and service-cycle tracking.

Contract status is calculated automatically from the contract end date — same Red/Amber/Green logic as the other registers.

Recurring routine tasks — distinct from Asset AMC renewals. Next due date is calculated from Last Completed + Frequency.

SLA status (Green/Amber/Red) is calculated automatically from the days-to-resolve targets set below.

A booking that overlaps an existing one for the same room is blocked outright, not just flagged — the room list below only needs setting up once.

Status is calculated from current stock vs. reorder level — Red when at/below reorder level, Amber when within 50% of it.

Today's on/off-duty status for deployed FM staff, plus a day-by-day attendance history per person — expand any row to view it.

An index of where documents are stored (paste a link to Drive/Dropbox/etc.) — this does not store the actual files.

A running meter-reading log — electricity, water, diesel. No RAG status here; this is consumption tracking, not a deadline.

Save a snapshot of today's health (Overdue / Due Soon / Healthy counts) and watch it build into a real trend over time. This can only show data from the day you start saving snapshots forward — it can't reconstruct months that already passed.

Real targets vs. actuals, not just Red/Amber/Green deadline status. Set a target percentage for each metric — actuals recompute live from your current data.

Patterns found in this site's own logged data — repeat repairs, vendor cost gaps, generator dependency, AMC bunching, utility spikes, and assets running past their own typical repair interval. No external benchmarks here, and nothing that claims to predict the future — just arithmetic on what your own records already show.

Periodic readings per zone. Thresholds follow common ASHRAE/WELL guidance (CO2 <800ppm good, 800–1000 moderate, >1000 poor; PM2.5 <12µg/m³ good, 12–35 moderate, >35 poor) — general guidance, not a certification.

Sewage Treatment Plant and Water Treatment Plant readings. Status is set by whoever's reading the plant — there's no universal "normal" threshold for MLSS, TDS, or hardness across every plant design, so this isn't computed automatically.

Estimated from the Utilities log and the Vehicle Fuel & Mileage log below — each logged entry's value is treated as consumption for that entry, multiplied by an emission factor. Indicative for internal tracking, not an audited GHG inventory.

Tracked as a working record of waste volumes and disposal routes — not converted to a CO2e figure, since the right factor depends heavily on disposal method and isn't something to guess at.

Covers both company-owned and vendor-owned vehicles used for employee transport and logistics. Company-owned vehicle fuel counts as Scope 1 above; vendor-owned (contracted) vehicle fuel counts as Scope 3. Electric vehicles are logged for mileage records but aren't converted to CO2e — this tracks fuel litres, not charging electricity.

A rollup of data already tracked elsewhere in this tool, organized into Environmental, Social, and Governance — not a certified ESG disclosure, a working internal view. The Social figure reflects current staff status, not a historical attendance rate.

Unplanned equipment failures — separate from the scheduled PPM checklist. Track status and how far repair has progressed.

Who's on site, who they're here to see, and when they checked in and out — with ID and badge tracking.

Permit-to-work register for hot work and cold work — with precautions and closure sign-off.

Health, Safety & Environment incidents — with root cause analysis. Expand a row to complete the RCA.

Internal and external audit findings — with risk factor, assigned owner, and target vs. actual closure dates.

Opex and Capex spend, logged for analysis and budgeting.

Enterprise risks — rated by Likelihood × Impact, a standard 3×3 grid. Each risk gets a mitigation plan and an owner.

This facility's own lease to the landlord/building owner. The warning window uses each lease's own notice period when set (falls back to 90 days if not).

Space this facility rents out to others. Rent we pay (above) can be logged as real Spend Opex entries; rent we collect here is income, which Spend Management doesn't track.

Every Red (overdue) and Amber (due within 30 days / SLA at risk) item across compliance, assets, and helpdesk tickets — most urgent first.

Everyone listed here sees and edits this site's live data. Roles: owner > admin > member (can edit) > viewer (read-only).

Off by default — turn this on only if you want it. When on, an email goes out when a new item is created, or when something turns Red/overdue (Contract Expiry, SLA Breach, Compliance Expiry, PPM Due, Inventory Shortage, Document Expiry) — never repeated for something that's already been red a while.

Off by default. When on, a red/overdue item also sends a WhatsApp alert to the numbers below (in addition to email, not instead of it). Those same numbers can also message this WhatsApp number directly with a question — "which licenses expire next month?" — and get an answer from the same AI Advisor logic used on the Dashboard.

Optional. Set this site's real-world location so a reading submitted from far away gets flagged for review — it still saves, nothing is ever blocked. Leave both fields empty to turn this off entirely; no location configured means nothing gets flagged.

By default, questions asked here and via WhatsApp go through this deployment's shared Anthropic key. Bring your own key from a different provider — Anthropic, OpenAI, or Gemini — and this site's questions route to that instead, billed to your own account.

Connect a meter, CMMS, or CAFM system that exposes a REST+JSON API, and this site's data will update on its own. Manual entry keeps working exactly as before — this is an additional way data can arrive, not a replacement.