Operational questions for the first month after handover

Can the team identify the running version and environment?

Begin by connecting the running service to its source. Identify the deployed version, how the build was produced and the differences between verification and production environments. Apps and servers may have different release dates.

Document configuration locations, edit permissions and application procedures instead of copying every value into prose. Keep secrets in their intended management system and record access instructions.

A useful first deliverable lists environment addresses, version checks, deployment history and owners. It helps the team narrow a later report to a specific environment and change rather than investigate everything at once.

Can the team make and verify a small change?

Complete a low-impact change in a verification environment: fetch, edit, run relevant checks, deploy and inspect the result. Look for steps that still depend on undocumented manual work by the outgoing team.

Correct stale commands, missing tool versions and inaccessible dependencies as they appear. Have another person follow the revised instructions to expose machine-specific assumptions.

Production changes should follow the agreed approval and scope. Use the rehearsal to define pre-deployment checks, signals to watch during rollout and criteria for stopping. The exercise establishes operational capability rather than merely familiarity with documentation.

Where does investigation start when something looks wrong?

Connect user-visible problems to investigation evidence. Document how to find the occurrence time, version, operation type and correlation identifier. Review how reports and logs avoid unnecessary personal data.

Walk through representative problems: where to check service and authentication status when login fails, or how to compare application records with an external dependency when one operation fails.

Also establish whether recovery has been rehearsed. Identify the recoverable data and point in time, the person who can authorize recovery and a safe practice environment. The existence of a backup alone does not answer those operational questions.

Turn questions into reusable operating knowledge

Use early questions to improve the handover material. Record who answered, which environment was checked and which procedure worked, then link the result into the relevant document.

Distinguish tasks operators can perform, work requiring development and issues owned by an external supplier. Record support hours and contact paths as actually agreed.

At the end of the month, review unresolved questions and temporary workarounds. Assign owners to operational blockers, documentation gaps and future development. The aim is not an absence of questions; it is a dependable way to find an answer and maintain it for the next person.