Action Hub
Use the actions hub when the damage is already real and the next question is practical: preserve access, protect evidence, and move into the right workflow before the device or claim window gets worse.
Action first
Use this hub when the damage is already real and the practical question is what to protect or do next. Start with the workflow that keeps access, evidence, or safe use from getting worse.
Use the action paths below when you need to:
Back up a device before the usable screen area shrinks further
Use an action path when access matters more than more comparison.
Document the damage before the visible pattern changes
Capture evidence while the screen still looks like this and before the record gets weaker.
Move work to a safer display path
If the device still runs but the built-in panel is no longer safe to trust, the workflow comes first.
If you still cannot tell what changed on the display, go back to the symptoms hub before you choose a workflow.
Primary workflows
The strongest live workflow gets the most space. Supporting routes stay visible underneath so the taxonomy still feels complete without forcing equal weight where it does not belong.
Keep working
Use this when the computer still runs but the built-in panel is too damaged to work from safely.
This keeps access, backup, and evidence capture possible without pushing the damaged panel harder than needed.
Best next route
Open Workflow
Use the strongest live workflow first when the practical need matters more than more taxonomy.
Protect data
Use this first when the display is unstable but the device may still power on and hold a connection.
The backup window can close fast after liquid exposure, growing pressure damage, or worsening touch instability.
Preserve evidence
Use this when return, warranty, insurance, or trade-in value may depend on how clearly the issue is recorded.
Good evidence prevents vague support conversations and helps you switch from diagnosis to proof quickly.
Diagnosis bridges
Mechanism and symptom pages should support the workflow choice here, not compete with it. This section is intentionally quieter than the workflow section above.
Diagnosis support
Use this when a squeeze, flex event, or closed-lid pressure event is the strongest cause behind the urgent workflow problem.
Diagnosis support
Use this when liquid exposure or staged worsening changes the safest next move.
Diagnosis support
Use this when thermal exposure is the stronger explanation and the workflow decision depends on that context.
Diagnosis support
Use the symptoms hub when the visible pattern is still easier to identify than the cause or the workflow.
First-move guardrails
This hub should reduce avoidable mistakes when the damaged panel still matters. The emphasis is on safe sequencing, not on squeezing in one more round of casual experimentation.
Keep the next move clearer than the taxonomy.
Next move
Choose the workflow that protects access, evidence, or safe use first, then use diagnosis pages only to sharpen that decision.
Reviewed and maintained by Jacob Dymond
Founder, ScreenDetect
Last reviewed 2026-04-09
ScreenDetect maintains this hub as a practical branch of the damage system. The guidance is written to help users preserve access, evidence, and decision quality while still leaving room to route back into the right diagnosis page.
Source basis