Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.loopiq.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Understand the Release Compliance Dossier

​
What this does

This article explains the Release Compliance Dossier and how teams use it to support release governance and audit review. A Release Compliance Dossier is a connected evidence package for a release. It helps answer a simple question: why was this release considered ready, and what evidence supports that decision?

​
What the dossier can include

Depending on how your organization uses LoopIQ, a dossier may include:
  • release details
  • related change requests
  • linked stories, tasks, issues, and defects
  • approval history
  • release certification decisions
  • test plans, test cases, test executions, and results
  • exceptions and deviations
  • risk notes or compliance context
  • linked documents
  • integration signals from source control, CI/CD, security scanning, or observability tools
  • final readiness notes and decision history

​
Why it matters

Without a connected dossier, teams often rebuild release evidence manually from chat messages, ticket comments, spreadsheets, manual notes, and document folders. LoopIQ reduces that manual reconstruction by keeping governance context close to the work. The dossier gives compliance owners, release managers, engineering leaders, and auditors one place to review release readiness evidence.

​
Before you begin

Make sure:
  • the release exists in LoopIQ
  • related work items are linked to the release where possible
  • required test records have been created or imported
  • approval policies are configured if your process requires them
  • exceptions or deviations are recorded when standards are not fully met

​
How to use the dossier

  1. Open the release or release certification record.
  2. Review the linked work items.
  3. Confirm change requests and approvals are present.
  4. Review test evidence and quality signals.
  5. Review open exceptions, deviations, or known risks.
  6. Add missing evidence or comments.
  7. Use the dossier during release review or audit preparation.

​
Good dossier hygiene

  • Link work items to the correct release early.
  • Avoid using comments as the only source of evidence when a structured field or linked record exists.
  • Keep exceptions and deviations explicit.
  • Confirm test results are complete before approving release readiness.
  • Use automation rules to request approvals or enforce required fields.