Tool
E-signature forms
People search for e-signature when they want someone to sign a document. Request Forms has a drawn signature pad on the form. The mark is stored with the response. This is not DocuSign. There is no certificate, no send-for-sign envelope, and no legal e-sign program.
The job
Get a mark that the person saw the text and agreed.
What Request Forms can do
- A signature block with a drawing pad and a Clear control.
- Required signature on acknowledgements, waivers, and confirm steps.
- The drawing is stored on the response.
- Pair the pad with checkboxes, file upload, and payment.
What it cannot do
- This is not a legal e-sign product and not a certified signature.
- No send-for-sign workflow, audit certificate, or identity proofing.
- The drawing must stay under about 2 MB.
- Use it for acknowledgements, not contracts you must archive as signed files.
How to build it
- Insert a Signature block. Mark it required if the mark is mandatory.
- Put the legal text in a Text or Heading block above the pad.
- Add a checkbox such as I agree, if you need a second confirm.
- Publish and open the response to see the stored drawing.
When to pick each
Pick Request Forms
- You need an on-form mark for a waiver, photo release, or request confirm.
- The signature is one field in a longer Request Forms flow.
Pick another product
- You need DocuSign, Adobe Sign, or a certified e-sign audit trail.
- You need to send a PDF out for signature and store the signed file.
Questions
- Is a Request Forms signature legally binding?
- The product stores a drawing. It does not run a certified e-sign program. Ask your counsel before you treat it as a contract signature.
- Can I send a document out to be signed?
- No. The person signs on the published form. There is no envelope or signer routing.
Sources
Related tools
Write this form
Describe it in plain language, or build it field by field.