Documents and signaturesBuild a document to sign

Build a document to sign

Turn a waiver, release or agreement into something people can sign on a phone at the door.

Waivers, media releases, volunteer agreements: write them once in eSign, place the signature fields, publish, and send them as often as you need.

Before you start: you need eSign access to see the area, and permission to author document templates to build one. Sending is a separate permission again, so the person who writes the waiver and the person who sends it do not have to be the same person.

Start a document

eSign > Templates, then New eSign Template

A template is the reusable version: write it once, send it a hundred times.

Name it, and choose where the text comes from

Four ways in:

  • Start from a Givable starter: a media release, an event liability waiver, a media release for a minor, or a volunteer agreement. Fill in the placeholders.
  • Upload a PDF, and place fields over its pages.
  • Upload a Word document, review the text, then continue.
  • Write it here, in the text editor.

Continue to fields

Givable renders your text into fixed pages and opens the canvas.

Add your signers

One row per person who signs, in signing order. Drag to reorder, or tick Everyone signs at the same time so they can sign in any order.

Place the fields

Drag from the Fields palette onto the page. Quick add signature block drops a signature, a date and a name together, which is what most documents need.

Publish

A published document is one you can send. The header tells you what is left to fix before you can.

A starter is a starting point, not legal advice. Have your own counsel read anything people will actually sign, especially where minors, media or liability are involved.

What you can place

FieldFor
Signature, InitialsThe signing itself.
Date signedFilled automatically when they sign.
Full name, Email, Company, TitleWho they are.
Text, Checkbox, Choice, DropdownAnything else you need them to answer.

Alongside fields you can place ordinary content: text, images, shapes, a QR code and tables.

Select any field and its settings appear on the right: who fills it, its label, whether it is required, what it must be (text, an email address, a phone number, a number or a date), and Show only when, so a question appears only when an earlier answer calls for it.

Every signer needs a signature field and a date signed field of their own. Givable will not let you publish without them, which is exactly the check you want before a hundred people sign the wrong version.

Filling fields in, and getting answers back out

Two different things, worth keeping straight:

  • Prefill puts what you already know into the document, so a supporter is not typing their own name again. Link a signer to a supporter or lead, then choose the field to prefill from. They can still change it.
  • Matching decides what happens to their answers afterwards. On the Matching stage, each signer can be left alone, matched to an existing supporter or lead, or matched with a new lead or supporter created when there is no match. Then map each document field to a record field, and choose whether it only fills blanks or overwrites.

Signatures and initials are never mapped to a record. They live on the signed document, where they belong.

How long a signed copy is good for

Valid for sets a lifetime: a waiver signed two seasons ago is not a waiver for this season. Leave it empty when a signed copy never expires. Expired means unsigned at the door.

Versions

The title opens version history. Opening an older version shows a banner telling you that you are looking at history, and nothing changes until you save. Return to latest brings you back.

Changing the document text after fields are placed clears those fields, because they belong to the pages that are about to be re-rendered. Givable warns you before it does it.

Still stuck?

We're here for you, and no question is too small. Tell us what you were trying to do and what happened, and we'll help you get it sorted.