OBJECTIVE: Check whether a service describes the same intake event consistently to its sender and reviewer. Use harmless synthetic documents in an authorized test environment, or perform a paper walkthrough. Do not upload malicious files, private records or invented live cases.
1. Define Four Outcomes
Prepare scenarios for a form without an attempted attachment, a rejected attachment, an accepted attachment awaiting review and an evaluated attachment. Write the expected receipt and reviewer status for each before testing.
For the rejection case, use a harmless file type that the documented test configuration does not accept, or simulate the response. Do not attempt to defeat the restriction.
2. Compare Both Views
Follow the synthetic submission to its receipt. Record whether the receipt identifies the accepted material and any unresolved problem. Then inspect the authorized reviewer view. Does it distinguish a rejected attempt from an absence of any attempt?
An accepted form with a rejected attachment is the key edge case. The expected result should not imply that all submitted material arrived merely because the form has a case number.
3. Follow the Approved Alternative
Use the documented recovery route or model it on paper. Check how the replacement reaches the same case, how the sender knows it was accepted and who verifies that it can be reviewed. Do not create duplicate cases solely to work around unclear instructions.
If a conversion is part of the route, inspect whether the information needed for the exercise survives. Record any limitation rather than assuming visual resemblance establishes equivalence.
4. Repair the Summary
Introduce a synthetic summary stating that no evidence was supplied. Correct it to reflect the observed intake history, then identify any decision that relied on the earlier statement. Preserve the distinction between correcting that history and accepting the document’s substantive claim.
Completion criterion: sender and reviewer views agree about what arrived, unresolved failures have an owner, and technical rejection is not presented as evaluation. The walkthrough does not certify the security of the upload system.
Read Intake Is Not Evaluation and the fictional Unopened Attachment for context.