Implementation Control

Implementation Control Brief

A fixed-scope brief for a specific AI workflow, defining what an internal team, current IT provider, software vendor, or AI implementation partner must satisfy before build begins.

This is not implementation, vendor project management, tool resale, or a guarantee that a selected vendor can implement the workflow.

AUD 12,500 to 18,000 · 1 to 2 weeks

Start the intake Compare interventions View sample output Download PDF
Problem

What problem this solves

Most AI implementation failures begin before build. A loose brief produces a loose system, weak acceptance criteria, unclear human review, poor audit evidence, and no reliable way for the buyer to judge whether the delivered system is fit for controlled use.

The Implementation Control Brief is the control layer that makes implementation specific, testable, and governable before money and time are committed.

Definition

What the brief defines

01

Workflow boundary

02

Business owner

03

Source documents or systems

04

Data sensitivity

05

Required outputs

06

Human review points

07

Evaluation criteria

08

Acceptance thresholds

09

Audit requirements

10

Security constraints

11

Exception handling

12

Handover expectations

13

Production-readiness gates

Output

What the client receives

The client receives a controlled implementation brief that a builder can respond to and the buyer can hold them to. It is written for business ownership, technical delivery, risk review, and acceptance testing.

It does not select a tool, sell a tool, configure a tool, manage the vendor, or deliver the implementation. It gives the organisation the conditions a chosen builder must satisfy.

When to choose it

  • The organisation knows the workflow it wants to pursue.
  • The question is what an internal team, current IT provider, software vendor, or specialist AI implementation partner must build, prove, log, review, and hand over.
  • The buyer needs acceptance criteria before implementation spend is committed.

When not to choose it

  • If the organisation still does not know which workflow matters, start with the Baseline.
  • If document reliability is uncertain, resolve that first with a Document Structure Review.
  • If the organisation is preparing for board-level scale and capital governance, use the 4-Week Structural AI Architecture Sprint.
Pathway

Where it sits in the Lumen & Lever pathway

The Implementation Control Brief sits after a viable workflow has been identified and before implementation begins.

A Baseline may surface the workflow. A Document Structure Review may confirm whether the source material can support it. The Implementation Control Brief then defines the conditions the chosen builder must satisfy. After a workflow is live, a Quarterly Control Review checks whether the system remains within the conditions under which it was approved.

Sample Output

A sample Implementation Control Brief is available for review. The sample uses an anonymised fictional client and illustrates the structure, evaluation criteria, audit requirements, and acceptance gates of an actual brief.

The sample output is available as both a viewable HTML page and a downloadable PDF. No gating, no signup wall, no analytics eventing.

View sample output Download PDF
Next Step

Brief the builder before build begins

The intake confirms whether the workflow is ready for an Implementation Control Brief or whether an earlier intervention should come first.

Start the intake