← Work / Consultancy report production /

Document Studio

A consultancy publishes long, technical reports for councils and clients, and getting a draft onto their brand template was hours of fiddly Word work every time. We built them a private web app that does the re-templating in one pass — and refuses to hand back a document if a single word of the content has changed.

The guarantee

Never changes a word — and proves it before it exports

Tier

Studio

Built

Oct–Nov 2026

Document Studio app (full page)

The report was finished. Formatting it wasn’t.

This client’s work ends in documents — feasibility studies, needs assessments, strategy reports — and they’re long, technical, full of figures and tables, and they go to councils who circulate them onward. The writing was never the bottleneck. Getting a finished draft onto the current house template was: heading levels to reassign, typed-in numbers to strip so automatic numbering could take over, floating images to pin down, captions that had drifted away from the thing they captioned, tables to bring to the house look, a cover and contents page to rebuild.

Hours per report, on the least interesting part of the job, right at the point when the deadline is closest.

One rule above all others

A tool that reformats someone’s report has exactly one way to lose their trust forever: quietly change what it says. So the whole thing is built around a rule it isn’t allowed to break — it only ever changes formatting, never content.

That isn’t a promise in the documentation. Before the app will hand back a finished document, it diffs every word against what went in, and if anything differs that shouldn’t, the export aborts rather than producing a file. Two exceptions are declared and logged: tracked changes that were accepted, and manually-typed heading numbers removed so the template’s automatic numbering can do its job properly.

The gate has already earned its place — it caught a genuine regression during the build, which is precisely the sort of thing that would otherwise have reached a client’s report unnoticed.

What it actually does

Upload a Word document, choose the template, and the pipeline runs through the stages a person used to do by hand: accept tracked changes and clear comments, free content trapped inside invisible layout tables, repair headings that lost their paragraph mark or skipped a level, apply the real heading styles so numbering flows automatically, rebuild the cover and contents from the template, pull floating images inline and scale anything over the margins, move every “Figure X” and “Table X” caption back above its item and bind it there so a page break can’t separate them, normalise tables to the house look, then transplant the template’s styles, numbering, theme and running headers.

Out the other end: the formatted document, a PDF preview, and a companion report listing every change made and the page it happened on.

A second pair of eyes, clearly labelled

Two read-only review passes add notes a human then decides on — spelling, terminology and cross-reference checks on the text, and a visual pass over the rendered pages for stranded headings, awkward breaks and tables that have become unreadable.

They’re advisory by design. Findings arrive as notes with page references, and where there’s a safe mechanical fix it comes as a suggestion the user can tick to apply. Nothing is applied on the app’s own initiative, and both passes fail soft: if the review is unavailable the job still completes without them. A document never fails because the clever part had an off day.

Built to be unremarkable in use

A FastAPI service in a container on Fly.io in Sydney, scaling to zero between jobs, with LibreOffice doing the PDF rendering and a regression suite built around a synthetic worst-case document plus a real past report. The interface is a single branded page with the team behind an access gate, and uploaded documents are deleted from the server an hour after processing.

The templates themselves were a deliverable in their own right — the portrait and landscape Word templates the team now write into, which is what makes the automated side possible at all.

The screenshots here run on a de-branded copy of the app and a sample document, because the live instance carries the client’s brand and their confidential reports. The interface, the pipeline and the change log are the real ones.

Services

Product Design · Document Engineering · Template Design · Backend Development · AI Integration · Deployment & Hosting