Skip to main content
Institute of Advanced Technological and Commercial Studies

Employers

The same level of training across every site

A distributed organisation faces a requirement that is simple to state and hard to hold: the same employee, at head office or in the regions, receives the same training and leaves the same record. This page describes how that consistency is built, and how reporting consolidates site by site.

What stays identical, what adapts locally

Consistency covers what is assessed; adaptation covers what is illustrated. That boundary is the only one that scales: it lets a site lead anchor an example in local reality without an inspection finding two different standards.

Identical everywhere

  • Learning objectives and the competencies assessed
  • The supervised hours of each module
  • The assessment and the pass threshold applied
  • The document awarded and how it is verified
  • The format of the export produced for an inspection

Adapted to the site

  • Examples and scenarios, drawn from the local field
  • The session calendar, set to the site's activity
  • The working language of induction materials
  • The local lead who answers questions
  • The equipment named, where it differs from site to site

How reporting consolidates

The dashboard reads at the level that serves you and only that: a regional director sees their sites, a site manager sees their departments, a team leader sees their team. Consolidation rolls up automatically, which removes re-keying and the discrepancy between two versions of the same figure.

  1. 01

    The person

    Their pathway, results and deadlines. The base grain, and the only one that yields named evidence.

  2. 02

    The department

    A team's progress, visible to its direct manager without going through human resources.

  3. 03

    The site

    All departments together, with contracting firms if they are tracked. This is the grain of an on-site audit.

  4. 04

    The organisation

    The consolidated statement, dated, exportable as is into an execution report or a board file.

What geographic spread actually changes

Each with its own obligations: they decide the common content, not geography.

sectors documented
4

Safety, digital hygiene and team practice: the three fields a distributed rollout opens first.

modules in the multi-site common core
173

Those that best absorb an activity gap between two sites.

self-paced programmes
8

Questions from distributed organisations

Our regional sites have an irregular connection.

Content downloads and runs offline; results sync when the signal returns, keeping their original timestamps. This constraint is handled by design: modules are built phone-first, which makes them light before it makes them portable.

How is the same standard held everywhere?

Through the assessment, which is identical and marked against the same threshold, whatever the site. Content may illustrate locally; the test does not vary. That is what an inspection checks: two people holding the same document passed the same test.

Can we roll out in waves, site after site?

It is the recommended rollout. A pilot site gives the measure of actual time, questions raised and window adjustments. Subsequent sites start with those settings, and their opening then takes days rather than weeks.

Can a site manager add a local module?

Yes, within their perimeter and following the approval circuit you have set. A local module stacks on top of the common core, and the export always distinguishes what belongs to the shared requirement from what belongs to the site's own initiative.

The same level of training across every site — Employers | IHETC — IHETC