Example workflows

Proven AI-assisted recipes - from turning a manual into a PM program to Monday-morning operations briefings.

These are workflows real teams run once an assistant is connected. Each lists the scopes it needs. Copy the prompts and adapt.

The Monday briefing (read-only)

"Give me a Monday briefing: overdue work orders by site with the three oldest called out, work requests that arrived over the weekend, PMs due this week, and any compliance items going overdue in the next 30 days."

The assistant sweeps list_work_orders, list_work_requests, list_pm_schedules, list_compliance_items and writes the summary you'd otherwise assemble from four screens. Scopes: reads only - this is the ideal first workflow.

Manual → PM program (the flagship)

Scopes: reads + pm_templates:write, pm_schedules:write, form_templates:write, form_template_items:write.

  1. Paste (or attach) the maintenance section of a manufacturer's manual.
  2. > "Turn this into a quarterly PM for the two Trane RTUs at the arena: build an inspection form with pass/fail checks and number readings where the manual gives ranges, a conditional 'describe the issue' on any fail, then a PM schedule with the form attached."
  3. The assistant looks up the real assets, builds the form template with conditional logic, creates the PM schedule, and links everything.
  4. You review the draft template and publish it.

An afternoon of transcription becomes minutes of review.

Field capture → work order (dispatch copilot)

"Resident says water pooling at the Elm/5th intersection. Find the nearest storm features, create a medium-priority work order to inspect the catch basin, assign to the drainage crew, due in 3 days, and note the resident report in the description."

Scopes: reads + work_orders:write. The assistant resolves the features by lookup, never by guessing IDs.

Budget variance narrative (reads + projects)

"For each active project, compare actuals and committed against budget lines, flag anything past 90% with milestones still open, and draft the finance-committee paragraph for the two worst."

Scopes: project reads. Pairs well with cost snapshots - ask the assistant to snapshot after it reports.

Data hygiene sweeps (reads, then targeted writes)

"List assets missing installation date or replacement cost, grouped by building, worst-count first."

"These 14 assets are all 2019 installs per the attached commissioning report - update their installation dates."

Bulk cleanups that never happen manually happen conversationally. Scopes: reads, plus assets:write only when you're ready to fix, not just find.

Parts reorder digest (read-only)

"Which parts are at or below reorder point? Group by supplier and draft the reorder email for each."

Scopes: parts:read, vendors:read.

Working habits that make these succeed

  1. Point at real things - "the arena", "WO-1234". The assistant resolves names to records via lookups; vague references produce clarifying questions, not guesses.
  2. Review before write. Assistants propose; you confirm. Keep that rhythm even after trust builds.
  3. Start read-only and add scopes per workflow - the security model is designed for exactly this progression.