Maintenance Request

Use this template for broken fixtures, leaks, HVAC problems, electrical issues, furniture damage, and other facility or equipment defects that need maintenance review. It is designed for actionable repair requests, not general feedback or incident reporting. If the issue affects safety or operations, the priority field and urgent_reason help route it correctly. For non-maintenance topics, use a different intake form to keep the workflow clean.

Any employee, tenant, or site user who notices a repair issue can submit it, depending on your access policy. The requester_information section captures a name and email so the maintenance team can follow up if more detail is needed. If you want anonymous reporting for sensitive environments, this template would need a separate anonymous submission option. For standard facilities workflows, named submissions usually make triage easier.

Use it whenever a new issue is discovered, rather than batching multiple unrelated problems into one request. That keeps priority, location, and photo evidence tied to a single work item and reduces back-and-forth. Repeated issues at the same location should be submitted again if they recur after a repair. If your team tracks recurring defects, you can add a duplicate-check or asset tag field.

The issue_summary should state the problem in one line, and issue_details should explain what is happening, when it started, and any immediate impact. Include the asset or fixture involved if known, plus any conditions that make the issue worse or safer to approach. Avoid vague language like 'not working' when you can describe symptoms. Clear details improve validation and reduce unnecessary site visits.

Priority should reflect the operational impact and safety risk, while urgent_reason explains why the request cannot wait. Use conditional logic so urgent_reason appears only when a high-priority option is selected, which keeps the form shorter for routine issues. Do not mark every request urgent, because that makes true emergencies harder to spot. If your process includes emergency escalation, define it clearly in the form instructions.

Ask users to upload clear photos that show the defect, the surrounding area, and any identifying labels or asset numbers if relevant. The photo_description field should explain what the images show and why they matter. Keep file guidance simple and accessible, and make sure the upload control works well on mobile. If photos are not possible, allow a text fallback so the request can still be submitted.

Yes, if the form collects requester contact details or photos that may include people, you should include a brief notice about how the data will be used and who can access it. Apply GDPR data minimization by collecting only the fields needed to dispatch and resolve the request. If the form is used in a workplace setting, keep the language clear about internal routing and retention. For public-facing locations, make sure the form meets WCAG 2.1 AA accessibility expectations.

You can add dropdowns for asset type, department, or service category, and use conditional logic to show asset-specific fields only when needed. Multi-site organizations often add building codes, asset IDs, or service zones to improve routing. Keep optional fields truly optional so the form stays quick to complete. If you integrate with a ticketing system, map the fields to the same categories your maintenance team already uses.

A form creates consistent fields, validation, and an audit trail, which makes requests easier to triage and track than scattered messages. It also reduces missing information because the form can require the location, priority, and photo evidence needed for action. Email and chat are useful for discussion, but they are harder to standardize and search later. This template turns an ad hoc report into a repeatable intake process.