A complete maintenance ticket in nine entries, with photo and urgency.
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.
Free. No form. The workbook has the same columns as the table below, with the score formula and a fatal-item check in place.
| # | Item | Audit question | Answer | Photo | What good looks like |
|---|---|---|---|---|---|
| 1 | Asset or area | Which asset or area needs repair, such as the AC, facade sign, shutter, trial room light, coffee machine or a live demo unit? | Text | No | Names the asset and its location in the store, with the asset tag if it has one. |
| 2 | Issue description | What exactly is wrong, and since when? | Text | No | Describes the fault in plain words, when it started and anything already tried. |
| 3 | Issue photo | Can you take a live photo that shows the fault clearly? | Photo | Required | Fault clearly visible, taken close enough to see detail, with a second wider photo if helpful. |
| # | Item | Audit question | Answer | Photo | What good looks like |
|---|---|---|---|---|---|
| 4 | Urgency level | How urgent is this: today, within three days, or at the next planned visit? | Text | No | One of the three urgency levels chosen, with a line explaining why. |
| 5 | Customer impact | Does this fault affect customers directly, such as a dark trial room, a broken lounge AC or a closed washroom? | Text | No | Says yes or no and which customer area or service is affected. |
| 6 | Safety risk | Is there any safety risk, such as exposed wiring, water near power, a stuck shutter or a blocked fire exit? | Text | Optional | Says yes or no, names the risk and what has been done to keep people away. |
| # | Item | Audit question | Answer | Photo | What good looks like |
|---|---|---|---|---|---|
| 7 | Preferred repair window | When can a technician work in the store with the least disruption to customers? | Text | No | Gives a day and a time window, usually before opening or after closing. |
| 8 | Store contact | Who will let the technician in and sign off the repair? | Text | No | Names the person and their role, with the store phone number rather than a personal one. |
| 9 | Earlier ticket reference | Has this fault been reported before, and if so what was the earlier ticket number? | Text | No | Gives the earlier ticket number or says this is the first report of the fault. |
Loaded into BorentisOps, each required photo is live, GPS and time-stamped, so a photo from yesterday or another store does not pass. Where the brand has a docket or display standard, Drishti scores the photo against it and marks the misses. Every fail raises a ticket with an owner and a deadline, and the maintenance executive sees the store on a heat map before the next visit.
The checklist runs offline and syncs when signal returns, in Hindi, English and Hinglish, and the operations score sits next to the store's selling score from Borentis Floor on one store card. Pricing is per store, so every store manager and staff member in the store is on the app.
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.