Tutorial ID | T-30 |
Section | Reporting & Billing |
Title | Finalising and Exporting the Completed Report |
Subtitle | Confirm validation, comments, version, formatting, and scope before a report leaves the platform for good. |
Before You Begin
You have a report that's been assembled and is ready for a final review before export.
You know who will receive the export and what they should and shouldn't see.
What You Will Accomplish
By the end of this tutorial, every report you export will be fully validated, free of open comments, confirmed as the correct version, checked after export for broken formatting, and scoped to exactly what the recipient should see.
Why Does This Tutorial Matter
A report stays provisional until you finalize it. Once it's exported, it leaves the platform's controlled environment — the linked references, the Validation Analysis, the audit trail — and becomes a standalone file you can no longer correct in place. Whatever is in that file when it's sent is what the recipient has.
Treating finalization as a quick click rather than a checklist is what lets an unverified statement, an open internal comment, the wrong version, broken formatting, or privileged content travel out of the platform with the report — each one a problem that's far more costly to fix after the fact than before export.
What to Do if Something Goes Wrong
The list below covers the most common problems when finalizing and exporting a report. Each entry follows the same pattern: what you'll notice, why it likely happened, a real example, and how to fix it.
Problem: A report is exported while it still contains statements that haven't been checked against their source.
Likely cause: The report was exported under time pressure before a final validation pass was run.
Example: A report goes out with three statements still sitting in the low Validation Score band, and the recipient has no way to know they weren't checked.
Fix:
Before exporting, run a final pass over the Validation Scores and resolve any low-scoring statements.
Confirm that every statement you're relying on has been checked against its source.
Export only once the report reflects your reviewed, confirmed version.
Problem: An exported report includes an internal note, a question to a colleague, or a “check this” flag.
Likely cause: Comments and internal annotations weren't cleared before the report was exported.
Example: A comment reading “confirm this date with the provider” is still attached to a statement in the version the attorney receives.
Fix:
Review all comments and internal annotations and resolve or remove them.
Confirm that no placeholder or draft text remains.
Check that anything intended to stay internal isn't included in the exported output.
Problem: The exported report doesn't reflect the most recent reviewed changes.
Likely cause: Multiple drafts were in play, and an older version was exported by mistake.
Example: A corrected version of a report exists in the platform, but an earlier draft — missing that correction — is the one that gets exported and sent.
Fix:
Confirm you're working in the latest, intended version before exporting.
Use version comparison to check the report contains the most recent reviewed changes.
Label the export clearly so both you and the recipient can identify it later.
Problem: References, headings, tables, or chronology order look different in the exported file than they did on screen.
Likely cause: Structure and formatting that appear correct in the platform can shift when the report is converted into a standalone exported file.
Example: A back-reference link that worked on screen points to the wrong page once the report is exported to PDF.
Fix:
After exporting, open the file and confirm that references and links are intact and point correctly.
Check that headings, tables, and the chronology order have carried over.
Re-export if anything is lost, rather than sending a degraded file.
Problem: An exported report includes content that shouldn't go to a particular recipient.
Likely cause: The report's scope wasn't checked against the recipient before export, so privileged or out-of-scope content stayed in.
Example: A report intended for an insurance adjuster still includes an attorney-only strategy note that should have been excluded.
Fix:
Confirm that the report's scope matches the recipient before exporting.
Remove or redact anything privileged or outside what that recipient should receive.
Keep a record of what was sent, to whom, and when.
Tip If the platform maintains an audit trail of exports, use it to confirm what was sent and when, rather than tracking it manually. |
Summary
Every report is now validated, free of open comments, confirmed as the correct version, checked after export for intact formatting, and scoped to what the recipient should see — treating finalization as a short checklist rather than a single click before it leaves the platform for good.