Who this is for: Teams demonstrating reporting workflows.
What to prepare
- Field definitions
- Consistent fictional dataset
- Builder states
- Saved report or clearly labeled preview
Scene-by-scene storyboard
60-second planning sequence · illustrative copy and visual direction
- 01
0–7s
Ask the reporting question
Show a neutral question card beside the sample workspace.
On screen:Which sample requests await review?
- 02
7–16s
Inspect the input
Show R-014 Awaiting review, R-015 Draft, R-016 Awaiting review and R-017 Approved. Keep the sample-data label.
On screen:Four illustrative requests
- 03
16–26s
Choose fields
Use the actual builder to select Identifier, Subject and Status. Hold the selected field names.
On screen:Show the fields needed to identify the work
- 04
26–36s
Define the condition
Set the verified Status equals Awaiting review condition and show its scope.
On screen:Status: Awaiting review
- 05
36–44s
Run and save
Perform the actual run and save sequence for Sample review queue. Preserve observed pending feedback.
On screen:Create Sample review queue
- 06
44–55s
Read the result
Inspect R-014 and R-016 in the resulting report with the active condition visible.
On screen:Two sample requests match
- 07
55–60s
Bound the interpretation
Hold the report title and condition while stating the limited answer.
On screen:This view identifies the matching sample records
Make it your own
- Report question and fields
- Choose one question and the actual fields and definitions needed to answer it.
- Illustrative dataset
- Replace all source rows, filter conditions and output counts as one consistent example.
- Run and persistence
- Supply the actual run/save path and label a preview accurately when no saved report exists.
Prepare the report model
Supply actual field definitions, filter semantics and save behavior. Confirm whether each row represents a request or an event. The illustrative count is valid only for the stated four-record dataset.
Adapt the reporting question
For a date-based question, identify which date field is used. For 30 seconds, begin with prepared fields and explicitly state that setup, then focus on the condition and result. Do not hide a consequential grouping or permission rule.
Review the interpretation
Compare every displayed row with the source dataset. Avoid conclusions about productivity, delay or workload beyond this example. If the report is merely a preview, use that label and do not imply it was saved for later use.
Review checklist
- Field choices serve one question.
- Result rows satisfy the shown condition.
- Preview and saved report are distinguished.