Resident and Field Engineer playbook
Capture local proof, preserve command context, and connect physical observations to the shared path.
Primary responsibility
The resident or field engineer grounds the incident in local reality. They can verify cabling, power, indicators, environmental conditions, device state, site differences, and command output that remote teams cannot observe directly.
Preserve context
Every command record should include purpose, target, timestamp, access level, expected signals, actual result, and whether the command was read-only or changed state. Screenshots without host, time, or scope often become unusable during escalation.
Compare sites and peers
When possible, compare the affected asset with a known healthy peer using the same method and time window. Record differences in configuration, firmware, topology, load, environment, and recent work. A peer comparison narrows the boundary faster than collecting more unrelated logs.
Stop conditions
Stop and escalate when access is unclear, a command could alter production state, physical safety is uncertain, evidence preservation would be compromised, or the expected target cannot be confirmed. Local presence does not replace authorization.
Expected outputs
Observed state, command evidence, photographs or site notes when appropriate, affected-versus-healthy comparison, local owner confirmation, and a concise handoff to the remote or specialist team.