Skip to content
Guides

Document automation: contracts and forms that fill themselves in

Vetrox · Published

The short answer

Document automation fills your own templates for contracts, forms and letters from the records you already hold, sends each document for e-signature and files the signed copy against the right record. It pays off for documents you produce often from the same template. Under Australia's electronic transactions laws an electronic signature is generally as valid as one in ink, but some documents have rules of their own, so check those before you automate them.

What document automation is

Most business documents are the same document every time, with a few details changed: the client's name, the dates, the amounts, which services or schedules apply. Document automation keeps the fixed wording in a template and takes the details from a record you already hold, such as the client in your CRM or the job in your operations system. Nobody opens last month's contract and types over it. For contracts it is often called contract automation.

It is the same idea as mail merge in Word, where placeholders called merge fields are filled from a data source such as a spreadsheet (opens in a new tab). The difference is what happens around it. A mail merge is run by hand, from a list someone has to prepare. An automated document is generated when the record reaches the right stage, goes out for signature and comes back to the record signed.

The picture below follows one contract along that path.

One contract, from the record to the signed copy

  1. 1

    The record is complete

    Names, dates, amounts and options are in your system, and nothing required is blank

  2. 2

    The template is filled

    Fields come from the record, and rules pick the clauses and schedules that apply

  3. 3

    A person checks the exceptions

    Standard documents go straight through. Changed terms wait for approval

  4. 4

    It goes out for signature

    Signers in the right order, with reminders for anyone who has not signed

  5. 5

    The signed copy is filed

    Saved against the record, together with the signing history

  6. 6

    The next step starts

    Tasks, the first invoice or a welcome email, with nobody forwarding the contract

The short version. The sections below take the steps in this order.

Which documents are worth automating

A document is a good candidate when most of these are true:

  • you produce it often, from the same template
  • the details already sit in a system, and someone copies them across
  • a mistake is expensive: a wrong name, an old clause, details left over from the last client
  • someone has to chase the signature
  • work cannot start until it is signed.

In most businesses that points to the same few: service agreements and engagement letters, employment contracts and new-starter forms, non-disclosure agreements, estimates and proposals, purchase orders, authority and consent forms, renewal letters and certificates.

Leave out the contracts that are negotiated clause by clause. A lawyer drafts those one at a time, and there is no template to fill. They can still be sent for signature and filed the same way.

Forms that come from someone else, such as a supplier's application form or an insurer's proposal, can be filled from your records too when the PDF has fillable fields. Check first that the organisation accepts the form completed and signed electronically. Australian Government agencies, for example, can set their own requirements (opens in a new tab) for signatures under their legislation, such as a particular signing platform.

Start with the template, and have it reviewed once

Collect every version of the document in use: the one on the shared drive, the one a manager keeps on their desktop, the one copied from the last client. Agree on one, and turn it into the master:

  • mark every detail that changes as a field, with a plain name such as “client legal name” or “start date”
  • mark each optional clause or schedule, and write beside it the rule that decides when it applies
  • lock everything else, so the wording is the same in every copy
  • give the template an owner and a version number, and print the version in the footer of every document it produces.

Then have the wording reviewed before it is automated, because automation sends the same words to every customer. The Australian Competition and Consumer Commission (ACCC) calls a pre-written contract that customers can only take or leave a standard form contract (opens in a new tab). Since 9 November 2023, proposing, using or relying on unfair terms in one has been banned, and penalties apply. The protection covers consumers and small businesses, which includes any business with fewer than 100 employees.

Two details matter for a template with options. A court deciding whether a contract is standard form also looks at whether the business has made other contracts that are the same or very similar, and how many times. And a contract may still be standard form when the other party can pick a term from a range of options the business has set. Offering a choice between your own clauses does not, on its own, make the contract a negotiated one. Only a court can decide that a term is unfair, so this review is a job for your lawyer: once for each template, and again whenever the wording changes.

Fill it from the record, not from memory

Every field in the template should come from one field in one system: the CRM, the job or order system, the HR system. If the same detail is typed in two places, decide which one the document reads, and connect the systems so the other copy follows it.

Documents need details that day-to-day work often skips. Add them to the record before you automate:

  • the legal name of the other party, not the trading name, and whether it is a company, a partnership, a trust or a person
  • who will sign, in what role, and the email address the document goes to
  • the details behind each rule: the state, the type of service, the length of the term
  • dates and amounts stored as dates and numbers, not as free text.

Then make them required. The document cannot be generated until the record is complete, so nothing goes out with a blank or a “to be confirmed”. If the details live in spreadsheets today, moving them into a proper system comes first.

Each generated document should record which template version and which values it used. When someone asks later why a contract says what it says, the answer is in the record.

Let rules pick the clauses, and a person check the exceptions

Rules are what turn a mail merge into a contract. Each one reads a field on the record and decides what goes into the document:

  • the type of party decides the signature block: two signature lines for a company signing by two directors, one for a sole director or a person
  • the state decides the governing law clause
  • the type of service decides which schedules are attached
  • the length of the term decides whether the renewal clause appears.

Keep the list short. A template with a handful of rules is easy to check. When a document needs dozens, it is usually two or three different documents, and each deserves a template of its own.

A document that follows the rules needs no review: that is the point. A document with anything outside them does. If someone changes a clause, adds special terms or sets an amount outside the agreed range, the document waits for approval before it can be sent.

Send a PDF, not an editable file. If a detail is wrong, correct the record and generate the document again, so the record and the contract never disagree.

AI has a place, but not in the legal wording. A fixed template gives the same clause every time, which is what a contract needs. AI is useful around it: reading the details out of an email or a PDF into the record, or drafting a description of the work from meeting notes for a person to check. Our guide to AI for business explains why work with one right answer every time is better left to a plain rule.

Electronic signatures: what Australian law says

This section and the next summarise official guidance. They are not legal advice: for a document that matters, ask your lawyer.

The Electronic Transactions Act 1999 is the Commonwealth law on signing and sending documents electronically. The Attorney-General's Department says it makes electronic signatures just as valid as signatures in ink for most Commonwealth processes (opens in a new tab). The Act names no particular technology. Section 10 (opens in a new tab) asks for a method that identifies the person and indicates their intention, and that is as reliable as appropriate for the purpose, or is proven in fact to have done both.

So, depending on the circumstances, a signature can be a name typed or drawn on a screen, an email that states acceptance, a ticked “I accept” box on an online form, or a signature made through a signing platform. A contract does not always need a signature at all: the ACCC notes that a buyer can accept one by signing, by saying so, or through actions such as paying or clicking “I agree” on a website (opens in a new tab). A signing platform earns its place because it keeps the evidence of who signed and when.

Three things to check before you rely on an electronic signature:

  • Consent. When the document goes to a private person or a business, you might need their consent (opens in a new tab) to the electronic method. It can be inferred from past dealings, but it is simpler to state it: a line in the document or the covering email saying it will be signed electronically.
  • The contract itself. Parties can agree on their own process, and a clause that requires paper may override the Act (opens in a new tab).
  • The state. The Commonwealth Act applies only to Commonwealth laws. Each state and territory has its own Electronic Transactions Act. They are generally very similar, but each may have different exemptions.

If the other side asks for a “digital signature”, ask what they mean. The department points out that the term is not used in the Act: some people mean any electronic signature, and others mean one with extra security features.

Companies, deeds and documents with rules of their own

Companies sign under the Corporations Act 2001, which has signing rules of its own: the department notes that parts of the Electronic Transactions Act do not apply to it (opens in a new tab). Under section 127 (opens in a new tab), a company may execute a document without a common seal if it is signed by:

  • two directors
  • a director and a company secretary
  • for a proprietary company with a sole director, that director, if they are also the sole company secretary or the company has no secretary.

Section 110A lets each of them sign an electronic form of the document by electronic means, under the same test of identity, intention and reliability, and they do not have to sign the same copy or use the same method. A company can execute a deed the same way, in electronic form and without a witness. Section 127 is not the only way a company can sign: an individual acting with the company's authority can execute a document on its behalf, and a company's constitution may set out other ways.

For automation, this becomes a rule. The record says what kind of party is signing and who signs for it, and the template adds the matching signature block and sends the document to each signer, so a document that needs two signatures cannot come back with one. Which way your documents should be signed is a question for your lawyer. The system then applies the answer every time.

Some documents have rules of their own and belong outside the first version:

For these, check the rule for that document before you automate it, or keep it on paper.

Send, chase and file without anyone doing it

Once a document is approved, it goes to the signers in order: usually the customer first, then whoever signs for you. Reminders go out on a schedule until everyone has signed, and a document that is declined or runs out of time goes back to its owner with the reason. Nobody keeps a list of who still has to sign.

When the last signature is in, three things should happen on their own:

  • the signed PDF is saved against the record and in the right folder of your shared drive, not left in the signing service or in someone's inbox
  • the signing history is kept with it
  • the record changes status and the next step starts: the team gets its tasks, the first invoice is raised, the customer gets a welcome email.

The signing history is your evidence. Google's eSignature, for example, adds an audit trail page to the end of the final PDF (opens in a new tab), with the time of each request and signature and each signer's name and email address. Let the signing service fill in the date each person signed too, instead of printing the day the document was generated.

Keeping the signed copy electronically is fine, on two conditions. The Attorney-General's Department's guidance on electronic records (opens in a new tab) is that they can be kept in place of paper as long as they can be reopened and read again, and the method used reliably prevents them from being altered. That is a good test for your own filing: keep signed copies as PDFs, in a place where staff can read them but cannot replace or change them.

With start and end dates on the record, a register of contracts can also warn you before one expires or renews.

What the tools you already have can do

Before anything is built, check what you already have against the steps above:

  • Word's mail merge fills a template from a spreadsheet. It runs in the desktop app, by hand, and stops at the finished document: sending, signing and filing are still up to you.
  • Microsoft 365 has content assembly (opens in a new tab), which turns a Word document into a template and generates documents from a SharePoint list, and eSignature (opens in a new tab), which sends PDFs and Word documents for signature, keeps an audit trail and also works with Adobe Acrobat Sign and Docusign. Both are add-ons billed by use, and an administrator has to set them up.
  • Google Workspace has eSignature (opens in a new tab) in Google Docs and for PDFs in Drive, on the Business Standard, Business Plus and Enterprise plans once an administrator turns it on. A request takes up to 10 signers, can send automatic reminders and ends in a final PDF with an audit trail.
  • Lark Base has an extension called DocuGenius (opens in a new tab) that lays a record out as a print template. With a Base automation, a PDF is generated from the template when, for example, a new record is added, and saved to an attachment field. Lark marks that automation step as beta, and an administrator has to add the extension first.
  • Your CRM, accounting software or e-signature service may have document templates of its own. When the details already live there, start there.

A built-in feature is enough when the details live in one tool and the document is simple. Building the workflow is worth it when the details come from two or three systems, when rules decide the clauses and who signs, or when a signature has to start work somewhere else. Then the document is one step in a larger process, and the system that runs that process should generate, send and file it.

Start with one document

Pick the document you produce most. Before it goes live, generate last month's documents again from the records and compare them with what was really sent. Every difference is either a gap in the data or a rule nobody had written down, and it is better to find them this way than in front of a customer.

Run the first few live documents past the person who used to prepare them. Then remove the old Word file from the shared drive, so there is one way to produce that document, and move on to the next one.

Where Vetrox fits

Vetrox is an Australian IT company that builds document automation for businesses across Australia. Your own templates stay the starting point: the fields come from the record, and rules pick the clauses or schedules that apply. The document goes out through the e-signature service you use, anyone who has not signed gets a reminder, and the record shows where each document is up to. When it comes back signed, the copy is saved to the right folder in your shared drive and the next step of the work starts on its own. We connect to each system through its own API, every run is logged, and a failure alerts a person. If a feature in a tool you already have covers it, we will say so on the first call.

Sources

  1. Attorney-General's Department: Electronic signatures (opens in a new tab)
  2. Attorney-General's Department: Choice and consent under the ETA (opens in a new tab)
  3. Attorney-General's Department: Exemptions to the ETA (opens in a new tab)
  4. Attorney-General's Department: Electronic documents, written information and records (opens in a new tab)
  5. Federal Register of Legislation: Electronic Transactions Act 1999 (compilation of 5 December 2025) (opens in a new tab)
  6. Federal Register of Legislation: Corporations Act 2001, sections 110A, 126 and 127 (compilation of 19 September 2026) (opens in a new tab)
  7. Australian Competition and Consumer Commission: Contracts (opens in a new tab)
  8. Microsoft Support: Use mail merge for bulk email, letters, labels, and envelopes (opens in a new tab)
  9. Microsoft Learn: Overview of content assembly (opens in a new tab)
  10. Microsoft Learn: Overview of eSignature (opens in a new tab)
  11. Google Docs Editors Help: Send signature requests and sign documents with eSignature (opens in a new tab)
  12. Lark Help Center: Automatically typeset and print with DocuGenius (updated 17 July 2025) (opens in a new tab)

Show us how your business runs today.

A 30-minute call to discuss the software you use, the work it handles and what needs to change.