Planning, implementation and handover.

We review recent examples with the people who know the process. For an approval workflow, that might mean a request form and its decision record. For reporting, it may mean the query and the source transactions.

Before reviewing private systems, we agree the access, confidentiality arrangements and people needed. Initial contact should not include passwords, customer records or unrestricted production access.

The written brief identifies what we will examine or change and what you will receive. It names the reviewers, acceptance conditions and dependencies on other teams. A review can establish missing detail before a build is commissioned.

We record who must resolve open policy, access or supplier decisions. If requirements change, we discuss the effect on scope, timing and fees before taking on the additional work.

We check the configuration or code against the agreed rules. Tests include cases the operating team will have to handle: a returned request in a workflow, for example, or a repeated event in an integration.

The people accepting the work review the test results and try the relevant operating tasks. We record unresolved issues and whether they prevent acceptance or need follow-up after handover.

Handover includes the agreed instructions, ownership and access information. Continuing monitoring, support or later changes need their own stated scope.

The handover can include configuration or code, test records and instructions for support. Its contents depend on the work commissioned.