Submit and track requests
Capture facilities, building repair and technology requests, then follow their progress in the school workspace.
RepairRequest
Give every request a clearer place to go.
Maintenance, building repair and technology requests in one school workspace. Help staff report the problem and give the team handling it a place to track the work.
Keep campus work from getting lost in an inbox.
Bring request details and the team responsible for following through into one workflow.
Add useful context
Request photo and file support lets staff provide information that helps the team understand the issue. Availability and limits are confirmed in the product scope.
Coordinate the team
Team invitations and administrative roles support the people handling requests. Review permissions around the responsibilities at your school.
Review the work
Reporting, exports and audit logs help the team look back at recorded request activity. Advanced API and webhook needs can be discussed separately.
From a reported problem to a visible next step.
Report the issue
Start with the request type and the information the facilities or technology team needs to assess the work.
Coordinate the response
Use a shared request record so the team can follow the issue through its agreed process.
Review and improve
Use recorded requests and reports to discuss what needs attention and how the school handles recurring work.
RepairRequest is for routine request coordination. It is not an emergency reporting or response service. Use the school’s established emergency process for urgent safety incidents.
Make the fit clear
before you start.
A useful request process needs clear responsibilities, suitable access and realistic support expectations.
How we approach school trust- Request categories. Agree what belongs in facilities, building repair and technology requests, and which issues need another school reporting process.
- Uploads and privacy. Set expectations for request photos and attachments. Avoid student, health or other sensitive information unless specifically required and approved for the workflow.
- Roles and reporting. Review who can submit, view and manage requests, who needs reporting access and how records will be retained.
- Availability and connections. Confirm features, plan limits, imports and any API or webhook integration for your school. No connection to another SchoolOS app is assumed.
Where do campus requests get stuck?
Bring us your current maintenance and technology request process. We’ll review what a useful first rollout would look like for your team.
Discuss RepairRequestPlease leave student names, records and sensitive details out of your first email.