Can a release include stale, conflicting or defective documents, and still allow 'proceed'?

**Can a release include stale, conflicting or poor-quality documents?** Yes, a buyer can ask for variation along defined axes. Typical ones:

- Expired or superseded versions of a document - Name, address or date mismatches between documents - Missing pages, unsigned forms or unreadable sections - Duplicates sent twice under different titles - Irrelevant attachments that look relevant - Late replies that only partly answer an earlier request

**Are these axes independent?** They can be combined, but a pilot should usually start with one axis per case so a failure can be traced to a cause. Combined cases suit later stages.

**Can the correct answer still be 'proceed'?** It should be, for a share of cases. A set where every file has a defect teaches an agent to always ask. Also ask for clean-but-unusual files, such as one that uses a permitted substitute document.

**How realistic are the defects?** That is for a buyer to inspect. The output is generated, so check a sample against what your own staff see, and look for patterns that are too tidy or too easy to detect from formatting alone.

**Can defect types be tied to a policy?** Yes. Each defect can reference the requirement it breaks, so the label is derived from the policy and not added afterwards by hand.