You already do the work. DullDocs proves it, and prints the report you hand the inspector.
The evidence exists. It is also in a filing cabinet, three email threads, a shared drive and a photo on somebody’s phone.
We have watched good managers lose a weekend to a filing cabinet. The villain here is not Ofsted. It is the scramble.
DullDocs is how you skip it.
Point DullDocs at your documents. It builds your checklist and scores where you stand. No card, no call.
A weekly to-do list, not a wall of red. Staff upload from a phone. Reminders start ninety days before anything expires.
One click, one inspector-ready report, every requirement cited to its source. Print it, or share a link.
One nursery, one scan, one report. No slides, no salesperson, no jargon.
Every document the EYFS framework expects, tailored to your setting, each with a live status.
Upload, photograph, email to your own private address, or import from Google Drive and OneDrive.
DBS, right to work, references and training, per person, in the statutory layout. Generated from your evidence, so it cannot drift.
Policies signed and declarations completed on a phone, by secure link. No staff accounts, ever.
Nudges from ninety days out, folded into one daily email. Never sixty-seven emails.
Unlimited reports, cited to statute. When the call comes, one button freezes your evidence pack.
Share a report with an inspector, a lender or a landlord and staff evidence detail is redacted automatically. Hover a bar to see what a senior role sees.
AI reads your documents. It never decides whether you are compliant. Anything uncertain waits for your confirmation, and the scoring model is public.
Read the methodology →A weekend rebuilding folders. A gap you find at the same moment the inspector does. A record you only hope is current.
One button. One snapshot. One evidence pack. You spend the morning with the inspector, not the filing cabinet.
Dull is what you want from compliance paperwork. Nothing expired. Nothing missing. Nothing surprising.
Dull on the outside, dependable on the inside.
“We don’t make your documents exciting. We make them handled.”
The scoring model is published. The sample report is public. The phrases we are not allowed to use are enforced by our own tests. Judge the name on that.
Everything is included on every rung. The first two hundred nurseries keep their price for as long as they stay a customer, even if they cancel and come back.
Single setting, five users. Running more than one nursery? Talk to us.
Registered early-years providers are inspected within a set window of registration and then on a recurring cycle, with the exact timing at Ofsted's discretion. The date is never in your control, so the only real preparation is being ready continuously.
It is the single list of vetting checks held for everyone working with children: DBS, identity, right to work, qualifications, references and prohibition checks. DullDocs generates it in the statutory column layout from evidence you already track, and exports it as CSV.
No, and we will not claim otherwise. DullDocs tracks evidence and produces an evidence-readiness score with a published methodology. It does not certify compliance and does not predict an inspection outcome.
No. Classification is deterministic first, with AI consulted only where the rules are uncertain, and an AI-read date never counts until a second independent reading agrees or you confirm it. Emailed documents always pass through your review queue.
Never. Policy sign-offs, declarations and uploads all run on secure expiring links sent by email and opened on a phone, with a per-person audit trail.
No. Every due email for one person folds into a single daily digest, plus an optional Monday summary for owners.
DullDocs does not ask for, structure or store per-child records. Registers such as attendance, medication and accident books are confirmed by manager attestation, which records that the register is kept and where, never its contents.
Because dull is what you want from compliance paperwork: nothing expired, nothing missing, nothing surprising. The published scoring methodology, the public sample report and the language rules enforced in our own code are how we back it up.
If the scan says you’re fine, that is a good afternoon. If it doesn’t, you found out before the inspector did.