Canadian bilingual benefits administration sits at the intersection of two hard requirements: the platform must work correctly in both official languages, and it must meet the same regulatory and UX standards as any financial services interface. For TimCare, that meant the theme needed to support two fully independent deployments - the English version and its French counterpart - where either could be updated, tested, and deployed without affecting the other.
The typical approach for bilingual WordPress sites is a single parent theme with a translation layer - WPML or a similar plugin handling language switching within the same installation. That approach creates hidden dependencies: a change to the parent theme touches both languages simultaneously. For a national benefits platform with regulatory obligations around French-language service delivery, that coupling introduces unacceptable risk. A template change that breaks the French PAD enrollment workflow cannot be allowed to slip through as a side effect of an English update.
The PAD enrollment workflow added a second layer of compliance requirement. Pre-Authorized Debit authorization in a Canadian benefits context follows a regulated process: the franchise owner must review the authorization terms in their language of choice, confirm their banking details, and receive a confirmation record. Every template in the enrollment sequence had to meet Great-West Life’s compliance requirements for automated payment authorization.
Independent EN/FR Codebases
The English (timcare-en) and French versions were built as fully independent standalone themes - no parent-child dependency, no WPML coupling. Shared design logic (CSS foundation, responsive breakpoints, typography system) was developed once and maintained as parallel copies in each theme rather than as an inherited dependency. Each language version could be tested, approved, and deployed on its own schedule without coordination. This was a deliberate architectural trade-off: more maintenance surface in exchange for deployment independence.
PAD Enrollment Workflow Templates
Custom page templates built for the PAD enrollment sequence - the series of screens a franchise owner steps through to authorize automatic premium deductions from their business account. Templates integrated with the platform’s existing enrollment form logic, guided users through the sequence with clear field labeling and error states, and delivered a final confirmation screen meeting Great-West Life’s compliance requirements for automated payment authorization.
Mobile-First Responsive CSS
Franchise owners access the platform from mobile devices when managing benefits away from a desk. The theme used a mobile-first CSS foundation so the administrative interface was fully functional on mobile - not just readable, but completable for complex enrollment tasks.
Administrative UX for Non-Technical Users
The interface was designed for franchise owners and their staff - not IT administrators. Navigation labels, form field descriptions, and status indicators written and laid out for clarity, with the assumption that users would be completing high-stakes financial tasks quickly and might be interrupted mid-process.
Enterprise Delivery Standards
Theme architecture, code quality, and documentation delivered to Great-West Life’s internal standards for a national rollout across the Tim Hortons franchise network. The same enterprise bar applied to all Great-West Life work.
The TimCare theme was delivered to Great-West Life’s standards and rolled out nationally across the Tim Hortons franchise network, serving franchise owners in both official languages across every province. The independent bilingual architecture meant the EN and FR versions could be maintained and updated on separate schedules without creating translation dependencies or compliance risk from cross-language template coupling.
