We begin with a short description of the present workflow and one representative example. For a repair, that could be a reproducible error with private information removed. For a portal, it could be the steps a member follows today.
Agree the first deliverable
Discovery identifies what needs investigation and what can already be estimated. The written scope names screens, data connections, content responsibilities and acceptance examples. A change that introduces a new workflow is discussed before it is added.
Review work in manageable pieces
Preview links, written questions and short demonstrations let your team review without a permanent meeting schedule. We agree overlap hours around UK and US working days, including seasonal clock changes, rather than assuming a fixed difference all year.
Prepare for everyday use
Acceptance covers the main task, a failed attempt and recovery. Handover includes account ownership, relevant source or configuration, maintenance responsibilities and an explanation suitable for the people taking over. Ongoing support is separately scoped.