DEV Community

Cover image for Proving people actually read internal documents is still a mess
Benjamin Touchard
Benjamin Touchard

Posted on

Proving people actually read internal documents is still a mess

I’ve worked on internal tools, compliance processes, and regulated environments for years.

And there is one recurring problem that almost everyone underestimates:

How do you prove that people actually read internal documents?

Not signed contracts.

Not legal agreements.

Just things like:

  • internal procedures
  • security policies
  • onboarding documents
  • mandatory trainings

The answers are usually disappointing.


How this is usually handled

In most teams, it looks like this:

  • a PDF sent by email
  • a shared folder or intranet page
  • a checkbox in a form
  • sometimes a signature on paper

When someone asks:

“Can you prove that employees read this document?”

The answer is often:

“Well… we sent it.”

That’s not proof.

And in audits, that difference matters.


Why existing tools don’t really fit

There are many tools for:

  • e-signatures
  • contract management
  • document workflows

They are usually:

  • heavy
  • expensive
  • SaaS-only
  • designed for legal or sales use cases

They solve problems like:

  • signing contracts
  • closing deals
  • external compliance

But internal acknowledgements are different.

They are:

  • frequent
  • low-risk
  • internal
  • boring but mandatory

Using a full contract-signing platform for that feels excessive.


What I actually needed

From a technical and operational point of view, I needed something simple:

  • prove that a document was presented
  • prove that it was acknowledged
  • keep a verifiable record
  • without managing contracts or identities manually

No document storage SaaS.

No legal framing.

No complexity.

Just proof of read, done properly.


A pragmatic response: Ackify

So I built Ackify, an open-source tool focused on one thing:

Internal document acknowledgements.

Ackify:

  • generates acknowledgement requests
  • records confirmations
  • produces verifiable proof
  • stays simple by design

It’s not a replacement for legal signature platforms.

It’s a tool for internal compliance and operational needs.

👉 Repository: https://github.com/btouchard/ackify-ce
👉 Website: https://ackify.eu


Why this problem is mostly ignored

Internal compliance is not shiny.

It doesn’t:

  • generate revenue directly
  • impress investors
  • fit growth dashboards

But it costs time, energy, and stress when done badly.

Big platforms optimize for contracts and transactions.

Small teams just need clarity and traceability.

This gap is where many open-source tools live.


Closing thoughts

Not every problem needs an enterprise platform.

Some problems just need:

  • a clear scope
  • a simple workflow
  • and reliable evidence

Internal acknowledgements are one of them.

Top comments (0)