Home › Platform › Pre-mapped Control Library

Platform · Run the audit

Pre-mapped Control Library: audit controls ready for every framework

In shortThe QULDEX Pre-mapped Control Library is a set of audit controls, clauses and evidence templates already structured for each framework and mapped to each other. Teams start an audit from a ready baseline rather than rebuilding it, keep one governed version across clients or business units, and update it once when a framework changes.

Why does setting up controls delay an audit?

1Teams spend days rebuilding clauses, controls, and templates before fieldwork starts.
2Manually maintained control sets drift across clients and business units.
3Framework revisions trigger costly rework when baseline structures are inconsistent.

What does the Pre-mapped Control Library include?

Controls already mapped across frameworks.

01

Pre-built control structures

Use framework-ready IDs, domains, and evidence templates from day one.

02

Cross-framework control linking

Align one control library with many standard obligations.

03

Managed framework updates

Keep libraries current as standards evolve without starting over.

What changes with the Pre-mapped Control Library?

Without it

  • Control IDs and evidence templates are built manually.
  • Cross-framework alignment is hard to maintain.
  • Version updates require ad hoc migration work.

With the Pre-mapped Control Library

  • Framework-ready structures are available on day one.
  • Control mappings and attributes stay centrally governed.
  • Revision updates roll out through managed updates.

How does the Pre-mapped Control Library work, step by step?

  1. Framework Owner

    Select framework baseline

    Start from ISO, SOC 2, NIST, or privacy baseline structures.

  2. GRC Lead

    Review domains and attributes

    Validate ownership, severity, and evidence expectations before launch.

  3. Program Architect

    Publish mapped control sets

    Deploy governed control libraries into active audit workspaces.

  4. Platform Admin

    Apply framework revisions

    Version updates without re-creating the full control model.

Roles shown are a typical setup; owners and approvers are configured per organisation.

Where does it fit in the eight audit phases?

The Pre-mapped Control Library is used most in Planning and Fieldwork.

01PlanningUsed here
02Risk
03FieldworkUsed here
04Findings
05CAPA
06Best Practices
07Reports
08Closure

See all eight phases in the Audit Workspace →

Which controls are built in?

Safeguards that apply every time, without anyone having to remember them.

Governed control versioning

Each control revision is versioned with author and reviewer context.

Template integrity controls

Evidence and test templates are managed centrally to prevent local drift.

Role-scoped catalog edits

Only authorized roles can alter baseline controls and mapping logic.

Pre-mapped Control Library: common questions

What is a pre-mapped control library?

A library of controls where each control is already linked to the clauses it satisfies in several frameworks, so the mapping does not have to be built by hand.

Can we add our own controls?

Yes. The live plan lists custom control attributes and custom control libraries alongside the pre-mapped set.

Can we track audit stages and approvals?

Yes. Stage transitions and approvals are tracked with timestamps and user accountability.

Do you support evidence-to-control linking?

Yes. Evidence can be mapped to controls and findings so reviewers can check relevance quickly.

Does the platform support role-based workflows?

Yes. Workflows can be configured for audit leads, reviewers, control owners and stakeholders.

Related

See the Pre-mapped Control Library on your own audit

A 30-minute walkthrough on your frameworks, with a specialist who fits your role.

Book a Demo