What should a maintenance request form ask?

A store manager notices that the front cooler is warm and the temperature is still climbing. They send a message to a group chat. Someone turns that message into a work order. By the time it reaches the repair company, the description simply says, "Unit not working."

No one gave bad information. The useful details disappeared as the request moved from one person to the next.

A good maintenance request form holds on to those useful details. It captures what the person at the location can actually see, makes the impact clear, and gives the facilities team enough information to decide what happens next. Its job is simple: help the next person act without guessing.

Start with eight practical questions

The best questions are ones a person at the location can answer without technical training.

1. Which location needs help?Fill this in automatically when possible. If several sites have similar names, include the address or location number.
2. Where at the location is the problem?Ask for a useful description such as "front checkout," "kitchen prep area," or "second-floor restroom."
3. Which asset or piece of equipment is involved?Let the person choose from an asset list or scan a QR code when one is available. They should still be able to submit the request if the asset is unknown.
4. What is happening right now?Ask for what they can see, hear, smell, or feel. "The cooler reads 42°F and is getting warmer" is more useful than "the compressor is bad." The first is an observation. The second is a diagnosis that may be wrong.
5. When did it start, and is it changing?A problem that started ten minutes ago and is getting worse may need a different response from one that has stayed the same for several days.
6. How is it affecting the location?Ask whether the issue is affecting customers, employees, inventory, security, or the location's ability to operate.
7. Is there an immediate safety risk or a chance of more damage?Give the person a clear way to report water near electrical equipment, smoke, sparks, a burning smell, an unsecured entrance, or another immediate danger.
8. Can they safely add a photo or short video?Photos of the equipment, control screen, alarm message, or surrounding area can help. Make it clear that no one should enter an unsafe area or get close to a hazard just to take one.

These eight questions cover what most requests need at the start. Keep the form short, and only show extra fields when an earlier answer makes them relevant. If every request opens a long list of questions, people will look for a faster way around it.

Ask for symptoms, not a diagnosis

Location teams know what changed and how it is affecting the business. Do not make them identify the failed part.

Compare these two requests:

The useful request never guesses at the cause. It gives the facilities team enough to select the right trade, judge the impact, and help the technician prepare for the first visit.

Use follow-up questions only when they change the next step

Different problems need different details. The form can reveal a few follow-up questions after the person chooses a category.

Refrigeration or HVAC

Ask for the current temperature, the normal temperature, and any alarm message shown on the control. For refrigeration, ask whether inventory is at risk. For HVAC, ask which areas are affected and whether the system is running at all.

Plumbing or water leaks

Ask whether water is still flowing, where it appears to be coming from, and what is below or beside it. Water above an electrical panel requires a different response from a slow drip under a break-room sink.

Electrical

Ask about smoke, sparks, heat, buzzing, or a burning smell. Find out whether one outlet or piece of equipment is affected, or whether power is out across a larger area.

Doors, locks, and access

Ask whether the location can still be secured. Is the door stuck open, stuck shut, or simply difficult to move? A door that will not latch is not the same as a door that squeaks.

Only ask for follow-up details that may change the trade, priority, safety response, or first visit.

Let the location report the impact

Priority codes belong to the facilities team. Labels such as P1, P2, or P3 may be familiar to facilities, but they mean little to someone who uses them only a few times a year.

Ask about the conditions instead:

• Could anyone be harmed?
• Is the problem causing additional damage?
• Can the location stay open and secure?
• Is there a safe temporary way to reduce the impact?

The location reports what is happening, and the facilities team uses those answers to set the priority.

Keep the full story on one work order

The original request, photos, calls, messages, vendor updates, approvals, completion notes, and invoice should stay connected to the same work order.

When part of the story lives in a group text and another part sits in someone's inbox, the next person has to rebuild the history before making a decision. Details get missed, and the same questions get asked again.

One record gives everyone the same version of the job, from the first report through completion.

Make the form easier than working around it

The form should work well on a phone held in one hand. When possible, it should already know the person's location. A QR code on a piece of equipment can fill in the asset information and reduce typing errors.

Once the request is submitted, send a confirmation that tells the person:

• The work order number
• How the issue was recorded
• The assigned priority
• When someone is expected or when the next update will arrive

A reply that says only "received" confirms delivery, but it does not tell the person what will happen next. When people know the request was understood and when they will hear back, they have less reason to call for an update.

Have a plan for calls and emergencies

People will still call. They may be dealing with an emergency, have a poor connection, or simply be used to speaking with the same facilities manager.

Take the call. If the situation is dangerous, deal with safety first and create the record once the immediate risk is under control. For a routine request, the person taking the call can complete the same form while speaking with the location.

The request still reaches the same record. It simply enters through a different person.

If one location or shift regularly avoids the form, look at what the form is asking them to do. A field may be unclear, the asset list may be outdated, or the form may require information they cannot access. Fixing that friction will do more than reminding people to "follow the process."

Review the requests that caused extra work

Once a month, review a small sample of completed work orders. Check whether the location, asset, symptoms, impact, and supporting photos were available before dispatch.

Pay attention to requests that led to:

• A follow-up call because an important fact was missing
• Two work orders for the same problem
• A change in trade after dispatch
• A change in priority after dispatch
• A delayed first visit because the asset or location was unclear

Each example tells you where the form, asset data, or instructions need attention. Improve the process instead of expecting location teams to compensate for a form that is hard to use.

A maintenance request should make the next decision easier

A strong maintenance request captures what the location team can see, what the problem is affecting, and whether there is an immediate risk. From there, facilities can set the priority, choose the right trade, and keep the work moving on one record.

The Pebble Platform keeps the request, the photos and every update on one work order. Our process carries that record through each handoff instead of restating it.