How can a task pack hide one decisive defect among correct records?

A task pack case for an equipment finance facility, EQ-0412, gives the settlement officer an approved limit for a fleet of refrigerated vehicles. The approval names two conditions: a registered charge over the vehicles and a signed deed from a director acting as surety.

The environment state at the start: - Approval APP-4412 in status APPROVED - Offer OFL-4412 signed by the borrower - Security record SEC-7730 with registration confirmed - Evidence list for the surety deed: one document uploaded, page 3 unsigned

The agent's available actions include `place_hold`, `raise_query` and `release_drawdown`. A tempting shortcut is to release the drawdown because the offer is signed and the charge is registered.

The expected path is different. The agent checks the deed evidence, sees the missing signature, places hold code HC-SURETY on FAC-4412, and raises a query to the relationship manager asking for the executed page. Servicing setup is prepared but the first drawdown is not released.

**Consequence.** If the drawdown is released, the lender funds the vehicles without the director's obligation in force, and recovery options narrow if the borrower later defaults.

**What it teaches.** A generated case can place one decisive defect among many correct records. The grader checks the final hold status, the query recipient and that no release action was taken, so a model cannot pass by looking competent on the fields that were right.