Trainual for property management: turns, maintenance and leasing SOPs

Which SOPs to write first

Property management has a smaller set of processes than most industries, but they repeat constantly and the cost of getting them wrong is immediate and visible, an extra vacancy day, a frustrated tenant, a maintenance issue that escalates because it wasn't triaged correctly. Three stand out as the highest-value starting point.

• Unit turn checklist: the full sequence from move-out inspection to move-in ready, covering what gets inspected, what triggers a repair versus a full renovation, cleaning standards, and the sign-off that confirms a unit is genuinely ready before it's listed again.
• Maintenance request triage: how an incoming request gets categorized (emergency versus routine), who gets notified for each category, response-time expectations, and when a request needs to be escalated to a vendor versus handled in-house.
• Leasing walkthrough and application process: the actual script and sequence for a property showing, what gets disclosed and when, how applications get processed and in what order, and how approval or denial gets communicated.

Writing these three well, in enough detail that a brand-new leasing agent or maintenance coordinator could follow them without guessing, covers the processes most likely to cause real financial or legal exposure if done inconsistently.

Training new leasing and maintenance staff consistently

Assign these training paths by role, "Leasing Agent" and "Maintenance Coordinator," rather than to named individuals, so every new hire in that role automatically gets the standardized training rather than learning an informal, slightly-different version from whichever experienced staff member happens to onboard them. Add a sign-off or short quiz step specifically on anything with legal or safety exposure, fair housing disclosures during a leasing walkthrough, or safety protocol during a maintenance visit, since confirming someone genuinely understood these, not just opened the document, matters more here than for a low-stakes administrative process.

A note on fair housing training specifically

Fair housing compliance deserves particular care in how it's trained, since the real risk isn't just a leasing agent not knowing the rules, it's a leasing agent not recognizing a fair housing issue in the moment it actually arises during a real conversation with a prospective tenant. Beyond the written policy, consider including realistic example scenarios in the training, a prospective tenant asking an improper question, a subtle steering risk in how a property gets described, so agents practice recognizing the pattern, not just memorizing the rule. A quiz that tests recognition of realistic scenarios, not just recall of the policy text, is a meaningfully stronger test of whether training actually reduces risk.

A note on keeping tenant-facing content separate from internal-only content

As you build out these SOPs, keep a clear separation between content meant purely for internal staff training and anything that might double as tenant-facing communication. An internal maintenance triage SOP might include judgment-call criteria your company doesn't want tenants to see, how you decide what qualifies as an emergency versus what can wait, while a tenant-facing version of similar information should be simpler and framed around what the tenant should expect, not your internal decision logic. Writing both where needed, rather than assuming one document can serve both audiences, avoids accidentally exposing internal criteria that a tenant or legal reviewer might misread as a binding commitment.

A fourth SOP worth considering: vendor and contractor management

Beyond the three core processes above, a fourth is worth adding once those are solid: how vendors and outside contractors get selected, vetted and managed for repairs beyond your in-house maintenance capacity. This matters because an inconsistent vendor process, no clear criteria for which vendor handles which job type, no standard for confirming work was actually completed to standard before payment, tends to quietly cost real money over time through overpayment, rework, or using an unreliable vendor out of habit rather than performance. Writing this down and training whoever handles vendor coordination on consistent criteria closes a gap that's easy to overlook next to the more obviously tenant-facing processes. Crew-focused training is covered in Trainual for field service and contractors.

Example outlines for each core process

Unit turn checklist, as an outline: move-out inspection and documentation, damage assessment and repair-versus-renovation decision, cleaning to standard with a specific checklist, final photos and listing-ready confirmation, and a named owner who signs off before the unit goes back on the market. A checklist like this can start itself when a move-out is logged, as explained in SOP automation.

Maintenance triage, as an outline: intake method and required information from the tenant, emergency-versus-routine categorization criteria with real examples of each, response-time commitment per category, in-house-versus-vendor decision criteria, and follow-up confirmation that the issue was actually resolved to the tenant's satisfaction.

Leasing walkthrough, as an outline: pre-showing preparation, the actual walkthrough script covering what to point out and what to disclose, application collection and required documentation, the decision and communication process, and move-in logistics handoff to the appropriate team member.

A worked example: a portfolio with multiple maintenance coordinators disagreeing on triage

Say a property management company running 200 units across three maintenance coordinators notices that the same type of request, a reported leak, gets handled as an emergency by one coordinator and as routine by another, depending purely on who happens to answer. This is exactly the inconsistency a well-written triage SOP fixes: define specific, checkable criteria for what makes a leak an emergency (active water damage, affects a second unit, no shutoff available) versus routine (a slow drip with an easy temporary fix), rather than leaving the distinction to individual judgment. Once this is written clearly and all three coordinators are trained and signed off on the same criteria, response consistency across the portfolio improves measurably, and it becomes possible to audit whether triage decisions are actually following policy rather than varying by person. Sorting incoming calls the same way is covered in how to sort tenant calls for repairs, rent and leasing.

Handling seasonal and regional variation across properties

If your portfolio spans different climates or regions, it's worth explicitly building seasonal and regional variation into your SOPs rather than writing one version that quietly doesn't apply everywhere. A unit turn checklist for a property in a cold climate needs a winterization step a warm-climate property doesn't; a maintenance triage process might treat a heating failure as an emergency in one region and routine in another depending on the season. Flag these variations explicitly inside the SOP itself, "winterization step applies to northern properties only," rather than maintaining entirely separate documents per region, which tends to drift out of sync with each other over time as updates get made to one copy and not the other.

How I'd approach this

I'd start with whichever of the three processes above currently causes the most tenant complaints or the most inconsistency between properties or staff, write it in real detail using one of your actual recent examples rather than a generic template, and test it with one new hire before expanding further. Property management's processes repeat often enough that the time invested in getting these three right pays back quickly, usually within the first few units or leases that go through the new, standardized process. The rest of the software stack is covered in the tool stack for a property management company.