Overview
The first week of using Orah is about building confidence, not achieving perfection.
This article outlines best practices to help boarding schools settle into daily use, identify issues early, and support staff during the initial rollout.
What to Expect in the First Week
During the first week, it’s normal to see:
Questions from staff
Small configuration changes
Minor data adjustments
Learning moments around workflows
This is expected and part of a healthy Go-Live process.
1. Keep Workflows Simple
During the first week:
Focus on core boarding workflows
Avoid introducing too many optional features at once
Prioritise roll calls and sign-in/sign-out
Once these are working smoothly, additional features can be layered in.
2. Monitor Roll Calls Closely
Roll calls provide the clearest signal of how Go-Live is progressing.
Best practices:
Review roll calls daily
Check for patterns in exceptions
Follow up quickly on missing students
If roll calls are running smoothly, most other workflows will fall into place.
3. Support Staff Actively
Staff may need reassurance during the first few days.
Helpful approaches include:
Checking in with House Parents regularly
Encouraging questions early
Providing quick guidance when needed
Reinforce that mistakes can be corrected and that accuracy improves with use.
4. Expect and Adjust Configuration
It’s common to refine:
Locations
Pass rules
Notification settings
Role assignments
These adjustments are normal and expected after real-world usage begins.
5. Review Data Daily
During the first week:
Review student assignments
Check sign-in/sign-out records
Ensure data reflects reality
Catching small issues early prevents larger problems later.
6. Avoid Overloading Staff
Avoid:
Introducing too many new features at once
Changing workflows daily
Expecting full mastery immediately
Confidence grows through repetition, not complexity.
Signs of a Successful First Week
Staff are completing roll calls independently
Student movement is recorded consistently
Questions decrease over time
Small issues are resolved quickly
What’s Next
After the first week:
Continue refining workflows
Introduce optional modules if needed
Review reporting and insights