Case Study: Simplifying Old Age Security (OAS) Access for Vulnerable Seniors in Canada

Reading Time: 2 minutes

Recently I read an article about a senior in Toronto who was nearly evicted as a result of errors at Service Canada with regards to their Old Age Security (OAS) benefit (CBC News article). Despite being fully eligible for OAS, the senior’s payments were suddenly stopped, and she spent weeks trying to get help, calling daily, waiting on hold, and receiving little to no resolution. This situation not only put her at risk of homelessness, but also highlighted serious process and service delivery failures within a system that is supposed to support Canada’s most vulnerable.

This case presents a clear opportunity to examine how service design, process review, and reengineering can prevent such failures and create a more human-centered approach to public benefits administration.

Problem Overview

The senior experienced the following challenges:

  • Unexpected Payment Disruption: OAS payments were halted without clear explanation or notification.
  • Poor Customer Support Experience: The individual was left calling daily with no way to escalate the issue or speak to a knowledgeable agent.
  • Digital and Bureaucratic Barriers: Complex systems made it difficult for the senior to understand what happened or how to fix it.
  • Lack of Accountability or Transparency: There was no tracking, no proactive outreach, and no timeline for resolution.

These issues point to systemic failures in both the operational design and support experience for public benefit recipients.

Key Impacts

  • Financial Instability: Loss of critical income triggered rent arrears and a near-eviction.
  • Emotional Distress: Weeks of stress, confusion, and fear of homelessness.
  • Public Trust Erosion: Decreased confidence in the reliability of Service Canada programs.
  • Increased System Strain: More calls, complaints, and dependency on advocacy groups and political intervention.

Opportunities for Process Review and Reengineering

1. Human-Centered Service Design

  • Simplify the Experience: Redesign application and support systems with seniors in mind, fewer steps, less jargon, and visual guidance.
  • Multiple Support Channels: Ensure non-digital options (in-person, mail, phone callbacks) are robust and staffed by trained, empathetic personnel.

2. Proactive Payment Safeguards

  • Automated Alert System: Immediately flag payment suspensions internally and notify recipients with explanations and next steps.
  • Risk-Based Monitoring: Use automation to detect disruptions for vulnerable individuals and trigger review before payments stop.

3. Escalation Framework

  • Dedicated Case Workers: Assign temporary case managers when critical benefit issues arise, especially those affecting housing or health.
  • Tiered Resolution Process: Establish response time targets and escalation paths for unresolved cases beyond 72 hours.

4. Transparent Case Tracking

  • Status Visibility: Implement a simple case tracking ID system accessible by phone, web, or text message.
  • Communication Templates: Standardize updates so recipients aren’t left guessing about the status of their claims or appeals.

5. Cross-Agency Integration

  • Unified Data View: Link relevant CRA and Service Canada systems to minimize errors due to outdated or mismatched records.
  • Internal Collaboration Protocols: Make it easier for front-line staff to collaborate across departments in real time.

Conclusion

The issue was only resolved after the media got involved, drawing public attention to her case.

But not every senior knows to call the media. How many others might be facing similar issues in silence, without knowing where to turn?

This case is a stark reminder that even small administrative errors can have life-altering consequences, especially for seniors living on fixed incomes. With thoughtful process review and human-centered reengineering, Canada can transform how we deliver public benefits, ensuring that systems meant to provide security and dignity in old age do just that.

So what would you have done?

  • Where would you start to fix this?
  • What is one change you would make first?

Share your thoughts (on LinkedIn). Let’s design systems that serve everyone better.

Follow me on LinkedIn.