Compliance tracking

Download Markdown ↓

Inputs and purpose

Use this workflow to prepare: Readiness tracker, gaps and evidence collection plan.

Start with: Company-approved requirements, controls and evidence inventory.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

Procedure

  1. Use the requirements supplied or approved for this business, including their applicability and effective dates. An unavailable requirement remains unknown.

  2. Map each requirement to the process owner, control activity, evidence and review frequency. Separate documented design from demonstrated operation.

  3. Rank missing or stale evidence by consequence and deadline. Assign practical corrective actions and verification owners.

  4. Return a readiness tracker with evidence references. Check that a completed document is not presented as proof of compliance in practice.

Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Identify issues earlier and prepare consistent reviews.

Possible success measures: Review turnaround, unresolved exceptions, evidence completeness. Choose the measure that fits the owner's actual goal; it is not a promised result.

Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the input guide, calculation reference or output template. For tool setup, use the shared instructions.

Plain-text instructions