An electronic signature (e-signature) is a digital method of signing documents or agreements. It can take various forms, such as a typed name, a scanned image of a handwritten signature, a signature that is drawn using a mouse, trackpad, touchscreen, or a click-to-sign button. It is important to note that  Liberty University has defined signature authority in the Contract Policy, and this guidance does not replace required contract routing through BuyLU. 

With contracts, agreements, waivers, and attestations, Liberty has to take measures to ensure that the electronic signature actually belongs to the person(s) against whom enforcement of the agreement is sought. This is fundamental to contract enforceability: for a contract to be legally binding, Liberty has to prove that the signature on the contract or agreement belongs to the person who purportedly signed it. For that reason, Information Services recommends that forms be reviewed by Legal and emphasizes that upstream business processes used to confirm identity are a part of establishing valid electronic signatures.

This page sets out to provide guidance for the different types of electronic signatures in our technology environment. 


Liberty University supports several methods for capturing electronic signatures. These methods are listed below in order of preference and must follow specific verification and record‑keeping requirements.

  1. LU Login Authentication
    • LU provides the user’s credentials
    • The user is authenticated using their LU login
  2. LU‑Verified Identity with Additional Validation
    • LU vets the user’s credentials through an additional business process
    • Examples include:
      • Faculty contract verification
      • Multifactor authentication (e.g., SMS or PIN verification)
  3. Drawn (Liquid) Signature
    • The signer draws their signature using a mouse or touchscreen (finger)
      • Typed or cursive-style font signatures are not permitted
    • Commonly used for non‑LU users
      • Example: Rock Wall Assumption of Risk form

Required User Acknowledgment

When capturing an electronic signature, the user must complete an active acknowledgment, such as:

  • Checking a confirmation box
  • Explicitly agreeing to terms before signing

Furthermore, to meet Legal requirements, all electronic signature tools must support the ability to reproduce the exact version of the form as it existed at the time of signature, including the signer’s electronic signature.

To learn how to request forms, please visit the Lightweight Forms Development page.


Below is a list of available tools, along with their appropriate use cases and features. These tools can be used for a variety of internal processes at Liberty University, including acknowledgments, approvals, and documentation.

Need help choosing the right tool? Use the following guidelines to determine the best option: 

ToolLegal Enforceability External Users  Version Control / Reporting Printable PDFStorage/ Accessibility
APEX/Raft Authentication (checkbox required)APEX -YES
RAFT -NO 
✔️ ✔️ 
Microsoft Forms Authentication (checkbox required)IT Implementation Required
Dropbox LU Account OR Requires business process for Identity Verification✔️ ✔️ 
Adobe SignLU Account OR Requires business process for Identity Verification✔️ ✔️ ✔️ 
DocusignLU Account OR Requires business process for Identity Verification✔️ ✔️ ✔️ IT Implementation Required
Wet Signature ✔️ ✔️ 

The following are important limitations that should be considered when using e-signatures at Liberty: 

  • Legal Enforcement: LU Legal Counsel prefers APEX/RAFT or wet signatures for documents that may lead to legal action. Digital signatures from Dropbox or Adobe are not considered fully verifiable/authenticated by LU. 
  • Authentication: When identity verification is required, Microsoft Forms and the PDF solutions do not meet standards. 
  • External Recipients: RAFT/APEX and Microsoft Forms are less suitable for users outside the LU network. 
  • Version Control: Because these tools need to be configured or confirmed, they do not support forms that require archived versions.
  • Wet Signature Requirements: Some processes still require a traditional ink signature, especially when legal or regulatory compliance is involved. 
  • Storage/Accessibility: Storage requirements must equal the business criticality of the document. This includes the ability to centrally report required fields.

If you have any questions regarding the use of e-signatures at the university or any of the e-signature tools, please contact your department’s BRM.