A complete maintenance ticket in nine entries, with photo and urgency.
Selected questions from each section. Try them.
Showing 9 of 9 items. The full template comes with weights, fatal items and the score formula.
Q1. Which asset or area needs repair, such as the AC, facade sign, shutter, trial room light, coffee machine or a live demo unit?*
Q2. What exactly is wrong, and since when?*
Q3. Can you take a live photo that shows the fault clearly?*
Q4. How urgent is this: today, within three days, or at the next planned visit?*
Q5. Does this fault affect customers directly, such as a dark trial room, a broken lounge AC or a closed washroom?*
Q6. Is there any safety risk, such as exposed wiring, water near power, a stuck shutter or a blocked fire exit?*
Q7. When can a technician work in the store with the least disruption to customers?*
Q8. Who will let the technician in and sign off the repair?*
Q9. Has this fault been reported before, and if so what was the earlier ticket number?*
GPS and time on every shot. No gallery uploads.
Drishti checks the photo against your standard.
Every miss gets an owner and a deadline.
Operations score next to the selling score.
A raise store maintenance ticket checklist is the short form a Store Manager fills when something in the store breaks, so the maintenance team gets everything it needs in one go: which asset, what is wrong, a live photo, how urgent it is, whether customers or safety are affected, and when a technician can come in. The Maintenance Executive reviews each ticket, assigns an owner and a deadline, and closes it with an after photo. It is not scored and has no fatal items, because it is a request rather than an audit. Tickets raised from failed items in other checklists land in the same queue, so the maintenance team works from one list across stores.
A technician should be able to read it and arrive with the right parts. That means the asset and its location, a plain description of the fault, a clear live photo, the urgency, whether customers or safety are affected, and a window when they can work. A ticket that just says the AC is not working usually needs two follow-up calls before anyone visits.
Both. Call the Maintenance Executive or the facility helpline straight away for anything dangerous, such as exposed wiring, a water leak near power or a blocked fire exit, and keep people away from the area. Then raise the ticket so there is a record with a photo, an owner and a deadline, and so the fix can be checked later.
Because it is a request, not an audit. Every entry is weighted equally and there is no pass mark or fatal item. What matters is that the ticket is complete. The Maintenance Executive reviews it, assigns an owner and a deadline, and closes it with an after photo once the repair is done, which is what the store is judged on.
Yes. The Excel download keeps the same columns BorentisOps uses: section, item, question, answer type, photo rule, weight, fatal flag and the note on what good looks like. It imports as a checklist, and a Borentis onboarding person maps the filled-by and reviewed-by roles to your people and assigns it to your stores. Tickets raised from failed items in your other checklists use the same fields, so everything lands in one queue.
Borentis is a retail conversation intelligence platform: Borentis Floor captures and scores the in-store sales conversation with the customer's consent. BorentisOps, which runs this template, is the store operations half, so that the operations score can be read next to the selling score on one card per store. The category is explained at what is retail conversation intelligence and how to measure in-store sales interactions.