> For the complete documentation index, see [llms.txt](https://guide.form.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.form.gov.sg/user-guides/advanced-guide/signatures.md). # Signatures ### **Ordinary Electronic Signatures** FormSG provides options that can be considered as Ordinary Electronic Signatures (OES) under the Electronics Transaction Act (ETA). When implementing OES, admins must ensure that they capture respondents' identity and intention, in clear proximity. This is so that the individuals are explicit in confirming their identity and agreeing to the stated declaration or purpose of the transaction. The form of OES adopted should be calibrated to the stakes of the transaction. When the risk mitigation steps are applied and documented, you can create a stronger form of OES that is more defensible. For more information about electronic signatures, refer to the [circular](https://intranet.mof.gov.sg/portal/IM/Circulars/ICT/Circular-Minutes/2021/Use-of-Electronic-Signatures.aspx) (government intranet-only) by SNDGO. {% embed url="" %} ***
Examples
Identity

  • Singpass & MyInfo

    • e.g Name, NRIC

  • Email field

    • Enable email OTP verification
    • Enable email domain restriction

  • Phone number field

    • Enable SMS OTP verification

  • Signature field

    • Verify against specimen signature
Intention
  • Checkbox field
  • Signature field
  • Yes/No field
Risk mitigation
  • Results page
  • Copies of the response (e.g. PDFs, emails)
  • Witnesses
{% hint style="success" %} Form admins can use a different combination and need to calibrate based on the stakes of their use cases. {% endhint %} *** ### **Identity** 1. **Singpass + MyInfo authentication** Using MyInfo, you may display the signer's name as a non-editable Name field.
2. **Email field with One-Time Password (OTP) feature enabled** By enabling OTP, the respondent must have access to their email inbox at the time of submission.
*** ### **Intention** 1. **Checkbox field acknowledgement** Include a clear checkbox option requiring signer to confirm their identity and acknowledge that ticking the box constitutes their electronic signature. Checkbox must be mandatory before submission.
2. [**Workflow**](https://go.gov.sg/formsg-guide-mrf) **approvals** In a workflow involving 2 or more respondents, you can use the Yes/No field for the respondent to provide their intention.
3. **Signature field** Include a signature draw field requiring signer to confirm their identity and acknowledge that providing the drawn signature constitutes their electronic signature. Signature field must be mandatory before submission.
*** ### Risk mitigation An encrypted submission stored on FormSG may look something like this: ``` 4x/NUd2bHR0HFMScOCo/GES0S3rKi9m5vatyeM0njnk=;wS2+yKR41S0aKlr4AK0/vn9BT6Ehwfot:zAa5tjq2IYVjJLiEea85kd5wePmfojzCTa9oZiZdFY9AEHmfDU8z++TrqwfGFuj28KB3MHC+4UC+aJX+XCY0Q4ruSxttDU3lMtrqV/st3J7DgwuhgXekRSKlxfhSP0wz6VmNZdjO/wlcmwfuH3VPqhUvpi+hQw+DCeUEFuLK502Iwxq7PU0Wm+VJgUcJqgDdMW/qcPq0H4YSxzIWY12C9dXGijDTaHClBPCbAFbasPaFYIehOEcTlwSZI8/J2bF2taAR+YyI/eq4p0ff3NnSWB1B4nU64T6LPnB0W+uuSywHZPYtXKAZb765zWz6iIkawvdHezoqAR+hHZYJik1nOCCpRnstAhxqxMkB7HR+ir+qpPlpZ70PRJyiaak81vzZtpSmKgIPsWE0oml7emkIj7IJLNygwo7z8LMRiNkV4oyEyimrOXEpJEqLIiFSDhp/7r5fAtSQjsxQ0BN592QrGHHaONd0YFJZ3CuZBLKL5iQrA8heebZBsBAkjydsZV3G3VKb68H4limpefbsSJFlsEDV0hMJDSXCJ/JZ9szOm+FgeZXsYz0mbZ02PxuC2x0ckIQWwkhRbyqL/iy9ZlAQeKjWdidWhuL7bIrPcOrV2ppif6UTKaAckLNcR8ZEujAxiDnJKIkH/As1tItx3cB8tWFMG3ug0c75NSv9D674pnrddxC0yeBc1FGRkKsieYWyGHu4I4HKAt8Lbn2SVs4HzkzVwY+XGbUs6uxVRBIRatQMtUygKlS3jRdljZ3Yzd3zNr5lDZwwgJTUs/QPbXEMIA7IaEV11rCx01xS/epuW4JZqFStM1xOt4S83uyoBxNDopcC8E4ZSCt3OInbg8ocbzYdihs21XS6FsldR9tYUndkr0Qhb0xMGCd9CT/mVDGmfPtvCDXf4uEbxr6tWKegnUvv+FLGhj+byXJMBb8zB61Z1PnY0Ph5p3lWv2wD4jDOiCmSysHxGYaVKi7q3Hjc/gGspY7/HNEUebUBxwneegxE4LZknjl4rWk6a3B5mceztap8f8jKz1qa0YoCsrrJoLXPIE+3NaxhU+WfK2RyEsvKtiyqXadmEJzWjNbGeSE2Buxzp/5BbOvincnpQIFb5dIYQiiOrNVE3Q6NyaVKLAP+9jXcallPKOauSiL9Dkj+SInFxPwCxt9IyNS93p6lg63b5umemDhXfi3GLO3f/qr0xdV/B+htXH9cq72vB7int+HiCsQZVNjPBeSews39TncrJSTbiYToYJXYFOvHW4V7qLo435rYKRdmxqz1o7aZJurzgZAxHk9+R5bezYEiT19ltY1NfgPbuc4cO0oNgqjSB0g7Sf1C9867SP789pX68LGIA+BhT4vJ3vaD2FOEHMTc22fXwgyY4dKPIIh/BFWitCt1X0Y+S+Qn++NcsCzry/hlHgmm2O+aoBqS1V0FY3yPAFXkGt4gGC5LEXVSwkeaohZqB44iX9LI1J+1iqcLQZNGXDvnqPcY4vrKosvYA0UTGgkssumavA1pMA+z3ZMbRAgKav3m6O1JoJBz+wz0m7eNYBSfXuSzyCxtWX7/CIefsZ532sUvGa0InGWGGdibHb10/PkJimN7yVQsWsLrA9Xozm0fV/NWFklEL6zeY8cO4iiLWHG9k16/UYLrs8axR4ZuKfmpZEb+Wf04uWKf8SiYo7rmfoRUfF5DK8meZnc+FgrpfwpWuWkrBedpo1ZTjHBsuE4wNGs75czEvh7mvtVxQbOtVnkle/Efo4gPfK3aq0z8yujX8c8gstv0gkTsW6PKVnXMaEiizHNqBooFvgH+Ax0IiH8lzg+q7mX1/ajl5J+bnLvPInCiF988wzP9P/u1X3hG72ohJY+DhqmnMhIYHf9izC2znFi7iKrNF+aJjR1dMsH2vRKaLVPlh/SGvTi93D58+xzcEjOl+NjgEoz7WcGaPAJbEzizi+U8bBz4sYFJvS8HT1GbGQJmmsFhep5fOT6yECfREYfUGt+SBPDprk24eJX6K+1U81nBhS79F7hyNUWq4tvIL1VGA2epRM9E+55pUvYoOqTxGkrmoHJk7bhm2xlKc7GiNMvzw9d/yiQ9nybTDztpEnsbeoTTGkcktUKD3TSFI/j6WNBl1FzzQa8LdGthFz8UmXgK652t5FwD8tp9gpIvoFA+hEZOy8Ju4+FqCgso6UDRTN0iJftba4dQMHYR13gHhIWQ46x9x97S70+CORQ6yo0Ki+jP69KddvFiPyjsgr8d9p8/HqkAq3F5qdLNsZqaQfj9pgCMzWizA4N3CfbEAtDZn6qAFJqyp8V5QjIcZ36uU/qZvLMd6pAGlilixccG7LsrhYDyliWCBK3QxDOW+RV/gDq+uouYS9N0mk5cDAtbhvFM+NNBJbCNFy/ER1dLYIRNxOrLqODExFZr/qAgRAX9p1pmzaeILoAeFW7aQT4kWeZ7lP77WnZrIg1kYzt3RQMEX8kmL7f1rwfYTC+C4wffa3dqb6i6wpr2ojIz6N7HoPlO+qB1qDClm9urWG1UBY/Fde1sJiX4tDYrRfuyDlasVQFQt772rtnKKk5giPI2W+ccLiEMyWkIsEk1hmwDlh9hf6Z9QTiF9naiaKplqj23NGDPGQ7+aKNo8ORzKvFnCs0lkVWFO3V82l7kE8x70ZCC6Rp9v4hhXDkDRrEIiYFD10hz+dKURknY8E3xMu7sfBLWYKi8m97pKy0CPEfM/i7+8D092HNeRwYdy/LhZx4= ``` * Form submissions once received are sealed (encrypted) and stored * Can only be unsealed with the secret key that only the form admin has. Any changes (even a single character) to the sealed data makes the unsealing fail as the data would be corrupted. * This results in a submission that is *write-once* and *tamper-proof.* * Form submissions are non-fungible * Submissions are uniquely assigned to a response ID and cannot be replaced or exchanged. * Form submissions are write-once only during submission. Copies of the submission, including through emails, PDF copies can be used for easier processing. However, it is important to retain the secret key and access the data through FormSG in the event of a dispute. *** {% tabs %} {% tab title="Singpass" %} ### :flag\_sg: :closed\_lock\_with\_key: Singpass & Myinfo option **Step 1: Click into "Settings" at the top** This can be found to the top navigation bar in your form.
After clicking settings, click on "Singpass" on the left navigation panel.
**Step 2: Enable Singpass authentication** Toggle/on the following: * Enable Singpass authentication * Collect NRIC/FIN/UENs with form submissions
After enabling Singpass authentication, respondents must log in with Singpass before filling the form.
**Step 3: Create Myinfo fields (optional)** With MyInfo, users can automatically pre-fill selected personal data fields using verified information from government sources, after providing consent through Singpass. Navigate to Create -> Add fields
Under the MyInfo tab, you will see MyInfo fields that can be created.
Each of these fields will state whether the data is verified for specific groups (Singaporeans, Permanent Residents, Foreigners with Singpass). If there is a green checkmark, it means that this is verified and the pre-filled information cannot be edited.
**Step 4: Receive output** If form admin's email was included in the email notifications settings, they will receive an email response with the unique response ID and submission timestamp.
If "Collect NRIC/FIN/UENs with form submissions" was toggled on, the NRIC will be captured in the response email under `Singpass Validated NRIC` . If MyInfo fields were created and submitted, they will also be captured with the `[MyInfo]` tag added. You may save this email for audit purposes. To view the responses later, you may also navigate to the form's Results and enter the secret key.
Open the form response by clicking its response ID.
Each response page also shows the unique response ID and timestamp.
In this example, the MyInfo name will also be captured with the `[MyInfo]` tag.
There is also a `SingPass Validated NRIC` captured.
Optionally, you may save this as a PDF: * Right-click anywhere on the page. * Select **Print**. * In the printer destination, choose **Save as PDF**. {% endtab %} {% tab title="Email OTP" %} ### :e-mail: Email OTP option **Step 1: Click onto "Add Fields" icon.** This can be found to the left panel in your form.
**Step 2: Create an "Email" field** To quickly find the field, you may use the search function.
**Step 3: Rename field name and toggle options** The default field name can be changed. The Email field also has several options that can be toggled on.
**Step 4: Set OTP verification (optional)** If you enable "OTP verification", the respondent will be required to verify their email using a One-Time Password before submitting. This ensures that the email address is valid and the respondent is the owner.
**Step 5: Restrict email domains (optional)** If you enable "Restrict email domains", only email domains listed will be allowed to be entered into the field.
This will be useful in scenarios such as allowing only your agency emails to be entered.
**Step 6: Receive outputs** If form admin's email was included in the email notifications settings, they will receive an email response with the unique response ID and submission timestamp.
The email address will also be captured in the response email. Notice that there is a `[verified]` tag added by FormSG. You may save this email for audit purposes.
To view the response later, you may also navigate to the form's Results and enter secret key.
Search for the response ID and click into it.
Similarly, the unique response ID and timestamp will be included in each response's page.
In this example, the email address will also be captured with the `[verified]` tag.
Optionally, you may save this as a PDF: * Right click on the page * Click on "Print" * Change printer destination to "Save as PDF" {% endtab %} {% tab title="Checkbox" %} ### :ballot\_box\_with\_check: Checkbox option **Step 1: Click onto "Add Fields" icon** This can be found to the left panel in your form.
**Step 2: Create a "Checkbox" field** To quickly find the field, you may use the search function.
**Step 3: Rename field name and options** The default field name can be changed.
In this example, we changed the field name to Declaration (or Acknowledgement) and options to clauses (or terms & conditions).
**Step 4: Set selection limits (optional)** In this example, the clauses must be checked completely in order to submit, hence we can set a minimum selection limit equal to number of clauses.
**Step 5: Receive outputs** If form admin's email was included in the email notifications settings, they will receive an email response with the unique response ID and submission timestamp.
The declaration and clauses will also be captured in the response email. You may save this email for audit purposes.
To view the response later, you may also navigate to the form's Results and enter secret key.
Search for the response ID and click into it.
Similarly, the unique response ID and timestamp will be included in each response's page.
In this example, the declaration and clauses checked will also be captured.
Optionally, you may save this as a PDF: * Right click on the page * Click on "Print" * Change printer destination to "Save as PDF" {% endtab %} {% endtabs %} :question: Refer to [FAQs](https://guide.form.gov.sg/faq/faq/signatures) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://guide.form.gov.sg/user-guides/advanced-guide/signatures.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.