MyDailyCheck calls or texts the people on your roster every morning, escalates to your team only when needed, and gives you council-reportable numbers when the inevitable heat dome, cold snap, or power outage hits.
You have a vulnerable-resident registry. You have a heat-warning protocol. You have staff who care. And every time the weather turns, you find out the registry is out of date, the protocol is somebody calling a phone tree by hand, and the staff are stretched.
When the next extreme weather event hits — and it will — you want to know your roster is covered. By 9 a.m. on the morning of the warning. Not by 3 p.m., not "we think so." Covered.
MyDailyCheck is the layer between "we have a list" and "we know everyone is okay."
Environment Canada issues the warning at 6 p.m. Your team flips the program into elevated mode — more frequent check-ins, lower escalation thresholds.
At 7 a.m. the next morning, MyDailyCheck starts calling. By 8:30, most of the roster has answered. By 9:00, the dashboard shows you who didn't — twelve people out of three hundred.
Staff or community paramedics visit those twelve. They find eleven who are fine (one is at her daughter's, two were asleep). The twelfth needed water and AC help. She got it within the hour.
When the council asks for the report, you have one. With timestamps. Every name. Every check-in. Every response.
CSV import from your vulnerable-resident registry, or one-at-a-time enrollment with consent.
Calls or texts at the time you set, with elevated frequency during extreme weather events. Every interaction is logged.
Your team only sees the people who didn't respond after retries. By 9 a.m. you know the gap; by 10, it's closed.
Without MyDailyCheck
With MyDailyCheck
When the heat warning comes down, staff scrambles to call hundreds of people manually. By the time the list is half-done, it's afternoon.
By 9 a.m. the dashboard shows the gap. Staff visits only the people who didn't respond. By 10, the gap is closed.
Council asks for an after-event report. Staff reconstructs it from call logs, memory, and email threads.
The report exports from the dashboard. Every check-in, every escalation, every response — timestamped and ready for council the same day.
Vulnerable-resident registry is out of date within months. Phone numbers change, people move, nobody updates the spreadsheet.
The system keeps the list live. Consent renewals, opt-outs, phone updates — handled inside the platform.
Elevated check-in frequency during extreme heat warnings. The roster is covered before the worst of the day.
For deep-freeze events when power outages and frozen pipes hit hardest. Confirm vulnerable residents are warm and reachable.
When the grid drops, the daily call still goes out (via SMS if needed) so you know who has heat, who has food, who needs a visit.
The roster stays current automatically — consent renewals, contact updates, opt-outs all live in the system.
Built by a Canadian company, hosted on Canadian infrastructure.
PIPEDA-compliant. Role-based access. Consent-first enrollment.
Reports that pass the council test: timestamped, exportable, defensible.
Talk to us about a pilot for your municipality. We'll work with your existing registry and protocols.