Reuse a document template

A reusable document template keeps the wording and layout for repeated requests while collecting the details that change. Use it for a recurring agreement, acknowledgement or consent process whose structure stays consistent.

Decide what belongs in the template

Keep approved wording, headings and explanatory text in the source. Identify the values that vary, such as customer name, reference number and service date. Keep each signer's identity and signature area separate so the completed document is unambiguous.

For example, an equipment agreement can reuse its terms while collecting the equipment reference, customer details and dates for each request. A manager's signature is a different task from the customer's signature, even when both appear on the same page.

Prepare and map the source

1. Start through Google Docs or the PDF upload path.
2. Review the extracted questions against the intended blanks. Remove accidental questions created from ordinary document text.
3. Map the changing answers to the correct locations. Check repeated values and similar names on later pages.
4. Configure the actual signer roles and whether people sign in one submission or through a workflow.
5. Preview a completed example before using the setup repeatedly.

Validate each new request

A reusable setup still needs the right recipient details. Check any prefilled name, date or reference before sharing. If a recipient may change a supplied value, decide whether the current field permissions should allow that change.

Inspect the generated PDF with a short and a long answer. A mapping that works for a short name may need more room for another customer. Confirm that signatures and dates appear under the intended person, and that any relevant attachment is available through the configured record workflow.

Updating the template

Review an updated template as a new document configuration before collecting more signatures. Check fields, placements, roles, notification content and output names after changing wording or page layout. Preserve the completed records of earlier requests as the records of what those people actually signed.

Use custom PDF generation for output design, prefill and permissions for known values, and signed records for the completed result. If an output is missing a value, check the question and its mapping before changing the source again.