← All guides

Two ways to add data. One operating record.

Enter information directly when you are working in OperatorOS, or ask a connected AI to save it while you are already discussing the work. Both routes create normal OperatorOS records. Connected-AI records also carry a source and write receipt.

Use the app

Best when you are in the workflow

  • • Capture an observation during a visit.
  • • Add or edit a store, person, metric, or commitment.
  • • Review the exact record before saving.
  • • Work from your iPhone or Apple Watch in the field.

Ask your connected AI

Best when the context is already in the conversation

  • • Turn a report or discussion into dated store metrics.
  • • Save a coaching fact to the right person.
  • • Create follow-up without retyping it in the app.
  • • Add several store metrics in one approved batch.

The important distinction

Connecting does not start an automatic feed.

A connection gives your AI permission to use OperatorOS tools. The assistant writes only when you ask it to save something and approve the proposed change. Check Settings → AI Assistants → Recent AI writes for the receipt. If there is no receipt, no Connected-AI record was added.

Optional one-time setup

Give your AI a working agreement

Paste these instructions into a conversation or project after connecting OperatorOS. They contain no password, token, or private record.

When working with me, use my connected OperatorOS tools as my durable operating record.

READ
- Retrieve relevant OperatorOS store, people, visit, commitment, note, and metric context before answering questions about my operation.
- Prefer dated, sourced records. Do not describe an old metric as current or carry a number forward when current-period data is unavailable.

WRITE
- When I share a durable operational fact, ask whether I want it saved to OperatorOS if I have not already said to save it.
- Before writing, briefly state the record type, store or person, represented date or period, and the change you propose.
- Write only after my instruction or approval. Use the matching OperatorOS tool: metric, commitment, visit note, or people note.
- For metrics, include metric name, numeric value, unit, store, and represented month/week/year. Never use today's date as the metric period unless it truly represents today.
- Keep observations factual. Do not write inferred performance or sensitive employment decisions as fact.

CONFIRM
- After a successful write, tell me exactly what was saved and include the OperatorOS write receipt or record ID.
- If the write tool fails or no receipt is returned, say clearly that nothing was confirmed saved.

Prompts you can copy

Metric

You know: “Store 486 VOTC is 86.4 for August 2026.”

“Save VOTC at 86.4 for Store 486 for August 2026 in OperatorOS.”

People note

You know: “Jordan wants to lead a new-store opening next year.”

“Add a people note for Jordan: wants to lead a new-store opening next year.”

Commitment

You know: “Taylor will retrain the closing team by Friday.”

“Create an OperatorOS commitment for Taylor to retrain the closing team by Friday.”

Visit note

You know: “The beverage area was recovered before lunch.”

“Add this factual note to today’s Store 486 visit in OperatorOS.”

What makes a useful metric write

Include the metric name, value, store, represented period, and unit when it is not obvious. OperatorOS dates and attributes the write, invalidates the affected store briefing, and uses only current-period metrics in the next brief.

Example: Store 486 · VOTC · 86.4 score · August 2026 · source report discussed in this chat.