A button click is labelled as a completed request

What to change

Separate attempts from accepted outcomes in both event definitions and report language. A click may help diagnose interest or friction, but it does not show that the practice received anything. Ask the developer to identify the acceptance signal available from the actual workflow. Test a rejected attempt and an accepted fictional submission, then verify that the report describes their different states instead of combining them into one commercial result.

A worked example

Illustrative example

Illustrative test: A failed attempt appears only in the attempt measure, while acceptance has its own event.

How to check the result

The dashboard distinguishes attempted interaction from verified receipt.

A mistake to avoid

Changing the label alone will not repair an incorrectly fired completion event.

Your action checklist

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordTrigger an incomplete fictional request and inspect the emitted events.Complete an accepted test submission through the approved route.Compare report labels with the two observed outcomes.

Evidence, open questions and decisionsNext action and responsible role

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.