Details live in the wrong places
A client’s tax number is in an email, their address is in a signed PDF, their date of birth is in a scan of a passport. Every form is a small archaeology exercise before it is a form.
For teams and professionals
Forms you fill for other people
Filling a form for yourself is a task. Filling forty of them for clients is a process, and the difference is not volume. It is that the details are not yours to remember, the documents are not yours to hold casually, and somebody will eventually ask you to show what you submitted.
One library the whole team shares
Per-document history of every change
Nothing filed on anyone’s behalf
The actual problem
The same form, forty times, with different people in it
The work is not hard. It is repetitive in a way that makes mistakes statistically inevitable and unevenly distributed across whoever happened to do it that day.
Everyone does it slightly differently
Two people on the same team fill the same field two ways. Neither is wrong; only one matches what the authority expects, and you find out which at rejection.
Rejections arrive weeks later
By the time a form comes back, the person who filled it is on something else and nobody remembers what was in the box or why.
You cannot prove what you sent
A copy in a shared drive is a copy of a file, not a record of who changed what and when. That distinction matters exactly once, and it matters a great deal.
Identity documents pile up
Doing this work means holding passports, payslips and tax numbers for people who are not you. Where those sit, and for how long, becomes your problem rather than theirs.
Onboarding takes a quarter
The knowledge of which box means what lives in the heads of whoever has done it longest, and leaves when they do.
HelperDoc prepares documents. It does not submit them, and it has no channel to any authority. The professional judgement, the signature and the filing stay with the person who is accountable for them — which is the only arrangement a regulated practice can actually use.
The line this product will not cross
How it works for a team
From a folder of PDFs to a repeatable process
Map the forms you use most, once
A form is read, its fields identified and its conditional sections understood a single time. Everyone who opens it afterwards gets that work for free.
Stable form keys mean two documents with the same title cannot overwrite each other, which is the failure mode that makes shared libraries untrustworthy.
Hold each person’s details once
A client’s confirmed details are stored against that person, not against a form. The next form that asks for the same thing offers the value with its source attached.
Matching is by meaning, person and address role — not by similar labels. A registered-office postcode and a home postcode are never treated as the same answer.
Fill, then review what is uncertain
Anything the system could not trace to something you supplied is left empty and flagged with a plain reason, rather than guessed at and buried.
The review screen shows the source and the confidence behind every suggested value, so checking is faster than retyping and safer than trusting.
Produce the PDF and keep the trail
The output is an ordinary PDF with the original layout intact. Every version is kept, with who changed what and when.
When a submission is questioned months later, the answer is a query rather than an archaeology exercise.
Who this is for
The work looks the same from several directions
Accountants and tax advisers
Annual returns, registrations and declarations across a client book, where the same twenty fields repeat and one wrong identifier costs a resubmission.
Relocation and immigration support
Residence, registration and healthcare paperwork for people who cannot read the form themselves, in the language they can read.
HR and people operations
Onboarding declarations, benefit enrolment and statutory forms for new staff, filled from details the employee has already confirmed once.
Legal and notarial practices
Standard-form documents where accuracy is the deliverable and the audit trail is the professional protection.
Agencies and outsourced back office
Form-filling as a service line, where margin depends on how long each document takes and how often one comes back.
Education and student services
Enrolment and funding paperwork at intake, where several hundred people need the same form explained in several different languages.
Compared with how it runs now
The Monday of a filing week
The current process
- Each person keeps their own folder of blank forms
- Client details re-gathered from email for every form
- Two colleagues fill the same field two different ways
- Uncertain values quietly guessed to finish the document
- A shared drive full of files with no change history
- New starters learn the forms by getting them wrong
With HelperDoc
- One shared library, each form read and mapped once
- Confirmed details held against the person and offered with their source
- The same mapping and the same checks, whoever is at the keyboard
- Untraceable values left empty and flagged with a reason
- Every version kept, with who changed what and when
- The knowledge is in the mapped form rather than in one person’s head
Control and accountability
What an administrator can actually see
Per-document history
Every change to every page, attributed and timestamped, including edits made directly to printed text.
Role-based access
Administrative actions sit behind their own role and a step-up check, so an ordinary account cannot reach them.
Provenance on every value
Where a suggestion came from and how confident it was, kept with the document rather than lost at submission.
Data controls
Retention rules, region-locked storage and export on request. Deleting a client deletes their documents.
Spend and throughput
Per-document processing cost and turnaround, visible without exposing the values inside the documents themselves.
No training on your data
Client documents are never used as training data. This is not a setting that can be switched on by accident.
In numbers
What you can rely on
27Languages a form can be explained in
FreeReading a form and reviewing it
EveryChange recorded with author and time
NeverUsed as training data
Questions
What teams ask before they move
Does HelperDoc submit anything for us?
No, and it is not a roadmap item. There is no channel to any authority. The product prepares the document; the submission, the signature and the professional judgement stay with you.
Can we hold client details without holding client documents?
Yes. A confirmed detail is stored against a person; the source document can be deleted independently once you have confirmed the value you needed from it.
What happens to a client’s data when we finish with them?
Deleting the client deletes their documents and their stored details. Export is available first if you need to hand a file over.
Can two people work on the same client?
Yes. The library and the person record are shared; the history records which of you made each change, which is the point of sharing them.
What if a form we use is not in the library?
Upload it and it is read on the spot. If you use it regularly it is worth having it prepared properly, and that is a conversation rather than a form.
How is this different from the Enterprise plan?
This page is the daily work. Enterprise is the commercial and security side of it: volume pricing, shared workspace administration, region-locked storage and a documented rollout. Same product underneath.
Start here
Try it on the form you fill most often
Bring the one that eats the most time. Reading it and mapping its fields costs nothing, and you will know inside ten minutes whether this fits how you work.
- Reading a form and reviewing the result cost nothing
- Five free credits, no card
- Your file is deleted after 30 days unless you keep it