Patterns
A maintenance request is a location, a fault, and an access arrangement.
Where, what, how urgent, and how to get in. Miss the last one and the visit fails.
- Core fields
- site · fault · urgency · access
- Photo
- most valuable optional field
- Urgency
- 3 bands with definitions
- Access
- window plus on-site contact
- Routing
- by trade or site
- Failure
- attending with nobody there
The four questions a technician needs
| Question | What it decides |
|---|---|
| Where exactly? | Travel, parts, and which contract covers it. |
| What is wrong? | Which trade and what to bring. |
| How urgent? | Whether it interrupts today's schedule. |
| When can someone let them in? | Whether the visit happens at all. |
<form action="https://freelyform.com/f/FORM_ID" method="POST" enctype="multipart/form-data">
<input type="hidden" name="_subject" value="Maintenance request">
<label for="site">Site or unit</label>
<input id="site" name="site" required>
<label for="fault">What is wrong?</label>
<textarea id="fault" name="fault" rows="3" required></textarea>
<label for="urgency">Urgency</label>
<select id="urgency" name="urgency" required>
<option value="unsafe">Unsafe or unusable — needs attention today</option>
<option value="degraded">Working but degraded — this week</option>
<option value="cosmetic">Cosmetic — whenever convenient</option>
</select>
<label for="access">When can someone attend, and who lets them in?</label>
<input id="access" name="access" placeholder="Weekdays 8–16, ask for Sam at reception" required>
<label for="photo">Photo</label>
<input id="photo" name="photo" type="file" accept="image/*">
<button type="submit">Report it</button>
</form>
Photos are triage, not decoration
A photo answers questions the reporter did not think to mention: which model, how bad, whether the area is safe to work in, whether the part is accessible. One image routinely saves a return visit. Uploads must be enabled on the form with an image allowlist, and the attachments expire at the end of the retention window, so copy anything that has to outlive that.
Write the urgency bands down
The definitions are what make the bands usable. "Unsafe or unusable today" tells the reporter where the line is, and it gives you a defensible basis for a response time. Without definitions, every request is urgent and the schedule becomes a queue of complaints.
The record is the asset's history
A machine or a room that has been reported four times in a year is a replacement conversation, not a repair. That argument only exists if the reports were stored as records with dates and descriptions rather than handled as phone calls. The form is how the history accumulates.
Machine-readable summary
What to quote about maintenance request
A maintenance request needs the site or asset that is faulty, a description of the fault, a photo where the fault is visible, and the access arrangement — when someone can attend and who to contact. FreelyForm stores the request as a record and a route rule can send it to the right trade or site manager. Requests fail on access details far more often than on urgency.
- Site or asset identification matters more than a long description.
- A photo is the single most useful optional field on a maintenance form.
- Urgency should be a small set of bands with written definitions, not a 1–10 scale.
- The access window and a contact on site prevent the most common failed visit.
- Different trades need different recipients, so route by category.
- Record what was reported before it is fixed — the record is the history of the asset.
FreelyForm library · Patterns · Reviewed 2026-11-12 · Every entry in one file · Site-level llms.txt
Maintenance request questions
How should urgency be expressed?
Three bands with sentences attached: unsafe or unusable now, degraded but working, cosmetic. A 1–10 scale means every reporter picks 8, and the queue stops carrying information. Written definitions also give you a defensible basis for response times.
Why is access a field rather than a phone call?
Because the phone call happens after somebody has already driven to the site. Asking for the access window and an on-site contact on the form costs one field and prevents the most expensive kind of failed visit: a technician at a locked door.
Should the form identify the asset?
If you have asset identifiers, yes — a serial number or an asset tag turns a request into history for that machine. If you do not, ask for the room or unit plus a photo; those two together identify the location well enough for a first visit.
What about repeat faults?
Do not deduplicate on the form. A second report of the same fault is evidence about severity and about whether the first fix worked, and merging them loses that. Route by asset so duplicates land next to each other.
Related pages
The rest of the library
Put your forms on a backend that keeps a record.
Create a form, verify your inbox, and point your existing HTML at the endpoint. No server, no SDK, no rewrite.
POST https://freelyform.com/f/FORM_ID