This E-Signature Guidance sets out to provide information on the different types of electronic signatures available in Liberty University’s technology environment and best practices for their use.  

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. 

Liberty University may accept and use electronic signatures when the applicable process includes an authentication method or other verification mechanism appropriate for the transaction, form, or business context. The appropriate authentication process may vary depending on the type of document, the identity of the signer, the nature of the transaction, record-retention needs, and the University’s acceptable level of business risk. 

Departments should not select an electronic signature tool based solely on the limitations or availability of a particular vendor platform. Tool selection should be based on the business unit’s requirements, including authentication, signer access, workflow, reporting, storage, version retention, and the ability to reproduce records when needed. 

Information Services is available to assist departments in evaluating available electronic signature solutions and related business processes


Liberty University supports several methods for capturing electronic signatures. These methods are listed below, based on available authentication and record-retention capabilities, 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, or
  • Explicitly agreeing to terms before signing, or
  • Selecting a button or similar action that clearly indicates the signer’s intent to proceed 

Departments should configure forms so that the signer’s action is clear, intentional, and able to be associated with the applicable record or form. 

Furthermore, electronic signature tools should support the ability to reproduce the exact version of the form or record that was presented to the signer at the time of signature, including the signer’s electronic signature and associated acknowledgment. 

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. Departments should select tools based on the requirements of the specific process, including signer population, authentication method, workflow needs, record retention, reporting, and storage.

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

Tool Authentication External Users Version Control / Reporting Printable PDF Record Retention / Accessibility
APEX/Raft Checkbox Required APEX – YES
RAFT – NO
✔️ ✔️
Microsoft Forms Checkbox Required IT Implementation Required
Dropbox LU Account
OR
Requires business process for Identity Verification
✔️ ✔️
Adobe Sign LU Account
OR
Requires business process for Identity Verification
✔️ ✔️ ✔️
Docusign LU 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: 

  • Authentication: The process should include an authentication method or verification mechanism appropriate for the transaction, signer population, and business risk. Different processes may require different levels of verification. When identity verification is required, Dropbox, Adobe, Microsoft Forms, and other PDF solutions are not recommended. 
  • External Recipients: Some tools may work differently for individuals outside the LU network. Departments should consider whether external users can access, complete, and submit the form without unnecessary barriers. 
  • Version Control: Version retention and historical form reproduction capabilities vary by platform and configuration. Departments should confirm that the selected tool supports their need to reproduce prior versions of the form. 
  • Wet Signature Requirements: Certain business processes, vendor requirements, or other operational considerations may require a handwritten signature. Departments should evaluate the requirements applicable to their specific process.
  • Record Retention/Accessibility: Departments should identify where completed records will be stored, who will maintain access, how long the records will be retained, and whether the records must be available for reporting or retrieval.

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.