Skip to content

Automation & Orchestration

Document automation: documents are outputs, not attachments

Most quotes start as a copy of the last one, with the old customer's name still in the footer. Document automation builds each document from the record and an approved template, sends it for signature when it needs one, and files it under the job with a name anyone can find, so nobody retypes, renames or drags files into folders.
Discuss your systemSee three documents ↓
Job J-544customerM.D.address9 Willow Ctworkreplace shut-off valveparts1 × ¾" valveprice$180Quote template v5{customer}For: M.D.{address}At: 9 Willow Ct{work}Replace shut-off valve{parts}Parts: 1 × ¾" valve{total}Total: $180Q-262_9-Willow-Ct.pdfgeneratedsent for signature14:02, in the portalsigned by M.D.15:12filedJobs / J-544 / Quotes

Documents are outputs, not attachments

In most offices a document is something a person makes: open last month's quote, change the details, save it somewhere, attach it to an email, chase the signature, drag the signed copy into a folder. Each step is a chance for the wrong name, the wrong price or a lost file.

Document automation makes the document a step in the workflow. The data comes from the record, the wording from an approved template, the name from a convention, and the destination from the job. Signing, sending and filing happen as part of the same run, and the record knows which version went out.

Three documents, one pattern

Different documents, the same four questions: where does the data come from, which template, where does it go, where is it kept.

Q-262 · extra work

data from
job J-544, price list v8
template
quote v5
goes to
the customer, for signature in the portal
filed
Jobs / J-544 / Quotes
name
Q-262_9-Willow-Ct.pdf

Four rules for documents nobody retypes

  1. One template per document

    Approved wording

    Each document type has one current template. Changing it is a decision, and the version is recorded.

  2. Data from the record

    Never retyped

    Names, addresses, prices and dates come from the systems that own them.

  3. A name and a home

    Findable later

    Every document gets a name by convention and a place under its job or account.

  4. Versions kept

    What went out

    If a document changes, the earlier version is kept, and the record knows which one the customer signed.

What document automation hands off

In

The record
job, customer, prices
Template
approved, versioned
Rules
naming and filing
Document step
fill → send → sign → file

Out

Document
named, versioned
Signature
when it's needed
Record updated
what went out, when

Worth building when documents are copied from old ones

Good fit

  • The same kinds of documents are made from records again and again.
  • People copy last month's document and edit it.
  • Finding a signed copy means searching someone's inbox.

Not the right fit

  • Each document is bespoke and written from scratch.
  • A handful a month, and the current way works.

Where it's built in

Next to document automation

Questions about document automation

Can we keep our existing templates?

Usually. Your current Word, Google Docs or PDF layouts become templates with fields where the data goes, so documents look the way they do today.

How does signing work?

Through an e-signature tool you already use, or the customer portal. The signed copy comes back to the workflow, is filed, and the record is updated.

Where are documents filed?

Where you already keep them: a shared drive, your job system or a document store, under a folder structure you agree once.

What do you build it with?

Often a document-generation step in n8n or Trigger.dev, your e-signature provider, and your existing storage. These are starting candidates, not requirements.