Opening proof path
SIRJ is loading the workspace, connector, or public page with the same proof path intact: ad spend, lead, booked job, invoice, paid.
See how SIRJ turns source records, dashboard changes, AI review decisions, weekly insights, and exports into client reports that prove the work behind each result.
Buyer questions
These answers separate a source-backed client report from a surface-level recap that asks the buyer to trust unsupported performance claims.
Proof-of-work client reporting shows the evidence behind the result: which sources synced, which leads or jobs changed state, which dashboard cards were created or updated, which AI outputs were reviewed, and which claims stayed blocked.
For an agency owner, this changes the report from a polished recap into a defensible client conversation about work completed, risk reduced, and revenue proof earned.
Inspect related proofIt should include source freshness, imported record types, dashboard updates, attribution confidence, unsupported states, reviewer decisions, sent or failed delivery status, and links to the source path behind the claims.
The client sees not only the number, but also what the account team and system did to make that number trustworthy enough for a business decision.
Inspect related proofAI-created summaries and dashboard cards must stay attached to supported source rows, metric definitions, date windows, review state, and unresolved gaps. If the evidence is weak, the output stays held or marked as unsupported.
This lets agencies use AI speed without handing clients a confident story that the underlying data cannot prove.
Inspect related proofIt reduces churn at the moment a client asks what the agency actually did this month. The report can show source fixes, held claims, reviewed cards, attribution changes, and the next source gap instead of only presenting outcomes.
Clients are less likely to treat reporting as decoration when the report explains the work path, the blocked risks, and the next action clearly.
Inspect related proofProof map
SIRJ keeps work evidence close to the report so clients can inspect source freshness, dashboard changes, review state, and delivery proof.
| Proof item | Source evidence | Client surface |
|---|---|---|
| Source sync and freshness | Connector health, recent sync runs, imported record types, stale-source state, and setup requirements show whether the report used current source evidence. | The report can name which sources were fresh, which source was held back, and which missing setup blocked a card or claim. |
| Dashboard card changes | Dashboard generation records the available source categories, unlocked cards, missing requirements, card rationale, and source-backed values for each client workspace. | A client can see which cards changed, which cards stayed locked, and why the dashboard is or is not ready for a specific claim. |
| Revenue attribution path | Spend, lead, deal, invoice, and payment records move through match rules, confidence states, exclusions, and no-match paths before revenue is credited. | The report can separate credited revenue from unmatched spend, open invoices, stale follow-up, and unsupported revenue states. |
| AI output review | Generated cards, Ask Data answers, weekly insights, and report summaries carry review state, source rows, requested changes, approval status, and held-output reasons. | Client-facing output stays blocked until the required review is approved or the unresolved state is intentionally kept visible. |
| Report delivery and export history | Report snapshots, export records, storage keys, recipient delivery records, failed-send states, and weekly notification history show what actually reached the client. | The agency can prove which report version was sent, when it was exported, whether delivery succeeded, and what evidence was included. |
Report surfaces
Reports, weekly digests, Ask Data answers, exports, and audit trails should preserve the same source path instead of creating separate stories for every surface.
| Surface | Buyer sees | Source path |
|---|---|---|
| Sample report | A client-ready report with source rows, campaign evidence, attention items, metric definitions, recommendations, and the unresolved gaps that still matter. | Report generation reads the same dashboard configuration, attribution output, insights, and review state used by the signed-in workspace. |
| Weekly insight digest | A recurring summary of what changed, which alerts matter, which revenue path needs follow-up, and whether the evidence is ready for client delivery. | Weekly insights read dashboard data, anomaly state, notification recipients, delivery records, and held-output state before sending. |
| Ask Data cited answer | A plain-English answer that cites the computed rows, date range, source filters, chart rows, and unsupported state behind a client question. | Ask Data constrains answers to supported query specs, tenant-scoped dashboard data, metric definitions, and cited source rows. |
| Export and audit trail | Export history, destination boundaries, storage state, compliance package status, and audit records that show where client-facing proof went. | Exports and compliance jobs preserve report snapshots, destination metadata, delivery status, and scoped retention behavior. |
Workflow
The workflow keeps source evidence, validation, AI review, report packaging, and next gaps together before a client receives the output.
Workflow detail
Each step shows how SIRJ turns source records and review decisions into the report artifact an agency can defend.
| Step | What happens | Visible proof |
|---|---|---|
| Capture the work evidence | SIRJ starts with source sync state, imported records, dashboard changes, Ask Data questions, review actions, weekly insight generation, and report export events. | Connector health, data lineage, dashboard builder, and reports pages show where each evidence type enters the reporting path. |
| Separate supported claims from blocked claims | The product checks source freshness, tenant scope, metric eligibility, attribution evidence, revenue state, and review status before a claim becomes report-ready. | Data validation and metric definition pages explain what gets blocked, marked unsupported, or allowed into client-facing proof. |
| Review AI-created output before delivery | AI-created dashboard cards, answers, report notes, and weekly insights need review state when the evidence is sensitive, incomplete, or client-facing. | Human review and AI dashboard builder pages show how generated work stays attached to source rows, rationale, and approval decisions. |
| Package the client-facing report | The report snapshot packages metrics, source rows, recommendations, attention items, unresolved gaps, delivery state, and export history into one client-safe artifact. | Reports, sample report, white-label reporting, weekly insights, and exports pages show how proof moves from workspace to client artifact. |
| Show the next proof gap | A proof-of-work report should end with the next source, review, follow-up, or delivery gap instead of pretending the client account is fully explained. | Revenue leak detection, connector health, and source coverage pages show which missing evidence should become the next action. |
FAQ
These answers make clear how source evidence, AI review, missing proof, and delivery history fit together before clients receive reports.
Yes. Normal reports often summarize performance. Proof-of-work reporting also shows the source evidence, review decisions, unresolved gaps, delivery state, and actions behind the result.
AI can draft sections when the source rows, metric rules, date range, and review state support the claim. If the evidence is weak, the output should stay held or marked unsupported.
The client-safe output should name the missing source, stale sync, unsupported metric, open revenue state, or review hold instead of turning the gap into confident performance copy.
It makes the agency's work visible every week: source repairs, follow-up gaps, reviewed outputs, report delivery, and the next action are easier to defend than a surface-level KPI recap.
Ready when the numbers need to hold up
Review source freshness, dashboard changes, AI output, held claims, report snapshots, exports, and the next proof gap before client reporting becomes a renewal conversation.