Enterprise DNA

Instead of ConvergePoint Conflict of Interest

Stop renting ConvergePoint Conflict of Interest. Own your disclosure system.

We build your version around your declaration rounds, bring across the agreed records and run it for you. See who owes a response and which assessments no longer match the facts.

ConvergePoint does not list a general licence price on its product page. Compare your actual renewal and agreed scope with a system built for your organisation.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

Compare your renewal

What ConvergePoint brings to the disclosure process

ConvergePoint combines disclosure collection and review inside Microsoft 365 SharePoint. Start with the parts your team uses each week, then agree what your owned version needs.

assignment

Declaration questionnaires

Custom forms collect gifts, outside roles, financial interests and relationships. Your version holds the agreed facts and original report fields.

event_repeat

Recurring disclosure rounds

Scheduled requests and reminders support repeat declarations. Your register separates a missing response from an explicit nil return.

groups

Review routing

Managers review and escalate declarations. Your version records the reviewer, their reason and the evidence behind each assessment.

task_alt

Management plans

Conflict resolutions and mitigation strategies sit alongside the disclosure. Your action owners and monitoring dates stay visible after the initial review.

query_stats

Reporting

The vendor provides reporting and oversight. Your owned version combines missing returns, changed interests and overdue actions for the next committee meeting.

shield

Microsoft 365 access

ConvergePoint provides access controls within its SharePoint product. We scope your identity connections and staff access when building your managed version.

Your records, your process

A disclosure is the start of the work

Declaration rounds

Know who still owes an answer

Open a round, record supplied responses and prepare the follow-up list.

  • check Request a declaration from each active person
  • check Record a nil response with its evidence
  • check Link declared interests to the round
  • check Show outstanding returns with their department and due date

Review evidence

Notice when the facts have changed

Each assessment records the version of the declaration it covered.

  • check Keep the reviewer and supporting evidence
  • check Reject a review by the person declaring the interest
  • check Flag amendments made after an assessment
  • check Preserve earlier decisions for the committee record

Management plans

Keep the agreed action alive

A managed interest carries a plan, a monitoring owner and a review date.

  • check Assign actions to named people
  • check Require evidence before completing an action
  • check Show monitoring dates coming up
  • check Inspect organisations named by more than one person

Committee records

Prepare the pack from the register

Produce declaration records, management plans and round summaries in your own brand.

  • check Generate documents from the recorded facts
  • check Read the weekly review as a private report
  • check Draft reminders for a person to check
  • check Flag personal records due for a retention-purpose review

Make it yours

Design your own ConvergePoint Conflict of Interest replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from ConvergePoint Conflict of Interest. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your ConvergePoint Conflict of Interest replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your ConvergePoint Conflict of Interest data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Interest Disclosures for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Interest Disclosures for Claude Code

Connected to your own database

Who still owes a declaration?

ROUND-01

Tle du
Annual interests declaration
E_on re
2026-10-23
Quested pe
5
Nding ni
4
L_returns di
0
Sclosed
1

ROUND-02

Tle du
Tender panel refresh
E_on re
2026-11-13
Quested pe
5
Nding ni
5
L_returns di
0
Sclosed
0

Ask it anything

Questions your disclosure register can answer

These questions run against the fictional demo records. Use your own review process and records when you make it yours.

chat_bubble Which declaration rounds still have outstanding returns?
chat_bubble Who has not responded, grouped by their department?
chat_bubble Which interests changed after their last assessment?
chat_bubble Which independent reviews are waiting or escalated?
chat_bubble Which mitigation actions still need evidence of completion?
chat_bubble Which management plans need monitoring in the next month?
chat_bubble Which named organisation appears in more than one person’s disclosures?
chat_bubble Who holds the most overdue monitoring reviews?
chat_bubble Which personal records need a retention-purpose review?
chat_bubble Who changed the register, and what did the record say before?

Switching

How to switch from ConvergePoint Conflict of Interest

A move usually involves agreeing which records and history to bring, mapping ConvergePoint’s report columns, then checking the imported register against the source before you switch.

  1. 1

    Agree what to export

    Decide which disclosures and related history you need to bring across. ConvergePoint documents Excel reports, but report headings are not fixed. Ask ConvergePoint what your account allows you to export, usually CSV or Excel, and which report best fits the records you have agreed to move. Plan separately for attachments, historic assessments and questionnaire responses, since they need their own mapping and checks.

  2. 2

    Prepare and load the records

    Add or import the people into the new register first. Then save the agreed report worksheet as a UTF-8 CSV and map its headings to the new register’s fields. Run the import’s test run before loading the records for real. This gives you a chance to check how the source columns will be read and correct the mapping before the records are added.

  3. 3

    Check the import results

    Review what the test run flags and resolve any issues before you proceed. Check that records are matched to the right people and fields, and reconcile the loaded register against the agreed source report. The importer keeps original columns and leaves repeated rows unchanged. Imported approvals remain source history, not a fresh review. Map and check attachments, historic assessments and questionnaire responses separately.

  4. 4

    Run both systems side by side

    Keep ConvergePoint available for a short period while you check the new register against it. Use the agreed records to confirm that disclosures and relevant history have carried across, and that your team knows where to record new information and decisions. Resolve discrepancies before treating the new register as the working record. A person needs to record a fresh assessment when an imported approval is not a current review.

  5. 5

    Switch off ConvergePoint

    Once you have reconciled the records and are ready to use the new register, stop entering new disclosures in ConvergePoint. Follow your organisation’s agreed retention and access handling for the old records before ending the service. Keep the source available as long as needed for the checks and retention approach you have agreed, rather than switching it off before the move has been reviewed.

construction

Where the real effort goes

The main work is usually mapping your own report fields and rules, then deciding how much history to bring. Attachments, historic assessments and questionnaire responses need separate mapping and checks, and imported approvals are not fresh reviews. If you have Enterprise DNA install and run the system, they do the record mapping and migration work with you, including agreeing what moves and how it will be checked.

Not ready for a call?

Get your ConvergePoint Conflict of Interest switch plan by email

We will send you the step-by-step plan for moving your business off ConvergePoint Conflict of Interest, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Start with the free version or have us build yours

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install
  2. 2 Run npm run demo with the fictional records
  3. 3 Open the folder in Claude Code, Codex, OpenCode or Cursor
  4. 4 Map your ConvergePoint report and test the import before saving it
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your disclosure fields and review rules
  • check Your ConvergePoint report mapped and checked
  • check A web front end and identity connections when agreed
  • check A different stack when it suits your organisation
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a monthly retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Your agreed history brought across and reconciled
  • check Your access, backups and retention process configured
  • check Your declaration rounds and committee reports maintained
Book a call

Questions

Instead of ConvergePoint Conflict of Interest, answered

Can you bring our ConvergePoint history across? expand_more

Yes, we agree the records first and reconcile them after migration. ConvergePoint documents Excel reports, but not a universal set of report headings. The free version imports a mapped disclosure report saved as CSV. Original columns are retained. Attachments, historic assessments and questionnaire responses need separate mapping and checks.

What happens to an approval if someone changes their disclosure? expand_more

The old assessment stays in the history. The register flags that it covered an earlier version, so the reviewer can assess the new facts. An approval written in an imported report remains source history until a person records a fresh assessment.

Can staff complete their own declarations online? expand_more

We build the forms, sign-in and review access your organisation needs into your customised version. The free version is an authorised operator’s workbench: the operator records declarations and decisions supplied by people and produces private reports.

Does this decide whether we are legally compliant? expand_more

No. It checks the recorded process: missing returns, stale assessments, overdue actions and retention-review dates. The review and monitoring pattern draws on New Zealand public-sector guidance. Your organisation sets its policy and gets appropriate advice on the rules that apply to it.

What would Enterprise DNA charge to build and run ours? expand_more

We scope one setup fee, then a retainer around your records, access and review process. Bring your current renewal and a sample report to the call. We agree what moves across, what gets built and how the result will be checked.

Bring your next declaration round to a 30-minute call

Walk Sam through your ConvergePoint renewal, one disclosure report and the decisions your committee needs to make. Agree the first working version and the records it must preserve.

Book 30 minutes with Sam Get the free version

Interest Disclosures for Claude Code is free and open source, published by Enterprise DNA.

Done paying for ConvergePoint Conflict of Interest?

Get your version built