What to Fix First When Your Affordable Housing Audit Reveals Ghost Tenants

Your phone rings at 7:13 a.m. It's the state housing finance agency. They finished their file review and found three tenants on your rent roll who apparently don't exist. No lease signatures. No utility bills. No one answering the door. You've got ghost tenants.

And now the clock is ticking. The compliance officer wants a corrective action plan in 14 days. The asset manager is asking about recertification backlogs. The residents who do live there are wondering why their neighbors' apartments stay dark. This isn't a theory problem—it's the kind of audit finding that gets properties flagged for enhanced monitoring or, worse, referred to HUD's Office of Inspector General.

Where Ghost Tenants Actually Show Up in Real Work

How phantom residents appear in rent rolls vs. inspection logs

The first place ghost tenants scream for attention is the gap between what your rent roll says and what your inspector's flashlight catches. I have seen properties where the rent roll shows a family of four in unit 2B for eighteen months straight. In the inspection log, that same unit has zero maintenance requests, zero pest-control entries, zero complaints about running water. The discrepancy is rarely subtle — it's a full year of nothing. Most teams catch this only when the HUD monitoring letter arrives. The rent roll shows income, the file shows a tenant, but the physical unit tells a different story. That hurts. The common fix? Pull the last three inspection logs alongside the rent roll for any unit flagged as occupied for six consecutive months without a single work order. It sounds obvious, but I have walked into properties where nobody thought to cross-reference those two documents in the same meeting.

Utility records as the first clue: zero usage for three months

Utility data is where ghost tenants get sloppy. Most compliance officers check utility allowance worksheets — they rarely check actual consumption logs. Run a simple query: units billed as occupied where water usage dropped below two gallons per day for three consecutive months. That threshold catches phantom residents, vacant units masquerading as occupied, and the occasional unit where the tenant lives elsewhere but keeps the lease alive for subsidy purposes. The trade-off is worth noting: some real tenants travel for work or go to seasonal care — three-month zero usage in August with a tenant who works oil fields is not necessarily fraud. But it's a flag. The catch is that many property management systems don't expose consumption data in a way that connects to occupancy status. You end up exporting utility bills into a spreadsheet and joining them manually. Not elegant, but it works. Most teams skip this because the utility company sends aggregated billing, not per-unit usage. You have to request the granular data. That request alone often reveals the problem.

Three-month zero usage in a unit billed as occupied is not proof of a ghost tenant. It's proof that you need to open the door.

— Compliance supervisor, rural LIHTC portfolio review

Mail forwarding requests and vacant-unit work orders

The quietest indicator lives in the maintenance log. Look for vacant-unit work orders — paint touch-ups, lock changes, final walk-through reports — filed after a tenant is supposed to be living there. Someone entered a work order for "winterize unit, no occupant" on unit 4C in November. The rent roll shows tenant Jones moved in October 1. That's a ghost. The forwarding address request at the property office tells the same story with less noise. If the post office has a change of address for that tenant dated two weeks before the lease start, or if the tenant left a forwarding address to a different state while the rent roll still lists them as current — you have found your gap. One concrete example: a property I consulted had a file for a tenant who supposedly lived in unit 7A for fourteen months. The maintenance team had replaced the unit's locks three times for "vacant prep." Nobody connected those work orders to the occupancy file. The compliance director said they thought the maintenance log was for common-area repairs. Wrong order. Maintenance logs for individual units are the canary. You just have to read them.

Foundations Readers Confuse: Vacant vs. Ghost vs. Unreported Move-Out

Vacant ≠ Ghost: Where Compliance Teams Get Stuck First

The audit report lands. Line 47 shows 'Unit 203 — presumed vacant.' Your asset manager flags it as a ghost tenant and wants to file an immediate cure notice. Slow down. I have watched compliance officers burn three months chasing a vacancy they mislabeled as fraud — and the real issue? A maintenance worker forgot to key the move-out date into the system. Under HUD occupancy standards, a unit is legally vacant the moment the household surrenders possession, even if the paperwork sits in a supervisor's inbox for two weeks. A ghost tenant is different: someone is collecting a subsidy for an occupant who doesn't exist — or for a person who left months ago but stays on the ledger. Confusing these two costs you credibility when you finally bring the case to the monitoring agency.

Why Recertification Gaps Are Not Automatically Fraud

Most teams skip this: a late recertification and a ghost tenant share the same symptom — stale income data — but the intent is worlds apart. A household that fails to recertify on time might simply be overwhelmed. Lost the paperwork. Child got sick. The lease says they still live there, the unit passes inspection, but the file is technically noncompliant for 45 days. That's a data gap, not a deliberate scheme. The catch is that HUD's Notice PIH 2022-12 treats both as potentially reportable events, so property managers rush to call everything a ghost. Wrong order. You lose enforcement leverage if you cry fraud on a fixable paperwork delay. We fixed this by building a 60-day flag system: anything under two months late gets a reminder letter, not a fraud referral.

“The difference between a ghost and a mistake is almost always paper — a signed form, a date stamp, a witness who saw the tenant move out.”

— Compliance director, LIHTC property, five-year portfolio review

Unreported Move-Out: The In-Between That Bites Auditors

Here is the muddiest ground: an unreported move-out. The tenant left quietly. Didn't tell the office. Didn't return the keys. The unit looks occupied — furniture still there, mail piling up — but no one has slept in the bed for three weeks. That sounds like a ghost tenant, legally speaking, and some regulators will treat it as such. But the operational reality is messier. The resident might have been hospitalized, jailed, or staying with family during a domestic violence crisis. I have seen cases where 'ghost tenant' accusations caused a family to lose housing over a two-week nursing home stay. The editorial signal here: always check the property's vacancy procedure first. If your policy requires a 14-day abandonment notice, and the unit is only empty for 10 days, you're dealing with a procedural gap — not a ghost. That hurts because it means you fix the process, not the person.

Patterns That Usually Work for Identifying Ghost Tenants

Cross-referencing HUD Form 50059 with lease signatures and ID scans

Most ghost tenants get caught in the paperwork seam — the gap between what a form says and what a human actually signed. I have watched teams print HUD Form 50059s, stack them neatly, and call it compliance. That's not verification. The reliable pattern works like this: pull the signed lease, pull the ID scan the applicant submitted at move-in, and put them side-by-side with the 50059 certification. You're looking for signature mismatch — a ghost tenant often gets signed by the head of household with a different pen pressure or a date that falls after the lease start. That hurts.

Reality check: name the policy owner or stop.

The catch is speed. When auditors arrive, compliance officers rush to produce something. They grab the 50059, wave it, and move on. Wrong order. The ghost tenant pattern reveals itself only when you check three documents in sequence: lease execution date, ID scan date, and 50059 certification date. If the 50059 predates the signed lease by even one business day — someone certified occupancy before the tenant existed. Honest mistake? Possible. But repeat that across four units in the same building, and you have a pattern, not a typo. We fixed this in one property by requiring a photocopy of the signed lease page clipped to the 50059 inside the tenant file. Slowed intake by seven minutes per unit. Saved us a six-figure disallowance.

Utility usage spikes or drops as behavioral red flags

Physical presence leaves a thermal trail. Ghost tenants don't shower, don't cook, don't run the AC on July afternoons. I worked a property where a unit showed zero water consumption for eleven consecutive months — yet the file claimed a family of three. The compliance officer had not thought to check the utility bill because the property paid water centrally. That's the blind spot: when utilities are bundled into rent, teams forget that consumption data exists somewhere.

Zero usage for three months is not conservation. It's a concrete sign nobody lives there.

— Regional compliance manager, during a 2023 audit debrief

The trick is to look for drops that coincide with reported move-in dates. A unit that consumed 400 kWh for five months, then drops to 12 kWh the month a new tenant supposedly moved in — that's a ghost, not a frugal resident. Utility spikes work the other way: a vacant unit that suddenly shows 300 gallons of water one month might mean someone squatted briefly, and the property never updated the file. Both patterns require utility data that most affordable housing software doesn't pull automatically. You have to ask the utility provider for a twelve-month usage history in CSV format. Annoying. Worth it.

Property access logs and key fob data as proof of physical presence

Key fob systems log every door open — elevator lobbies, building entry, parking garage. Ghost tenants don't swipe. Period. One property I consulted for had a building with electronic fob readers on every stairwell door. The tenant file showed a single mother with two school-age children living in unit 412. The fob log for that unit showed zero swipes over six months. Zero. Not one entry. The lease had a valid signature, the 50059 was dated correctly, and the ID scan matched. But the fob data proved the unit was empty that whole time. The resident had moved out quietly, sublet the unit to a cousin who never registered, and the property never caught it because annual recertification was done by mail.

Most teams skip this check because they assume fob data is hard to export. It's not. Most systems let you run a report by unit number for a date range — takes three clicks. The pitfall: you must match the fob assignment to the tenant name in your property management system. If the resident never picked up a fob, or if the fob was issued under a misspelled name, the data looks normal but is worthless. Cross-reference the fob serial number against the tenant roster, not just the unit number. That said — even perfect fob data proves presence only for the person who swiped. Household members without fobs won't appear. So this pattern works best when combined with utility data and interview notes from maintenance staff who actually enter the unit for repairs. No single method catches every ghost. Three methods in parallel get close.

Anti-Patterns and Why Teams Revert to Them

Over-relying on tenant self-certification without independent verification

I have watched compliance teams breathe a visible sigh of relief when a tenant signs a form stating they still live in the unit. That signed paper feels like a shield. The catch is—it's not a shield; it's a receipt for a lie. A ghost tenant will certify occupancy without hesitation because the alternative means losing the rent subsidy that keeps the scheme running. We fixed this by cross-referencing every self-certification against two unrelated data points: the last maintenance work order and the unit’s utility consumption pattern. That sounds boring until you catch a tenant who swore they lived there but whose electricity meter showed 14 kilowatt-hours over six months. Wrong order. Not yet. You verify first, then trust.

Most teams skip this because it takes an extra fifteen minutes per file. That fifteen minutes feels unbearable when you have forty units to review before Friday. So the shortcut wins—until the audit reopens and the same ghost reappears with a signed form that buys nobody anything except a corrective action plan.

Ignoring maintenance work orders that show prolonged absence

The plumber knows before the compliance officer does. When a unit generates no service requests for seven straight months in a building where the average resident calls maintenance three times per year, something is wrong. That absence is data—not noise. Yet I see teams treat work-order logs as operational trivia, not compliance evidence. They look at the certification form and the EIV report, but they never ask: When was the last time someone fixed a leak in that bathroom?

The psychology here is ugly: maintenance logs are messy. They contain canceled appointments, duplicate entries, and notes from contractors who spell tenant names differently each time. Sorting through that mess feels like punishment. So teams revert to the clean, orderly EIV report—which is often three months stale—and call it good. The trade-off is painful but simple: you either wade through the messy truth or you certify a vacancy as occupied and refund HUD later.

Using outdated EIV reports as the sole check

Enterprise Income Verification reports are powerful. They're also never real-time. By the time HUD processes wage data and you pull the report, a tenant could have moved out, moved back in, died, or simply vanished—and the EIV will still show a warm body earning income at an address they abandoned six weeks ago. That delay is baked into the system. What hurts is when teams treat a three-month-old EIV printout as definitive proof of occupancy rather than a starting point.

“The EIV said she was employed at the factory. Nobody checked whether she still worked there or still slept here.”

— compliance officer, post-audit debrief, 2023

Reality check: name the policy owner or stop.

I have done this myself: pulled a clean EIV, filed it, moved on. It felt efficient. It was wrong. The anti-pattern is treating a delayed snapshot as a live camera. The fix is to time-box EIV usage: pull it at move-in certification, then use work orders and unit inspections for ongoing verification. That switch alone killed three-quarters of the ghost units in one portfolio we cleaned up last year. The rest required fishing through maintenance logs—the messy work nobody wants but everybody eventually pays for.

Maintenance, Drift, and Long-Term Costs of Ghost Tenants

Retroactive rent adjustments and subsidy clawbacks

Ghost tenants don't just vanish when you finally evict the fictional household or update the lease file. That's the easy part. The hard money hits months later when the state housing agency performs its file review and discovers you collected housing assistance payments—Section 8, project-based vouchers, whatever—for units that had nobody legally occupying them. I have seen a single phantom tenant trigger a $48,000 clawback because the subsidy ran for fourteen months before anyone checked the utility consumption logs. The agency demands repayment of the incorrect subsidy, plus interest, often calculated at the rate used for federal debt. That hurts. And here is the detail most teams miss: retroactive rent adjustments must be applied to every month the ghost was counted, even if the unit sat truly empty or was occupied by a different household not on the lease. The math gets ugly fast.

Most property managers assume they can re-lease the unit and forget the past. Wrong order. HUD’s verification protocols require you to recertify the tenant’s income for each month of ineligibility—good luck reconstructing pay stubs for someone who never existed. The compliance software will reject your retroactive entries unless you override the date stamps manually, which triggers audit flags. One Oregon-based owner I worked with spent seven months untangling a single ghost tenant’s subsidy trail, and the clawback from the tax credit syndicator ate two years of cash flow from that building. That’s the real cost: the money leaves, and it doesn’t come back.

LIHTC noncompliance penalties and extended use agreements

The Low-Income Housing Tax Credit program handles ghost tenants differently than HUD does, and the penalties are stickier. LIHTC compliance doesn’t just look at whether rent was collected—it looks at whether the unit was available to a qualified low-income household for the entire compliance period. A ghost tenant occupying a unit that should have been leased to a verified income-qualified household means that unit fails the next physical inspection. Fail enough units across a building, and the IRS can recapture a portion of the credits taken over a decade. That’s not a fine; that’s a credit reversal that can hit six figures for a single building.

Worse is what happens under extended use agreements, the thirty-year covenants that many states tack onto LIHTC deals. Ghost tenants violate the extended use period because the property effectively had ineligible occupants—or no verified occupants—during those months. State housing agencies track this through annual owner certifications. Lie on the certification, and you risk debarment from future allocations. I have watched a management company lose two pending tax credit applications because their ghost tenant pattern during the first fifteen-year period made the state suspicious about their controls. The ripple effect is hard to quantify because you never know which deal you didn’t win.

Operational drift: how ghost tenants strain property management resources

The less obvious cost is the slow creep of operational dysfunction. When a ghost tenant exists, your lease file says someone lives there, so maintenance work orders for that unit go unassigned—why inspect a unit that appears occupied? Meanwhile, the real condition of the unit deteriorates. Water leaks, pest issues, appliance failures—none get reported because the official occupant doesn’t exist. By the time you discover the ghost, the unit needs a full rehab that could have been prevented with routine inspections. One client in Florida found a ghost tenant after eighteen months; the unit had mold behind the refrigerator, a broken toilet flange, and rodent damage that totaled $14,000 in repairs. That cost landed entirely on the owner because no tenant security deposit existed to claim damages.

Ghost tenants hollow out your portfolio from the inside—the subsidy recapture is the headline loss, but the deferred maintenance kills your property’s long-term value.

— Director of asset management, mid-Atlantic LIHTC portfolio

Staff time also bleeds away. Your compliance officer spends hours reconstructing files for an audit response. Your property manager redoes certifications. Your accountant files amended subsidy requests. All that labor is unproductive—it fixes a past mistake rather than running current operations. Most teams I’ve consulted with underestimate this drag by about 40%. They budget for the financial penalty but not for the three weeks of administrative chaos that follows a single ghost tenant discovery. The catch is you often can’t hire temporary help because affordable housing compliance requires certified professionals, and those people are expensive and scarce. So your existing staff burns out, turnover spikes, and the next audit finds more ghosts because nobody had time to do the basic move-in verification. That’s the drift—each ghost tenant pulls your team further away from the process that prevents ghosts in the first place.

When Not to Use This Approach

When the 'Ghost' Is Actually a Data Entry Error or a Temporary Sublet

Not every missing signature means fraud. I once watched a property manager spend three weeks chasing a “ghost” in Unit 204—only to find the tenant’s son had sublet the apartment for a summer internship while the leaseholder was abroad. The paperwork was a mess. The HUD-required lease addendum was signed in May, filed under the wrong unit number, and never scanned. That isn’t a ghost tenant. That’s a filing cabinet that needs a fire. Aggressive investigation in this scenario burns goodwill with the family, ties up compliance staff, and—worst of all—flags a false positive to the housing authority. The catch is that data-entry errors look identical to fraud in an audit report: names mismatch, signatures missing, occupancy dates gap. Call the tenant first. Ask whether someone moved in temporarily. Three minutes of human conversation often save three months of forensic accounting. If the answer is “yes, my nephew stayed for six weeks,” you need a temporary-occupancy rider, not an eviction notice.

Scenarios Where a Full-Scale Audit Is Disproportionate to the Risk

Small properties with five units. Or a building where one household’s tax credit allocation is under $4,000. I have seen oversight boards demand tenant-by-tenant re-certifications for a single apartment whose subsidy value barely covers a roof repair. The math breaks. The compliance officer’s hourly rate multiplied by the number of interviews and document pulls quickly exceeds the potential clawback. What usually breaks first is staff morale—teams burn out on low-yield hunts while bigger violations drift unnoticed. That hurts. The smarter move is a triage rule: if the suspected ghost tenant occupies a unit whose tax credit value is below 5% of your portfolio’s annual compliance budget, flag it, log it, but don't launch a full-scale audit. Monitor the next recertification cycle instead. Most “ghosts” in cheap units resolve themselves when the tenant fails to renew and the apartment turns over naturally.

State-Specific Exceptions for Short-Term Medical Absences

Some states have a carve-out that no auditor tells you about until you’ve already over-corrected. In California, for example, a tenant who enters a 90-day rehabilitation facility is still “occupying” the unit for compliance purposes—even if no one sleeps there. Aggressive auditors in other states would flag this as a ghost. Don’t. The regulatory logic is that the lease remains active, belongings stay in place, and the tenant intends to return. I have seen a Massachusetts property nearly lose its Low-Income Housing Tax Credit allocation because management demanded a unit inspection during a cancer patient’s six-week hospital stay. That was not compliance. That was harassment.

“The rule is not that someone must sleep there every night. The rule is that the unit must be the tenant’s fixed residence.”

— paraphrased from a 2024 HUD Q&A on temporary absence policies

Honestly — most housing posts skip this.

If your audit flags a unit empty for 45 days, check state administrative guidance before sending a cure letter. Medical absences, military deployment, and elder care visits all have allowed durations that vary wildly by jurisdiction. Overriding those protections with a blanket ghost-hunt protocol creates liability you don't want: fair housing complaints, tenant-lawyer letters, and—ironically—a reputation that makes genuine ghost audits harder to defend.

The One Question to Ask Before Launching Any Investigation

Will the energy spent here prevent a real compliance failure elsewhere? Honest answer is often no. Ghost tenants exist—they drain subsidies and inflate vacancy rates. But a team that treats every audit flag as an emergency will eventually exhaust its resources on clerical ghosts, short-term sublets, and state-exempt absences. The discipline is knowing when to walk away. Prioritize units with high subsidy value, long-term vacancy patterns, and zero supporting documentation. Let the rest sit in a log with a 90-day review date. That's not negligence. That's triage—and triage keeps your affordable housing program solvent.

Open Questions and FAQ About Ghost Tenants

Can digital identity verification replace physical file reviews?

Every quarter some software vendor pitches me a tool that claims to solve ghost tenants with biometric login or recurring selfie checks. The demo is slick. The catch is reality. I've watched a property manager implement a facial-recognition portal only to discover that families shared one phone—whoever answered the door first authenticated as the leaseholder. Digital identity verification works beautifully for bank accounts. For affordable housing compliance, where elderly relatives live with grandchildren and English is a second language for half the tenants, the false-positive rate climbs fast. The physical file still carries weight because a file can hold contradictory things—a rent receipt from June, an inspection note from July that says "no one home," a call log showing three unanswered wellness checks. No single digital system ties those threads together yet. Yet is the operative word. I'd bet we'll see hybrid models within three years, but right now swapping paper for pixels alone creates new blind spots. Worse—some auditors reject purely digital proof chains for recertifications. So the short answer: no, not yet. The long answer: start with physical files, layer digital tools on top, and never let the software make the final call on occupancy.

What if the tenant is deceased and the family hasn't reported it?

This situation lands in my inbox at least twice a year. The leaseholder died eight months ago. The adult child stayed, kept paying rent, and never told the office. Legally the unit became a ghost tenant the day the leaseholder stopped holding legal tenancy. Practically—the family's grief collides with your compliance timeline. Most state housing agencies allow a grace period (often 30 to 90 days) for reporting a death, but the burden falls on the household to notify, not on the landlord to detect. That sounds fine until the family fears eviction and hides the death entirely. I've seen one solution work consistently: a simple letter mailed to every unit every six months asking, "Is the leaseholder still living here?" with a prepaid return envelope. You'd be shocked how many families quietly check "no" and mail it back. They want to comply—they just don't know how. The trade-off is administrative cost. Sending 200 letters per quarter costs time and postage. Not sending them costs certifications.

How do state laws differ on notice requirements for vacated units?

You can't assume federal rules cover everything here. They don't. California, for example, requires a formal 30-day notice before you can re-let a unit the tenant has already abandoned—even if you have photographic evidence the apartment is empty. Texas treats abandonment more like property law: if rent is unpaid for two consecutive months and the unit appears vacant, you can change the locks without court order. That difference changes how you sequence your audit response. In California you document, notify, wait. In Texas you document, lock, re-lease. The pitfall is acting on the wrong state timeline and triggering a wrongful eviction suit. I recommend keeping a one-page state-by-state cheat sheet in your compliance binder—not a legal opinion, just the statutory citation for abandonment definitions and notice windows. Your lawyer writes the opinion; you write the checklist. Most teams skip this step. Then they copy a procedure from a sister property in another state, and the seam blows out in month three of the audit.

'The hardest ghost to catch is the one the family keeps alive out of fear, not fraud.'

— property manager, LIHTC portfolio, after a 2024 compliance review

One more unresolved angle: what happens when a ghost tenant resurfaces physically years later claiming they never moved out? That scenario feels like a corner case until you lose a Monday to it. I've seen a former resident show up at lease renewal with a cardboard box of utility bills from another address, insisting the property manager fabricated the vacancy. The file had a signed move-out form—later proven forged by a maintenance worker. So the open question that keeps me up: how many of our certified vacancies are built on paperwork we never truly verified at the point of exit? Next time you clear a unit, call the emergency contact listed on the lease. Not for permission—for a sanity check. If they sound surprised the tenant moved, you just found a problem before the auditor does.

Summary and Next Experiments

Triage checklist: first 72 hours after discovery

You just got the audit results. Ghost tenants everywhere. Don’t panic — but don’t sit on it either. The first 72 hours decide whether this becomes a quick fix or a compliance nightmare that haunts your next certification. I have seen teams waste that window chasing paperwork instead of people.

Here is the order that actually works. Pull the rent roll and the actual physical occupancy log — side by side, same time stamp. Then walk the units in question. Knock. Check mailboxes. Look for toothbrushes, not just lease signatures. The catch is that utility data takes longer to pull, so start that request immediately but don’t wait for it to decide your initial response. Wrong order — you lose a day and the trail gets colder.

Flag every mismatch with a sticky note on a physical board. Digital tools are fine, but a wall map with red dots keeps the team honest. Assign one person per cluster of units — no more than fifteen per person — and give them a hard deadline of 48 hours to confirm actual status. Then call the agency contact with a preliminary count before they ask. Honesty buys time. Silence buys follow-up audits.

Pilot a quarterly cross-reference between utility data and rent rolls

That sounds like extra work, and it's — for the first cycle. But the long-term cost of ghost tenants isn’t recertification dollars alone; it’s the drift in your vacancy calculations that throws off next year’s budget. A pilot run on one property, say the seventy-two-unit building you just cleaned up, costs about four hours of data wrangling per quarter. That's a cheap insurance policy.

You match October’s gas usage against October’s rent roll. Zero consumption for three months but still listed as occupied? That’s a red flag worth a site visit, not just an email. The trade-off is that utilities lag by a billing cycle and shared-meter buildings muddy the signal. However, even a rough match catches the egregious cases — the ones that auditors spot from across the room.

We found twelve ghost units in one afternoon by comparing water bills to lease start dates. Nobody had run that report in two years.

— Compliance officer, Midwest HUD portfolio, 2024

Track your corrective action timeline for agency submission

Most teams skip this, then scramble when the agency asks for dates. Build a simple spreadsheet now — column one: unit ID, column two: date discovered, column three: corrective step taken (deletion, retroactive lease, back-dated termination), column four: date completed. That’s it. No dashboard, no vendor tool, just a shared Google Sheet with freeze panes. The seam that blows out is when two people edit the same row. Assign ownership per unit, not per action.

What usually breaks first is the narrative explanation. Agencies want to know why the ghost appeared, not just that you removed them. A single sentence per unit — “Lease renewed but tenant moved out same week, system not updated” — can save you months of back-and-forth. That hurts less than trying to reconstruct events from memory six months later. One rhetorical question: does your current process survive a random file pull by the regulator? If not, this is your lowest-risk experiment. Run it once, see where the gaps live, then fix only those. The rest can wait.