Systems Triage

Systems consulting triage worksheet.

Use this worksheet when the work is not just a parts quote: infrastructure troubleshooting, systems administration, buildouts, migrations, vendor decisions, documentation gaps, or a technical problem that does not fit a neat category yet.

Collect First

Details that separate symptoms from the actual work.

Current Symptoms

  • What is broken, slow, unreliable, undocumented, or blocked
  • Which users, offices, servers, VMs, applications, devices, or services are affected
  • When the issue started, whether it is constant or intermittent, and what makes it worse

Change History

  • Recent hardware, software, network, firewall, DNS, storage, backup, or vendor changes
  • New error messages, alert history, monitoring graphs, support tickets, or outage notes
  • Known deadlines: office move, license renewal, hardware failure, audit, launch, or cutover

Access and Impact

  • Who can approve access to servers, hypervisors, switches, firewalls, storage, backups, and vendor portals
  • Business impact, outage tolerance, maintenance windows, and rollback expectations
  • What has already been tried and what should not be touched without approval

Triage Output

A consulting engagement should end with usable next steps.

The useful result is not a vague recommendation. It should identify the current state, likely causes or constraints, immediate stabilization work, longer-term options, owner handoff, and the information still missing.

Good Fit

Use this path for random infrastructure problems that still need disciplined work.

Buildouts and Moves

  • Small office, server-room, rack, network, storage, and remote-access buildouts
  • Equipment selection, vendor quote review, cabling assumptions, and cutover planning
  • Documentation and handoff notes for the person who has to support it later

Troubleshooting and Cleanup

  • Slow systems, failing hardware, unstable services, backup gaps, storage pressure, or network weirdness
  • Messy ownership, stale documentation, old credentials, incomplete diagrams, and vendor finger-pointing
  • Stabilization first, then a practical repair, replacement, or migration plan

Migrations and Vendor Decisions

  • Platform changes, cloud-to-on-prem decisions, Proxmox planning, storage moves, and service migrations
  • Vendor quote review, technical due diligence, lifecycle planning, and replacement timing
  • Risk, downtime, rollback, and support expectations before work starts

Need Triage?

Turn the messy problem into a concrete next step.

Web Tech can review the current state, identify missing information, and help separate troubleshooting, replacement, migration, and documentation work.

Request Systems Consulting