By team

SignAndGo for larger organisations.

A district council team, a national franchise, an iwi trust's commercial arm or a multi-site health provider has different questions from a two-person firm. How will this sit beside our systems, who controls access, and how do approvals work? This page covers what SignAndGo offers at that scale, a pilot worked through step by step, and how to talk to us.

Control over who does what

Workspaces have admins who manage members and their roles. Two-step sign-in adds protection to each account. Templates can be shared across the workspace so every branch sends the same approved wording, while private templates let a specialist keep drafts to themselves until they are ready.

Approvals inside the flow

Larger organisations rarely let a contract go out without someone checking it. Add an approver who reviews the document before anyone signs, or after everyone has. A procurement lead can approve supplier terms before the supplier sees them; a general manager can give final approval once the other party has signed.

Review-only envelopes cover the documents people must confirm they have received rather than sign, such as an updated policy or a site induction pack.

Connecting to your own systems

The API and webhooks let your developers build SignAndGo into the systems you already run, such as an HR platform or a customer portal, and receive notice as envelopes change status. Organisations on Xero can file signed documents there automatically. Staff who use an AI assistant can connect it to check on envelopes and send documents.

A worked example: supplier onboarding in procurement

Here is how a regional council's procurement team might run a first pilot. The council is invented for illustration, and the documents are its own.

  • The team builds one template holding the supplier agreement, the council's code of conduct for suppliers and a supplier details form.
  • The form has text fields for the supplier's NZBN, bank account and insurer, a date field for when their insurance renews and an upload field for the certificate of currency.
  • A procurement lead sits as an approver before signing, so no agreement reaches a supplier until its schedule has been checked.
  • The supplier's authorised person signs, and a general manager gives final approval after signing.
  • A webhook tells the council's contracts system when each envelope completes, so the supplier's status changes there without anyone retyping it.
  • After four weeks the team reviews the envelopes that stalled and why, adjusts the message and the reminder setting, and only then offers the template to other departments.

What tends to go wrong at scale, and the fix

  • Old wording in circulation: retire superseded templates as soon as the new one is shared.
  • An envelope sent to a supplier's general inbox: name the person who will sign, so the right person is the one who acts on it.
  • A signer who should not be signing: the audit trail shows each name, email address, time and IP address, so it is clear who acted. Send a fresh envelope to the right person.
  • Terms queried mid-way: the supplier declines with a reason, the envelope stops, and procurement sends a corrected one.
  • Staff changes: make removing leavers from the workspace part of the standard exit process.

Questions your security team will ask

Expect questions about access control and record keeping, and answer them with specifics. SignAndGo records every view and signature with names, email addresses, times and IP addresses, issues a completion certificate, and gives each signed document a verification ID anyone can check online. Our privacy policy lists the services we use.

What to send us

Enquiries are handled by email at sign@signandgo.com.au. A short note saves a lot of back and forth. Tell us:

  • Roughly how many people will send documents, and how many envelopes go out in a typical week.
  • The documents involved, for example supplier agreements, staff onboarding or customer forms.
  • Any systems you want SignAndGo to connect to, and whether you have developers available.
  • Who decides, and any timing you are working to.

Frequently asked questions

How do we start a conversation?
Email sign@signandgo.com.au with a short description of your team, your documents and the systems involved.
Can approvals happen after signing as well as before?
Yes. An approver can review before anyone signs, or give final approval once everyone has signed.
Can our developers connect SignAndGo to our systems?
Yes, through the API and webhooks, which let your systems send envelopes and hear when their status changes.
Can one department keep its templates separate?
A template can be shared with the workspace or kept private to the person who made it.
Can staff confirm they have read a policy without signing it?
Yes. Send it as a review-only envelope and each person confirms they have received it.

See SignAndGo for your team

Send your first envelope in a few minutes, and keep every signed copy with its audit trail.

Get started