# Synthetic document test recipe

Version: 19 September 2026. No customer data. No processed output is included.

Create a DOCX titled Renewal summary with the following paragraph:

Customer Morgan Hale is reviewing account AC-48217. Contact morgan.hale@example.com. The next step is to review the renewal on Friday.

Add a two-column table:

| Field | Value |
| --- | --- |
| Customer | Morgan Hale |
| Email | morgan.hale@example.com |
| Account reference | AC-48217 |
| Next step | Review renewal on Friday |

## Two separate app tests

### ChatGPT web

Record the exact browser, extension and ChatGPT interface. Attach the document with the file button. Repeat drag-and-drop separately. Ask for a short renewal brief. Record the configured action and inspect any returned document and actual submitted content.

### Claude web

Record the exact browser, extension and Claude interface. Use its document attachment path, then separately test drag-and-drop. Ask for a short renewal brief. Do not carry the ChatGPT result over to Claude.

## What to inspect

- Whether the configured identifiers are protected before submission.
- Whether the remaining paragraph and table are readable.
- Whether unrelated content is preserved.
- Whether a blocked action stays blocked without employee override.
- Whether the event and employee notice match that attempt.
- Whether any restoration/download behavior is included in the test scope. Restoration is not upload redaction.

Use separate synthetic workbooks/PDFs for formulas, hidden sheets, comments, scanned pages or unusual document structures. Keep those results not-tested until actually checked. This recipe is not a claim that all formats or input paths behave identically.