Prepare for CAM content by practicing decisions, not just definitions: split occupancy losses into named sub-causes, trace budget variances to a specific line, size concessions before offering them, enforce the lease through the documented sequence, and order work orders by severity. Then score yourself against the casework rubric.
Telling Physical, Economic, and Effective Occupancy Apart
Physical occupancy counts occupied units, economic occupancy compares collected rent with gross potential rent, and effective occupancy nets concessions and uncollected rent. Scenario questions require matching the metric to the decision it informs, not reciting definitions.
Physical occupancy divides occupied units by total units and answers a marketing question: is anything vacant? Economic occupancy divides actual collected rent by gross potential rent and answers a revenue question: how much of the scheduled income actually arrived? Effective occupancy adjusts for concessions and uncollected amounts, sitting between the two. The inputs differ—unit counts for the first, dollars for the second and third—so the same property can look healthy on one measure and strained on another. Keep the calculation inputs separate in your notes so a scenario's wording tells you which figure is requested.
Worked scenario: a 200-unit property averages $1,000 in scheduled monthly rent, so gross potential rent is $2,400,000 a year. Ninety-five percent of units are filled, yet only $2,040,000 was collected—an 85 percent economic occupancy. A plausible mistake is attributing the entire gap to vacancy and buying more advertising. Split the loss instead: ten vacant units explain $120,000, leaving $240,000 lost to concessions, delinquency, or write-offs. The better decision is auditing collections and concession spending before touching the marketing budget, because advertising cannot recover rent that was scheduled but never collected. Splitting the variance names the actual problem.
| Metric | What it measures | Key inputs | Common misuse |
|---|---|---|---|
| Physical occupancy | Share of units occupied | Occupied units divided by total units | Reading it as a revenue figure |
| Economic occupancy | Collected rent against gross potential rent | Collected dollars divided by scheduled dollars | Blaming marketing when collections cause the gap |
| Effective occupancy | Occupancy after concessions and uncollected rent | Revenue adjusted for concessions and write-offs | Mixing it with physical occupancy in one comparison |
Tracing a Budget Variance to the Line That Caused It
A budget variance is the difference between budgeted and actual results on a specific line. Applying it well means resisting one-number explanations: decompose revenue into vacancy, concessions, and collections, and separate controllable expenses from ones the site team does not set.
Gross potential rent is a ceiling, not a result. Subtract vacancy loss, concession cost, and uncollected rent to reach rental income; subtract operating expenses—payroll, repairs, utilities, marketing, insurance among them—to approach net operating income. NOI differs from cash flow because it excludes debt service and capital expenditures, a distinction scenario questions can exploit: a property can post strong NOI while a strained cash position comes from loan payments or capital work on the schedule. When reading any property narrative, ask which line moved before deciding which action fits, and compare like periods rather than mixing monthly and annual figures.
Practice the trace with a one-line symptom. Suppose utilities run noticeably above budget mid-year. A first instinct is to conclude the budget was set badly; a better sequence is to check rate changes, occupancy changes, and equipment condition, because each points to a different response—a rebudget, a leasing push, or a repair request. The same discipline applies on the revenue side: name the sub-cause before choosing marketing, concessions, or collections work. In casework, write the line name and the sub-cause in one sentence, then attach the action; that sentence is the reasoning a scenario answer needs to demonstrate.
Pricing Moves: Concessions, Renewals, and Consistency
A concession is a temporary price adjustment—free rent, a reduced rate, or a waived fee—used to fill units or retain residents. Scenario decisions should state the goal, size the cost, and apply the offer consistently rather than one-off.
Distinguish the forms because they cost differently: a month of free rent on a twelve-month lease equals roughly one month of revenue across the term, a permanent rent reduction compounds at every renewal, and a waived fee may be small in dollars but sets a service precedent. Compare any offer against its purpose—a filling concession responds to vacancy, a retention concession responds to renewal risk, and confusing the two can give away revenue without addressing the real cause. Sizing the cost before offering, then recording the terms in the resident file, keeps pricing defensible when the same situation recurs.
Worked scenario: a leasing team offers a half-month concession to one walk-in prospect to close today, while the published special offers none. The plausible mistake is treating the concession as a private judgment call; the better decision is deciding at the property level what concession, if any, applies to the community and applying it uniformly. If the deal is genuinely unique, document the business reason—unit condition, move-in date, lease term—so the file shows a consistent standard rather than favoritism. Why it matters: pricing consistency is both a revenue discipline and a fairness safeguard that documentation makes visible.
Enforcing the Lease Identically Across Residents
Lease enforcement in scenario questions turns on process: cite the specific lease provision, follow the notice sequence the lease and applicable law set, apply it to every resident the same way, and document each step with dates and objective language.
Build the sequence from documents, not from memory of similar situations: the lease defines the violation and any cure period, the notice must state what is required and by when, and the file should show delivery and content. Enforcement differs from negotiation—negotiation changes future terms by agreement, enforcement applies current terms as written. Keep the two separate because a scenario that offers 'talk it out informally' and 'issue the notice the lease requires' is testing which path the situation calls for, and the documented path is the one that protects both the resident and the operator.
Worked scenario: two residents are named in noise complaints in the same week. The site manager issues a formal notice to one and makes a friendly phone call to the other because they know that resident personally. The plausible mistake is relationship-based enforcement; the better decision is running the identical sequence—verify the complaint, apply the lease provision, issue the same notice type—for both, documenting each step. Why it matters: selective enforcement is a fairness failure regardless of intent, and consistent process is the defense. In casework, an answer that varies process by personality should lose to one that varies it by documented facts.
Prioritizing Work Orders by Severity, Not Arrival
Maintenance triage ranks work by risk to habitability, safety, and property—not by when the request arrived. Life-safety and habitability items precede cosmetic ones, and every priority decision should be recorded with its reasoning so the queue tells a defensible story.
Sort requests into categories before assigning times: emergencies threatening safety or habitability, urgent items that will worsen quickly, routine repairs, and scheduled work such as make-readies. A backed-up drain flooding a unit, a reported inoperable smoke detector, and a dripping faucet may arrive in the same hour, but they do not belong in the same place in the queue. Make-ready work has its own clock because a vacant unit earns nothing, yet it still does not displace an active habitability issue in an occupied home. Writing the category on each ticket is what turns triage from opinion into a reviewable process.
Worked scenario: a Monday queue holds a sewage backup in an occupied unit, a reported inoperable smoke detector, a leaking faucet, and a lightbulb request, logged in that order. The plausible mistake is first-in-first-out dispatch that sends the technician down the list while the detector waits. The better decision is severity triage: backup and detector both receive immediate response for safety and habitability, then the faucet, then the bulb, with timestamps and reasoning on each ticket. Why it matters: response order is an operational record, and a documented severity system shows why any given item waited and what was verified afterward.
| Category | Examples | Priority logic | Record on the ticket |
|---|---|---|---|
| Emergency | Sewage backup, active leak flooding a unit, loss of essential service | Respond immediately | Time reported, time dispatched, category |
| Life-safety | Inoperable smoke detector, broken exterior lighting | Treat at emergency level | Verification of the repair and any test |
| Routine | Dripping faucet, appliance adjustment | Schedule within the normal workflow | Category and scheduled date |
| Make-ready | Turns preparing vacant units | Balance against habitability items | Target ready date versus actual |
Documentation That Survives Case-Analysis Review
Strong documentation is contemporaneous, objective, and complete: what happened, when, who was involved, what action followed, and what notice or verification exists. In scenario analysis, the documented file—not the memory of a conversation—is treated as the operative record.
Contrast objective entries with conclusion entries. 'Resident stated the upstairs unit was loud at 11 p.m.; complaint logged, notice issued per lease' records facts and process. 'Problem tenant again' records a judgment and supports nothing. Objective writing also separates observation from inference in inspection notes: a dated description of a condition is evidence, while a phrase like 'negligent resident' is an opinion that weakens an otherwise good file. When a scenario asks which action best protects the operator, the option that creates a dated, factual, retrievable record generally outperforms one that relies on informal communication alone.
Practice by auditing your own written answers. After each casework item, check whether a reader who was not present could reconstruct the event: the date, the people, the observation, the action, and the follow-up. Apply the habit to maintenance tickets, incident notes, and enforcement letters alike, because the standard is one standard. Fair housing and professional-conduct questions fit the same frame—consistent criteria, applied uniformly, recorded at the time—so treat documentation as the connective tissue across the domain rather than a separate topic to review at the end. A file that reads cleanly is the visible form of consistent practice.
A Casework Routine, Rubric, and Readiness Checks
Rotate through three passes: concept drills on the metrics and sequences above, timed casework on invented property narratives, then mixed review where you explain each answer aloud. Score yourself against the rubric below and repeat the cycle, adjusting emphasis to your weakest area.
An adaptable sequence: spend the first stretch mapping the domain areas—financial operations, leasing and marketing, maintenance, resident relations, and professional standards—and writing the one-sentence purpose of each metric and procedure. Next, build five to ten invented property worksheets and drill the traces: occupancy splits, variance naming, triage ordering, and enforcement steps, with a timer to build fluency. Then move to casework, writing a reasoned answer for each scenario before checking it against the rubric. Finish each cycle with mixed review across all areas so no single topic develops a long gap between passes.
Readiness checks: you can compute all three occupancy measures from a short narrative without hesitation; you can name the sub-cause of a revenue or expense variance before proposing an action; you can order a mixed work-order queue by severity and justify each position; you can state the enforcement step a situation requires and why the documented path applies. These are learning milestones, not predictions of any outcome. Administrative details of the CAM credential—format, fees, and enrollment—belong to the National Apartment Association; confirm current requirements directly at naahq.org rather than relying on third-party summaries.
- Exercise: write a 15-line property narrative with scheduled rent, actual collections, concession totals, and a Monday work-order list; solve it, set it aside, then re-solve it two days later.
- Expected observations: first-pass answers tend to skip naming sub-causes and dispatch by log order; the second pass should show sub-cause naming before actions and severity-based dispatch with reasons.
- Rubric level 1 — Recall: defines the metrics and categories correctly with notes open.
- Rubric level 2 — Application: computes figures and orders the queue correctly, but with effort or second attempts.
- Rubric level 3 — Fluency: produces figures, named sub-causes, and governing reasons quickly and consistently without notes; reach this level on the financial and triage drills before heavy mixed review.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.