Implement

What the activity covers

Implementation is the fieldwork: interviews, document review, observation and assessment, with the evidence cited against each rating and the interpretation checked where behaviour is judged.

What a working implement step looks like

Implementation produces the file an auditor or a later evaluator reads. Keep the rating sheet, the evidence cited, the interview notes and the list of documents reviewed, with the period each covers. Where a rater could not obtain evidence, record that as a finding rather than filling the gap with an assumption; the model treats uncertainty as information, not as a failure.

The artefact this activity leaves

• The rating sheet per dimension and aspect, with evidence cited.
• Interview notes or confirmations for behaviour ratings.
• The list of documents reviewed and the period they cover.
• A log of anything the design did not cover, with the reason.

What goes wrong

Fieldwork that records only the documents and never the behaviour produces a rating that overstates maturity.

Who owns it in a group

The controller's governing body owns the programme, but the activity has to reach every entity in the boundary. For implement, record which board or committee took the decision, which entities were included, and where an entity's own view differed. A programme that runs only at group level produces a group result that the entity boards do not recognise. Where an entity is excluded, record why: a recent acquisition, a joint venture with reserved matters or a board that has asked to be treated separately. An exclusion that is written down is a scope decision; an exclusion that is silent is a defect in the evaluation.

Where it sits

• All five activities
• The three aspects
• The six-point scale
• All 35 requirements