School implementation guide
Plan a school rollout that your team can manage
Work through school approvals, staff ownership, family participation, and a reviewable first deployment of visual narratives.
By the StoryRetriever team · September 7, 2026 · Product and workflow guidance
Read and adapt the proposal
Proposal: evaluate StoryRetriever for our school Situation we want to support: [describe a routine without identifying a child] Evaluation lead: [name] Staff / sponsored families / sites: [counts] Evaluation task: create, review, and share a fictional visual story on our usual devices. Required review: privacy, data agreements, accessibility, and account administration. Budget: request a written organization quote. Sponsored family access is $23.88 per family annually; staff and site terms require confirmation. Success criteria: [first useful story, successful recipient access, staff feedback] Review date and decision owner: [date and role] Next step: [approve evaluation scope or request more information] Reference: Plan a school rollout that your team can manage
Start with a routine and an owner
Pick a situation your staff already support, such as arrival or a transition between spaces. Name a school lead who can coordinate the evaluation and a separate contact for purchasing or approval where needed. Write down what a useful first deployment would look like in ordinary language.
A small scope makes feedback easier to interpret. One team creating and sharing a suitable story can reveal unclear instructions, access problems, and training needs before a broader launch.
Complete the approval work before student use
Use the public examples and fictional account content while reviewers assess the product. Ask your school which data agreements, accessibility evidence, identity requirements, and device checks it needs. A browser-based tool may still require school approval.
Send required agreements for review rather than assuming a signature or a standard turnaround time. Confirm your deployed access configuration, including any school-managed login or roster workflow, before relying on it.
- Review the privacy policy and trust information with the appropriate school lead.
- Test the actual devices and assistive technology staff and families expect to use.
- Confirm account ownership, sharing permissions, retention requirements, and offboarding responsibilities.
Make the family introduction specific
Explain why the story was created, how to open it, and who to contact if it does not reflect the child's experience. Distinguish reading a shared link from joining the organization or receiving sponsored access. Families should know what each invitation allows.
Decide how feedback returns to the staff member who maintains the story. If a routine changes, review the relevant words and images together. Use language that describes the child's actual situation rather than assuming every child should respond in the same way.
Review the rollout and plan continuity
At the agreed review date, check how many intended staff could create a useful resource and whether invited families could access it. Ask what required extra help. Keep workflow feedback separate from any educational or clinical outcome assessment.
Before the school year ends or staff change, review administration, family participation, and any managed-student requirements. Each building has its own organization administration; include that operational responsibility in any multi-building proposal.
Useful next steps
- Explore the product walkthrough
- Prepare your organization quote request
- Review trust and privacy information
- Read the accessibility statement
These guides support evaluation. They are not a signed agreement, a customer case study, or a claim of a particular clinical or educational outcome.
A clear next step
Let's work through your setup.
Tell us about your team and what you need to evaluate. We'll use your inquiry to discuss fit, pricing, and the next steps.