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

# Contracts, invoices & forms

> What clients do in the portal — sign contracts, review invoices, fill out forms, and follow updates, all in one branded place.

Once a client is [in the portal](/features/client-portal/inviting-clients), it becomes their home for acting on their events: signing agreements, filling out what you need, and seeing what's owed. This page walks through each of those, from the client's side.

## Signing contracts

Contracts you send for an event show up in the client's portal — on the **Contracts** page and on each event's **Contracts** tab — with a status so the client always knows where things stand.

<Steps>
  <Step title="Open the contract">
    The client selects **Review & sign** on a contract that's ready for signature.
  </Step>

  <Step title="Sign in the portal">
    The signing window opens **right inside the portal** — the client never leaves. Signing is powered by **SignWell**, and the signature is recorded against the document with a tamper-evident audit trail.
  </Step>

  <Step title="Done">
    Once signed, the contract shows a **signed** state with the date. An already-signed contract simply confirms it's complete.
  </Step>
</Steps>

<Note>
  On enterprise plans, contracts can be signed under **your** brand rather than Soundcheck's — see [white-label branding](/features/contracts/white-label-branding). The full lifecycle (draft, sent, signed, declined) is covered in [contracts & e-signatures](/features/contracts/overview).
</Note>

## Reviewing invoices

The **Invoices** page gives the client a plain view of the deposits, balances, and payment requests your booking team has shared — each with an amount, a due or paid date, and a status. The dashboard also summarizes their **open balance** and recent invoices at a glance.

<Info>
  The portal shows invoices for the client to review — it isn't a checkout. Collect payment through your usual [payments](/features/gigs/payments) workflow; the portal keeps the client informed of what's due and what's settled.
</Info>

## Filling out forms

Forms you assign to a client — questionnaires, intake, or feedback — appear on the **Forms** page and on the relevant event, each showing its purpose, any due date, and whether it's still **required** or already **submitted**.

<Steps>
  <Step title="Open the form">
    The client selects **Fill out** on a form that still needs a response.
  </Step>

  <Step title="Complete it in the portal">
    The form opens embedded in the portal under your branding. Answers go straight to your booking team on submit.
  </Step>

  <Step title="Submission is confirmed">
    The portal confirms the response. For **JotForm** forms this happens the instant the client submits; for **Form.io** forms it confirms once the response reaches Soundcheck. Either way it's recorded against the right customer or event.
  </Step>
</Steps>

<Card title="Portal forms" icon="clipboard-list" href="/crm/integrations/portal-forms">
  How your team builds forms in JotForm or Form.io and assigns them to clients.
</Card>

## Following updates

Each event has a **Messages** area where your booking team can share updates and replies in one place, instead of scattered email threads. The portal's **Messages** page routes the client into whichever event they want to catch up on.

Every event workspace also shows the **notes** and any **files** your team has shared for that event, so the details a client needs travel with the event rather than living in someone's inbox.

## A note on what's shared

Clients only ever see what's tied to their own customer record — their events, their contracts, their forms, their invoices. You control what appears by linking gigs to the customer and assigning forms and contracts. When in doubt about what a specific client will see, [preview their portal](/features/client-portal/inviting-clients#preview-the-portal) first.

## Related pages

<CardGroup cols={3}>
  <Card title="Client portal" icon="browser" href="/features/client-portal/overview">
    The full picture of what clients see.
  </Card>

  <Card title="Contracts & e-signatures" icon="file-signature" href="/features/contracts/overview">
    How contracts move from draft to signed.
  </Card>

  <Card title="Inviting clients" icon="user-plus" href="/features/client-portal/inviting-clients">
    Get a client into the portal.
  </Card>
</CardGroup>
