Industry · Professional Services

CPD is evidence. Not attendance.

Structured CPD, technical uplift across the firm, and alignment to sector standards for accounting, legal, engineering, and consulting practices. One framework. Multiple bodies. Evidence per practitioner.

Archival grid of dark charcoal document blocks with orange seals and a magnifying glass, illustrating audit and evidence.
Why this matters

Practice quality reviews audit backwards from the evidence.

Professional body inspections, practice quality reviews, and internal partner committees ask the same question in different words. How do we know practitioners at this grade, in this practice, on this engagement, were competent to perform the work? A CPD hours register does not answer that question. A framework, an assessment record, and a chain of decisions about progression in grade do.

The Foundry treats professional standards, sector guidance, and firm methodology as sources of structural obligation. Frameworks encode what practitioners at each grade must know, apply, and demonstrate. Programs generate to fit. Evidence accumulates per practitioner, not per training event.

Six moves for professional services

Technical discipline across the firm, evidenced.

CPD architecture

CPD programs structured to professional body expectations (state boards of accountancy, ICAEW, CA ANZ, bar associations and law societies, engineering bodies) with hours, categories, and outcome mapping evidenced per practitioner.

Technical uplift across the firm

New methodology, new standard, or new regulation rolled out consistently across offices and grades. One framework, variants appropriate to role, evidence of coverage per practice group.

Alignment to sector standards

Alignment to sector standards (auditing standards, ethical rulings, code of conduct, technical guidelines) encoded at clause level and evidenced through instruction and assessment.

Training on client obligations

For engagements requiring evidence that staff are trained to a client's sector obligations, the framework can encode requirements specific to the client and export evidence tied to the engagement.

Progression by grade

Technical competency mapped to grade (analyst, senior, manager, partner) with progression thresholds defined at the framework level, not left to individual reviewer discretion.

Evidence for practice quality

For practice quality reviews and inspections by professional bodies, coverage, verification, and CPD evidence export in a form ready for external review, not manufactured after the notice arrives.

How it runs

From standard to evidence of progression by grade.

Structure precedes instruction. Only once your professional standards lead has approved the framework does the platform generate the material and CPD evidence that satisfies it.

STEP 01

Interpret the standard

Professional body CPD expectations, sector standards, ethical rulings, and internal methodology are ingested and parsed at clause level.

STEP 02

Structure by role and grade

Competencies and CPD obligations are tagged to specific practice roles and grades. Progression thresholds are defined per grade, not per module.

STEP 03

Construct the framework

A technical framework for the whole firm is proposed. Your professional standards lead reviews and approves before instruction, verification, and CPD evidence are generated.

STEP 04

Evidence per practitioner

CPD records, technical uplift coverage, and progression evidence by grade are exportable per practitioner, per practice group, and per engagement.

What you get out

Evidence a practice quality reviewer will accept without follow up.

Frameworks aligned to CPD from professional bodies, sector standards, and firm methodology. Programs that satisfy them, per grade, per practice, per office. Verification that survives external inspection. CPD evidence per practitioner ready for annual reporting to the professional body.

When the practice quality reviewer arrives, the artifact you present is a framework, not a defense reconstructed from an LMS.

Common questions

How professional services engagements work, in detail.

The framework can encode CPD expectations from multiple bodies concurrently: for example, state board and AICPA obligations for a US accounting practice, CA ANZ and CPA obligations in Australia, or bar association and specialist accreditation obligations for a legal practice. One program can satisfy multiple regimes, and evidence exports in the format each body expects.
The Foundry does not replace the methodology. It structures it. Your practice retains ownership of the methodology as source. The framework encodes what practitioners at each grade must know, apply, and demonstrate. Programs are generated to fit. When the methodology updates, the framework updates and downstream programs regenerate.
One approved framework can carry variants specific to an office or jurisdiction without duplicating the underlying competency model. The technical standard remains consistent. Local regulatory and market variations are inspectable branches on the framework.
Where an engagement requires evidence that the team is trained to the client's sector, standard, or system, the framework can encode requirements specific to the client. Evidence of coverage and verification exports in a form ready to attach to the engagement file.
Yes. Coverage, verification history, sign off chains, and CPD records are exportable in a coherent, versioned form suitable for practice quality review. The framework itself is the primary artifact. The evidence pack is its supporting record.
Bring a methodology

See your technical model for the whole firm take shape.

Send us your methodology, a technical guideline, or a CPD obligation your practitioners are accountable for. In 45 minutes on your material, you leave with the framework the Foundry produces.

We reply within one business day.