The surveyor asks which
version you approved.
Show them.
Bindersnap is where your policy manual lives — for clinics, surgery centers, home health agencies, and behavioral health programs. Every policy keeps its own approval record: who signed off, when, and on exactly which version.
No demo call, no implementation project · Cancel anytime
- v1 Annual review draft — Renee Alvarez Oct 02 · 09:14 Superseded
- v2 Isolation section rewritten — Renee Alvarez Oct 09 · 14:37 Superseded
- v3 Medical Director edits accepted — Renee Alvarez Oct 14 · 16:02 Approved · Locked
- Tomas Lang Quality · designated reviewer Oct 14 · 16:41
- Dr. Alan Petrie Medical Director · designated reviewer Oct 14 · 17:08
Only designated reviewers can approve. You have view access.
A shared drive is not
an approval record.
The policies sit in a folder nobody owns. The sign-offs sit in
somebody's inbox — sometimes one belonging to a person who
left two years ago. And when the survey window opens, the
question is always the same:
"Who approved this one, and when?"
You should not have to spend a weekend reconstructing that.
You already have the policies. What you need is the proof.
Word, PDF, whatever the last person left behind — Bindersnap versions and approves your files exactly as they are.
-
Store
Every Policy, One Place
Every policy gets its own page, its own version history, and its own approval record. Point your staff at one link instead of a folder they have to guess their way through. No migration project, no consultant.
-
Approve
Sign-Off That Cannot Be Back-Dated
Every approval is stamped with the person, the date, and the version they actually read. Approved versions lock — a revision arrives as a new version with its own review, never as a quiet edit to the one already signed.
-
Produce
Evidence While They Wait
Asked who approved the current version and when? It is on the page, in front of you, while the surveyor is still in the room. Asked for the whole history? Every version is there in order, each with the sign-offs it collected — no support ticket, no vendor in the middle.
An approval nobody can
quietly edit —
including us.
Most policy systems keep an approval as a row in their database. A row can be changed by anyone with the right access, and you would never know. Change ours and everyone can see it.
-
Version 1 Approved
R. Alvarez, RN · 4 Mar
- carries
- first entry
- sealed
- a91f04c
-
Version 2 Approved
Dr. E. Whitfield · 19 Jun
- carries
- a91f04c
- sealed
- 7c3e8b2
-
Version 3 Approved
R. Alvarez, RN · 2 Dec
- carries
- 7c3e8b2
- sealed
- e5d19af
Go back and change one word of version 2 and its fingerprint
is no longer 7c3e8b2 — but version 3 still
carries that. A step cannot be removed, re-dated, or slipped
in without breaking every link that follows.
-
Sealed
The fingerprint is calculated from the version's exact contents. There is no quiet edit.
-
Linked
Every entry carries the fingerprint of the entry before it, so the order is part of the record too.
-
Open
Kept as ordinary commits and plain files — not a private schema that only we know how to read.
The shared drive.
Or a record that holds up.
Same policies, same people — a very different survey week.
The review happens on the policy.
Not in your inbox.
Questions get raised on the version they are about, and the answer stays attached to it. What has to happen before a version reaches the floor is your call — and once you set it, the system holds the line instead of the person who remembers to.
Every question stays with its version
The Medical Director raises a point, the author replies underneath, and the whole exchange stays attached to the version it was raised against. Six months later it still reads in order.
Set the rule once. It holds.
Require two approvals, or the Medical Director specifically. Refuse to publish while a question is still open. Clear old sign-offs whenever a new version arrives. You pick which rules apply; after that nobody has to remember them.
The publish gate keeps its own history
The rule that holds a version back while a question is open is stored as a committed file, not a checkbox in a database. Turn it on or off and that change is a commit, with a name and a date on it.
My wife came home frustrated with her policy system often enough that I started asking questions. Reviewing a document meant opening it in Word, which not everyone had. Getting one approved meant a meeting, then an email chain, then keeping track of who had signed off on which draft.
I build software for a living, and I kept thinking: isn't this just a pull request? A change, the people who reviewed it, and the exact version they approved, all in one record. Engineers have worked this way for decades and stopped noticing it was ever hard. She did not need more software. She needed the thing my industry takes for granted.
So I built it for her.
David Gray Founder, Bindersnap
Be ready for the next survey.
Starting today.
Load the policies you already have, name the people who approve them, and let the record build itself from there. The other systems want a demo call, a quote, and a quarter of implementation. This one wants an afternoon.
No demo call, no implementation project · Cancel anytime
- Encrypted at rest AES-256 storage
- Encrypted in transit HTTPS, browser to server
- Named approvers Limit who can sign off