Changelog

Last Updated: August 16, 2026Scope: Customer-visible changes to the Parry platform

This page records changes to the Parry platform that affect what customers see or do. Changes marked significant are additionally communicated by email to each customer’s designated contact, in line with our customer notification policy.

Availability incidents are not recorded here — those are notified by email to each customer’s administrative contact and covered by our Service Level Agreement.

August 14, 2026

More reliable document analysis

A contract whose analysis failed can now be re-submitted straight from chat instead of appearing stuck, and a failed run no longer produces an empty deal record with no supplier or value.

Duplicate uploads caught earlier

Uploading the same document twice — from any entry point — is now detected before a second analysis is dispatched, so you are not billed twice for the same work and the pipeline does not fork.

August 12, 2026

Significant — customers notified

Original documents are always kept

Every route that accepts a document — upload, batch upload, chat, email scan, and connected cloud storage — now stores the original file and records that it did. Previously some routes read a document for context and discarded it, so the source was not available to open later.

Erasure now covers draft revisions

A GDPR erasure request now removes draft revision history along with the rest of the record, and the disposition is recorded in the register.

August 11, 2026

Significant — customers notified

Open the contract behind a finding

The source document can now be opened and downloaded from the deal view and from an approval card. If Parry prices a clause, you can read that clause.

Contracts dropped into chat run the full pipeline

A contract attached in chat now goes through the same analysis as any other intake path — findings, opportunity, and supplier context — rather than being read for context and discarded.

Deal detail reads as a statement

The deal screen was rebuilt to read as an audited record: figures in a single ink colour, plain-language event descriptions instead of internal event keys, and empty fields that say what is actually missing.

August 9, 2026

Batch upload survives a refresh

Refreshing the page during a batch upload no longer loses the batch, and a batch where nothing was actionable now says so explicitly instead of appearing to have failed.

Clearer opportunity pipeline

Pipeline stage tiles are readable against the light theme, and each stage action now states what it will do before you take it.