AI operations reporting from your own records
Quick answer
AI operations reporting is a short weekly summary built from your own records. Every figure names its source, and a figure that can't be sourced is labeled, not guessed. In Omni Studio, the Reports employee prepares it. Sharing it outside your business, or sending any follow-up it suggests, waits for your approval.
AI operations reporting is a short summary of the week, built from your own records. AI employee Nora, who handles billing, books, and reports, reads your jobs, invoices, payments, estimates, and leads and puts the summary in front of you. Every figure names its source and when it was last updated, and an unsourced figure is labeled as unsourced.
Nora prepares the report. Sharing it outside your business, or sending any follow-up it suggests, waits for your approval.
What should AI operations reporting contain each week?
Read it in the order you'd ask the questions. Outcomes come first, because they're what you care about. Activity comes second, because it explains the outcomes.
- Start with what landed: work booked and finished, invoices paid, estimates accepted.
- Then a short paragraph on what changed since last week, with no wall of charts.
- Next is what's waiting: overdue invoices, estimates that went quiet, jobs nobody confirmed.
- Last is what was handed to you, meaning the items the AI employees left for a person, and why.
A count of conversations handled doesn't belong at the top. It shows how busy the system was and says nothing about whether anything improved.
How does Nora build the weekly summary?
Nora reads the records, drafts the summary with the source beside each figure, and waits. You read it, edit it, and decide whether it's shared.
Where does each figure come from?
A number you can't trace is a guess. The report keeps the source and the last update beside each figure, so you can see where it came from.
| Your question | What the report shows | Where it comes from |
|---|---|---|
| Did we get paid? | Invoices paid and overdue | Invoice and payment records, connected or imported from a CSV file |
| Is work moving? | Jobs booked and finished | Job records and the calendar |
| Who is waiting on us? | Open estimates and quiet leads | Estimate records and the inbox |
| What needs me? | Items handed to you | The approval queue and the decision log |
When a figure can't be sourced, the report says so and tells you what's missing. For example, a report that needs a completion date on every job will name the jobs that have none, instead of averaging the rest. You fix the records and the number appears. That's slower than a guess on day one, and much cheaper than finding out later that a number was wrong.
How should you read revenue by technician?
Owners often ask for revenue per technician. It's a useful report once the terms are fixed, and a misleading one before. Agree on what counts as booked, completed, and collected revenue, and how to treat warranty work, rework, and work with no technician assigned. Keep the source event and its date, so a manager can explain why a number changed.
Then separate capacity from performance. A technician with fewer jobs may be serving a different mix, driving farther, handling callbacks, or covering another crew. Read revenue next to revisits, response time, and travel before you draw a conclusion. Use the numbers to start a conversation about coaching and process. Ranking people automatically is a misuse of them.
A good first version is an exception list: jobs with missing closeout details, unusual discounts, unbilled work, and revenue that cannot be tied to a source record. A person resolves each one and writes down why.
Who reads it, and when?
Name one person who reads the report each week and owns what it points to. A report that's everyone’s job is nobody’s. Once a month, ask three questions. What did the AI employees handle well? Where did they hand off too often? Which rule should change? To review the AI employees themselves, see what an owner needs to see to keep AI employees on track. For the wider question, see whether AI employees are reliable enough for business operations.
Note. A report is a draft for you to review. It isn't an accounting opinion. If you need a packet for your accountant or your bank, the same records can prepare it, and you read it before it goes anywhere.
What to do next
Write down the three questions you ask yourself every Monday. Those are your first report. The weekly owner reports use case shows the steps. Month-end for a small business applies the same idea to the close. If your books are in QuickBooks, the AI QuickBooks integration guide explains the connection. Or start free and read a report built on sample data.
See the other AI employees in the Omni Studio AI employee library.
Frequently asked questions
What is AI operations reporting?
It's a short weekly summary built from your own records: what landed, what changed, what's waiting, and what was handed to you. Every figure names its source and last update. In Omni Studio, Nora prepares it, and you decide whether it's shared.
What happens when a figure cannot be sourced?
The report labels it and tells you what's missing, instead of guessing. For example, a report that needs a completion date on every job names the jobs that have none, rather than averaging the rest. You fix the records and the number appears.
Can it report revenue per technician?
Yes, once the terms are fixed: what counts as booked, completed, and collected, and how to treat warranty work, rework, and unassigned jobs. Read revenue next to revisits, response time, and travel, and use it to start a conversation about coaching. Ranking people automatically is a misuse of it.
Where do the figures come from?
From your invoice and payment records, job records and the calendar, estimate records and the inbox, and the approval queue. They can be imported from a CSV file. Your setup includes connecting your QuickBooks and Stripe accounts for invoice, customer, and card payment workflows.
Is the report an accounting opinion?
No. A report is a draft for you to review and carries no accounting opinion. If you need a packet for your accountant or your bank, the same records can prepare it, and you read it before it goes anywhere. This is general information, not accounting advice.
Sources
- Omni Studio weekly owner reports use case, Omni Studio, read Oct 7, 2026.
- Omni Studio connections and their status, Omni Studio, read Oct 7, 2026.
Omni Studio facts come from omni.studio and the Omni Studio product team.
