Choose One Scheduling Change and One Record
Use DEMO-017, a fictional appointment at an ophthalmic practice. In the example, a patient asks to move it from 09:00 to 10:30. A scheduler handles the change, and a coordinator checks what needs attention next. Treat the patient’s request as spoken context unless the software actually records requests.
Fix four details before preparing the screens:
Record: DEMO-017 · Change: 09:00 → 10:30 · Roles: scheduler and coordinator · Administrator’s check: the record’s current status and the owner of the next task.
Check the role names against the exhibitor’s product. If the next task goes to someone other than a coordinator, use that person’s actual role throughout the demonstration.
One appointment stays identifiable as the presenter moves from the scheduler’s change to the coordinator’s next task.
Show Each Role’s Action and Next Task
Move through the product in the order the staff would. Show a save, approval, refresh, or manual lookup when the handoff depends on it.
Staff Role | Starting View | Action Shown | Visible Change | Next Task |
|---|---|---|---|---|
Scheduler | DEMO-017 at 09:00 in the scheduling view | Enter 10:30; save or submit if required | The product’s actual result after the action, whether saved or pending | Complete any required step before the next role checks the record |
Coordinator | The view this role actually uses to check appointments | Find DEMO-017; show any required manual lookup or refresh | The time and status this role can actually see | Handle the next task assigned in the chosen workflow |
Both roles may use the same software screen. If the interface does not identify who is acting, place a small role label in the booth graphics beside the monitor. Keep it visually separate from the product interface.
Keep the Record and Change Visible as Screens Switch
Keep a short reference strip within the visitor’s sightline: DEMO-017 · Original: 09:00 · Requested: 10:30 · Current role. Update the role label when views change, but leave the record and times in place. The strip is a presentation aid, not a software feature.
Follow one presentation order:
Original booking → scheduler’s action → next role’s actual view → next task
The arrows show the order of the explanation, not an automated handoff. At each switch, explain one new action or state. If the original time disappears after the edit, use a labeled before-change reference. Keep a backup screenshot of the same record only to preserve the sequence.
Finish by asking the administrator to name the next owner and task. If the answer is unclear, improve the transition between screens.
The display brief places the product screen, presenter, and visitor discussion where the workflow remains easy to follow.
Convert the Workflow into a Booth Display Brief
Write the display brief after rehearsing the sequence. Two roles can share one monitor when visitors can follow DEMO-017 and the role change. Show two product views at once only when comparing them matters. Mark where the presenter and visitors will stand before choosing display equipment.
Brief Field | Entry for This Demonstration |
|---|---|
Scenario and record reference | DEMO-017; requested move from 09:00 to 10:30 |
Roles shown | Scheduler, then coordinator or the actual next role |
Required product screens | Original booking, edit or submission result, and next-role view; these may appear in sequence |
Reference information that stays visible | DEMO-017, original and requested times, and current role, outside the product interface |
Workflow graphics or labels | Short role and next-task cues, clearly separate from the software |
Presenter position | Beside the screen without hiding the product action |
Visitor viewing position | Able to read the product view and record reference together |
Consultation requirement | Brief questions at the screen; a separate point if another demonstration runs at the same time |
Content owner and readiness check | Exhibitor’s demo owner verifies product states; asset owner delivers matching labels and reference images |
If an administrator is still asking questions when the next walkthrough starts, the ASCRS software booth layout needs room for both visitor groups.
Compare [San Diego booth rentals against the brief’s screen support, graphic surface, and discussion needs before choosing counters or display structures.
Questions About Scheduling Workflow Demos
Does a scheduling change demo need two monitors?
Only if visitors must compare two product views at the same time. A sequential presentation may work on one monitor if the record and active role remain clear.
Should the demonstration show every staff role?
Show the people who handle this change or own its next task. Add another role only if that person’s action is needed to answer the administrator’s question.
What if the next staff view does not update automatically?
Show the manual check, pending state, or other step the product actually requires. Do not let a presentation arrow imply an automatic update.
Other product displays and buyer meetings may need the same space. Account for them in the wider ASCRS 2027 booth plan
