BardisCare
One view across every community.
A custom operations concept showing how a senior-living operator with several communities can replace per-building spreadsheets, paper inspections and emailed reports with one system built around how communities actually run.
BardisCare is a fictional product concept created by PiTech Consultants to demonstrate custom software and business automation capabilities, and part of Bardis, PiTech’s family of software concepts. It is set in Tessaly Senior Communities, an invented operator with three communities in central Ohio. It is operations software, not a clinical record: it holds no resident health information. It is not client work, and no client results are implied.
The problem
Picture an operator with three communities. Each building keeps its own occupancy spreadsheet, and the regional view is whatever someone assembled on Friday. A move-out starts a turnover that lives in emails and a maintenance log; the apartment is marked ready when someone says it is.
Inspections are done on paper and their findings re-typed into work orders, if they are re-typed at all. License renewals, fire drills and vendor insurance certificates sit in different calendars, so a deadline is noticed when it is close. Leadership asks for the monthly numbers and gets a week of copying.
None of this is unusual. The care platform handles care well; the operations around it are where the hand-offs, and the surprises, collect.
Before and after
One spreadsheet per building, reconciled by hand
- Move-out notice emailed to maintenance
- Turnover email logged by hand
- Paper inspection findings re-typed
- Maintenance log status asked for by phone
- Occupancy spreadsheet one per community
- Compliance calendar kept by one person
- Friday report assembled from all of them
One system
- Move-out
- Turnover
- Inspection
- Work order
- Ready
- Reserved
- Move-in
- Report
- Compliance horizon
- Incidents
- Coverage
- Command Center
- Entered once
- Every community the same way
- Deadlines on one timeline
- Reports from the records
What I built
Command Center
A morning brief across the portfolio — occupancy, items needing attention, incidents awaiting review, compliance due, aged work orders and coverage gaps — with every number opening the records behind it.
Community dashboards
One per community: a floor-plan board of every apartment, building systems with their status, and that community’s work orders, compliance, incidents and inspections.
Occupancy and turnovers
Move-out to turnover checklist and make-ready work order, ready only when the work is done, then reserved and moved in — all from the same records.
Work orders and inspections
Checklist inspections whose findings become corrective actions and work orders, verified when they close.
Compliance horizon
Licenses, inspections, drills, vendor insurance and staff certifications on one twelve-month timeline.
Incidents
Operational incidents only. A resident-involved event cannot close until clinical follow-up is confirmed as documented in the care system.
Team operations
Coverage gaps imported from scheduling, the float pool and cross-trained cover, so a gap is visible before the shift.
Reports
A monthly operations packet, twelve-month trends and CSV exports, computed from the records rather than typed in.
Inside the demo
Six screens that carry the workflow. Select one to open it in the interactive demo.
-
Command Center One morning brief across every community, with each number opening the records behind it. -
Community dashboard A dashboard per community: every apartment on the floor plan, and building systems tied to their work orders. -
Occupancy Every apartment’s state across the portfolio, read from residency and turnover records. -
Compliance horizon Licenses, inspections, drills, vendor insurance and certifications on one timeline. -
Inspection A checklist inspection whose findings become corrective actions and work orders. -
Reports A monthly operations packet computed from the records, not entered.
Why it matters
One view across communities
Leadership sees every community the same way, instead of a different spreadsheet from each building.
Turnovers that cannot skip a step
An apartment is ready only when its checklist and work orders are done, so a move-in does not land on unfinished work.
Deadlines before they are overdue
Licenses, drills, insurance and certifications sit on one timeline with what is coming due, not in a calendar one person keeps.
Numbers nobody re-keys
Every figure on every screen is calculated from the records, so the monthly packet is not a week of copying.
A clear line with clinical systems
Operations data lives here; resident health information stays in the care platform, by design.
A record of who did what
Work orders, inspections and incidents carry their history, so a hand-off between shifts does not lose anything.
About the demo
- Everything in it is invented: the operator, its three communities and their towns, staff, residents’ apartments, vendors and history.
- It runs on a fixed date — Monday, February 8, 2027, 8:12 AM — so it always opens on the same morning.
- Changes you make are kept only in your browser, and Settings resets them.
- It holds no resident health information, and nothing you do leaves the page.
Your communities don’t need BardisCare.
They need operations software built around the way they actually run. Tell me what’s not working, and I’ll tell you plainly whether custom software is the answer.
You’ll hear directly from PiTech, typically the same business day.