Maintenance & Incident Report: Keep Our Office Running

Incident Profile

Reported By

First Name

Last Name

Date

Time

Location of Issue

Category of Maintenance

Security/Access (Broken locks, alarm codes, gate issues)

Safety/Hazard (Tripping hazards, exposed wires, leaks)

Climate/HVAC (Temperature control, air quality, ventilation)

Kitchen/Amenities (Appliances, plumbing, hygiene supplies)

IT/Shared Tech (Printers, monitors, cables, lobby displays)

Priority Rating

P1: Critical – Immediate threat to security, safety, or office opening (e.g., cannot lock front door).

P2: High – Impacting productivity or comfort (e.g., coffee machine broken, room too hot).

P3: Standard – Routine repair or replenishment needed (e.g., flickering light, low stationery).

Detailed Observation

Description of the Issue: (Please provide specific details. If an appliance is broken, note the brand/model if visible.)

Action Taken

Action

Select

Details

A
B
C
1
The area cordoned off/marked
 
2
Issue resolved immediately
 
3
Temporary fix applied
 
4
Professional maintenance required
 
5
Management notified
 

Administrative Tracking (For Office Manager Use)

Status

Select

Assigned Contractor/Staff

Quote/Cost

Completion Date

A
B
C
D
E
1
Pending
 
 
 
2
In Progress
 
 
 
3
Resolved
 
 
 

Form Template Insights

Please remove this form template insights section before publishing.

Detailed Insights on the Maintenance & Incident Report Template

1. Categorization as a Diagnostic Tool

By requiring the user to select a category (e.g., HVAC, Security, IT), the form does the heavy lifting of sorting.

  • Trend Analysis: If "Security/Access" is flagged repeatedly, it reveals a systemic issue with hardware rather than a one-off human error.
  • Vendor Management: It allows you to quickly see which service providers (plumbers, electricians, cleaners) are being called most often, helping with budget forecasting.

2. The Priority Matrix (P1–P3)

This is the most critical feature of an advanced report. It removes subjective "panic" and replaces it with objective urgency.

  • P1 (Critical): These are "showstoppers." If the front door won't lock or there is an active leak near a server, the office cannot function. This rating triggers immediate escalation.
  • P3 (Standard): These are "quality of life" issues. By labeling them as P3, you acknowledge the problem without disrupting the workflow of the maintenance team for minor fixes.

3. Accountability through "Initial Action"

The "Did you attempt a fix?" and "Was management notified?" questions serve two common-sense purposes:

  • Safety Continuity: It ensures the person who discovered the hazard didn't just walk away. If a floor is wet, checking "Is the area cordoned off?" ensures that the hazard is managed until a janitor arrives.
  • Reduced Duplication: It prevents multiple people from calling the same repair service, saving time and administrative overhead.

4. Cost and Resource Tracking

The administrative footer (Quote/Cost/Contractor) turns the report into a financial document.

  • Asset Lifecycle: By tracking repairs on specific items, you can see when the cost of maintaining an old printer or coffee machine has exceeded the cost of simply replacing it.
  • Audit Trail: It provides a clear history of "who, what, when, and how much," which is invaluable for end-of-year facility reviews or when discussing lease renewals with a landlord.


Mandatory Questions Recommendation

Please remove this mandatory questions recommendation before publishing.

Mandatory Questions & Core Rationale:

1. Priority Level (P1, P2, P3)

  • The Question: What is the urgency level of this issue?
  • The "Why": This is the single most important question. In a busy office, facility managers cannot address every "flickering light" immediately if there is a "broken front door." Forcing the user to choose a priority level ensures that resources are directed to the most critical threats first. It filters out the "urgent" from the "merely important."

2. Precise Location

  • The Question: Where exactly is the issue located?
  • The "Why": Vague reports like "the sink is leaking" are unhelpful in large offices with multiple kitchens or restrooms. Mandatory location data (e.g., "Level 2, East Wing Restroom, third stall") ensures the maintenance person doesn't waste an hour hunting for the problem, which reduces labor costs and ensures a faster fix.

3. Incident Category

  • The Question: Is this a Security, HVAC, IT, or Plumbing issue?
  • The "Why": Categorization is mandatory for routing. An online form can use this answer to automatically notify the right person (e.g., sending an IT issue to the tech team and a broken lock to the security lead). It prevents the report from sitting in a general inbox while a critical problem remains unaddressed.

4. Detailed Observation/Description

  • The Question: Please describe the problem in detail.
  • The "Why": "Broken printer" is a symptom; "Error code 502 on the paper tray" is an observation. Mandatory details allow the responder to arrive prepared with the correct tools, parts, or keys. It eliminates the "investigation trip," turning a two-step repair into a one-step solution.

5. Immediate Action/Containment Status

  • The Question: What has been done to secure the area?
  • The "Why": If a hazard is identified (like a shattered glass panel or a major spill), it is mandatory to know if it has been cordoned off. This ensures that the person who found the issue has fulfilled their common-sense duty to protect others until the professional repair team arrives.


To configure an element, select it on the form.

To add a new question or element, click the Question & Element button in the vertical toolbar on the left.