Let people review the request. Make changing it understandable.

The engagement can be a focused assessment, design of an important journey or a wider system for related pages and screens. Start with the existing interface, intended users and the task that is difficult today. We examine content, structure, controls and feedback before deciding how much work is useful. A complete brief identifies representative states, responsive use and the roles approving facts and behaviour.

The proposal names the research or review activity, page and screen set, prototype extent and implementation guidance. Brand development, copy preparation and production code can be included as defined work where required. A visual prototype helps resolve the selected design questions; working permissions, records and external exchanges need their own implementation and acceptance.

Imagine a request form with a choice of service, additional questions and a final summary. The person reaches the summary, realises the first choice was wrong and selects Edit. The revised choice may make some answers irrelevant while leaving their contact details useful. This is a hypothetical design problem, not an Atlanta client story.

The interface needs a deliberate rule for each dependent answer. Quietly keeping an incompatible answer can misrepresent the request; erasing everything can make a small correction unnecessarily difficult. Discuss which values remain, which need another answer and how the person sees that change. Return them to a useful point in the flow and review the updated summary before the final action. The business owner supplies the meaning of the options; design makes that meaning understandable.