Visibility on a quiet channel
Most investigations can reconstruct what left by email or upload. Far fewer can say what walked out of the building in a folder.
PaperTrail is our open source print auditing tool for Windows. It reads the Print Service event log, turns it into a searchable record of who printed what, where and when, and produces an audit report you can hand over. It runs entirely offline, so nothing it sees ever leaves the building.



Screens from PaperTrail running locally with a month of sample print jobs. The users, machines and documents are sample data.
PaperTrail is not a flagship and was never meant to be. It stays in the portfolio because print remains a genuine exfiltration path, because small utilities age well, and because publishing the source is the only reasonable way to ask someone to run an auditing tool on their estate.
Most investigations can reconstruct what left by email or upload. Far fewer can say what walked out of the building in a folder.
When something has gone wrong, a print record is often the difference between a theory and a timeline.
Anything that watches user activity should be inspectable by the people it watches. The source stays public for that reason.
An audit in PaperTrail is a case. You open one, bring in the logs, read what they say, and finish with a report that carries the auditor's name and the period it covers.
Each case keeps one organisation, site and period apart from the rest.
Read the local system live, or import one log file or a whole folder.
Duplicates are merged and system noise is separated from printing.
By user, computer, printer, paper size and hour of the day.
A branded audit report with the sections you choose and the auditor named.
CSV or JSON for anything the report does not cover.
It is deliberately small. Everything it captures is something an investigation later turns out to need.
The document name and the job, so a later question about a specific file has an answer rather than a shrug.
The user account behind the job, which is usually the first thing anyone asks and the hardest thing to reconstruct afterwards.
The workstation and the queue, which is what turns a single record into a pattern across an estate.
The timestamp, which is what makes the record a timeline rather than a list, and what makes after hours activity visible at all.
An audit usually starts with a narrow question from someone who is not technical. Who printed the contract? How much does the finance floor print after hours? The reports answer in their terms.
Every report is drawn from the same cleaned record for the case, so the executive summary and the per user detail can never disagree. Choose the sections, name the auditor and the period, and export a branded PDF.

Most print audits that come back empty fail for the same few reasons, none of them about the tool. Get these right first.
Windows keeps the Print Service operational log disabled by default. Until someone enables it, there is nothing to audit, and a gap that started on day one cannot be filled later.
Where printing goes through a server, its log covers every desk behind it. Where people print directly, each workstation holds its own piece, and a folder import brings them together.
Print records show what people do. Tell staff the record exists and what it is used for, and keep access to it as narrow as the investigation that needs it.
Runs on one Windows machine. Nothing it reads is sent anywhere.
Each audit kept apart by organisation, site and period.
Branded PDF for people, CSV and JSON for other tools.
The code is public, so anyone it watches can read it.
The questions that come up most often, answered the way we would answer them on a call.
Yes, and the source is public. Anything that watches user activity should be inspectable by the people it watches, which is the main reason it is open rather than a commercial decision.
Because most investigations can reconstruct what left by email or upload, and far fewer can say what walked out of the building in a folder. It is the one channel that almost nothing watches.
No. It records the job, the user, the host and the time. The content of what was printed is not captured, which keeps it useful for investigation without turning it into surveillance.
It stays in the portfolio. It is deliberately small, which is precisely why it ages well and why it has not needed to change much.
Whether that means PaperTrail on its own or a broader look at data leaving the organisation, the conversation is worth having either way.