Variance Comments
Variance Comments
The numbers say what happened. The comments say why — and what to do about it. This is the standard you push to property management every month.
Every month you read variance reports. If the variance column is the only thing telling you a story, you're already operating 30 days behind. Strong comments turn the report from a backward-looking ledger into a forward-looking decision tool — they tell you whether the variance is a one-time event or a trend, whether PM has it handled or needs help, and what to expect next month.
The problem is that most property managers were never trained to write variance comments. "Water was higher this month" gets submitted as if it explains something. It doesn't. This module is the format you require — and the rubric you grade against.
Set the standard
A vague comment is a refused comment. You define what an acceptable comment looks like — the format, the specificity, the threshold — and you don't accept reports that fall short. Coach the first month. Reject by the third.
Push it down
The PM team needs the same framework you do. Share the standard, train against it, and require the pre-submission checklist before you'll review. Comments improve when PM knows exactly what "good" looks like before they hit send.
The cost of weak comments
Vague comments don't just annoy — they translate directly into bad decisions:
- ①You can't tell one-time from recurring. "R&M was over budget" might be a single HVAC failure or the start of a deferred-maintenance avalanche. Without specifics, you can't reforecast and you can't act.
- ②Trends hide for months. Three months of "utilities were higher" before someone notices a meter problem. Specific comments would have surfaced it in week one.
- ③Investor confidence erodes. Owners and LPs read variance comments. When the comments are weak, the comments themselves become the story — and the question shifts from "what's happening at the asset" to "do we trust the operator."
- ④Budgets stop being defensible. Without a record of why lines moved this year, building next year's budget is guesswork. Strong comments are the institutional memory of the asset.
What "good" looks like
A strong variance comment passes a simple test: could ownership read it six months from now and still understand exactly what happened and why? Three parts, specific details, and either a confirmed resolution or a concrete plan. That's the bar. The rest of this manual is how to set it, push it down, and grade against it.
A variance comment is not a description of the variance. It's the asset manager's ability to make a decision without making a phone call.
The 3-Part Framework
What. Why. Plan. Every significant variance gets all three. No exceptions.
Think of every variance comment as a three-sentence mini-report. The numbers above it have already shown what happened. The comment's job is to make the variance decision-ready — to give ownership enough information to either move on or take action without a follow-up email.
The three parts
The What
State the variance briefly in one sentence. Acknowledgment, not explanation — the numbers already showed what happened. One line is enough.
The Why
Explain the root cause. This is the most important part — and the one PMs are weakest on. Be specific: unit numbers, vendor names, dates, dollar amounts. Vague language like "higher than expected" is not acceptable. The test: if ownership reads this six months from now, can they understand exactly what happened?
The Plan
Tell ownership what happens next. Is this one-time? If so, confirm it and say when the line normalizes. Is it a trend? If so, what's the corrective action? Every comment ends with either "resolved" or "plan to bring back to budget."
Stitched together
The same example as one continuous comment — the actual format PM submits. Notice the structure is visible even without explicit labels: a sentence of acknowledgment, a paragraph of root cause with specifics, a forward-looking close.
Two formats PM can use
Both work. Pick one and require it across the report so reviewers know what to expect:
Explicit "WHAT / WHY / PLAN" tags at the start of each part. Easier to enforce and easier to grade.
WHAT: [one-sentence statement].
WHY: [root cause with specifics].
PLAN: [next steps or resolution].
Three sentences or short paragraphs in order. Reads more natural but easier to skip a part — grade carefully.
[Statement.] [Root cause with specifics.] [Resolution or plan.]
When PM submits a comment that's missing the Plan, don't write the plan for them. Send it back and ask "What's the plan?" The skill you're trying to build isn't variance writing — it's variance ownership. They need to be the one figuring out what happens next.
When a Comment Is Required
Not every line needs a comment. These thresholds settle the question so PM stops asking — and stops omitting.
The two-trigger rule
A comment is required if either threshold trips. Both directions count — favorable variances need the same explanation as unfavorable ones. A line that came in $5,000 under budget isn't a win until you know why; it might be deferred work that's about to land next month.
Variance of more than $1,000 in either direction. This is the floor for materiality at most assets. Larger portfolios can scale up — but never let the dollar threshold be the only filter.
Variance of more than 5% of the budgeted line amount. This catches the small-dollar lines that are still meaningful as a ratio — payroll allocations, small utility lines, recurring vendor fees.
Over-communicating is always better than leaving ownership to guess. If PM is debating whether a variance is worth a comment, the answer is yes. Train the team that an unnecessary comment costs you 30 seconds; a missing one costs you a phone call.
Quick reference
| Scenario | Required? | Why |
|---|---|---|
| $1,500 over budget on a $20,000 line | Yes | Trips the dollar threshold. |
| $400 over budget on a $2,000 line | Yes | 20% variance — trips the percentage threshold. |
| $2,000 favorable on payroll | Yes | Favorable variances are not free passes — could be unfilled positions or deferred turns. |
| $200 over budget on a $40,000 line | No | Below both thresholds — noise. |
| Line on budget but trending up over 3 months | Yes | Threshold not tripped, but trend deserves acknowledgment. When in doubt — comment. |
Setting the threshold for your portfolio
$1,000 / 5% works for most stabilized assets. Adjust by portfolio profile:
- ›Smaller assets (<100 units): consider $500 / 5%. Materiality scales down.
- ›Larger assets / institutional: $2,500 / 5% is common. The percentage trigger does more work as the dollar threshold grows.
- ›Distressed / turnaround: $500 / 3%. You want the most granular visibility while you're fixing things.
- ›Lease-up: stay tight ($500 / 5%) on operating lines; loosen on revenue lines until stabilization.
Pick a threshold and put it in writing. The single most common variance complaint from PM is "I didn't know I had to comment on that." A documented standard ends the debate — and gives you something to point to when reports come back thin.
Line Items & Their Drivers
The accounts that swing most, what causes them to move, and exactly what you should expect to see in the comment.
These six lines account for the majority of variance comments at most assets. Each one has its own pattern — its own usual suspects, its own specifics that make a comment useful. Use this page to coach PM on what "good" looks like by line, and to know what to ask for when comments come up short.
| Line Item | Common Causes | Must Be in the Comment |
|---|---|---|
| Vacancy / Loss to Lease | Unexpected move-outs, slow renewals, competitor concessions, seasonal demand | How many units vacant, which specific units, why they vacated, how many leased pending move-in, expected occupancy recovery date |
| Utilities | Billing cycle length (30 vs. 38 days), leaks, running toilets, irrigation, occupancy change | Billing period dates, specific repair made and when, whether issue is resolved, expected normalization of the line |
| Repairs & Maintenance | Emergency repairs (HVAC, water heater, roof), seasonal issues, deferred items, appliance failure | Specific repair, cost, whether one-time or recurring, any warranty / vendor dispute, preventive action taken |
| Turnover / Make-Ready | Higher-than-budgeted move-outs, heavy-damage units, vendor delays, slow completion | Number of turns vs. budget, which units had heavy damage and why, security deposit claims filed, average turn days |
| Payroll | Overtime (tied to turns or emergencies), unfilled positions, temp staffing, bonuses paid | What drove overtime (hours and cause), open positions and fill date, whether OT is expected to recur |
| Marketing / Advertising | Added ILS platforms to combat vacancy, special campaigns, rate increases by vendors | Which platforms added and why, expected duration of elevated spend, current lead and tour pipeline |
Questions to ask property management
If a comment on any of these lines comes in thin, these are the follow-ups that pull specifics out of PM and train them to include the answers up front next month:
- Vacancy: Which units are vacant? When did each become vacant? How many of those vacancies are leased pending move-in?
- Utilities: What were the billing dates for this period? Were any leaks or irrigation issues identified and repaired? When does the line normalize?
- R&M: Which specific repairs drove the variance? Was any of it covered by warranty? Is there a recurring failure pattern we should be tracking?
- Turnover: How many turns did we complete vs. budget? Any heavy-damage units? Security deposits filed? Average turn days?
- Payroll: What's the breakdown of overtime by event? Are any positions open? Is OT expected next month?
- Marketing: Which ILSs are we currently spending on? Why was each added? What's the current pipeline doing in response?
Red flags in line-level comments
- "Higher than expected" or "lower than expected" — no root cause given.
- Utilities comment with no billing period — almost certainly the real explanation.
- R&M comment that doesn't name the specific repair or unit — PM may not actually know.
- Payroll over budget with no overtime breakdown — masks scheduling problems.
- Marketing over budget with no campaign name or pipeline data — likely no strategy behind the spend.
- Favorable variance with no explanation — could be deferred work landing next month.
- Same line over budget three months running with the same comment template — PM is copy-pasting; there's a trend hiding.
Cross-reference related lines. A high turn count should appear in the Turnover comment and the Payroll comment and potentially the R&M comment. When comments don't reconcile across lines, the report is telling you that PM hasn't actually thought it through.
Good vs. Poor Comments
Four real comparisons. Each pair shows the comment ownership got — and the comment ownership needed.
A strong comment is specific — unit numbers, dates, dollar amounts, vendor names, and a clear next step. A weak one is general — restating the obvious without adding insight. Calibrate against these and share them with PM during onboarding and quarterly reviews.
"Water was higher this month."
"We had more vacancy than budgeted."
"We had some unplanned repairs."
"Overtime was high this month."
Don't grade in your head — grade in writing. When you reject a comment, copy the strong version of the same line item back to PM as the bar. Showing the gap is faster than describing it, and it eliminates the "what do you want from me" pushback.
Pre-Submission Checklist
For property management to confirm before the variance report goes out. Push this down and require it — sign-off included.
A checklist works only if it's used. The bar is simple: PM does not send the variance report until every item below is checked. Asset managers should reject reports that arrive without confirmation that the checklist was run. Print this, share it digitally, embed it in the report template — whatever it takes to make running it the default.
Submission sign-off
Required before the variance report is released.
If a variance report arrives without the checklist signed, send it back unread. It sounds harsh — and it works. Within two cycles, the checklist becomes part of PM's monthly close routine and the quality of comments improves measurably. Inspect what you expect.
Variance Report Reviewer
A live, fillable grading sheet for the asset manager. Paste a comment to score it, then walk through the report line by line.
Comment Strength Checker
Paste a single variance comment to score it against the six checks that separate ownership-ready comments from coachable ones.
Report Metadata
Capture the basics so this grading sheet is auditable.
Top-of-Report Checks
Three quick checks before reading the line-by-line comments.
Line-by-Line Grading
For each commented line, mark a grade and any follow-up needed. Pass = ownership-ready. Coach = accepted, but PM gets specific feedback. Reject = send back for rewrite.
Debrief & Coaching Notes
Patterns across the report — for use in next month's training conversation with PM.