Abivian.Book a demo
Menu

The platform / four connected chapters

Know what matters.
Move it forward.

An obligation becomes a question of evidence. A finding becomes work. Work needs people, time and follow-through.

Abivian connects that journey in one workspace.

Explore is Abivian’s conversational workspace. Ask questions with selected requirements, company evidence and saved records in view. Examine the basis, test your thinking and prepare the next step.

Understand the obligation

What is expected?

Clarity about the legal duty, without losing the detail that changes its meaning.

Start with your business

Find the relevant law.
Then define the work.

Start with your business activities, products and jurisdictions. Use that scope to identify relevant law, then work through its requirements and their applicability to your company.

  1. Business context
  2. Relevant law
  3. Requirements

A source-linked starting point for reviewing your obligations.

Keep the law close.
Make the work clearer.

See who must do what, in which circumstances. Abivian brings related legal duties together while keeping definitions, conditions and exceptions attached.

Then consider what applies to your company. If a deciding fact is missing, the answer stays Needs information, not a convenient assumption.

Why the detail makes a difference

A short summary can lose a condition that changes who must act, when or how. Follow the source words and relationships behind Abivian’s interpretation.

Understanding the duty, deciding whether it applies and assessing company evidence are different tasks. They stay distinct.

Inspect the saved legal text in Abivian

Understand your position

Where do I stand?

A view you can explain: what the evidence supports, what it does not, and what to ask next.

Know the company.
Not just the documents.

Connect the entities, activities, people and controls described in your material. Follow recorded facts back to their source rather than searching for the same answer again.

Assessment compares applicable duties with company evidence. Gap analysis makes specific findings inspectable. A missing record and a failed control are not the same thing.

Company knowledge, connected Concept illustration
Policies · procedures · records
Entities
& activities
People
& responsibilities
Controls
& evidence
Connected facts, with their source passages.

A statement in a document is not proof that a control works in practice.

View a historical assessment example
Historical Original Assessment / DORA 032Actual applicationInspect screen ↗
Actual historical Original Assessment and its retained basis.
DORA requirement 032: historical Original Assessment, captured 22 October 2026. The 0% score belongs to that saved requirement assessment.

The basis matters
more than the badge.

Historical Original Assessments remain distinct from the latest accepted results. “Not met” may mean missing evidence or a demonstrated deficiency. Those call for different next steps.

This Assessment example reviews documented evidence. Operational control checks are a separate workflow.

Assessment → Remediation → Reassessment

From finding the gap
to demonstrating the fix.

Illustrative example · monthly access review

01 / Identify the gap
“Why is this requirement only partially met?”

The policy requires monthly access reviews. The evidence does not establish that May’s review happened.

02 / Understand the basis with Explore

The policy is clear.
The review record is missing.

The policy names an owner and a monthly review. The supplied log has no review date or results. That supports a finding about missing evidence, not a conclusion that nobody did the work.

Access review policy · §4

“The Compliance Lead reviews user access monthly and records decisions and follow-up actions.”

Review log · May

Owner: Compliance Lead.
Review date: blank.
Results and next steps: blank.

Your follow-up

“What should I ask the owner for?”

A practical next step

Ask for May’s dated access-review record. If the review is outstanding, organise it and record the decisions and follow-up actions.

Take this gap into the action plan →

Build practical capacity

How do I get it done?

Turn the finding into a response. Put your time into the decisions, with help doing the work.

The same monthly access review

A clear finding. A practical response.

  1. 03 / Plan with an owner

    Make the next step someone’s work.

    In Remediation, turn the finding into a plan with practical steps, an owner, a priority and a date.

    Owner
    Compliance Lead
    Action
    Complete and document May’s access review
    Due
    7 June · high priority
  2. 04 / Do the work

    Review access.
    Record the decisions.

    The owner checks access, documents the results and assigns any follow-up actions. Use Documents to refine the review briefing, then review and export the working copy.

    See Documents in use ↓
  3. 05 / Update evidence & reassess

    Show what changed.
    Keep the rest in view.

    Bring the completed review record into the evidence for reassessment. Inspect the updated assessment and its basis to see which findings are resolved and which remain.

    Resolved, if supported

    The dated results demonstrate May’s access review.

    Still to resolve

    A flagged access removal still needs its completion record.

The action records the work. The reassessment establishes what it proves. Keep the completed task and the evidence of closure connected, but distinct.

Finding gaps should help you move forward, not leave you with hundreds of problems to sort out alone.

Not every finding needs a new process. Your organisation may already be doing the right thing without its documentation clearly expressing it. Abivian brings together its understanding of the requirements and your business to help draft missing explanations, clarify responsibilities and improve policies and procedures. You can resolve straightforward documentation gaps with Abivian’s help, rather than starting from a blank page.

Where something needs more substantial attention, Abivian helps you understand why, bring related findings together and organise clear actions. Separate the important issues from the clutter. Decide what to tackle first, involve the right people and keep sight of progress.

You stay in control of the work.

Compliance involves judgment. Abivian helps you examine interpretations, understand what genuinely applies and choose a proportionate response, informed by your obligations, business priorities and risk appetite. The aim is not to create unnecessary work or push your organisation towards over-compliance. It is to help you meet your obligations and pursue the standards you have chosen, with clarity and confidence.

Resolve what can be resolved now. Give serious issues the attention they deserve. Keep the whole process manageable.

Abivian Documents

Don’t just discuss the document.
Work on it.

Tell Explore what to change. See the edit in the Word-like editor alongside the conversation. Working documents autosave in your shared library. Review the wording, refine it yourself, save named versions and export when needed.

Three requests. Three visible changes.Illustrative example · three document edits

Change 3 of 3 · Review cycle

Review Cycle: Quarterly

Policy template.docxIllustrative working copy
Document
Policy cover with the title Access Review Policy, Document Owner set to Compliance Lead, and Review Cycle set to Quarterly. Quarterly is selected.
Review Cycle updated · review the highlighted field
ExploreIllustrative example
Conversation
You

Set the cover table’s Review Cycle to Quarterly. Keep the approval fields unchanged.

Explore

Set Review Cycle to Quarterly. Approval fields remain unchanged.

Visible in the document

Review Cycle → Quarterly

The current change is highlighted.
Thinking: HighCurrent document
Describe the next change…
Review, refine and export your copy
  1. 01Change the cover title
  2. 02Name the owner
  3. 03Set the review cycle
Illustrative example: a scripted conversation with three document edits. Review the sample wording and policy fields.

Illustration complete. Review, refine and export the working document.

Read all three requests and inspect each edit

1. Change the cover title

YouChange the cover title from Access Control Policy to Access Review Policy. Leave the policy text unchanged.

The visible editAccess Control Policy → Access Review Policy. The policy body stays unchanged.

Access Review Policy selected as the updated cover title.Inspect title change ↗

2. Name the document owner

YouIn the cover table, replace the Document Owner placeholder with Compliance Lead.

The visible editDocument Owner: [Enter document owner name and title] → Compliance Lead.

Compliance Lead selected in the Document Owner table cell.Inspect owner change ↗

3. Set the review cycle

YouSet the cover table’s Review Cycle to Quarterly. Keep the approval fields unchanged.

The visible editReview Cycle: an unfilled frequency placeholder → Quarterly. Approval fields stay unchanged.

Quarterly selected in the Review Cycle table cell.Inspect review-cycle change ↗

Send your request → see the edit in your working document → review and refine it. Working documents autosave in the shared library; save named versions and export when needed.

The change, where you need it.

Ask for a tighter paragraph, a clearer responsibility or a new section. The requested edit appears in the document, not just as a suggestion to copy and paste.

Draft, refine and build on your work.

Review and edit the saved working document. Keep document approval and evidence of work in practice distinct from drafting. Original case evidence stays separate.

Keep the whole job in view

How do I keep it alive?

The work between the milestones deserves a place of its own.

Controls

Put your controls
to the test.

Abivian derives testable controls from your regulatory requirements and checks the operational material you supply against them. Review PASS or NOT PASS results, with each control connected to its regulatory source.

From the control to the check Workflow illustration
The expectation

Source-linked control

The requirement and its regulatory basis.

The material you supply

Operational data

For example, logs, code, policies or contracts.

Verification

Check the material
against the control.

The result to review
PASS
or
NOT PASS

Decide what needs attention.

Control API

Connect checks to your operational workflows.

Your systems can submit operational data to Abivian for verification against controls. Bring checks into the workflow where the work happens, without moving each record by hand.

The consolidated compliance Calendar

Make room for
what needs to happen.

Bring reviews, evidence requests and meetings across the cases you can access into one view. Filter by case, people, type or status. See what is competing for the same hours.

Calendar / people, cases and working appointmentsActual applicationInspect screen ↗
Actual consolidated Calendar detail with discovery, filters and demonstration review and evidence appointments.
Calendar with demonstration appointments, captured 24 October 2026. Mobile detail: 20 October; inspect the full month.

One working picture.

Shared and private events across cases you can access.

Plan from your sources.

Create appointments; review source-derived candidates and suggested changes before accepting them.

Follow the work through.

Track appointments alongside the evidence of completed work.

Reporting

Explain where you stand.

Use Explore to reason and draft. A saved report setup combines its instructions, called a Skill, with an optional writing Style and document Template. Use that setup to draft and refine your report in Documents.

Audit trail / retained work

Be ready for “show me why”.

Follow saved document history, requirement history and activity. Keep the evidence, the assessment basis and management decisions distinguishable.

See Explore beside saved legal text
Explore / a conversation with the case in viewActual applicationInspect screen ↗
Actual Explore response beside a separate saved legal-text pane.
Explore alongside a separately opened Article 11 legal-text reader. Application capture, 24 October 2026.

MCP server · Claude and ChatGPT connectors

Use Abivian from the assistant you already use.

Bring authorised Abivian records into a conversation in Claude or ChatGPT. Prepare for a review without copying the case between tools.

Explore integrations →
Saved in Abivian

Requirements · applicability · assessments · gaps · remediation plans

In Claude or ChatGPT

“Which gaps remain open for this requirement?”

Abivian offers an MCP server and connectors for Claude and ChatGPT. The connectors provide read-only access to your authorised Abivian records.

A basis you can examine

Follow the reasoning.
Not just the answer.

See the sources, company evidence and basis behind a conclusion. Keep unresolved questions visible, so you can judge what the answer supports and what still needs review.

How the reasoning works →

Understanding. Capacity. Action.

Your next move.
With more behind it.

Bring one question from your working day. See how Abivian connects the understanding and the work around it.

Application detail

Retained application screenshot. Its date and context are in the page caption.