Make stale-tab changes visible before they overwrite newer work

What to change

Ask the supplier to demonstrate how the interface identifies stale information and supports a deliberate resolution.

A worked example

Illustrative example

A practice manager edits a draft contact page in one tab and later saves an older copy in another. The interface flags the conflict for review.

How to check the result

Accept when conflicting stale edits produce an understandable decision and the visible result matches the selected resolution.

A mistake to avoid

Merely showing a generic save failure does not tell the visitor that their page is older than the stored version.

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 recordOpen a fictional editable record in two tabs. Change and save a value in the first, then attempt a conflicting change in the second.Inspect the second tab's response. Ask the supplier to show whether it refreshes, warns or offers a review route rather than silently treating old content as current.Choose a supported resolution and verify the final displayed values in both tabs. The visitor should know which version was retained.

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.