In most studios the question of "what to deliver to the client at project end" gets handled improvisationally: send the latest files, make a pretty PDF presentation, sometimes a printed album. All of this as final documentation.
The problem is the project has three audiences with different document needs:
- Client wants a beautiful album for understanding and showing friends
- Contractors want working documentation for execution
- Court / insurance wants a process report with timestamps, if it comes to a dispute
The third is usually underestimated. And when "comes to a dispute" happens, the evidence base does not exist because nobody collected it.
Below: what kind of PDF report solves all three jobs and what goes into it.
Three document types
1. Design album (for the client)
- Cover with project name and address
- Final mood boards and visualizations by room
- Mood board with references
- Description of stylistic decisions
- Specifications of key materials and items
A presentational document. Beautiful renders, minimum text, focus on aesthetics. Done often, no disputes.
2. Working documentation (for contractors)
- Room plans with dimensions
- Electrical plan (outlets, switches, lighting)
- Plumbing plan
- Material specs with SKUs
- Details and elevations
- Custom furniture drawings
A technical document. Cannot execute without it. Always done.
3. PDF report (for everyone)
- Event log with timestamps
- Approval history by phase
- Mood board versions with approval marks
- Client annotations and designer responses
- List of brief changes
- Iteration count per phase
A process document. The most underrated and the one that saves you in disputes. Below we focus on this.
What goes into the PDF report
Section 1: Project card
- Name, address, area
- Party details (client and designer)
- Contract: number, date, key terms
- Team: who worked and in what role
- Timeline: planned vs actual
Section 2: Brief and its evolution
- Final version of the brief
- List of brief changes during the project (with dates)
- Approved scope of work
Critical: if a year later the client says "we wanted something else," you open this section and show what the brief was and when it changed and why.
Section 3: Phases and their approvals
Per phase:
- What was in scope
- Start and end dates
- Number of iterations
- Who approved (name, email, timestamp)
- Final result version
Example table:
| Phase | Start | End | Iterations | Approver | Time |
|---|---|---|---|---|---|
| Layout decision | 14.02.2026 | 22.02.2026 | 2 | client@example.com | 14:32 |
| Concept | 23.02.2026 | 03.03.2026 | 3 | client@example.com | 18:15 |
| Mood boards | 05.03.2026 | 21.03.2026 | 4 | client@example.com | 10:05 |
Section 4: Event log
Chronological list of all significant events:
14.02.2026 09:12 - Designer uploaded layout V1
14.02.2026 11:30 - Client opened layout V1
15.02.2026 14:08 - Client left 3 annotations on V1
16.02.2026 10:15 - Designer uploaded layout V2
17.02.2026 18:43 - Client approved layout V2
...
This section is the main process evidence. When the log shows "client approved V2 on 17.02.2026 18:43," there is nothing to argue.
Section 5: All versions and annotations
Per key mood board version:
- Image
- Creation date
- Client annotations (with coordinates and text)
- Designer responses
- Status (draft / sent / approved / rejected)
Not necessary to include ALL intermediate versions (that would bloat to hundreds of pages). Key ones: first, pivot points, final. Full archive on the platform with links from the PDF.
Section 6: Financial report
- Payment schedule
- Actual payments (dates, amounts)
- Closed phases
- Open balance (if any)
Section 7: Implementation and author supervision (if applicable)
- Site visits
- Progress photo log
- Project deviations (approved or not)
- Final photo log
Section 8: Metadata and signatures
- Report generation date
- Generator (name, email)
- Document hash (integrity check)
- Digital signature (optional)
What makes the PDF report legally significant
The PDF itself is not evidence. What turns it into evidence:
- Server-side event fixation. Timestamps from the server, not from the user's device. Stronger than "a date stamp in Word."
- Inability to change retroactively. A platform with an audit log cannot "rewrite history." Each record is immutable.
- Party identification. Email and account tied to the contract (see article on party identification).
- Contract clause recognizing platform events as equivalent to written documents.
Without these four, the PDF report is just a nicely formatted file. With them, full evidence in court.
When the report saves money
Specific situations where having or lacking a PDF report changes the outcome:
Case 1: Client demands 6 months later that you redo kitchen mood boards "because you did not approve the final version with me." Without the report, your word against theirs. With the report, you open the log, show the approval date and time. Dispute closed in 5 minutes.
Case 2: Client refuses to pay the last phase "because you missed the deadline." Without the report, you try to prove the delay was on their approvals. With the report, a table: "Concept phase, 3 iterations, between V1 and V2 the client took 12 days to respond when the norm is 3."
Case 3: Client sues for a refund citing "unprofessional service." Without the report, hard process. With the report, you prove the full scope of work, approved phases, and correspondence. Win rate multiplies.
How to generate the report in Roomix
In Roomix the PDF report generates automatically:
- Open the project
- "Export → PDF Report"
- Choose scope (full / approvals only / final versions only)
- Get a ready PDF with the log, versions, marks, annotations
This closes the "process" portion. The album and working documentation you still produce in your familiar tools, but they now ship alongside process evidence, not alone.
What to do right now
- Open 2 to 3 of your recent projects
- Try to assemble an event log retroactively
- If you struggle, you lack the infrastructure
- On the next project, start tracking events on a platform with an audit log
- In 3 months you will have an automatic PDF report for every new project
CTA
PDF reports in Roomix are included on all plans, including free. Create a project and see how it works, even without real clients, on a test project.
See also: legal validity of approvals, 9 contract clauses.