An operating board for a fictional nonprofit community of 142 affordable apartments in three buildings, of the kind built under the federal Section 202 model with project based rental assistance on every apartment. Wrenmarsh Commons is invented, in an invented town, and every figure on this page is generated mock data. What is real is the shape of the job: a waiting list, an annual review for every household, a turn clock on every empty apartment, and a rent split between the tenant and the subsidy that has to reconcile every month.
October 2026 · the board is drawn as of 30 September 2026, with 48 months of history behind it. The period selector sets the window every figure is calculated over, and the prior period of equal length is what the deltas compare against.
Every household here has an annual income review on the anniversary of its move in, and the anniversaries are not spread evenly, because move ins never were. This dial is the shape of that year: one spoke per calendar month, its length the number of reviews falling due, stacked by apartment size. The shaded band is the four month notice window, which is the work already sitting on somebody's desk.
Illustrative mock data. Anniversary months, household counts and the notice window are invented for this sample.
Two lines on two axes. Occupancy barely moves in a building like this one, so the line that tells you something is the second: the average tenant share drifts up as incomes drift up, and the subsidy quietly absorbs the difference.
Illustrative mock data. Monthly occupancy and rent shares are generated, not observed.
Illustrative mock data. Applicant records are invented. This panel ignores the apartment status filter, because an applicant is not an apartment.
Illustrative mock data. Contract rents and household incomes are invented for this sample.
Illustrative mock data. Apartment numbers, vacancy days and turn stages are invented.
Illustrative mock data. Referral records are invented and no resident information of any kind appears on this page.
None of this is difficult. It is just the same assembly, on the same schedule, from the same four systems, for the rest of time. That is exactly the kind of job worth handing to something that does not get bored.
Illustrative mock data. The reports, recipients and hours are illustrative for a community of this size, not a measured result.
Illustrative mock data. Every answer recalculates from the filters above.
A private model, on a machine inside your own network, answering in plain language over your own numbers. Nothing leaves the building, no resident record goes anywhere near a public service, and every answer points at the figure it came from.
Illustrative mock data. The answer shown is generated from this board's current filter state.
Replaces: the occupancy specialist counting anniversaries off a lease list every month and typing the notice letters one at a time.
Builds the notice queue four months out, drafts each letter with the household's own dates in it, books the appointment, and raises a hand when a household has not answered after thirty days.
About 11 hours a month
Replaces: finding out at the month end meeting that an apartment has been empty since July and nobody knew whose task it was.
Starts a clock the day keys come back, carries the apartment through clean, repair, inspect and ready, names the person each stage is waiting on, and hands the next name off the list to the office when it is showable.
About 7 hours a month
Replaces: a binder and a spreadsheet that disagree, and a twice yearly update letter mail merged by hand in an afternoon nobody has.
Holds position order with its date stamps intact, prints the update letters, records the replies, and retires an unreachable applicant with a dated trail of every attempt instead of a shrug.
About 9 hours a month
Illustrative mock data. Hours are illustrative estimates for a community of this size, not a measured result.