Nothing gets filed because somebody assumed it was fine
A disclosure is a statement your company is legally standing behind. The question an auditor asks is never "is this number right". It is "who decided it was right, what did they look at, and when". That answer should already exist.
Every touch on every number, in the order it happened
Who changed the figure, what it was before, which document they attached, who approved it and when. It is kept per data point and per answer, and it is the thing you hand over when somebody asks how a number got into a filing.
Nothing on this trail can be edited or removed. A correction is a new entry, not a rewrite.
-
04 Sep · 16:05
JLJessica Lee Approved the value Reviewed against the assurance memo before approving.
-
04 Sep · 11:18
MKMarta Kowal Changed the value19,140→18,420tCO2eRestated after the assurance memo. 3 narratives and 2 questions flagged for re-check.
-
03 Sep · 09:40
JSJosh Silva Attached a source Assurance memo.docx · ¶ 4.2
-
01 Sep · 14:22
GGGreta Gärtner Moved it to Draft From Not started.
-
12 Feb · 08:03
System Extracted from a document Utility invoices 2025.pdf · p. 12–15
Illustration with sample entries, not a product screenshot
Ownership is a name, not a shared inbox
Work lands on a person, not on a team address. Questions, regulations and data points all carry one owner, so the load is visible: who is carrying too much, who has room, and what nobody has picked up yet. Watchers get the updates without getting the job.
Four roles, and nobody has to be an admin to do their job
Most people in a reporting cycle need to answer three questions and go back to their day job. A smaller group verifies numbers. A smaller group still signs off. Access follows that shape instead of fighting it.
Group people the way your org already works, then assign to a team rather than chasing an individual.
Regulations, reports, competitors, documents and communications can each be switched on or off per company, so people only see what they bought.
Domain-based sign-in, so joining and leaving is handled where you already handle it.
Illustration of the role model, not a product screenshot
Told once, in the place you already are
Assignments, mentions, regulation movements and value changes reach you in the app, in a digest, or in Slack. The useful part is the control to stop them for a few hours when the team is heads-down.
The rest of the cycle
See how LoneReport works, end to end
A walkthrough of the full cycle, from the rules that apply to you through to a filed report. We’ll focus on the parts that matter most to your team.
Book a Demo Questions first? support@lonereport.com