Know what you have
See the documents, versions and owners that make up your governance library.
Policy Vault · Governance that stays current
Every policy.A clear commitment.
Know what is approved, where coverage is missing and who needs to act. Policy Vault connects your governance inventory to review, publication and attestation, so the policy stays connected to the people responsible for it.
Built for your institution. Shaped around your data.
DocumentsObligationsAttestation
A question worth askingEXAMPLE
Which procurement document still needs an owner?
An organised library makes the next responsibility obvious.
See what is missing
Connect obligations to the documents that address them and the gaps that need attention.
Carry the commitment through
Keep approval, publication, attestation and the next review in one accountable lifecycle.
SEE IT IN ACTION
Make the policy useful beyond publication.
Follow the work from an organised inventory to a commitment people have acknowledged.
01 / 03
Give every document a clear place.
Find ownership and version gaps before they become unanswered governance questions.
- Classify policies, standards and procedures in one inventory.
- Make missing owners and unclear document status visible.
Interactive example with fictional data. The product’s configuration and interface may differ.
Governance workspace Example workspace
GOVERNANCE REVIEW
Which procurement document still needs an owner?
The third-party review procedure has no assigned owner. The supplier onboarding policy already has an accountable owner and a current approved version. Assign the procedure owner before starting its next review.
An organised library makes the next responsibility obvious.
THE CONTEXT BEHIND THE ANSWER3 example records
Document inventory
Third-party review procedure · Owner missing
Fictional record for this example. Policy register
Supplier onboarding policy · Procurement owner assigned
Fictional record for this example. Version record
Supplier onboarding policy · Approved version 2
Fictional record for this example.02 / 03
Turn the gap into a piece of work.
Connect an internal requirement to the document evidence and the action needed to complete it.
- Review the document map against a defined requirement.
- Give an uncovered commitment an owner and a response.
Interactive example with fictional data. The product’s configuration and interface may differ.
Governance workspace Example workspace
GOVERNANCE REVIEW
Where is our supplier-review coverage incomplete?
The policy requires an annual supplier review, but the procedure does not define its schedule or accountable owner. That gap needs a procedure update and review before the documentation can be considered complete.
A coverage finding points to a specific change.
THE CONTEXT BEHIND THE ANSWER3 example records
Supplier policy
Annual supplier review required
Fictional record for this example. Review procedure
Schedule and accountable owner not defined
Fictional record for this example. Coverage finding
Procedure update required · Open
Fictional record for this example.03 / 03
Follow the commitment after approval.
See the difference between a published policy and a completed acknowledgement process.
- Keep the approved version connected to its intended audience.
- Follow open attestations through the responsible owner.
Interactive example with fictional data. The product’s configuration and interface may differ.
Governance workspace Example workspace
GOVERNANCE REVIEW
Is the revised access policy ready to close?
Version 3 is approved and published. Manager acknowledgements are still pending, and the policy owner’s follow-up action remains open. Complete that attestation step before closing the review cycle.
Publication is visible. So is the work that follows.
THE CONTEXT BEHIND THE ANSWER3 example records
Version history
Access policy version 3 · Approved and published
Fictional record for this example. Attestation record
Managers · Acknowledgement pending
Fictional record for this example. Review action
Policy owner follow-up · Open
Fictional record for this example.THE CAPABILITIES BEHIND IT
Turn the policy library into a governance record.
See the documents you hold, the obligations they address and the work needed to close a gap. Keep the approved commitment, its owner and its lifecycle in one place.
BUILT AROUND YOUR TEAM
Policy owners, compliance teams, governance functions and accountable business leaders.
01Create the governance inventory
Organise policies, standards and procedures by document type, owner, status and review cycle. Establish a clear view of what exists before deciding what needs revision or creation.
02Map documents and obligations
Connect governance documents to the obligations and institutional areas they support. Inspect the document map to understand relationships, overlapping material and commitments that need a clear owner.
03Identify gaps and coverage
Assess where the inventory leaves a requirement or governance area without adequate documentation. Record gap findings with the context an owner needs to develop a response.
04See readiness in context
Use coverage and readiness views to focus review and remediation. Keep the scope, criteria and outstanding findings visible so a summary can be traced to the underlying assessment.
05Control the document lifecycle
Move from draft to review, approval and publication with explicit responsibilities. Distinguish proposed wording from the approved version and retain the decisions behind a change.
06Publish, attest and revisit
Make approved commitments available through the defined publishing process. Include attestation responsibilities and follow-up in the lifecycle, with review triggers that keep the library current.
From governance inventory to approved commitment.Explore the process
Inventory and classify
Collect the governance documents in scope. Confirm their type, current status, owners and relationships to the institution’s processes.
Map the coverage
Review relevant obligations and connect them to the document map. Identify missing coverage and material that needs further assessment.
Draft the response
Assign a policy owner to address a gap or change. Develop the proposed document with the relevant requirements and supporting context.
Review and approve
Resolve reviewer comments and obtain the required approval. Preserve the distinction between proposed changes and the accepted commitment.
Publish and attest
Release the approved version through the agreed process and assign the relevant attestation responsibilities.
Monitor and revisit
Follow outstanding actions, review dates and changes that affect the document. Keep the inventory and coverage picture aligned with the current policy set.
YOUR DATA. YOUR DECISIONS.
Built around your governance responsibilities.
Use your document hierarchy, approval authority and review cycles as the foundation. Keep the process understandable to owners and readers alike.
Explore the Aliph approachYour document model
Organise the library around your policies, standards and procedures, preserving the versions and relationships that matter.
Your approval path
Define who drafts, reviews, approves and attests, including reassignment and the handling of rejected changes.
Your assessment criteria
Review coverage against the requirements your specialists determine apply, with findings that explain the work still needed.
Plan your first implementation
Establish the document map
Bring the inventory and representative documents, including drafts and superseded versions. Define document types, ownership and the institutional areas in scope.
Agree assessment and authority
Confirm applicable obligations through specialist review. Define coverage criteria, gap categories, approval responsibilities and the rules for publication and attestation.
Connect the ongoing process
Prepare the migration and access model, then test a complete policy lifecycle. Establish how findings, actions and related GRC records remain connected as documents change.
What to evaluate. Check inventory completeness, document classification and the reasoning behind coverage findings. Test the full draft-to-attestation lifecycle, including rejected changes, reassignment and a policy update triggered by a new requirement.
A LITTLE MORE CONTEXT
Make your next
decision an informed one.
Your questions, answered.
How is Policy Vault different from a document repository?
A repository stores files. Policy Vault connects the governance inventory to classification, ownership, obligation mapping, gaps, coverage and the policy lifecycle. The document sits within a process that records what needs attention and who approves the commitment.
What do the coverage and readiness views show?
They organise the assessment of documents against the requirements and governance scope selected by the institution. The result is meaningful when the criteria, mappings and outstanding findings have been reviewed and can be inspected.
Does a readiness view or regulatory label certify compliance?
No. A view or label identifies the scope of work; it is not a certification. Specialists determine applicability and assess whether documents, controls and evidence support the institution’s compliance position.
What happens after a policy is approved?
The lifecycle continues through publication, relevant attestations and future review. Owners maintain the approved version and respond to changes, findings or review triggers that require the commitment to be revisited.
How does it connect to the GRC product family?
Policy Vault supplies the record of institutional commitments. Aliph Risk & Compliance connects those commitments to risks, controls and evidence; Agentic Studio supports draft reporting; AliphChat provides a conversational route into approved information.
YOUR NEXT CHAPTER
Bring one policy that keeps getting stuck.
We’ll work through its ownership, coverage and approval path, then show how the complete review cycle can fit together.