Docs

Appearance

Implement Phase ​

Implement is where governance becomes real: controls move to executed status, evidence becomes traceable, and readiness changes are reviewable.

ScopeDefine the system and governance scope
ImplementExecute controls and attach evidence
MonitorKeep governance continuously current
AuditPrepare internal review and exports

Outcome ​

You leave this phase with:

  • prioritized requirements and controls with assigned owners
  • evidence attached to the controls that matter most
  • execution and fulfillment statuses that match what evidence supports

Time to first value: 60–120 minutes
Prerequisites: the project is scoped and frameworks are attached

Path at a glance ​

1

Prioritize the backlog

Start from the biggest gaps and highest exposure

2

Execute controls

Implement the control and record how it was done

3

Attach evidence

Link artifacts that prove execution

4

Run reviews

Use review flows so status changes are auditable

Step 1: Prioritize what matters first ​

Goal: work on the controls that move readiness the most.

Where in Modulos

  • Project → Requirements
  • Project → Controls

Do this

  • Identify requirements that are not fulfilled and map them to their key controls.
  • Prioritize controls that are high impact for your current scope and risk posture.
  • Assign Owners for execution and Reviewers for approval workflows.

You’re done when

  • the next set of controls to implement is clear, owned, and reviewable

Step 2: Execute controls and document implementation ​

Goal: implement the control in reality and capture the operational truth.

Where in Modulos

  • Project → Controls → select a control

Do this

  • Follow the control intent and guidance.
  • Use the control report fields to document what was implemented and where it lives.

You’re done when

  • the control implementation is described clearly enough to be reviewed

Step 3: Attach evidence to prove execution ​

Goal: make the work auditable by linking artifacts.

Where in Modulos

  • Project → Controls → select a control → Evidence
  • Project → Evidence

Do this

  • Attach the strongest, most specific evidence you have.
  • Prefer evidence that is durable (policy, ticket, design doc, audit log extract) and tied to the control.

You’re done when

  • a reviewer can verify execution from the linked evidence without backchannels

Step 4: Use review flows for status changes ​

Goal: turn progress into an auditable record.

Where in Modulos

  • Project → Controls for control execution statuses
  • Project → Requirements for requirement fulfillment statuses
  • Project → Reviews where review requests appear

Do this

  • Move controls to executed only when evidence supports it.
  • Mark requirements fulfilled when mapped controls are executed and correctly evidenced.
  • Use reviewers to approve changes where required by your operating model.

You’re done when

  • statuses match reality and can be defended via evidence and audit trail

Next ​

Monitor phase

Add signals and schedules so governance stays continuously current

Compliance Lead path

A role-based walkthrough for driving readiness end-to-end