Implementation and Validation

A finding is not a fix.

Putting an agreed change into practice, then finding out whether it reached the people doing the job.

Request a consultation

Why this is a separate engagement

Departments rarely fail at knowing what to fix.

They fail at the eighteen months afterwards, when the report is in a drawer, three of the twelve items got done, and nobody can say which three.

Two halves

Getting it done, and finding out whether it got done.

These are different pieces of work and a department can buy either without the other. A system put in place two years ago can be validated without Northline having implemented it. A change that will never be exercised can still be implemented properly.

Implement

Getting the Change Into Practice

  • Implementation planning

    Sequencing the work: what happens first, what has to be true before each step, who owns it, and what the department can realistically absorb alongside running calls.

  • Rollout of new systems and processes

    Getting a designed system into operation. Briefing the people who will run it, working through what breaks on contact, and adjusting rather than defending the design.

  • Procedure and guideline revision

    Turning an agreed revision list into revised documents the department can put through its own adoption process. Northline drafts and recommends; the department adopts and owns.

  • Corrective action tracking

    A register of what was agreed, who holds it, and where each item stands.

Validate

Finding Out Whether It Reached the Job

  • Exercises

    Designed against a scenario the department is exposed to, run with the partners it would rely on, with stated objectives and findings recorded against them.

  • Operational validation

    Checking whether a change reached practice: whether the people doing the work know about it, are trained in it, and are doing it when nobody is watching for an exercise.

  • After action review

    Structured review after an exercise or a real incident, focused on what the systems did rather than on individuals, with findings that carry owners and dates.

  • Reassessment

    Re running the original assessment against the baseline recorded at the time, so movement can be shown per area rather than asserted. Improvements and declines are both reported.

Reassessment

Measuring against the same ground.

Where a Department Readiness Assessment has been done, the report records the basis it was made on. A reassessment works from that basis, so what is reported is movement rather than a second set of observations that may or may not be comparable.

It is faster and cheaper than the original, because the profile, the document set and the department's own context already exist.

What a Reassessment Reports

  • What improved, by area, and what the evidence for that is.
  • What did not move, stated as plainly as what did.
  • What declined. Reported as prominently as improvement, because a report that only ever finds progress is not measuring anything.
  • Priority issues from the original assessment, and whether each one is closed on evidence rather than on assurance.
  • Anything new since the baseline.

Afterwards

Ongoing advisory support and an annual review.

Where Northline has delivered an engagement, an ongoing advisory arrangement can follow it: standing access for the questions that come up between projects, and an annual review of what has changed. It is a continuation of delivered work rather than a product, and it is arranged with departments Northline has already worked with.

There is nothing to buy here today. If it is relevant, it comes up after an engagement, not before one.

Scope of This Work

Northline plans, supports, drafts and evaluates. The department adopts, operates and remains the authority over its own systems and procedures.

An exercise or a validation activity confers no certification, accreditation or regulatory approval, and is not a determination of compliance with any requirement. It reports what was observed against the objectives that were set for it.

Equipment testing, legal opinion and occupational health and safety program work sit outside this scope. Where the work identifies one, it says so and names the kind of specialist required.

Scope, exclusions and what each side provides are set out in writing before work begins.

Next step

Bring the plan that stalled.

An existing report, an agreed action list, or a system that went in and never quite took. The conversation starts from what already exists rather than from a blank page.