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
I'm presenting!

I'm excited to be presenting at the 2025 SQA Annual Meeting next week - "Is it the Right Tool for the Job? How QA and Regulatory Professionals can Guide Software Decisions in Regulated Environments" As our familiar software tools become more feature-laden and generalized, it's critical to ensure that software meets clear use cases and basic user requirements. And with generative AI being shoehorned into every platform, defining if and how software is appropriate for the intended use has never...

Last time we left off with a cliff-hanger of a question: How do you prove you're you when signing a document? There are several ways I've seen that the 3rd party providers prove that it's you who's signed the document: You clicked a link from an email. You paid for the service with a credit card. You provided some government issued photo ID. Someone, such as a notorized public or your HR department, has verified it's you in person. Obviously these are very different levels of assurance. Then...

There are several levels of 'signatures' that you can apply to an electronic document. The first and most basic is just an image of your written signature. One common option for this is to print the document, sign and scan it back in again. A more convenient version is to have an image of your signature saved that you can paste into documents. This is what many free versions of pdf software and word processors offer as a basic document signing option - a 'stamp' of your saved signature image....