Construction · Document management 2025–2026

Company standards editor

Reworking drafts to match the company standard

The task

A construction company with an internal standard for technical documentation: set margins, fonts, section structure, table formatting. Drafts arrive from different departments in varying states of readiness.

A technical writer reformatted every document by hand. Several days per draft. Some had a structure, some didn't, tables and images were scattered at random. If the standard changed, the instructions would have to be rewritten from scratch.

The task: turn a draft into a final docx to the corporate standard without losing tables, diagrams or meaning. One standard for now; the architecture had to allow other templates later.

The solution

The tool extracts the content while keeping tables and images, maps sections to the ones the standard requires and rewrites paragraphs in a formal style without changing the meaning. The output is a docx with the right font, margins and headers.

At the end it checks the result against a checklist and produces a report: which points of the standard are met and what needs a person's attention. The writer fixes the exceptions instead of every margin.

The stack is built around docx: python-docx for assembly, a separate layer of formatting rules, and an LLM for rewording without inventing facts. The prompt strictly forbids adding data that wasn't in the draft.

How it works

The pipeline: parsing the input docx or markdown, extracting the heading structure, matching it to the standard's template, generating placeholder sections for anything missing, marked "content required".

Tables and figures are carried over programmatically, without the model. The LLM touches only text blocks. This reduces the risk of "hallucinations" in numbers and dimensions.

The standard's checklist is stored in YAML: the item, the criterion, automatic or manual check. Adding a new corporate standard means a new rules file, with no code changes.

Industry context

Needs like "a company standards editor" and "automating technical documentation formatting" are typical for construction and design companies with their own standards. Regulators require consistency, while each department writes in its own way.

Word remains the handover format for many clients. The tool doesn't replace the engineer, but it removes hours of copy-pasting formatting.

The result

A document that used to take several days of manual layout is assembled in hours, with a final check by the writer. Tables and images are in place, and the structure matches the corporate standard.

How the work went

The first step was digitising the corporate standard: fonts, margins, numbering, table requirements. Without a machine-readable checklist, automation is pointless.

We ran ten old drafts of varying messiness. Based on them we set up the section mapping and the rules for when the LLM rewords and when it leaves the text as is.

The technical writer got a review mode: questionable paragraphs are highlighted, and there is a checklist report before the final docx is exported.

Adding a second standard for another branch is built into the config: the same engine, a different YAML file with rules.

For construction holdings with several company standards, this saves weeks of manual layout for every design department.

FAQ

Won't the model distort technical data? Tables and numbers are carried over programmatically. The LLM touches only text paragraphs, and the prompt forbids adding facts.

Does it only work with docx? The input is docx or markdown. The output is docx to your standard. PDF input would be a separate piece of work.

How many standards can be connected? The architecture is designed for several YAML configs. One corporate standard of the client is in production now.

Who checks the result? A technical writer or engineer. The system provides a checklist and a draft; a person carries the final responsibility.

Who it's for

Construction and design companies with an approved company standard for technical documentation. The more departments write drafts, the bigger the gain from a single pipeline.

Holdings with several branches can keep different YAML standards in one tool. The technical writer controls quality instead of copying margins.

If you hand over documentation to the client in docx under strict rules, a formatting error often matters more than an error in the text. Automatic checklist checks reduce rejections.

Compared with the alternatives

A Word template with macros breaks when a department sends a table of non-standard width. Assembling the docx programmatically keeps the layout more stable.

Outsourcing a technical writer for every document doesn't scale as projects grow. The tool takes care of formatting, and the writer focuses on meaning.

General LLM chats without the standard's checklist produce text that looks similar but fails the client's acceptance.

Summary

The technical writer moved from layout to content: the standard's checklist is closed automatically, and questionable passages are flagged before export. One corporate standard is in production, and a second one is added through the config.

For construction companies with their own standards, this removes a bottleneck when handing over documentation packages. Let's discuss your standard on a call and estimate how long it takes to digitise the rules.

Working with the studio

The first stage is digitising your standard into a machine-readable checklist. Without it, any automation would be guessing. We go through the standard together with the client's technical writer and record the exceptions.

The second stage is running archived drafts and setting up the section mapping. The third is training reviewers to work with the non-compliance report. Timing depends on how thick the standard is and how many document types there are.

How to start

Send us a sample of the standard and two or three drafts of different quality. We'll digitise the checklist and run it on your files. A call and a timing estimate take 30 minutes. Contact @vasilk1t.

We build a prototype for one document type in 5–9 days with no prepayment, so the technical writer can compare it with manual layout.

Development is based in Saint Petersburg; calls and demos happen by video for clients anywhere.

If the standard changes once a year, updating the YAML checklist takes a day. Documents from earlier periods can be run through the same pipeline in a batch.

Have a similar task? We'll go through it on a half-hour call. For new clients we build a working prototype in 5–9 days, with no prepayment.