Skip to main content
U.S. flag

An official website of the United States government

Dot gov

The .gov means it’s official.
Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you’re on a federal government site.


The site is secure.
The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.


Ask users for…


Use: Deployed
Use this pattern when you need a user to provide their signature as a statement of truth.


When to use this pattern

Under laws such as the Government Paperwork Elimination Act (GPEA), 44 U.S.C. 3504 note, the Uniform Electronic Transactions Act (UETA), … and the Electronic Signatures in Global and National Commerce Act (ESIGN), 15 U.S.C. 7001, et seq., an e-signature has the same legal weight as a handwritten signature and cannot be considered invalid simply due to being electronic. The laws establish criteria for valid e-signatures, along the following lines: Intent to sign, consent to do business electronically, association of the signature with the record, attribution to the person signing, and a record of the digital transactions. The United States practices an open technology approach, meaning there’s no law requiring use of a specific signing technology for an e-signature to be legally binding, as long as it meets the criteria.

Federal register Vol. 87, No. 60


Example of the statement of truth signature pattern.
The Statement of truth component captures a digital signature from the user.

How to design and build

This pattern is used at the end of a form review page.

Layout details

How this pattern works

  • Signature pattern does not exist in every form. If your form needs a certification statement or statement of truth, we recommend using this pattern.
  • When using this pattern, do not add the privacy policy checkbox at the end of the form. The user does not need to check another checkbox for privacy policy.

Implementation details

Generating a PDF: When generating a PDF for submission, for example when using the Benefits Intake API, the following rules must be adhered to.

Generating a PDF

This guide is for software engineers generating a PDF for submission to the Benefits Intake API.

  • Veteran’s name from Statement of truth is entered into the Signature field. Enter the input from the Statement of truth text-input into the Requester’s or Veteran’s signature field on the PDF. If the form is not using the Statement of truth component yet, use the user’s signed-in name. NOTE: All forms should implement the Statement of truth component.
  • Current date is entered into the Date Signed field. Enter the current date into Date Signed or Date field usually found next to the Signature field on the paper form. Entering the current date without asking the user for it is appropriate.
  • Date & timestamp and authentication level are added at the bottom right of all generated pages. At the bottom right of each page the date and time in UTC as well as the authentication level of the submitter of the form must be indicated. This takes the Date and timestamp watermark format.
  • Date and timestamp the form in the VA DATE STAMP box, when available. If the paper form you are populating has a VA DATE STAMP box in the upper right-hand corner, this field must be populated with the date and time in UTC that the form was submitted. This takes the Date and timestamp VA DATE STAMP box format. NOTE: Older versions of some forms may not have the VA DATE STAMP box.
  • All date and time stamps are in Coordinated Universal Time (UTC). Use the UTC timezone when generating date and time stamps on forms as this is how form submission data is stored.
  • All date and time stamps must be the date the form was initially submitted. Date the time stamps must be the date the form was initially submitted and not the date and time the PDF was generated. This is a requirement due to potential delays or submission issues. This ensures Veterans get the earliest possible date – when they first hit submit.

Date and timestamp watermark format


Signed electronically and submitted via at 11:30 UTC 2023-12-13. Signee not signed in.

Identity Assurance Level 1 (IAL1)

Signed electronically and submitted via at 11:30 UTC 2023-12-13. Signee signed in but hasn’t verified their identity.

Identity Assurance Level 2 (IAL2)

Signed electronically and submitted via at 11:30 UTC 2023-12-13. Signee signed with an identity-verified account.

Date and timestamp VA DATE STAMP box format

Application Submitted:
11:30 UTC 2023-12-13

Example PDFs are available.

Components used in this pattern

Page templates available for this pattern

  • VADS Templates contains a page template for the Review page which contains this pattern.
Edit this page in GitHub (Permissions required)
Last updated: Apr 02, 2024