Internal maintenance
Send routine and qualified repair work to the onsite team with the property context, scope, access plan, target, and expected verification.
BUILDING MAINTENANCE REQUEST FORM
A building maintenance request form that routes work clearly
Give occupants, staff, front desks, and property teams a clear way to report common-area and building-system conditions with the exact service, safety, security, and access context the responder needs.
For non-emergency building service intake. Publish separate emergency and specialist reporting routes wherever safety, security, fire, gas, structural, or utility conditions require them.
Free for up to five users. No credit card required.
Adapt fields, workflows, and dashboards without code. Explore 1,000+ app templates and use cases
Explore the sample records before you copy the app. Add real tenant, access, vendor, and property information only in your own secured workspace.
Exactbuilding, floor, area, and system context
Visibleservice, safety, and security impact
Ownedresponse and restoration target
A building request form should locate the condition precisely enough for safe triage
Shared spaces and building systems often have no tenant unit number. The form needs a location model that fits how people actually navigate the property.
- 01
Property and navigable location
Capture site, building, floor, wing, room, common area, entrance, plant space, or a recognizable landmark. Use property-specific choices where they reduce ambiguity, and allow staff to correct the location during triage.
- 02
Observable condition and service impact
Ask what the reporter sees, hears, smells, feels, or cannot use; when it began; whether it is intermittent; and how it affects occupants, access, operations, rooms, customers, or shared services.
- 03
Safety signal and immediate action
Collect visible warning signs and whether the area has been isolated, marked, shut down, or reported through the emergency channel. Trained staff decide the formal severity and further control.
- 04
Access, reporter, and evidence
Record who can clarify the issue, preferred contact, access hours, escort or key needs, occupancy constraints, event or business-hour conflicts, and optional photos. Protect restricted building and security information.
Use the request facts to choose the right maintenance path
Issue category helps filtering, but location, safety, impact, access, responsibility, skill, and timing determine the real response.
Approved vendor or specialist
Route trade, warranty, specialist inspection, or contracted service work with only the information the provider needs and an accountable internal owner.
Inspection before repair
When the condition or responsibility is unclear, create an inspection or assessment first rather than dispatching an invented scope.
Planned project or capital review
Move recurring, broad, high-cost, or non-urgent conditions into a planned decision without losing the original request, occupant impact, interim control, or communication obligation.
Turn reporter context into a practical first decision
These are routing questions, not technical diagnosis.
| Question | Example answer | Possible next step |
|---|---|---|
| Where exactly is it? | East stairwell, level 2, above fire door | Route with map/location and access details |
| What is happening? | Exit sign flickers after several minutes | Life-safety triage and specialist check |
| Who or what is affected? | Shared egress route remains open but visibility is unreliable | Interim control and urgent owner |
| Can the team access it? | Common area before opening; no tenant entry required | Schedule vendor window |
| What proves restoration? | Sign remains illuminated through the required test | Documented verification and closeout |
Building intake needs privacy, safety, and operational boundaries
The same form may be used by occupants, staff, reception, and facilities; their access and vocabulary are not identical.
Offer focused reporter paths
Keep the public or occupant form short. Give trained staff the additional fields for technical context, responsibility, priority, cost, and internal routing.
Protect sensitive locations
Restrict security systems, keys, access controls, resident details, back-of-house spaces, plant rooms, vendor pricing, and internal risk notes to the roles that need them.
Keep service updates understandable
Tell the reporter that the issue was received, what happens next, whether access or more information is needed, and when the area returns to normal use. Avoid internal workflow labels.
Link recurrence to property decisions
Repeated requests at one area or system should feed inspection, preventive work, vendor, condition, budget, or capital review rather than being counted as unrelated tickets.
CONFIGURE THE OPERATION AROUND YOUR PROPERTIES
Adapt intake as buildings, tenants, and service ownership change
Facilities administrators can update location choices, questions, routing, and views without replacing the request system.
A building request workflow can be built in hours and a focused location, field, route, or queue change can often be made in tens of minutes.- 01
Add a building, floor, area, access rule, or issue category.
- 02
Show specialist questions only for the selected condition.
- 03
Route a property or risk class to a different team or vendor owner.
- 04
Create a recurrence, backlog, access, or service-impact dashboard.
Use Jodoo for configurable building-service intake and follow-through
Jodoo connects the request to property context, maintenance work, inspection, communication, evidence, and management review.
Keep specialist building systems authoritative
BMS, fire, access control, energy, CMMS, contractor, asset, and property platforms may own telemetry, tests, preventive plans, equipment history, permits, or financial records. Link the relevant identifiers.
Configure by site without creating uncontrolled copies
Use shared core fields and site-specific conditional questions, routing, service windows, and views. Govern emergency wording and required evidence centrally.
Do not present software as technical authority
The form does not diagnose a fault, approve a repair method, certify a building condition, or replace competent safety and trade decisions.
Questions about building maintenance request form
What should a building maintenance request form include?
Include property and precise location, observable condition, when it began, operational or occupant impact, visible safety concern, reporter contact, access constraints, service window, and optional evidence. Staff should add priority, responsibility, trade, scope, cost, and verification.
How is this different from a tenant request form?
A building request may concern common areas, staff spaces, plant rooms, public facilities, shared services, commercial suites, or rooms without a tenant relationship. Its location, access, service impact, and security fields may be broader.
Can the form route different issue types?
Yes. Use category, property, location, visible risk, impact, access, and responsibility to select a triage queue or owner. Do not over-automate technical diagnosis from the reporter’s category alone.
Should staff use the same form as occupants?
They can share a governed core record, but staff may need a richer internal path. Use conditional fields and permissions so occupants are not exposed to technical, financial, security, or other requester data.
How do building requests support preventive maintenance?
Recurring requests reveal patterns by location, system, issue type, interval, vendor, repair, cost, and reopen rate. Use the pattern to decide inspection, preventive tasks, scope changes, training, or capital assessment.
SEE THE WORKING PROPERTY SYSTEM
Inspect the building request and response workflow
Open populated requests from apartments, hotels, housing, and mixed-use property, then follow each issue into response ownership, work, inspection, verification, and portfolio review.
Open the building request form