Review the details before your district's pilot.
Bring your IT team into the conversation. Review staff access, data handling, exports, and accessibility requirements alongside the people who manage your facility rentals.
Give staff access for the work they do.
Staff sign in with individual accounts. District administrators assign roles and schools, so access follows each person's responsibilities within the district.
School staff work within their assigned schools. Finance access covers financial records and relevant reporting across the district. A staff role does not grant access to another district's records.
Review your team's access needs.
We'll discuss who needs to approve rentals, prepare requests, manage payments, and view reports. Bring any district sign-in requirements to that review so we can confirm the supported setup.
Plan for the records your district needs.
Wise Old Owl does not sell district or renter data or use it for advertising.
Authorized staff can download CSV exports of reporting and online payment records. Access to exports follows staff permissions, including restrictions on financial information and school scope.
If your district ends its pilot or stops using Wise Old Owl, we'll help with available exports and an agreed records handoff. We'll settle the scope before the pilot, including any documents, agreements, or messages your district needs. CSV exports are not a complete archive of every file and conversation.
Bring your data review questions.
Share your requirements for hosting and data location, retention, deletion, agreements, and records access. We'll review them with your IT team before setup and confirm what can be supported within the pilot.
Document retention and an end-of-pilot handoff need to account for the records your district must keep.
Working toward WCAG 2.2 Level AA.
We're working toward WCAG 2.2 Level AA and will review your district's accessibility requirements before pilot setup. This is our target, not a claim of current conformance.
Our target covers the marketing site, renter application, and staff application. Accessibility assessment and improvement work are underway.
Discuss accessibility needs early.
Tell us about the assistive technologies and workflows your district needs to evaluate. We'll discuss the current assessment status and any known limitations as part of the IT review.
Questions to bring to your technical review.
How is staff access controlled?
Staff sign in individually. Access depends on their assigned role, district, and schools. District administrators manage staff roles and school assignments; operational and financial access follow those permissions.
Can we export records or retrieve them when we leave?
Authorized staff can export reporting and online payment records as CSV files. If your district leaves, we'll help with available exports and an agreed records handoff. We'll settle the scope before the pilot, including any documents, agreements, or messages your district needs.
Can we use our existing sign-in, calendar, or accounting system?
The current pilot uses individual staff sign-in, staff-entered blackout dates, and CSV exports. Bring any district single sign-on, calendar, or accounting integration requirements to the IT review so we can confirm what the pilot can support before setup.
What is your accessibility status?
We're working toward WCAG 2.2 Level AA and will review your district's accessibility requirements before pilot setup. This is our target, not a claim of current conformance.
Include your IT team in the walkthrough.
Share your technical questionnaire and the requirements that matter to your district. We'll review them together before pilot setup and agree on the scope. For fees, refunds, and outside payments, see the Payments guide.