Workflow and period
Controlled process, consequential action, and applicable time boundary.
Practitioner operating method
The Closure Method
The Closure Method turns an observed gap into an approved, testable, and sustainable standard. It is the bridge between readiness work and evidence that the control operates in the consequential workflow.
Four-phase loop
Context first. Approval before testing. Evidence before closure.
The method is intentionally practitioner-led and client-owned. The client approves the standard; the practitioner identifies gaps, supports remediation, and asks the questions that make operation testable.
1
Phase 1: Establish context and find the gap
Begin with the organization, applicable context, assurance calendar, and material workflows. Narrow to one workflow. Spot the soft answer and identify the evidence gap or control-operation gap.
2
Phase 2: Close and approve
Develop remediation with the client. Policies, standards, criteria, and controls remain proposed until approved in the client’s own system with owner, version, approval reference, and effective date.
3
Phase 3: Translate into testable criteria
Create the criteria package that defines the workflow, period, rule identifier, testable condition, authority requirement, required fields, provenance, framework mapping, and result categories.
4
Phase 4: Validate and sustain
Re-run the diagnostic against the approved standard. Where appropriate, progress to periodic review, shadow assurance, runtime governance, and ongoing exception and drift review.
The criteria package
What Pulse needs to evaluate the approved standard.
The package defines the evaluation requirement. It does not retrieve source data or replace the client systems that hold it.
Rule identifier and version
Approved standard, effective date, and ownership.
Testable condition
The precise condition Pulse or the diagnostic must evaluate.
Authority requirement
The role, delegation, approval, or pseudonymous actor token required to act.
Required fields and provenance
The evidence fields, source systems, and lineage required for the check.
Mapping and result categories
Applicable obligation mapping and the allowed result set, such as allow, escalate, or block.
Practitioner role
Do not answer for the client.
The practitioner listens for vague or soft answers, then asks the follow-ups that distinguish a control that exists on paper from a control that can be shown to operate.
- Who approved it?
- Which version was effective?
- What system records the approval?
- Which fields must exist?
- Who may override?
- How is the exception preserved?
- Can one decision be replayed?
“The client owns the answer. The practitioner owns the discipline of making the answer testable.”Pulse Governance operating principle
Close the gap, then prove the closure.
Scope one workflow where the approved standard and actual execution need to be connected.