A maintenance issue may first arrive by phone, email, text message or conversation. If the important details stay scattered across those channels, it becomes harder to assess the request, assign the work and explain what happened later.
A structured request form creates one dependable starting point. It supports practical coordination and record-keeping; it does not determine legal responsibilities, emergency procedures or compliance requirements. Property managers should follow their agreements, policies and applicable local rules.
Why a consistent request process matters
Even a straightforward repair can involve several people: the person reporting the issue, the property manager, an owner, a tenant and a vendor. A shared record reduces repeated questions and gives each person the information needed for the next step.
Consistency also makes open work easier to review. When every request captures the same core details, a manager can compare priorities, identify delays and see which items still require approval, scheduling or confirmation.
Start with the property and contact details
Record the property, unit or specific area affected. Include the reporter's name, contact information, relationship to the property and preferred contact method. Add the date and time the request was received and identify the team member responsible for coordinating it.
If the property has an internal reference number, include it. Consistent identifiers help connect the request to inspection notes, vendor records, invoices and the master property file.
Describe the issue in useful detail
Ask the reporter to explain what they observed, where it is happening and when it began. Encourage plain descriptions rather than a diagnosis. “Water is collecting beneath the kitchen sink” is often more useful than an unsupported conclusion about which part has failed.
- Exact room, unit or common area
- What was seen, heard, smelled or otherwise observed
- When the issue began and whether it is ongoing
- How frequently it occurs
- Photos or supporting details, when appropriate
Record impact without making assumptions
Note how the issue affects use of the space, building operations or planned activities. Ask whether any equipment, fixture or area is currently unavailable. These facts help the manager apply the organization's own priority and escalation process.
A general form should not invite the reporter to make technical, safety or legal determinations they are not qualified to make. Provide separate, clearly communicated instructions for emergencies and situations requiring immediate contact.
Capture access and scheduling information
Record the preferred appointment windows, the best contact for arranging access and whether notice or coordination is required. Note relevant practical details such as keys, entry instructions, pets, restricted areas or an on-site contact, while avoiding unnecessary personal information.
Access information can change, so confirm it before the visit rather than relying indefinitely on an older request. Keep sensitive access details only where authorized staff and vendors can use them appropriately.
Track approvals and responsibility
Some work can be assigned immediately, while other requests need an estimate, owner approval or confirmation of responsibility. Give each approval a clear status, owner and date so the request does not stall between inboxes.
Record the selected vendor or internal team member, the work-order reference and the planned service date. If the scope changes, update the record instead of relying on a separate message that may be difficult to locate later.
Document the work and follow-up
After the visit, record what was completed, any parts or return work required, the completion date and supporting invoice or reference number. Then confirm whether the person who reported the issue has been updated.
A request should not be marked complete simply because a vendor attended. Define what completion means in your workflow: the work is finished, documentation is received, the affected party is informed and any follow-up item has a new owner and due date.
A practical maintenance request checklist
Before assigning or closing a maintenance request, confirm that the record includes:
- Property, unit and exact location
- Reporter and preferred contact method
- Date received and assigned coordinator
- Clear description and observed impact
- Access and scheduling information
- Priority under your established process
- Approval, estimate and vendor status
- Work completed and remaining follow-up
- Communication and closure confirmation
Connect requests to a wider operations record
The individual form captures the details of one issue. A maintenance tracker then helps the manager review all open and completed work across properties, while a master operations tracker connects maintenance with inspections, move-ins, incidents and vendor coordination.
Review your form after several real requests. Remove questions that do not help the next action, clarify fields people often misunderstand and keep emergency instructions separate and prominent.
Natural next step: Property Manager Operations Kit
The Property Manager Operations Kit provides ten editable forms and trackers for coordinating property setup, tenant communication, maintenance, inspections, vendors, incidents and ongoing operations. It includes the Maintenance Request and Work Order Form discussed in this guide.