Technical writers are usually the only person in the building whose job is writing, which means nobody edits them. Engineers review for accuracy, product managers review for messaging, and the prose itself — structure, consistency, whether a procedure actually works when followed — goes unchecked from draft to publication. Writers know this, which is why so many have a private list of pages they are not happy with and no time to return to them. A second professional reader is the one resource the role is structurally denied.

We edit what technical writers produce and the documents that shape that work — user guides, administrator documentation and procedures, API and developer documentation, release notes and knowledge base articles, documentation plans and audience analyses, style guides and terminology decisions, structural proposals for reorganising a documentation set, topic templates and authoring guidelines, content audits, and the business case for documentation resourcing that many writers end up making alone. We also edit the professional material writers need for their own careers — CVs, portfolios, writing samples, proposals and rate letters for contract work, and conference proposals. Our editors are used to working within an established style guide rather than imposing preferences, and we will tell you which of your rules are actually being followed.

The audience and task analysis is the document that determines the quality of everything downstream, and it is the one most often skipped because it produces no publishable output. Without it, scope is set by whoever asks loudest and the documentation set grows to cover everything equally. We work with writers on this so that it names the distinct reader groups and what each is trying to accomplish, so that the tasks are ranked by frequency and by the cost of getting them wrong, and — the part that makes it valuable — so that it states explicitly what will not be documented and why. That written decision is what lets a writer decline the fourteenth request for a page nobody will read, and it is the strongest evidence available when arguing for another writer, because it turns a workload complaint into a scoped, costed proposal.

Everything you send is treated in confidence, including unpublished documentation, internal plans and career material. Whether you are a lone writer with no one to review your work, a contractor preparing a portfolio, or a documentation lead making the case for a bigger team, we can give your writing the second read the role rarely provides.