Skip to content

Feature

Documents drafted from your approved sources

Draft reports, spreadsheets and other supported outputs from approved sources, where those types are switched on for the deployment you buy.

Updated 21 Aug 2026

Definition

Asset and export workflows exist in the product; marketed formats still need release-level testing and configuration review.

01

What the product supports

What a deployment actually offers depends on the release you are buying and how it is configured.

  • The mechanism is built
  • Availability varies by release
  • Scope varies by configuration
02

How to evaluate it

Use representative documents and record the expected result before running the test.

  • Source retention
  • Template consistency
  • Export fidelity
  • Reviewer approval
03

What procurement will ask for

Record enough for someone else to run it again: how it was set up, what kind of documents went in, who ran it, where the data went, what happened when it failed and who reviewed the result.

  • Configuration and source types
  • Users and data path
  • Failure behaviour and reviewer
  • Operational dependencies

What this page does not prove

  1. B1A mechanism that exists is not a guaranteed result.
  2. B2Configuration decides what is available, where data goes and who supports it.
  3. B3Regulated decisions remain with authorised people.

Test the claim on your documents

Pick a real piece of work, agree what a good answer looks like, then go through the results together.