Prepare a non-sensitive sample
Use invented sample content clearly marked as a test, with participants who have agreed to take part. Do not use real customer agreements, personal data or a transaction as a convenient demonstration. Establish which product actions are authorized and whether a trial would create a payment commitment. This guide does not authorize a purchase or signup. The goal is to answer a limited workflow question without creating misleading operational evidence.
Test more than a successful click
Check the intended roles, required and optional fields, document readability and the requested signing sequence. Include a scenario that exposes the specific uncertainty you are evaluating, rather than pressing through only the easiest path. A preview can establish layout but may not demonstrate delivery. A submitted sample can establish one observed path but not long-term reliability. Label each result by what was actually exercised and what remains untested. W3C guidance explains why form controls need associated labels describing their purpose. Include that recipient-accessibility question; it is not a claim that this merchant has passed an accessibility audit.
Inspect the finished record
Open the resulting sample and compare it with the expected document and participant set. Where the product provides an associated audit record, check that the two can be related. Do not treat a success banner as a substitute for inspecting the output. Keep incomplete, declined and completed observations distinct. If a request outcome is uncertain, investigate its existing record rather than creating a second sample with an indistinguishable title.
Save a concise acceptance note
Record the sample version, date, relevant configuration, observed result and remaining questions. Avoid retaining real access links or codes in a broadly shared note. A later material change should trigger the affected checks again, not a claim that old acceptance covers new behavior. Use the requirements checklist as the reference so testing leads to a decision rather than an endless tour through every feature in the product.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Available fields and recipient assignment — Merchant documentation · help.signaturely.com · Merchant-controlled · checked 2026-09-21
- Send a signature request — Merchant documentation · help.signaturely.com · Merchant-controlled · checked 2026-09-21
- View and download the audit trail — Merchant documentation · help.signaturely.com · Merchant-controlled · checked 2026-09-21
- W3C WAI: labels identify the purpose of form controls — Standards and certification reference · w3.org · Publisher independence not verified · checked 2026-09-21