A preview uses test credentials in the production package

What to change

Validate environment-specific destinations without exposing secret values in the review. Ask the supplier to show safe identifiers for production endpoints and explain which configuration source supplies them. Use an approved synthetic check to confirm the intended receiving environment after deployment. The acceptance evidence should distinguish public functionality from preview fixtures, while sensitive credentials remain in their appropriate protected management system rather than screenshots or handover documents.

A worked example

Illustrative example

Illustrative test: A harmless test action reaches the intended production service rather than a preview fixture.

How to check the result

The deployed environment mapping is correct and independently evidenced.

A mistake to avoid

Printing credentials into a release report creates unnecessary exposure.

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 recordList environment-dependent endpoints using non-secret identifiers.Compare the release configuration with the approved production mapping.Run an authorised synthetic request and verify the receiving environment.

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.