Apply / your decision record

Make the call.
Explain your decision.

Identify the facts that matter, any missing evidence and the next action. Name the responsible role and explain what would change your decision. Do not assume that an unmentioned approval, exception or assessment exists. Allow around 8–12 minutes.

One useful record

YOUR CASE / MONITORING AFTER RELEASE

A high-risk creditworthiness system starts producing unusually low scores after an upstream data-format change. A deployer reports that eligible applicants were rejected, including a cluster from one region. The provider has not yet established the cause. The support team proposes waiting for the monthly dashboard before escalating.

Your output / a practical record

Post-market monitoring and incident record

Make the next decision explicit. Connect it to evidence, unresolved questions and an accountable role.

Draft: Post-market monitoring and incident record

1. System, event, source and time of awareness2. Affected people, consequences and immediate containment3. Serious-incident and other reporting trigger assessment4. Responsible roles, recipients and reporting clocks5. Evidence, cause analysis and corrective action6. Validation, communications and closure criteria

Check your reasoning

I recorded the data-format change, unusual scores and reported rejection impacts without inventing a cause.I separated known facts from reporting-trigger and severity questions requiring review.I assigned immediate containment, reporting assessment and corrective-action owners.I preserved awareness times and evidence, with validation and closure criteria.

This is a self-review. Compare with the worked example if you need help. Every field needs a response of at least 10 characters; text length does not assess its quality.