PaperlessZen for the office of general counsel
A legal hold lands on a Tuesday. The matter names a gift from 2011, and counsel needs the executed agreement, every amendment, and proof that none of it changed after signing. The advancement VP forwards the request down the hall. An hour later the answer comes back: the signed copy is in a drawer, or on a shared drive named by whoever scanned it, or with a colleague who retired last spring. Nobody can search it, and nobody can swear it was never altered.
That is the moment this page is about. Not storage. The ability to produce the right document, prove it is the real one, and freeze it until the matter closes.
The original is never altered, and every version is kept
The document counsel cares about is the executed one, the version with signatures on it, exactly as it was when the parties agreed. A system that lets that file be overwritten, renamed, or quietly edited is a liability, not a record.
PaperlessZen does not overwrite originals. When a document changes, the prior version is kept, not replaced, so the executed copy stays intact and every version before and after it is still there to see. You can show what the signed agreement said on the day it was signed, and you can show every change that came after, in order.
That is the foundation counsel needs before anything else. If you cannot trust that the file is the real one, nothing built on top of it holds up.
Legal holds and retention that override deletion
An agreement is not just a document. It is a record with a lifespan your policy defines and, sometimes, a matter that freezes that lifespan in place.
PaperlessZen treats governance as final. Records can be locked to a retention schedule, so they live exactly as long as policy says and no less. When a matter requires it, a legal hold freezes a document and overrides any retention or deletion until you lift the hold. Even an ordinary delete is a soft-delete: the underlying file is kept, not destroyed.
The actions that change what a document is or how long it lives are the most sensitive in the system, so they are held behind a separate governance permission. Placing a hold or changing a retention schedule is not something an ordinary account can do by accident. You decide who carries that permission, and every use of it is on the record. For the schedules side of this, see records retention.
A hold you can prove is a hold that holds up.
Executed agreements, findable in seconds
Counsel does not have time to guess which drive and which naming convention holds a file. When a hold or an audit or a dispute names an agreement, the document has to surface fast.
Every page of every scanned agreement becomes full-text searchable, not just the file name. You can search a phrase you remember from an indemnification clause and land on the exact document and the exact page.
You can also ask the archive a plain question, like “which agreements reference this fund.” PaperlessZen returns the passage and the page it came from, with the text highlighted. It does not write you a summary and ask you to trust it. It shows you the source clause, so what goes in front of a judge, an auditor, or a board comes straight from the document, not from a paraphrase. That distinction matters most when the stakes are legal.
A defensible chain of custody
Capture
The executed agreement lands in PaperlessZen and the original is stored without alteration.
Version
Every later change is kept as a new version. The signed copy stays intact and visible.
Log
Every view, share, and download is recorded against the document.
Hold
A matter freezes the record in place, overriding retention and deletion until the hold is lifted.
Produce
Search finds the document, and the audit trail shows who touched it and when.
When someone asks who accessed a document, when, and under what authority, the answer is a record you can produce, not a reconstruction from memory. Every view, every share, and every download is logged. For institutions that get audited, or that simply need to show a board or a family that a confidential file was handled properly, that trail is the difference between a calm answer and a scramble. You can read the full posture on the security page.
Sending a confidential agreement outside the institution
Sharing a confidential agreement with outside counsel, an auditor, or the other side of a matter is where most document leaks actually happen, so it is where PaperlessZen is strictest.
An external share is a single-use token bound to one document. The recipient’s token resolves to a short-lived download link, not to standing access to your archive. The link expires on its own when its window closes. And if you are not sure whether a link is still out there, you do not have to wonder. You revoke it, and it is closed. That is the honest version of secure sharing, a token you control from the moment it exists to the moment you shut it off.
The drawer, and the system that replaces it
The drawer and the shared drive
The executed copy is somewhere, but nobody can search for it
No way to prove the file was never altered after signing
Deletion is one misclick, and a hold is a sticky note on a monitor
Access is whoever has the network path, with no record of who opened it
A governed system of record
The executed agreement is full-text searchable in seconds
The original is never overwritten, and every version is kept
Legal holds and retention override deletion, gated behind a governance permission
Every view, share, and download is logged, and external shares are revocable
What is enforced today
Enforced today
Originals never altered, with every version kept.
Retention schedules and legal holds that override deletion.
Governance actions held behind a separate permission.
Soft-delete, so an ordinary delete keeps the underlying file.
A complete audit trail of every view, share, and download.
External shares as single-use, expiring tokens you can revoke immediately.
Deployment into your institution's own cloud subscription, so your documents never leave your environment.
Straight talk about beta
PaperlessZen is an early-beta product, and we would rather be clear than impressive. Everything on this page is enforced today. During beta, every deployment runs in the customer’s own cloud subscription, so the hosting and residency questions a review opens with are answered by your own environment and your existing provider agreements. What remains, our software practices and our roadmap toward formal certifications like SOC 2, we are glad to cover directly with your team, and we will be honest about what is in place now versus what is on the roadmap. If your office has a questionnaire, send it. We will answer it plainly. You can also read how we frame our commitments on the trust page.
See it against your own agreements
Book a demo and bring a handful of your own executed agreements and a scenario, a hold, an audit, or a dispute. We will make the documents searchable while you watch, place a hold, and show you the audit trail and the chain of custody behind it.
Frequently asked questions
Can we prove a document was never altered after it was signed?
Yes. The original is never overwritten. Every version is kept, and each view, share, and download is recorded, so you can show what the executed document said and who touched it after.
How do legal holds work, and who can place one?
A legal hold freezes a document in place and overrides any retention schedule or deletion until you lift it. Placing a hold and changing retention are gated behind a separate governance permission, so an ordinary account cannot do either by accident.
Does the search write us an answer we then have to trust?
No. When you ask the archive a question, it returns the passage and the page it came from, highlighted, so you read the source clause yourself. It retrieves; it does not compose.
How do we send a confidential agreement outside the institution safely?
External shares use a single-use token that resolves to a short-lived download link. It expires on its own, and you can revoke it at any moment, so a link that was appropriate last week can be shut off the moment it is not.
Do you have formal security certifications?
PaperlessZen is in early beta. The controls on this page are enforced today. Formal certifications like SOC 2 are on the roadmap, and we will tell you plainly what exists now versus what is planned.