Status & Incident Communications
Last reviewed June 30, 2026 for Vanta/SOC 2 evidence. This is the Measured HRIS customer-facing status and incident communication reference while the reviewer-dependent external status-vendor decision remains tracked separately.
Current operating posture
Measured HRIS is hosted at measured-hris-5rayt2.benmore.ai. This page is public and available outside the authenticated application. The app is operated through the Benmore platform with live app health checked through Benmore diagnostics, request logs, captured errors, and route probes.
Status components
| Component | Coverage | Current posting |
|---|---|---|
| Core HRIS app | Public app entry, dashboards, admin workflows, and API-backed pages. | No active incident posted. |
| Authentication and session access | Login, signup/access request, MFA setup, and role-gated access. | No active incident posted. |
| Payroll and compliance workflows | Payroll run, tax, onboarding, benefits, documents, and reporting surfaces. | No active incident posted. |
| Employee data access | Self-service, tenant-scoped records, secure sensitive-data flows, and audit trails. | No active incident posted. |
| Support and incident intake | In-app support widget, support inbox, assigned customer contacts, and escalation path. | No active incident posted. |
| Modern Treasury/payment rails | Sandbox money-movement evidence only; live payment origination remains gated. | No active incident posted. |
Incident communication path
- Customer administrators report availability, payroll, authentication, or data-access issues through the in-app support channel or their assigned Benmore/Measured contact.
- Benmore operators triage using app health, request logs, captured client/server errors, audit events, and database state.
- Material incidents are communicated to affected customer administrators with scope, impact, impacted components, workaround, remediation status, next update timing, and closure notes.
- Payroll, treasury, tax, or employee-data incidents are escalated as security/compliance events and tracked to closure.
Maintenance and incident history visibility
Planned maintenance is communicated through the same customer administrator path before the window begins. This app-hosted page records the current public posture and communication process; it is not an independent historical uptime ledger. If an auditor or customer requires independent status hosting, the SOC 2 evidence packet requires an external status-page URL or export with component history, maintenance history, subscriber notifications, and created/updated/resolved communication timestamps.
Owner and notification responsibility
- Status-page control owner: Benmore/Measured HRIS compliance owner recorded in the SOC 2 evidence packet.
- Incident triage owner: active Benmore operator assigned to the Measured HRIS support lane.
- Customer notification owner: assigned Measured HRIS customer contact or support owner for the affected administrator group.
- Evidence owner: Vanta/SOC 2 evidence owner confirms whether this interim page is accepted or an external status vendor is required.
Vanta/SOC 2 evidence posture
This page can be attached as interim Vanta/SOC 2 evidence only if the reviewer accepts an app-hosted public status reference. If independent hosting is required, attach the external vendor URL/export, component list, incident-history visibility, notification owner, and screenshot evidence before marking the application status-page control verified.
Operator checks
benmore health measured-hris-5rayt2 benmore check measured-hris-5rayt2 benmore errors measured-hris-5rayt2 benmore requests measured-hris-5rayt2 benmore probe measured-hris-5rayt2 GET / benmore probe measured-hris-5rayt2 GET /status.html