The DORA Register, assembled from the data, not kept as a parallel spreadsheet.
Most firms maintain their DORA Register of Information as a spreadsheet assembled for annual reporting, usually by reading contracts and chasing owners for missing context. On this platform the Register is produced from the supplier, contract, function, and entity work your team already performs. The system recognises gaps, protects relationships, and shows what needs attention before the reporting deadline arrives.
What does DORA Register of Information software do?
DORA Register of Information software brings together information about your entities, technology providers, contracts, ICT services, and business functions, then turns it into the required regulatory register. Ariadnah produces all fifteen templates and the XBRL-CSV reporting package from the same records your team maintains during the year.
Your team works with suppliers, contracts, services, and functions in their normal context. Ariadnah uses those connections to build the Register, so there is no second workbook to keep in step.
Before filing, the platform flags missing links, incomplete assessments, and overdue reviews. Your team can fix the underlying record once and see the change reflected in the Register.
The Register is generated, not transcribed.
The common alternative is a workbook. When the annual filing cycle approaches, someone opens a template from the NCA, reads the outsourcing contracts, and copies field values across. The workbook is not the system of record for anything else. It is a reporting output that happens to hold every supplier, contract, and function the firm uses. The next filing cycle, the process repeats, because there is no link back to the underlying data.
On this platform the Register is a view. A supplier is one record. A contract references that supplier and lists the ICT services it covers. A function is an object the contract can support. The B_06.01 and B_02.02 rows are generated by walking those references, not by copying them. When a contract is amended once, the Register row that depends on it is current. A completeness audit endpoint surfaces the rows the data does not yet support, so the gaps are visible before the submission window opens.
This is the specific claim: the Register of Information is not a parallel spreadsheet on this platform. It is what the data model already says, read in the EBA DPM shape.
GRC tools store the Register. This platform generates it.
Most GRC platforms that advertise DORA support hold the Register as a dedicated table: a set of fields that mirror the B-table columns, populated by a compliance analyst. The supplier list and the Register are two datasets that happen to contain the same supplier names. Reconciliation between them is a human process.
On this platform the Register and the supplier list are the same dataset, read two ways. The supplier record carries identification, ultimate-parent chain, and framework-tagged classifications. The contract record carries governing law, service country, and data storage country. The B_06.01 junction object links a function to an entity with a full assessment. The Register rows are derived by joining these records in the shape the DPM specifies.
The practical effect is that adding a new contract updates the Register immediately. Moving a function from one supplier to another updates the Register immediately. The reconciliation step between "what the firm actually uses" and "what the Register says it uses" does not exist, because there is only one source.
The platform produces the Register. People carry the judgement.
The Register of Information is generated from the data the platform already holds: suppliers, contracts, functions, entities, and branches, with entity identifiers verified against GLEIF. All fifteen RT schema tables are produced from that data, so the Register is a view of your live third-party landscape rather than a workbook someone maintains next to it.
The submission artefact is produced in the platform: an XBRL-CSV report package with per-table exports and filing indicators, packaged for the NCA's ingestion format. The annual filing stops being a transcription exercise.
What no platform can automate away is the judgement. Deciding whether a service is substitutable, what a credible exit plan looks like, and how a contract clause maps to a B-table column are interpretation decisions. Our specialists carry those with your team, and the decisions are recorded in the platform as they are taken.
The practical questions behind this solution.
Plain answers about what the platform does today, where people still decide, and what remains outside its scope.
What data does a DORA Register of Information platform need?
It needs information about your entities and branches, technology providers, contracts, ICT services, the business functions they support, and the relevant assessments. Ariadnah keeps this information connected, so it can build the reporting tables without asking the team to enter everything again at filing time.
Does Ariadnah produce all DORA Register of Information templates?
Yes. Ariadnah produces all fifteen Register of Information templates from connected supplier, contract, service, function, entity, and branch data. It also creates the XBRL-CSV package needed for the reporting process.
How is Ariadnah different from a DORA Register spreadsheet?
A spreadsheet is another copy that the team has to maintain. Ariadnah builds the Register from the organisation's live supplier, contract, service, function, and entity records. Change the underlying information once and the Register uses that change too.
Does Ariadnah remove the need for regulatory judgement?
No. Ariadnah builds the Register and shows where information is missing. People still decide whether a service is critical or replaceable, what a credible exit plan looks like, and how a contract should be interpreted.
A discovery call, not a product demo.
You describe the compliance problem consuming the most of your team's time. We walk the platform through an example close enough to your operation that you can judge whether this way of modelling compliance fits how you want to work.
Book a discovery call →