Paper vs. electronic signatures


In paper systems we use the “dated signature” or “dated initials” to do so many things:

  • Identify people
  • Identify when something happened
  • Signify that a step was completed
  • Establish the order in which things were completed
  • Ensure the correct person completed a step
  • Prove that a document was reviewed by appropriate roles
  • Approve or otherwise attest to something about a document

…and so on.

Basically the limitations of paper mean that anytime we want to distinguish a record from any random scrawl we add an initial or signature to it, assuming that a signature is somehow impossible to forge and uniquely traceable back to the person who applied it.

Digital systems don't have the same limitations as paper - the system can monitor, log and control all sorts of things without the need for something like a signature. It can keep track of who and when. I can enforce who can do what and in what order. It can reliably link various layers of metadata to any data.

We have many ways to accomplish those things digitally, including immutable audit trails and logs, timestamps and other metadata, tracking logins, putting functionality behind some kind of password, key or biometric barrier, and so on. You can even add blockchain to that list.

Furthermore, these other methods are more desirable than mere "dated signatures" because they can contain information that can be acted on by other parts of the digital system. Someone completing a document review workflow step in a certain way can automatically trigger not only the next step in the workflow, but might also automatically open up a deviation for late signing.

So an electronic signature is only actually needed when there's a requirement for someone to approve or otherwise attest to something about a document in a formal or legal manner. That is, when another human requires it!

Until next time, thanks for reading!

– Brendan

p.s. Enjoy this message? Read more at the Hyland Quality Systems website.

The Daily HaiQu

I'm Brendan Hyland. I help regulated facilities transform their software, spreadsheets, workflows and documents from time-consuming, deviation-invoking, regulatory burdens, to the competitive advantage they were meant to be. Join me every week as we take a few minutes to explore, design, test and improve the critical systems we use in our facilities.

Read more from The Daily HaiQu

It’s the first step of the problem solving framework that I was taught back in Engineering school. Not ‘Plan’. Not “Define”. “I want to and I can”. That particular framework - the McMaster Six Step - never gained the popularity of the ones now used today, but in the end they all contain the same basic elements - research, planning & design, implementation, evaluation and iteration - just stated in different ways. However I’ve never really seen this particular element called out explicitly...

Black music production equipment with headphones on desk

My eight year old son figured out a hack to make the music service work better for him. The kids have a Google smart speaker that is attached to a Spotify account so they can just ask for any of their favourite music. Anyone who has pre-teens in the house probably knows how much such a setup is used - all day every day. Coming from someone who had to run to the double-cassette boom box to press the record button any time a new favourite song came on the radio just so I could listen to it...

A reporter interviews a smiling man holding a book.

I’ve seen several quality leaders complain this week about their disappointment with generative AI - they’re not getting the results they expected. And I understand why - context is king! If you just ask AI to write a procedure or generate a quality document, you’ll get generic, mediocre output. Without enough context, AI can only produce something generic based on its training data. But how do you give it that context? By the time you’ve gone back and forth trying to “engineer the prompt” to...