> For the full site index see https://www.fenwickautomation.com/llms.txt > Every page has a Markdown version at the same URL with .md appended. # How to pick the one document to automate first Score your documents on repetition, judgement and whether the data exists, and the order picks itself. Why the gate usually beats the monthly report. 10 September 2026 · 5 minute read Pick the document with the most repetition in it, the least judgement in it, and facts that already exist somewhere a system can read. Score your shortlist on those three things and the order picks itself. Sometimes the winner is not a document at all. It is the check that should happen before anyone starts writing one. ## Which document should you automate first? The one that is most repetitive, needs the least judgement, and draws on information you already record. If two documents come out level, build the cheaper one, because the first build has to pay for the second. That is the short answer. The rest of this is how to score them, and why the document with the biggest yearly cost against it is often the wrong place to start. ## Start from the list, not from the worst offender If you have worked out [what your paperwork costs you a year](https://www.fenwickautomation.com/writing/what-paperwork-costs-your-business-a-year.md), you have a list of documents with hours and pounds against each of them. The temptation is to take the top line and start there. That is usually a mistake. If the top line is the monthly client report, it is usually the last thing to build, not the first. A report is assembled from data that has to exist before anything can assemble it. Start there and the early weeks go on fixing job sheets rather than saving anyone an afternoon. So take the few that cost the most, and put each one through four questions. ## Test one: how much of it is the same every time? Take the last several versions of the document and read them side by side. Mark the parts that change. In a method statement for the same kind of work, it is often the site address, the access arrangements, the plant on site and the paragraphs of sequence. Everything else is identical, and someone retypes or re-checks all of it anyway. The rough rule: if most of the words are the same every time, the document is worth drafting from your own templates. If every version is genuinely different, leave it alone. There is nothing there to automate, only writing to do. ## Test two: how much judgement is in it? Judgement is not the same as difficulty. Pricing a job from a rate card is a rule, even a complicated one, and a rule can be written down. Deciding that this particular client will walk if the price goes over a certain figure is judgement, and it stays with the person. Count the decisions in the document that could not be written as a rule your team would all agree with. A few are fine, and they become the points where the draft goes to a named person. If there are many, you are not automating a document. You are trying to automate someone’s experience. Leave that document with the person. ## Test three: does the information already exist? For each document, ask where the facts come from. If the site address, the order number and the scope are already in a job record, an inbox or a spreadsheet, a system can read them. If the only place they exist is in the head of the person writing the document, or in a phone call that never got written down, there is nothing to draft from. This is the test that quietly moves things down the list. It is also the easiest one to skip, and skipping it is how a first build runs late. Somebody’s spreadsheet turns out to be doing more work than anyone admitted, and it has to be sorted out before it can be relied on. ## Test four: what does it cost when it goes out wrong? This one does not change the order much, but it changes what you build. A quote with last month’s prices in it costs you margin. A generic method statement on a live site costs a great deal more than margin. Nothing is fully automated where a mistake costs money or safety. That is a permanent rule here, not a phase we grow out of. What the test decides is where the sign-off sits and how much of it there is, not whether a person is involved at all. ## Why the check usually wins Now put the check on the work coming in through the same tests. It can outscore every document on the list. Look at where the time on a method statement or a quote really goes. Often it is not the typing. It is that the job arrived without the drawing, the site address or the order number. Somebody had to chase them before a single useful word was written. Fixing the document does not fix that. A [job-intake gate that stops half-specified work](https://www.fenwickautomation.com/services/lead-qualification.md) does, and it is the cheapest thing on the list to build because it has no judgement in it at all. It compares what arrived against a list you wrote, and drafts the request for the rest in your own wording, for you to check and send. That is why it makes a good first build. It is cheap, it pays back fast, and it makes every document downstream easier, because the facts are all present before the drafting starts. ## What the order tends to look like For a firm doing site work, the gate is likely to come first. Then the document that is mostly boilerplate, usually method statements or job packs. Then quoting, once the pricing rules have been written down and agreed. Reporting comes last, once there is clean data to report on. Yours may differ, and it should, because the scoring is done on your documents rather than on a template. But if your order has reporting first and the intake check nowhere, it is worth going back through the four tests before anyone builds anything. ## Doing it on your own documents Take the most expensive documents on your list and score each one on the same simple scale for repetition, for freedom from judgement, and for whether the facts already exist. Add the three scores. Build the winner. Already know which document eats the most time in your week? [Book the 10-minute call](https://www.fenwickautomation.com/contact.md) and describe it. You will leave knowing whether it fits, with a rough estimate: a range for the first route. If it’s not worth doing, I’ll say so. The paid audit does the scoring on your real documents. It gives you what your paperwork costs a year, in your own figures, and what to build first. **Blake Fenwick**, founder of Fenwick Automation Some of the systems we've built, running right now. [More about Blake Fenwick and how we work](https://www.fenwickautomation.com/about.md). [Blake Fenwick on LinkedIn](https://www.linkedin.com/in/blake-fenwick-a5ba95433/) ## Related - [Lead qualification: the route this piece is about](https://www.fenwickautomation.com/services/lead-qualification.md) - [How to work out what paperwork costs your business a year](https://www.fenwickautomation.com/writing/what-paperwork-costs-your-business-a-year.md) Last updated: 10 September 2026