What is the Gatheroo signature field?

The Gatheroo signature field is a coming-soon feature that will allow end clients to sign directly within a request — eliminating the need for printing, scanning, or separate e-signature tools.

Can I get clients to sign documents online as part of onboarding?

Yes — electronic signatures are increasingly common in professional client onboarding. Many tools offer a dedicated signature field where clients draw or confirm their signature digitally. Gatheroo is adding a Signature field to support this directly within a client request, so you can collect acknowledgements and sign-offs without needing a separate e-signature tool.

Is an electronic signature legally valid?

In most jurisdictions, electronic signatures are legally valid for a wide range of document types under laws such as the eSign Act (US), the Electronic Transactions Act (Australia), and eIDAS (EU). The key requirements are usually that the signer consented, intended to sign, and the signature is attributable to them. Always check the specific requirements for your industry and jurisdiction.

Signature Field in Gatheroo

What this does: The Signature field lets you collect legally-recorded signatures from one or more contacts within a Gatheroo request. It is designed for situations where you need a client, trustee, or other party to formally sign off on a document or declaration.

Setting up the field

When you add a Signature field to a request, you can customise it with the following options:

Field name: give the field a clear label, such as “Client Signature” or “Trustee Declaration”
Make this field mandatory: require the signature before the request can be marked complete
Include a “signing as” choice: display radio button options (e.g. Myself, Trustee) so the signatory can indicate the capacity in which they are signing. You can add as many choices as needed, and optionally enable an “Other” free-text option
Display as horizontal vs. vertical list: controls how the signing-as choices are arranged on screen
Lock fields when signed: prevents changes to the signature after submission (enabled by default)

How it looks in your builder

Selecting “include a signing as choice” will display a list that you can amend – whether you are asking someone to sign as a company official, trustee, parent etc. You can add as many choices as you need.

When you look at the request on your “Preview” tab, you will see the field is greyed out. This is expected.

How it works for your contacts

Each contact with access to the request sees their own signature field, labelled with their name.

They are asked to:

Select the capacity in which they are signing (if “signing as” choices are enabled)
Print their full legal name
Enter the date of signature
Draw or enter their signature in the provided field
Click Submit Signature

A client view of a signature being completed

Multiple signatories

If your request includes more than one contact, each person receives a unique link and sees a separate signature field assigned to them.

In the Gatheroo “Publish and Send” tab, you can see and amend which contacts are required to sign via the Required to sign toggle on each contact’s link.

Contacts who are not required to sign can still be shared the request link – they simply will not have an active signature field assigned to them.

Each contact will see a signature field for each contact required to sign, but they will only be able to sign the field connected to their unique magic link URL.

You are only able to add 1 signature field per request. The signature field option will be greyed out if you have already used this field in the current request.

Example with 2 contacts

ClientA will see 2 fields as both contacts are set to be required to sign, but the second field is locked.

ClientB will also see 2 fields, and the first is locked as it is allocated to ClientA.

A note on the signing-as choices

The “signing as” options (e.g. Myself, Trustee) are configured by you in the request builder. These are not legally-binding role assignments – they are a declaration by the signatory of the capacity in which they are acting. Make sure your choices reflect the options relevant to your use case before sharing the request.