Every housing authority has a continuity problem. Most just don't know it yet.
It usually surfaces when someone leaves. An executive director retires after twelve years and takes with her every vendor relationship, every workaround, every unwritten rule about how the agency actually operates. A maintenance supervisor goes out on medical leave and suddenly nobody knows which contractor to call for the HVAC units in Building 7, or where the equipment warranties are filed, or why the work order system has a field that nobody fills out but that apparently matters at audit time.
The institutional knowledge gap isn't a people problem. It's a documentation problem. And the fix is simpler than most agency leaders realize: a position playbook.
What a Position Playbook Actually Is
A position playbook is a structured operational document that captures everything a person in a specific role needs to know to function effectively from day one — not the job description, not the org chart, but the actual working knowledge that makes someone effective in that seat.
It's not an HR document. It's not a policy manual. It's the answer to the question every new hire or interim leader asks in their first two weeks: What do I actually need to know to do this job right?
A well-built playbook for a housing authority role typically covers:
- Role scope and decision authority — what this person owns, what they approve, and where the handoffs are
- Key relationships — internal staff they depend on, external vendors and contractors, HUD contacts, partner agencies
- Critical systems and access — what software they use, where files live, what accounts they manage
- Recurring responsibilities — daily, weekly, monthly, and annual tasks with deadlines and dependencies
- Active projects and their status — what's in flight, what's pending, what's been promised to whom
- Institutional knowledge — the unwritten rules, the workarounds, the history behind decisions that still shape current operations
- Where to find things — physical files, digital records, emergency contacts, vendor contracts
The goal isn't to document everything. It's to document enough that a capable person stepping into the role can get operational within days, not months.
Which Positions Need One
Not every role carries the same continuity risk. The positions where a departure creates the most operational exposure are the ones to prioritize.
Executive Director. The most obvious one — and the most commonly neglected. The ED carries the HUD relationship, the board relationship, the institutional memory of every significant decision the agency has made. When this seat goes vacant without a playbook, the interim leader spends months reconstructing context that should have been documented.
Chief Operating Officer. The COO is where operational continuity lives day to day. This is the person who knows how the maintenance department actually functions, why the procurement calendar is sequenced the way it is, and what the ED doesn't have time to track. In agencies where the COO role exists, it's often the most knowledge-dense position in the building — and the one least likely to have a succession plan.
Finance Manager. Federal fund management, drawdown procedures, audit relationships, vendor payment processes, financial system access. A finance vacancy during an audit cycle is one of the most dangerous situations a housing authority can be in. A playbook doesn't replace expertise, but it ensures the next person isn't starting from zero.
Maintenance Supervisor or Director. This is the role where institutional knowledge is most at risk and least likely to be documented. Long-tenured maintenance supervisors know every quirk of every building, every shortcut in the work order system, every contractor worth calling and every one to avoid. That knowledge walks out the door with them unless someone captures it.
Property Manager. Resident relationships, lease compliance patterns, recurring issues by property, local resources — the property manager role is highly relationship-dependent. A playbook won't replicate those relationships, but it gives the next person a map.
Modernization or Capital Projects Coordinator. Active procurement files, contractor relationships, project status, HUD approval history — capital work is document-intensive and deadline-driven. A playbook here is as much about protecting active procurements as it is about continuity.
How to Build One
The most common objection is time. Nobody in a housing authority has bandwidth for a documentation project. That's real — but a position playbook doesn't have to be built all at once, and it doesn't have to be perfect to be useful.
Start with the highest-risk positions first. Which role, if it went vacant tomorrow, would create the most immediate operational disruption? Start there.
Interview the person currently in the role. Block two or three hours with them. Ask them to walk you through their week, their recurring responsibilities, their critical relationships, and the things they know that nobody else does. Record it. That conversation is the raw material for the playbook.
Build the document collaboratively. Give the draft back to the incumbent and ask them to fill in the gaps. Most people, when they see their role documented, immediately think of three things that are missing. That iteration is where the real institutional knowledge surfaces.
Update it annually. A playbook that's two years out of date is still useful — but build in a process to refresh it. The simplest trigger: every annual performance review includes a playbook update as a standard agenda item.
Don't wait for a transition to start. The worst time to build a position playbook is when someone has already announced their departure. You're rushing, they're disengaging, and the most valuable knowledge — the nuanced stuff — doesn't make it in. Build the playbook while the incumbent is fully engaged and has time to do it right.
"The worst time to build a position playbook is when someone has already announced their departure. Build it while the incumbent is fully engaged."
The Bigger Picture
HUD's oversight framework rewards agencies that demonstrate institutional stability. Consistent documentation, clear decision-making chains, and evidence of operational continuity are the hallmarks of an agency that isn't dependent on any single person. When a monitoring review team walks in the door, the question they're trying to answer is: does this agency have systems, or does it have people?
Both matter. But only one survives a transition.
A position playbook won't prevent leadership turnover — nothing will. But it changes the equation from a crisis to a managed transition. And in public housing, where federal oversight is continuous and the margin for operational disruption is narrow, that difference is significant.
If your agency doesn't have position playbooks for your highest-risk roles, the right time to start building them was a year ago. The second best time is now.