• Record each discipline's standard: Capture all six business units' competence expectations in a structured master, so the standard is explicit rather than remembered.
• Support confirmation with evidence: Give the confirmation decision a documented capability record to draw on, built up across the year rather than assembled at the end.
• Keep grading outside discretion: Compute grades automatically from captured inputs, so the assessment measures capability rather than the reporting relationship.
• Require two perspectives: Capture input from both the reporting manager, who sees the work, and the business head, who holds the discipline standard.
• Prevent standards drifting apart: Hold one master task definition with business-unit views, so a change is made once and applies everywhere.
• Deliver the full platform: Implement core HR, performance management, recruitment and payroll alongside the learning framework.

• A standard that is written down: Each of the six disciplines now holds its first-year expectations in a structured master task list rather than in the experience of individual senior staff. New cohorts are assessed against the same standard as the ones before them.
• Confirmation supported by a record: The confirmation conversation draws on a graded capability record built across the year, which changes it from a judgement formed at the end into a review of something both parties have been able to see throughout.
• Development visible while it can still be acted on: Capability gaps surface during the window rather than at the review date, which gives the business the option of addressing them while the engineer is still building — and shortens the path to client deployment.
• Grading that holds its meaning: Grades compute from captured inputs with two required perspectives, so the assessment stays a measure of capability rather than of the reporting relationship.
• One definition, six views: A task definition changes in one place and applies across every business unit, which keeps the disciplines aligned without requiring them to be identical.
• Sustained engagement across a full year: Making the running grade visible to the new joiner moved the prompt for weekly submission to the person being assessed, which is what carried the framework through a complete cohort.

• Competency framework design translated into a working HR instrument: Task architecture, weighting, grade bands and automated computation.
• Multi-business-unit form architecture: Multi-business-unit form architecture: one master definition with unit-specific views, keeping disciplines aligned without flattening them.
• Long-horizon engagement design: Sustaining structured input across 52 weeks through participant visibility rather than administrative chasing.
• Validation against historical outcomes: Validation against historical outcomes as an adoption technique, securing stakeholder commitment before go-live.
• Distributed enablement: Distributed enablement for a site-deployed workforce, using business unit champions in place of central support.
• Probation automation: Probation automation across confirmation, extension and non-confirmation with letter generation.

This engagement deepened Interloop's capability in competency architecture — designing assessment instruments that live inside the HR platform rather than in a separate learning system, where they become part of the operating rhythm instead of another tool to maintain.

In a consultancy, capability is the product. It deserves to be built deliberately.