How Teachers Can Submit Maintenance Requests Without Calling Facilities Staff

Teachers can submit maintenance requests without calling facilities staff through one district-approved form or text-based intake that creates a trackable work order. The front end should be simple for a requester; the routing, priority rules, asset context, and accountability belong behind the scenes.

Give staff one obvious entry point

Place one “Report a facilities problem” link in the staff portal, intranet, or other tool employees already use. If the district supports text-message intake, publish one number and the same rules everywhere.

Avoid separate email addresses for HVAC, plumbing, electrical, and grounds. Teachers should not need to know which trade owns a problem.

Keep the request short

Ask for:

• school and room or exact location;
• a plain-language description of what happened;
• when the problem began;
• whether safety or instruction is affected;
• access notes; and
• an optional photo.

“Water is spreading from the sink in Room 12” is more useful than a long category tree. The system can classify the request after submission.

Put emergency instructions beside the form

Routine software intake is not an emergency reporting channel. Display the district’s approved procedure for fire, gas odor, active flooding, exposed electrical hazards, security concerns, and other life-safety events.

Teachers may select an urgency level, but facilities staff should confirm the final priority using district policy and available evidence.

Acknowledge and track the request

Send a reference number and confirmation that the request was received. Use plain statuses such as received, assigned, in progress, waiting on parts, and closed.

Do not promise a repair time the team cannot meet. Acknowledgement reduces follow-up calls; false precision creates more of them.

If several people report the same problem, combine the work without discarding the requesters. Each person should receive the appropriate update while technicians work from one operational record.

Give facilities the context to act

The system should connect the request to the building, room, related asset, recent work, inspections, and similar open issues. Relevant schedule, energy, or supported building-system signals can help facilities decide whether the next step is a technician visit, controls review, inspection, or clarification.

AI can summarize and organize this context. It should not make an unsupported safety decision or treat a likely cause as a confirmed diagnosis.

Technicians need the request, priority reason, location, history, photos, and access notes on a mobile device. Closeout should record what was found, what changed, the asset’s condition, and any follow-up.

Pilot before district-wide rollout

Start with one or two schools and review:

• incomplete submissions;
• emergency issues sent through the wrong path;
• duplicate requests;
• time to acknowledgement and triage;
• follow-up calls;
• work orders missing location or asset context; and
• requester feedback.

Adjust categories, instructions, and notifications before expanding.

Where Edviro fits

Edviro includes native maintenance-request, CMMS, work-order, asset, inspection, and mobile field workflows. A district can use Edviro to replace an incumbent work-order and asset system, or integrate Edviro with the CMMS it chooses to keep.

Edviro can also connect operational context such as schedules, energy data, and supported building signals to the request. Facilities staff retain authority over priority, field work, safety, and closure. Supported control actions require the necessary integration, permissions, safety review, operating bounds, and customer authorization.

The best request process is easy enough that staff use it and structured enough that facilities does not have to call back for the basic facts.