Operations that stay accountable.
Supervisor approval, guard-authored revisions, instant maintenance routing, and current SOP access.
Report lifecycle
Original statements are immutable. Corrections are new attributed versions or administrative addenda. Supervisor edits require recorded written permission; after separation, only a distinct administrative supplement is permitted.
Maintenance delivery route
Each new request will immediately notify BOTH the property manager and DLS supervisor. A maintenance-worker copy is optional when the property authorizes it. The supervisor monitors acknowledgments and, if overdue, receives a follow-up alert to place a phone call. This page simulates those actions; no email or call is sent.
What we'll cover Thursday
Owner decision points
Who can request follow-ups? Who may issue limited administrative supplements? What acknowledgment deadline starts the supervisor call escalation? Will the property enable a maintenance-worker copy? Which SOP changes require re-acknowledgment?
Report review & revision
Switch the simulated role to see how the same report behaves for the guard and supervisor.
Incoming reports
Report detail & actions
Maintenance intake
Every request is immediately routed to BOTH property management and DLS supervision. The supervisor owns acknowledgment follow-up; maintenance-worker copies are property-controlled.
New maintenance request
Notification routing
Sensitive resident information should stay behind an authorized link, not be placed in the email subject or message.
Request activity
SOP library
One authoritative current approved edition, with version history and staff acknowledgment tracking.
Document register (demonstration)
Current source review draft. Includes on-property timekeeping, incident reports, confidentiality and shift handoffs.
Individual login, account recovery, suspended users, audit logging and acknowledgment.
Versioned corrections, written consent, administrative addenda, dual maintenance notifications, supervisor phone escalation, SOP release controls.
Automatic document update — production design
Once a policy is approved, ConciergeOS should publish it from a central version store. Guard phones and supervisor browsers fetch the newest published revision, while prior signed versions remain archived.
Accountable reading
Staff see a “New SOP version” indicator; material changes require them to acknowledge receipt and complete assigned training. Open incidents retain a reference to the SOP revision applicable when the event occurred.
Not yet operational: live documents, automated sync, acknowledgment registry, and controlled edit approvals.
Production readiness
The review website is live; the property operations system is not yet production-ready.
Release gate checklist
These are required validation steps, not a claim that security or notifications are already active.
Suggested implementation order
Meeting-ready links
There is no deadline-based automated deployment here. The go-live date depends on security and user acceptance testing.