> ## Documentation Index
> Fetch the complete documentation index at: https://docs.valaclaims.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Forms & vSign

> Prepare supported forms, review values, and collect electronic signatures.

## Overview

Use **Forms** in a Client record to prepare supported VA forms and eligible reusable organization documents, review the information shown, and collect electronic signatures through vSign. Available forms and sending options can vary by organization configuration.

<img src="https://mintcdn.com/vala/Kbb5xaypKnuoA7df/images/client-record/forms.png?fit=max&auto=format&n=Kbb5xaypKnuoA7df&q=85&s=fa9898b3d478e8baaf830e9712b3ebfe" alt="The Forms tab with Draft, In Review, Sent for Signature, and Signed columns." width="1440" height="900" data-path="images/client-record/forms.png" />

*The Forms board tracks a document from preparation through signing.*

## Before you begin

* Open the correct Client record.
* Verify the Client information, form fields, and intended recipients.
* Confirm that the form or reusable document is available to your organization.

## Prepare and send a form

<Steps>
  <Step title="Add or generate the document">Use the available form or eligible reusable organization document option.</Step>
  <Step title="Review populated information">Open the document, review the populated values, and edit where the form supports editing.</Step>
  <Step title="Move through review">Use the current board columns: <strong>Draft</strong>, <strong>In Review</strong>, <strong>Sent for Signature</strong>, and <strong>Signed</strong>.</Step>
  <Step title="Confirm recipients">Before sending, verify every form field and recipient. Review any visible warning about unpopulated form fields.</Step>
  <Step title="Send and monitor">Send for signature, follow the signing status, and review the signed result before relying on it.</Step>
</Steps>

## Signing choices

You can send a single document for signature or create a multi-document signing packet when at least two eligible documents are available. Where supported, a saved **Primary POC** can supply contact-mapped fields and the Client-side e-sign recipient while Client identity fields remain the Client's. For each send, you can choose or override the POC without changing the saved Primary POC. With no saved Primary POC, the Client's own contact information is used. Choose **Client (self)** to use the Client's own information for the Client-side contact and signing role.

## Best practices

* Verify every form value and recipient against approved information before sending.
* Use the Primary POC only when it is the appropriate contact for that send.
* Review the signed result and preserve it according to your organization's process.

## Related pages

<CardGroup cols={2}>
  <Card title="Details" icon="user-pen" href="/veteran-records/client-details">Verify Client information before preparing forms.</Card>
  <Card title="Relationships" icon="users" href="/veteran-records/relationships">Set or review a Primary POC.</Card>
</CardGroup>
