Skip to content

Contact

This form posts a message to the server. It is the only part of this site that sends anything anywhere — the validator does not use it, and no register is ever attached to it. What follows is what to put in the message so the reply is worth reading.

Do not send a register through this form

This form accepts an email address and a message. It cannot accept a file — there is no attachment field, and the endpoint behind it rejects anything that is not those two values. That is a deliberate boundary rather than a missing feature: no server here ever receives register data.

If you want a register checked before you file, the free checker reads it in your own browser and uploads nothing. During an engagement, contract and register files are exchanged under a signed non-disclosure agreement, and never through this page.

Or write directly

contact@doravalidation.com

If you would rather use your own mail client — to keep the thread, to copy a colleague, or because a form is the wrong shape for the question — this address reaches the same person. It wants the same things: the three facts a scoping enquiry turns on, or the error code and the message text if a filing came back rejected.

One limit applies harder here than it does to the form, because email will not stop you the way the form does: do not attach a register or a contract. There is no attachment field above for a reason, and an attachment sent to this address lands in a mailbox — which is the thing the rest of this site is built to avoid. During an engagement those files move under a signed non-disclosure agreement. Before one, they do not need to move at all.

What should a scoping enquiry include?

How many entities you file for, roughly how many ICT contractual arrangements each one holds, and which authority you file with.

Those three facts are enough to answer with a figure rather than a range. The rate is per contractual arrangement and the count is cumulative across a group, so the total number of arrangements is what moves the price — not the number of entities, which is why twenty funds sharing six providers do not cost twenty times one fund.

If you do not know the arrangement count yet, say so. Establishing it is the first work of the engagement rather than a precondition of it, and an estimate to the nearest ten is enough to quote against.

What should an enquiry about a rejected register include?

The error code and the message text, exactly as they were returned to you.

A code such as ICTO004 names a specific defect, and the fix follows from the code rather than from a description of it. Paste the string verbatim rather than paraphrasing: the wording separates cases the code alone does not, and it is the thing that can be matched against published guidance.

If what came back is a table of data quality findings rather than a single rejection code, say roughly how many rows it runs to. That is the difference between an afternoon and a week, and it is the question that would otherwise be the first reply.

What happens to what you send?

Your email address and your message reach a server. Nothing else on this site does.

There is no analytics, no tag manager and no third-party script anywhere on this site, so sending this form is the only network request that carries anything you typed. The privacy page states what is stored, what is not, and what is still to be published about it.

There is no newsletter and no automated sequence behind this form. A message is read and answered, or it is not; nothing else happens to it.