# Report on Salesforce delivery from what actually shipped. > SyncOnAI 360 Reports is a dashboard of widgets on one report engine, the same engine each project's Reports tab uses. Widgets cover delivery, deploys, org health and audit trends, can be arranged freely, and each one states how much of the data it covers, so a report never implies more certainty than it has. Source: https://synconai360.com/features/reports ## Key facts - **1**: Report engine for the dashboard and every project - **4**: Areas covered: delivery, deploys, health and audit - **Every**: Widget states how much data it covers - **30s**: Command Center refresh interval ## Why Salesforce status reports take so long to build Status reporting means pulling numbers from a ticketing tool, a deploy log and an org health tool into slides. The numbers disagree, take hours to assemble, and say nothing about how complete they are. - **Numbers from five places.** Delivery, deploys and org health each live in a different tool with a different export. - **Two report engines.** Project reports and leadership dashboards are built twice and drift apart. - **False precision.** A chart drawn from partial data looks just as confident as one drawn from all of it. - **Effort over insight.** The hours go into assembling the report, not acting on it. ## What can Salesforce delivery dashboards show? Add widgets for delivery, deploys, org health and audit trends, and arrange them as you like. Because work items link to the deploys that delivered them, delivery widgets reflect what shipped rather than what was dragged across a board. Older saved snapshots remain on the page below the live widgets, so earlier reporting is not lost when the dashboard is redesigned. - Delivery, deploys, health and audit widgets - Arrange freely - Saved snapshots kept below ## Why does one report engine matter? The main Reports page and each project's Reports tab use the same engine, so the widget a project lead builds and the one leadership reads show the same numbers in the same way. There is no second reporting layer to reconcile. Project reports sit alongside the board, backlog, sprints, roadmap and releases, so delivery leads report where they plan. - Same engine for projects and leadership - No reconciliation between layers - Reports beside the plan ## How does a report show how complete it is? Every widget says how much of the data it covers. A health trend that includes three of five connected orgs says so, rather than presenting a partial picture as the whole. The same principle runs through the platform: missing data is reported as missing, not as zero, so decisions made from a dashboard rest on what is actually known. - Coverage stated per widget - Partial data labelled - Missing never shown as zero ## Where do leaders see the whole picture? The Command Center shows pulse metrics for portfolio health, metadata, AI readiness, the sales pipeline, backlog and the action queue; an org portfolio with health scores; PM backlog KPIs and sprint progress; recent agent runs; a sales snapshot; and an activity feed of syncs, deploys and audits. It refreshes about every thirty seconds, and its layout can be rearranged and sections hidden, with the layout saved in the browser. - Pulse metrics across the workspace - Org portfolio and delivery KPIs - Activity feed and action queue - Custom layout ## How do you report to a client or to leadership? Build a dashboard for the audience: delivery and deploys for a steering group, health and audit trends for a platform review. Because every widget states its coverage, the conversation stays on what the numbers show rather than on whether they can be trusted. For an external audience, share org health and audits as read-only links that expire, and keep the dashboard itself for the team. - A dashboard per audience - Coverage keeps trust - Read-only links for outsiders ## Building a dashboard 1. **Connect.** Orgs, projects and deploys feed the report engine. 2. **Add widgets.** Pick delivery, deploy, health and audit widgets. 3. **Arrange.** Lay them out for your audience. 4. **Read honestly.** Each widget states its coverage. ## Status reporting, with and without SyncOnAI 360 | Without | With SyncOnAI 360 | |---|---| | Exports from five tools into slides | One dashboard over connected data | | Project and leadership reports disagree | One report engine for both | | Charts that hide missing data | Coverage stated on every widget | | Delivery by card movement | Delivery linked to actual deploys | ## Who reads the reports - **Delivery leads.** Report progress from what actually shipped, because work items link to the deploys that delivered them, with the same widgets on each project and on the main dashboard. - **Consultancies.** Show each client delivery, deploys and org health in one place, with coverage stated on every widget so nothing looks more certain than it is. - **Platform owners and executives.** See health, delivery, agent runs and the action queue across every org in the Command Center, refreshed about every thirty seconds. - **Salesforce admins.** Track health and audit trends for the orgs you look after, and keep earlier snapshots when the dashboard changes. - **Practice leads.** See the sales snapshot, recent pursuits and win rate beside delivery in the Command Center, so the pipeline and the work it creates are read together. ## Frequently asked questions ### What can Salesforce dashboards in SyncOnAI 360 show? Widgets for delivery, deploys, org health and audit trends, arranged as you like. ### Is it the same as project reports? Yes. The main Reports page and each project's Reports tab share one report engine. ### How does it handle missing data? Every widget says how much of the data it covers, and missing data is never shown as zero. ### Can we keep old reports? Older saved snapshots remain on the page below the live widgets. ### Is there an executive overview? The Command Center shows pulse metrics, the org portfolio, delivery KPIs, agent runs, the sales snapshot and an activity feed. ### Can we customise the Command Center? Yes. Rearrange and hide sections; the layout is saved in your browser. ### Can we share reports with clients? Health reports and audits can be shared as read-only links that you can withdraw at any time. ### Are reports on every plan? Yes. Every plan includes every feature. ### How current is the data? The Command Center refreshes about every thirty seconds. Org health and audit widgets reflect each org's latest sync and audit. ### Can project leads build their own reports? Yes. Each project's Reports tab uses the same widgets and the same report engine as the main dashboard. ### Do reports include CRM data? Reports cover delivery, deploys, org health and audits. CRM records are not stored; for record data, ask the chat, which queries the org live.