Illustrative workflow
Review and share a client report
Build a report around one authorized client scope, explain source definitions and missing inputs, preview the artifact, and verify recipient access before sharing.
Published by the Bach.ai team · Editorial standards
Evaluation guide with illustrative examples. This is not a customer case study, execution receipt or promise of feature availability in a particular account.
1. Choose the scope
Select the client brand, connected accounts and reporting window. A multi-brand agency view does not authorize mixing client data into one report.
2. Review the evidence
Confirm currency, timezone, source definitions and freshness. Keep store revenue separate from advertising attribution and mark missing data honestly.
3. Explain the next decision
Separate observed results, diagnoses, estimates and proposed actions. Name the evidence and uncertainty behind each recommendation.
4. Preview as the intended reader
Check the actual shared/exported artifact for account scope, layout, charts, labels and branding. Available sharing and white-label options depend on the account plan.
5. Check access before distribution
Use the supported access controls. Verify that the intended recipient can read the report and that unrelated client data is absent. An export or link alone does not establish delivery.
Worked example
Synthetic example: Meta purchase value and store sales can overlap. Present them as separate defined measures; do not sum them into a larger revenue headline.
If the flow cannot continue
Check access, connected sources and permissions. If evidence is missing or stale, reconnect or collect sufficient data before judging performance. If an action is unsupported or the result is uncertain, inspect the account’s status and receipt rather than assume success or repeat a write.
Review product capabilities · Ask about a workflow requirement
Last updated