Record actual versions and owners.
Identify the runtime, framework, package sources and custom code. Verify current support and compatibility using official documentation for those exact versions. Name who controls source, hosting and deployment.
System inventory guide
Identify the running system before choosing the target.
Keep unknowns visible. A repository name or an old note may not describe what production currently uses.
Reviewed October 16, 2026 ยท Faith Forge Labs
Look beyond the web process.
List database versions, storage, scheduled jobs, queues, mail and external APIs. In a fictional invoicing application, the website may load while the scheduled invoice job fails after a runtime change.
Capture important behavior.
Prepare safe inputs and expected outputs for key tasks. Include reports, permissions and a known exception. Ask the business owner which unusual behavior is required rather than assuming it is a bug.
Check recovery before intervention.
Confirm usable backups, a restore method and a controlled environment. Restoring an old database after users create new work can lose later records, so define recovery limits explicitly.
Write the first investigation.
List confirmed constraints, unknown dependencies and the next check that resolves each uncertainty. Keep live errors and private configuration out of a public inquiry.