Write a Maintenance Request That Gets Fixed the First Time

It is 2pm on a Saturday. The ice machine at your store has stopped dropping ice, and the drink line is getting long. You text your manager: "ice machine broken." Three days later a technician shows up, finds a machine that looks fine, and leaves. Nobody told him it only fails when the store is busy. Whether you use maintenance request software or a text thread, the wording of the request decides whether the first visit works.

That visit cost a call-out fee and fixed nothing. The cause was a three-word request.

This post is for store managers and shift leads who write the request. It covers what to include, how to take the photo, and how to set urgency. It works on paper, in a text thread or in a purpose-built tool. The information matters more than the tool.

Why most requests fail

A request is a message to someone who is not standing next to the problem. They have to guess what you mean, and when they guess wrong, you get a second visit.

The usual failures are small:

• "Broken" with no description of what the equipment is doing.
• No location. Which fryer, which restroom, which door?
• No sense of how bad it is, so everything looks the same size.
• No photo, so the reader has to imagine the scene.

What to include in every request

Answer these five questions. It takes about two minutes.

1. What is it? Name the equipment and, if you can, the make and model from the label. "Walk-in cooler" is good. "Walk-in cooler, compressor on the back wall" is better.
2. Where is it? Store, area, and which unit if there are several. "Left fryer" beats "fryer".
3. What is it doing? Describe what you see, hear or smell. "Display reads 8°C, was 3°C at open" is a symptom. "Cooler is acting up" is not.
4. When does it happen? Constant, only at peak, only after cleaning, only in the morning. Intermittent faults are the ones that get missed on a visit.
5. What have you already tried? Reset the breaker, cleaned the filter, moved the product. This saves the technician from repeating it and tells them what you ruled out.

You are not diagnosing the fault. You are describing it.

Take a photo that helps

A photo often settles a question that a paragraph cannot. Take two or three:

• A wide shot so the reader can tell which unit and where it sits.
• A close shot of the problem itself, such as the leak, the frost, the error code or the damaged part.
• The nameplate. The label with make, model and serial number lets a contractor bring the right parts. Make sure the numbers are readable.

For a noise or an intermittent fault, a short phone video can help more.

Set the urgency honestly

If every request is urgent, none of them are. Decide with a simple test.

• Emergency: a safety risk, active flooding, no heat or cooling that threatens food or staff, or anything that forces you to close. Call as well as submit the request.
• High: the store can still run but is losing sales or working around a failure. A fryer down in a store with two.
• Medium: it needs fixing this week and is not hurting service yet, such as a slow drain.
• Low: cosmetic or can wait for the next visit, such as a loose handle or a flickering bulb in the back room.

Whether something is a code or safety matter is for your local authority, insurer or manufacturer to say. When in doubt, mark it higher and say why in one sentence.

A request that works

Here is the ice machine example, rewritten. This is an illustrative request, not a real one.

Ice machine, front counter, store 7. High. Stops dropping ice during the lunch rush, around 12 to 1:30. Fine at open and after 2pm. Panel light is solid, no error code. Filter cleaned today, no change. Photos attached: wide shot, the empty bin, and the nameplate. Drink line is backing up without it.

A technician reading that knows the unit, the symptom, the timing and the model. The first visit has a real chance of being the only visit.

What maintenance request software does after you submit

Writing the request is half the job. Someone then has to decide who fixes it and when.

In Concoct, store staff submit the request from a phone browser, and it can carry photos. Someone on the owner or operations side reviews it and turns it into a work order. Assigning a contractor is done by an owner, operations manager or dispatcher, not by the store manager. Priorities are fixed at Low, Medium, High and Emergency, and the form is not customisable, so what you write in the description carries a lot of weight.

You can limit a store manager's account to their own location, so they only see their own requests. Concoct has no configurable approval rules, and it does not send text messages. Vendors get an emailed link per job, covered in how to manage vendors who refuse to log in.

If you are the owner reading this, the best fix is not a better tool. It is a short template taped inside the office door and a rule that a request without a location and a photo gets sent back. The restaurant and convenience store maintenance checklist is a good place to start on what staff should be checking before they write one.

Close the loop

A request that disappears teaches staff to stop writing them. Tell people:

1. Someone has seen it.
2. When it will be looked at.
3. When it is done. Ask the store to confirm the fix held, especially for intermittent problems.

If the same equipment keeps showing up, it may be cheaper to replace than to repair. Keep the records in one place, as described in franchise maintenance, every location in one place, so the pattern is visible.

Try it with your stores

If your requests live in text threads and you want them in one list with photos and a status, see pricing (billed per location, with unlimited users) or book a demo and we will walk through the request flow with your setup. Either way, the template above works today.

FAQ

How long should a maintenance request be?

Three to six short sentences. Cover the five questions above and add photos instead of more words.

Should I include the serial number?

Yes, if you can read it. Photograph the nameplate. It helps the contractor bring the right parts and lets you track repeat problems on one unit.

What if I am not sure how urgent it is?

Pick the higher level and give one sentence of reasoning. Reviewers can lower it.

Do I need maintenance request software, or will a shared inbox do?

A shared inbox works for one or two stores. Past that, photos get lost and nobody can see status. With several sites and contractors, one list with a status on each request saves time.

Can store staff dispatch a contractor in Concoct?

No. Store staff submit the request. An owner, operations manager or dispatcher decides who it goes to and creates the work order.

Can a vendor attach photos or an invoice to the job?

Not through the Concoct vendor portal. Vendors can accept or decline, give an arrival time, update status and add a short written note on completion. They email invoices, and your team attaches them.