Example engagements

How an engagement plays out

Our client work is covered by confidentiality agreements, so we don't publish client stories. These illustrative examples show how we approach typical processes in regulated organizations, and exactly what we'd measure.

Financial services

Client onboarding intake for a financial institution

Illustrative example. Not a client project. It shows how we'd approach this kind of work and what we'd measure; real results depend on your baseline.

New client applications arrive as emails with document attachments. Staff check them, re-key details into the client system and route the file to an advisor.

Where it typically starts

  • Several business days from application to advisor assignment
  • Every application re-keyed by hand
  • No single view of where an application is

What we'd aim for

  • Same-day routing for complete applications
  • Re-keying removed for standard cases
  • A person still approves every new client record

How the six weeks run

  • Week 0–2 — Map the process, rate the agent's model risk, register its Entra Agent ID and owner
  • Week 3–5 — Agent reads documents and drafts the record; workflow routes it for approval; evaluation set built from anonymised samples
  • Week 6 — Go-live with Agent 365 cost alerts and an Agent Fact Sheet for the model inventory
OSFI E-23 model inventory entryHuman approval on every recordEvaluation set rerun on each change
Government and public sector

Bilingual service request intake for a public agency

Illustrative example. Not a client project. It shows how we'd approach this kind of work and what we'd measure; real results depend on your baseline.

Residents send requests by email and web form in English and French. A small team reads, sorts and acknowledges each one before it reaches the right officer.

Where it typically starts

  • Acknowledgement can take a couple of business days
  • Triage done by hand, in two languages
  • Requests sometimes reach the wrong team first

What we'd aim for

  • Instant acknowledgement in the resident's language
  • Triage within the hour during business hours
  • Officers make every decision; the agent only sorts and summarises

How the six weeks run

  • Week 0–2 — Process map, decision points identified, design notes shaped for the Algorithmic Impact Assessment
  • Week 3–5 — Bilingual intake on Power Pages, classification workflow, summaries for officers, clear notice that automation is used
  • Week 6 — Go-live with audit trail, accessibility check and a published fact sheet
Algorithmic Impact Assessment inputsNotice to residentsAccessible bilingual forms
Healthcare

Referral triage for a community health organization

Illustrative example. Not a client project. It shows how we'd approach this kind of work and what we'd measure; real results depend on your baseline.

Referrals arrive by email and e-fax. Intake staff read each one, enter it, and look for urgent cases among the routine ones.

Where it typically starts

  • Urgent referrals can wait in the same queue as routine ones
  • Each referral entered by hand
  • Status checks handled by phone

What we'd aim for

  • Possible urgent referrals flagged to a person within minutes
  • Routine entry prepared for staff to confirm
  • No clinical decisions made by the agent

How the six weeks run

  • Week 0–2 — Data flow map for the privacy impact assessment, minimum data agreed, approved tools only
  • Week 3–5 — Agent extracts referral details and flags urgency for a clinician; staff confirm every entry
  • Week 6 — Go-live with access reviews, monitoring and a fact sheet for the privacy office
PHIPA privacy impact assessment inputsLeast-privilege accessClinician review of every flag

What would this look like for your process?

In a free 30-minute call we'll sketch the baseline, the target and the controls for one of your processes.