Open case queue
Every open case by stage, with owner, age and the next action due.
A manager oversight app for senior placement agencies shows open cases, coordinator workload and the response windows the agency has promised families. Built for iOS and Android, it lets the general manager act on a slipping case before a family calls another agency.
Families searching for a placement agency compare response times, how clear the fees are and how much time a coordinator will give them. Many call three agencies in one afternoon and choose the one that answers within the hour. Hospital social workers choose partners in much the same way, based on how often their patients are placed quickly.
For this project, the oversight app exists to keep those response promises. A general manager who can see unanswered calls, cases waiting on a community and tours not yet confirmed can act before a family moves on. The app is an internal tool, but it is the reason families get the response they expected. A slow reply is often the moment a family starts looking elsewhere, so the window deserves close tracking.
The first release should show the open case queue by stage, the workload for each coordinator and a daily summary of response times and open tasks. Together those views show what slipped overnight, which coordinator is carrying too much and which community holds are at risk, all drawn from records the case system already holds.
Placement forecasts by month, profit reporting by community and automated coordinator assignment can wait. Forecasts need a long run of clean case history to be useful, and assignment rules depend on how the team prefers to work. A later phase can add them once the first views are trusted.
At 7:50 a.m. the general manager opens the app and sees the overnight summary. Four families called after hours, and one of those calls has no response yet. The queue lists that call first, with the coordinator on duty and the time it was logged. He assigns the call to the coordinator with the lightest load, checks that she has the case notes open, and adds a note.
Late morning he checks the cases waiting on a community. Two room holds are close to expiring and one tour has not been confirmed. The app shows the coordinator who owns each item, and he sends a reminder from the queue. By the end of the day the summary shows every call answered inside the window, with both holds recorded as renewed.
Every open case by stage, with owner, age and the next action due.
Open cases and due tasks for each coordinator, so work moves before anyone is overloaded.
Shows calls and family messages inside the agency's window and flags any at risk of missing it.
A start-of-day page with overnight calls, missed windows and community holds to check.
We need the stages of your case process, the response windows you promise families and partners, the list of coordinators and their regions and the community holds you track. If cases sit in more than one system, we list each source and the fields we will read, so no figure depends on guesswork. A sample weekly report from your current process helps us match the numbers the team already quotes.
Access rules come next. Managers see cases and tasks, coordinators see their own caseload, and nobody sees commission or referral terms in the oversight view. We agree those roles during scoping, and every export or view is logged.
Begin with the morning call the general manager already holds with the team. Put the open queue on the screen for that meeting, so the discussion starts from the same list. Coordinators who see their own load and due tasks in the same place are more likely to keep the list current.
One coordinator becomes the queue champion, the response rules are written down before the first day, and the general manager reads the summary with the team each Friday. Post-launch support covers new queue views, stage changes and store updates as the agency's process changes.
Track response times for calls and family messages, the number of cases waiting on a community for more than a day and the share of tours confirmed before the family's preferred date. Those are the figures that show whether families are getting the response they expected.
Record the same measures for the months before launch so the comparison is fair. Review them with the team each month, and retire any view nobody uses. A small set of numbers the team checks every day beats a large report that arrives after the decision has been made.
The queue shows stage, owner and next action, not medical detail. Case notes and assessments stay in the case record, and access follows the role settings. Every view and export is logged for the agency's records.
The view is built to help them, not to rank them. Coordinators see their own cases and the team total, and managers use the figures to rebalance work. We recommend agreeing that purpose with the team before launch, so the tool is seen as support.
Where the CRM allows it, the app reads case stages and task dates from it. Where it does not, a daily export keeps the queue accurate. The CRM remains the system of record for case data.
Each figure links back to the case records, so a manager can check it in a click. If a record is wrong, the fix is made in the source and the change is logged. The team agrees the definitions before the first report is shared.
Bring your response rules to a free call, and the scope and price come back in writing.