Provider OS
Lesson 9 / 12
Reports and Exports
A report-reading lesson for source handoffs, preview states, export readiness, and approval-required downloads.
Use reports to understand operating history while respecting export gates and private-data boundaries.
Why this matters
Reports can help you understand profit, jobs, invoices, estimates, expenses, labor, and trust activity, but exports must stay controlled and redacted.
What this feature is
Reports help providers understand business signals and source workspaces, while exports remain gated when private data or approval is involved.
Safe to use now
- Read report previews, source labels, and source handoff links.
- Use reports for understanding, not for exporting private data from training.
Provider example
A provider reviews reports before making staffing or pricing decisions, then opens the source workspace instead of exporting private rows from training.
What to click next
- Open Reports for report cards and previews.
- Open the source workspace when the report points you there.
- Use Support if you need a report that is not approved yet.
What not to do yet
- Do not export customer/provider/worker/profile data from training.
- Do not bypass export gates or redaction requirements.
- Do not present previews as final accounting statements.
Short video
Lesson focus
Workspace cue
Report source map
Reports point back to live source workspaces such as invoices, quotes, jobs, expenses, timesheets, reviews, and referrals.
Key highlights
- Reports are useful when you know the source behind the number.
- Export actions remain gated when redaction, scope, or approval is required.
- A preview is not a permission to download or share private data.
Before you start
- Know which business question you are trying to answer.
- Keep customer, provider, worker, and profile data inside approved screens.
- Expect export gates when a download could contain sensitive records.
Step by step
- Open Reports from Provider OS.
- Choose a report card that matches your business question.
- Read the source label before trusting the report.
- Use source handoff links to open the related workspace when needed.
- Stop at export gates unless explicit approval exists.
Ready to apply
- You can find Reports.
- You can identify a report source.
- You know when export is gated or approval required.
If you get stuck
- If you do not know which report to use, start from the workspace you already understand.
- If an export is gated, treat the preview as read-only guidance.
What success looks like
You can use reports for business understanding without leaking or overclaiming export behavior.
Quick checklist
- Open Reports.
- Pick one report card and read its source label.
- Open its source workspace, then return.
Practice it in the live product
The lesson stays public, but the CTA routes directly into the live HubbCentral surface tied to this workflow.