Locations have shifts (including shifts that cross midnight), the people who work there, incident types, due hours and a QR code. Checklist templates hold tick, yes or no, number with limits, text, choice and photo items, each with an optional SOP link; schedules (daily, weekdays or monthly, at shift start, shift end or a clock time, assigned to a role or a person) make due runs, a run keeps its own copy of the template, and a run not finished in its window is marked missed by the cron. The phone run screen saves each answer on the tap, asks for a note on a failing answer and offers to log an incident filled in with the item and reading. Incidents have type, severity, a due date from severity, an assignee, comments, root cause, corrective action, photos and a history through open, in progress, resolved and closed, with email to the assignee and, for high and critical, to managers and alert addresses when email is set up. Each location has a public report form at /report/<token> (QR code, on or off, new link on demand, honeypot and rate limits) where a visitor reports an issue without signing in. Handovers carry a summary, a task list, readings and the shift's runs and incidents, and the next shift acknowledges them by name. SOPs have steps with warnings and photos, an owner and review date, a version for each publish, must-read assignments by role and location with acknowledgements per version, and a print view. Home shows what is due now, missed today, open incidents, the last handover per location and SOPs to read. An API at /api/v1 with an API key or the workspace key lists locations, SOPs, runs, incidents and handovers and creates incidents, with a change feed; webhooks fire on incidents, runs and handovers. Three optional Claude features draft an SOP from a description, a checklist from an SOP and a handover from the shift's runs and incidents, and only draft; they are off without a key. There is no offline queue and no link to Assets yet
Daily operations of a connected domain's locations and shifts: checklists and scheduled runs filled on a phone, an incident log with a public report form opened from a QR code, shift handovers acknowledged by the next shift, and SOPs with versions and must-read acknowledgements, with a home page of what is due, missed or open, an API with webhooks and a feed, and three optional AI drafting features.Company equipment belongs to Assets; stock belongs to Inventory; customer support tickets belong to Support; approvals belong to Approvals; long-form documents belong to Writer and Documents.