Facilities defects, logged where they are and closed on evidence.

A fault, a room, a photo, a contractor, a closed record.

A tenant on level six emails to say the air conditioning in the east meeting room has been blowing warm since Tuesday and there is a stain spreading across the ceiling tile. That email is the whole job in one line: something is wrong, in a specific place, and the person telling you cannot fix it. So it becomes a defect with a photo of the tile, a timestamp, and a location that resolves to a point. Assign it to the mechanical contractor in two taps; they attend, close it out with a photo, and the status change is logged with who did the work and when.

Where a job needs a scope, line items and a cost code, it becomes a work order instead, with a backcharge flag that keeps warranty work separate from what the tenant pays for. We wrote the longer version of this argument in the part facilities managers inherit.

• Logged against a room, not a floor
  East meeting room, level six, ceiling tile nearest the window. The location tree resolves to a point, so the third aircon fault in that room shows up as a pattern, not three emails.
• A photo with its capture time
  The stain on the tile, taken on the day, keeping the original device timestamp and who took it. Eighteen months later nobody argues about when it appeared.
• Occupants report it themselves
  A tenant contact raises it from their portal with a photo. Someone scanning the QR label on the door lands in that room’s list, or gets a short form that a manager approves.
• Issued to the contractor, no account
  The mechanical contractor gets an email with a link that opens the job. They attend, upload a photo of the finished work, and cannot mark it complete without one.
• Closed by you, not by them
  The contractor marks it complete; a manager or building manager closes it. Each transition stamped with a name, a role and a time.
• Chased when it goes overdue
  A workflow rule escalates anything past its due date and sends the outstanding list on a schedule. Nothing stalls in an inbox.

The walk-through that raises its own faults.

Build the plant-room walk, the fire-door check or the car-park inspection once as a reusable checklist and run it per floor or per building. Answer yes or no as you go. Every No raises a tracked fault linked back to the question, and the question flips back to Yes on its own when that fault closes, so the walk and the fault register never drift apart. Mark the checks that must not be waved through as hold points, and the walk waits on them.

What IssuesId does not do is put next month’s walk in a calendar for you. It tracks what the walk found and who owes you the fix; the schedule stays yours. For the honest version of that line, read how do you track overdue inspection items across a large site?

• Condition walks from a checklist
  Build the walk once — plant room, fire doors, car park, roof — and run it per floor or per building. Yes or no, with a photo where it is a no.
• A No becomes a fault on its own
  Every failed check raises a tracked defect linked back to the question, and the question flips back to Yes when that defect closes. No re-keying.
• Hold points for the checks that matter
  Mark the fire-door check a hold point and the walk waits on it. Nothing gets waved through because it was 4:45 on a Friday.
• One list across every building
  The checklists page lists every walk running across the organisation, filtered by building, location, status and last activity, with a marker on any hold point still open.
• Reports that send themselves
  Save the outstanding-faults report once and schedule it daily, weekly or monthly to whoever needs it, with nobody logged in.
• Works in the basement
  Plant rooms and car parks have no signal. The record saves on the phone and syncs when you are back upstairs.