SOFTWARERADAR — SMARTSHEET REPORTING EXAMPLE

Guide: https://softwareradar.co.uk/guides/smartsheet-sheets-reports-dashboards/
Fixed review date: 16 October 2026. All projects, people roles and tasks are fictional. These are planning files, not Smartsheet exports, a completed product trial or customer data. No account, report, dashboard, sharing setting, published link or subscription was operated.

source-tasks.csv contains six unique flat task rows, three each from Site A and Site B. There are no parent/summary rows. The same columns are proposed for both sources. Two tasks are Complete and four are open (any status other than Complete). Overdue means open AND due_date before 2026-10-16. A02 and B03 match. B02 is due on the review date and is not overdue. The two overdue rows are part of the four open tasks, not additional tasks. These are task counts, not hours or project completion percentages. Date comparisons are calendar-day ISO dates; no time-of-day or dynamic current-date calculation is supplied.

expected-overdue-report.csv is the expected two-row selection from the six source tasks, not two additional tasks to append to a live source. The controlled-change check proposes moving B03 due_date to 2026-10-18 in a separate test copy. The expected overdue count becomes one, the open count remains four, and B03 stays Blocked. A changed due date does not resolve its blocker. This change has not been performed in Smartsheet.

reporting-review.csv has six proposed checks. Actual environment, retained plan, viewer role/seat type, observed result, evidence, reviewer and decision are blank. Review both source-sheet permissions for direct report access and the report widget Viewer Mode for dashboard access. Map this editorial schema to an authorised environment; these files do not configure a Smartsheet account or enforce permissions. The two-source reporting design needs a plan supporting multi-sheet reports; Pro allows one source sheet per report.