An operating board for a single campus continuing care retirement community of 280 living units across five unit types: cottages and apartments in independent living, then assisted living, memory care and skilled nursing. Stillmeade Village is a fictional organization invented for this sample, in a fictional North Carolina town. Every figure on this page is generated mock data. The point of the board is the shape of the work, not the numbers.
A North Carolina continuing care community is licensed by the state Department of Insurance and reports quarterly under the continuing care statute, Chapter 58, Article 64 of the General Statutes, including occupancy broken out by type of living unit. That report is a tedious recurring job assembled by hand in most business offices. On this board it is a side effect of the same numbers everybody already needs.
Drawn as of the quarter ended 30 September 2026. The four controls below set the scope that every figure, chart, table, callout and total on this page is calculated over.
Every resident in scope, drawn from the living unit type they entered the community at to the one they live in tonight. A rental community has nothing to put in this picture. A continuing care community sells this picture, and then almost never looks at it.
Illustrative mock data. Residents, entry levels and transfers are generated, not observed.
Illustrative mock data. Quarterly occupancy is generated, not observed or published.
This grid is what the quarterly continuing care report asks for: units by type, how many are occupied, and what the rest are doing. Subtotals add to the campus total by construction, which is the part that takes a business office a day to prove by hand.
Illustrative mock data. These counts are generated for this sample and are not any real community's published occupancy.
Illustrative mock data. Entrance fees, refund percentages and the amortization are invented.
Illustrative mock data. Fees are invented and are not any real community's rates.
Illustrative mock data. Future residents, deposits and wait times are generated.
Illustrative mock data. Departure reasons are generated, not observed.
Illustrative mock data. Every answer recalculates from the four controls above.
A private model on a machine inside your own network, answering in plain language over your own census, billing and contract tables. Nothing leaves the building, there is no per seat license, and every answer points at the figure on this board that it came from.
Illustrative mock data. The answer shown is generated from this board's current filter state.
Replaces: the business office rebuilding occupancy by type of living unit from the census system, the move in log and two spreadsheets, four times a year, then reconciling it against the general ledger by hand.
Pulls the quarter end census, builds the grid above, ties the subtotals to the total, and produces the pack with every figure traceable to a row.
About 14 hours a quarter
Replaces: a controller updating the entrance fee liability schedule in a workbook after every move in, internal transfer and departure, and rediscovering the declining balance amortization each month.
Recomputes the refundable balance per contract, rolls the schedule forward, and flags any contract whose plan or date does not match the signed agreement.
About 11 hours a month
Replaces: the residency counselor rebuilding the waiting list by unit type before each board meeting, from a spreadsheet that only she can read.
Keeps the list in deposit order per unit type, names the next three calls when a unit is projected to open, and surfaces any future resident with no contact in 90 days.
About 8 hours a month
Illustrative mock data. Hours are illustrative estimates for a community of this size, not a measured result.