Many standards organisations continue to rely on specialist XML conversion providers to transform Word documents or PDFs into structured XML. For some, this is a legacy of earlier publishing programmes; for others, it remains the most practical way of handling complex documents or publication backlogs.

There is nothing inherently wrong with this approach.

In fact, during ISO's large-scale XML transformation programme, more than 25,000 standards were successfully converted into structured XML through carefully managed conversion workflows involving specialist suppliers. At that scale, external expertise was essential to meeting ambitious timelines.

The important lesson, however, was that successful XML conversion was never simply about choosing the right vendor.

XML Quality Doesn't Happen by Accident

High-quality XML is the result of robust quality assurance.

Regardless of where conversion takes place, organisations need clearly defined business rules, comprehensive validation procedures, experienced reviewers and sufficient editorial resources to verify that the resulting XML accurately represents the source document.

Without these controls, XML quality can vary considerably.

The reality is that the quality of any XML conversion is only as good as the quality assurance framework surrounding it.

The Hidden Operational Costs

Managing an external XML conversion process also introduces operational overhead that is often overlooked.

Editorial teams need to prepare files, review converted XML, manage supplier queries, resolve issues, monitor quality metrics and coordinate delivery schedules. Procurement teams may periodically need to retender conversion contracts to ensure continued value for money, while contract management and supplier governance become ongoing activities in their own right.

None of these activities directly improve the content itself—they are simply part of managing a separate production process.

Bringing XML Creation into the Editorial Workflow

Modern publishing workflows offer an alternative.

Rather than treating XML conversion as a separate production stage, icTools generates standards-compliant STS XML as part of the editorial process within Microsoft Word. Validation, structural checking and XML construction occur while editors are still working on the document, allowing issues to be identified and resolved immediately.

This eliminates the need for a separate conversion workflow for both routine and highly complex standards documents.

The result is not only faster production but also greater transparency, simpler quality assurance and reduced operational overhead.

A Better Way Forward

Structured XML remains one of the most valuable assets a standards organisation can create. But creating it should not require managing an entirely separate production ecosystem.

By integrating XML creation directly into the editorial workflow, organisations can reduce complexity, improve quality and free their editorial teams to focus on what matters most—producing high-quality standards.