Make the demonstration about your work, not just a tour of menus. Choose fictional scenarios and record what is actually demonstrated. Do not treat a screenshot, roadmap item, or verbal statement as the same kind of evidence as a completed workflow.
Choose the people and the process
Identify the roles that would use the platform: reporters, reviewers, task owners, facilities personnel, school safety personnel, and workspace administrators. Ask which responsibilities each role should and should not have.
Scenario 1: Staff intake
Ask to see a non-emergency staff concern entered and submitted for review. What information is required? What does the reporter see afterward? Who can find the report, and what action happens next?
Scenario 2: Administrator review
Ask to see how a reviewer finds outstanding reports and incidents requiring attention. Distinguish the submitted information from later classification, investigation, or follow-up decisions. Do not assume a report automatically becomes an incident.
Scenario 3: Assignment and follow-up
Ask to see a task created, assigned, given a due date, updated, and completed. What prerequisites or permissions apply? How is overdue or unassigned work identified? What does another authorized reviewer see?
Scenario 4: Facility concern
Use a fictional facility issue. Ask to see the location, category, priority, assignment, due date, status, and resolution. Confirm which actions are available to the reporter, facilities staff, and administrators.
Scenario 5: Plans and operational review
Ask to see the safety-plan and drill-planning areas relevant to the proposed deployment. Review which users may see planning details. Explore how the team reviews open work and finds the records it needs.
Record the evidence
For each requirement, write what you saw, the user role demonstrated, and who will resolve any open question. Keep a separate note of answers that still need technical, privacy, or procurement verification.
| Requirement | Evidence seen | Status | Follow-up owner |
|---|---|---|---|
Status options: demonstrated now; requires configuration; requires verification; not currently available. Do not mark a feature as current merely because it is planned.
Questions before the next step
Ask for the proposed scope, price, agreement terms, onboarding responsibilities, support arrangements, and any implementation prerequisites. Identify the technical and privacy review required before using student records. Discuss export and exit needs without assuming a particular format or service is included.
Keep separate decisions separate
Product fit, technical/security evidence, legal/procurement approval, and operating readiness are different decisions. A positive demonstration does not resolve the other reviews.
This resource helps organize a demonstration. It is not a product specification, a promise that every requested feature exists, a security assessment, legal advice, or emergency-response guidance.