Avoice for technical directors

Every set that leaves the office, checked

You can't personally review every drawing, spec, and submittal, but the quality is still on you. Avoice checks every set to your standards before it goes out, so nothing slips through while you're looking elsewhere.

Book a demo

Office master

Your office master, under your control

Your master specification is years of decisions about systems, products and wording. Avoice makes it the starting point of every spec, so project teams draft from what you approved instead of copying the last job.

  • One master, every team. Approved clauses, section templates and prelims in one versioned library across the practice.
  • Enforced as they draft. House rules and preferred products are applied while the spec is written, not checked at the end.
  • Fix it once. Correct a master clause and every new spec follows the correction.
See Practice Voice
Read the office master guide →

Your standards, enforced on every project

You set the conventions. The question is whether they're actually followed on every job, by every team, under deadline. Avoice applies your technical standards consistently across the practice, so quality doesn't depend on who's on the project or how late it is.

/ 01

Own the office master

Set the practice's master clauses, prelims and house rules once. Every team drafts from them, without you chasing each one.

/ 02

Errors caught before they reach site

Clashes, missing clauses, schedule mismatches, and coordination gaps flagged automatically, while there's still time to fix them and before they become site problems.

/ 03

Standards compliance, every time

NBS, Uniclass, NATSPEC, CSI MasterFormat checked on every spec, so nothing goes out non-compliant regardless of who wrote it.

/ 04

Visibility across every project

See the technical health of every job in one place, so you know where the risk is before it surfaces, not after.

/ 05

Junior work, senior quality

Avoice raises the floor on every team member's output, so a Part 1 draft leaves the office at the standard you'd sign off on yourself.

Questions

What technical directors ask us

Does accepting an AI draft count as reasonable skill and care?

The test is your review, not the software. Issuing any draft unread, whether it came from a template, a past project or an AI, is hard to defend. A documented review is what holds up.

Avoice makes that review easier to do and to show. Every clause traces back to the drawing, report or standard behind it. Anything unresolved stays visibly flagged instead of being buried in prose. The spec is checked against the drawings before issue. A clause-level record shows who reviewed and accepted each change.

I'm philosophically against AI writing specifications. Why would I use this?

You don't have to change your view to test it. Treat Avoice like a new graduate whose work you haven't seen yet. Give it one live project, review its draft the way you would theirs, and keep your current process running alongside.

Better still, turn your objections into the test. Decide up front what would convince you: source accuracy against your own spot-checks, whether it missed anything your master would have caught, and how long the review took. If it fails, you've lost nothing.

If you'd rather not let it write anything yet, start with checking instead. Run a spec you've already issued through Avoice and see what it finds.

Can it be confidently wrong? How would I spot it?

Yes, like any drafter. Two things make it easier to catch. Every clause shows its source, so a claim with a weak source stands out. And where Avoice isn't sure, it marks the item to double-check instead of writing it with confidence.

Spot-check clauses that rest on general good practice rather than your project documents, and any clause that hinges on a specific number.

Who keeps the content current when a standard or regulation changes?

Avoice does, every day. Every standard is tracked by number, edition and withdrawal status, checked against more than 1,200 sources, alongside the Building Regulations and manufacturer product data. When something is superseded or withdrawn, Avoice shows the exact live projects and clauses it touches, so the change can be accepted or amended there and then, with an audit trail.

A record of what was current is also saved every time a spec is issued, so you can always show which edition a clause was written to.

If AI writes the spec, how do junior staff learn?

It's a fair worry. Deleting boilerplate you don't understand doesn't teach anyone either.

In Avoice every clause comes with guidance written for that project: what's missing, what needs deciding, and what to watch for. Anyone can ask a clause why it says what it says and where it came from. The reviewer still owns the outcome, so the review conversation between junior and senior stays where it was.

How does it handle fire safety and higher-risk buildings?

Clauses carry Building Regulations findings against the Approved Documents, and fire classifications cite their test standard, for example reaction to fire to BS EN 13501-1. Give it your fire strategy report and it writes to it.

It doesn't replace your fire engineer or the fire strategy. Where the strategy is silent on something the spec needs, Avoice flags the gap instead of filling it.

Read the guide: Higher-risk buildings guide

See all 93 questions