From first report to verified closure

User Guide

Use Escalation Binder to coordinate the work happening now and preserve the operational record your team will need later.

Start in five minutes Share with your team

Quick start

Learn the workflow with the guided demo

  1. Launch Escalation Binder. On first use, choose Load Guided Demo. Later, use Load Demo in the main toolbar.
  2. Open Checkout API degradation. The demo contains a complete SEV1 response with realistic roles, references, updates, decisions, evidence, and follow-up work.
  3. Review the orange readiness card. It identifies missing or unfinished work without preventing you from documenting the response.
  4. Move through the binder. On iPhone, use the Section menu. On iPad and Mac, use the section strip.
  5. Open Export. Preview the readable Markdown packet to see how the full escalation record comes together.
The demo is safe and repeatable.

Loading it again reopens the existing demo and preserves your changes. It does not contact customer systems or modify another escalation.

Before the first escalation

Configure your workspace team

Escalation Binder uses one workspace roster for escalation owners, technical leads, communications leads, checklist owners, approvers, and follow-up owners.

  1. On the configuration screen, add at least one named team member.
  2. Enter the person’s name and role. Add the people who may own response work or receive a handoff.
  3. Choose Continue to enter the workspace.
  4. Use Configure Team in the main toolbar whenever the roster changes.

The roster is workspace-level. You do not need to recreate the same people inside every escalation.

Create the record

Start a new escalation

  1. Choose New Escalation from the escalation list toolbar.
  2. Give the binder a clear title, then select its type, severity, and status.
  3. In Overview, add the case number, owner, customer or business context, product, environment, summary, current state, and affected systems.
  4. Add known start, detection, mitigation, resolution, and closure times as they become available.
  5. Use the readiness card as a live review list. Blocking items identify information required for a defensible packet; warnings point to useful operational context.
Write the current state for the next responder.

State what is happening now, what has changed, and what the team believes. Avoid turning Current state into a long event log—the Timeline is the better home for sequence.

Active response

A practical operating sequence

1

Establish command

Assign the escalation owner, technical lead, and communications lead. Record the objective and next update time in Ops Map.

2

Map the sources of truth

Add the channel, bridge, ticket, runbook, dashboard, logs, customer thread, vendor case, and other references responders need.

3

Capture before classifying

Drop customer reports, notes, terminal output, links, and file references into Workbench. Promote them when their role is clear.

4

Preserve response decisions

Record stakeholder wording, decisions and alternatives, checklist progress, and complete handoff snapshots.

5

Verify recovery

Capture the recovery signal, validation method, monitoring window, stakeholder confirmation, rollback state, and remaining risk.

6

Export the packet

Review the Markdown report and preserve a JSON packet before a major handoff, archive, or deletion.

Inside the binder

What each section is for

Overview

Identity, ownership, short narrative, current state, important timestamps, tickets, tags, and readiness review.

Ops Map

The live operating plan and every location responders need: channels, bridges, tickets, runbooks, dashboards, logs, alerts, status pages, threads, documents, repositories, paths, queries, and access notes.

Response

Updates preserves exact stakeholder wording. Decisions records what was chosen and why. Checklist tracks required response steps. Handoffs captures state, risks, next commitments, and must-open references.

Workbench

A capture inbox for raw notes, email, chat, screenshots, terminal output, links, and file references. Use each item’s action menu to promote it to Timeline or Evidence, connect it to root-cause work, or associate it with an action item.

Timeline

The ordered sequence of alerts, customer reports, deployments, actions, decisions, status updates, handoffs, and other events. Include the actor, source, and exact time when known.

Evidence

Supporting material with source, path, notes, sensitivity, hash and capture metadata, managed-file controls, and an explicit Include in export setting.

Impact

Affected users, systems, regions, duration, business impact, scope, and related operational consequences.

RCA

Root cause, contributing factors, detection gaps, response gaps, prevention work, and durable learning.

Action Items

Owned follow-up work with priority, status, ticket link, and implementation detail. High-priority open actions remain visible in readiness review.

Closure

Recovery verification, monitoring period, stakeholder confirmation, rollback state, known remaining risk, follow-up ownership, and postmortem commitment.

Export

A complete Markdown report for people and a versioned JSON packet for backup, archive, or controlled transfer.

Private collaboration

Share one escalation with specific people

Sharing is per escalation. It does not expose the rest of your workspace, and it is deliberate packet synchronization rather than live field-by-field co-editing.

Owner workflow

  1. Open the escalation and choose Share with Team.
  2. Choose Publish Latest Changes to create or update the shared packet.
  3. Choose Manage Invitations, add the participant’s iCloud account, and select read-only or read-and-write access.
  4. Send the invitation using the collaboration sheet.

Participant workflow

  1. Accept the invitation on a device signed into the invited iCloud account.
  2. Review the incoming packet summary before importing it.
  3. If granted edit access, make changes and choose Publish My Changes.
  4. The owner chooses Refresh from Team, reviews the incoming revision, and confirms the import.
Publish and refresh are intentional.

Local edits do not silently overwrite someone else’s copy. Escalation Binder shows revision and recency warnings before replacing matching local packet records.

Participants need iCloud Drive enabled. Managed evidence file bytes remain on the device that imported them; collaborators receive the evidence metadata and documented location only.

Evidence handling

Preserve provenance without losing control of files

  • File reference: records where a source file lives without moving or changing it.
  • Managed original: copies a file into Escalation Binder’s private application storage and records a SHA-256 hash.
  • Redacted copy: keeps a separate working copy while preserving the managed original.
  • Classification and sensitivity: document who should handle the material and why.
  • Include in export: determines whether the evidence record appears in exported packets.

Managed imports have a 100 MB per-file limit. Source files selected from outside the app are never altered. Sharing and JSON export include metadata and paths, not managed file bytes.

Portability and backup

Export before handoff, archive, or deletion

Markdown

Use Preview Markdown for a readable report containing the response story, timeline, decisions, checklist, handoffs, evidence metadata, closure record, action items, and packet history.

JSON

Use Preview JSON, Copy JSON, or Save JSON for the complete versioned packet used by Escalation Binder’s import workflow.

Import

Choose Import JSON in the main toolbar and select a packet. Review the escalation identity, revision, and recency warning before confirming. Matching packet-owned records are replaced only after confirmation.

JSON is the recoverable working packet.

Markdown is intended for reading and review. Keep a JSON export when you may need to restore, transfer, or continue editing the binder later.

Finish responsibly

Close, archive, or delete

Before closing

Set the resolved and closed times, complete the RCA summary, verify recovery, finish the monitoring window, capture stakeholder confirmation, document remaining risk, and assign follow-up work. The readiness card identifies missing closure evidence.

Before deleting

  1. Export a JSON packet and, when useful, a Markdown report.
  2. Choose Delete Escalation from the escalation list toolbar.
  3. Read the confirmation carefully. An owner stops the related share and deletes the shared packet; a participant leaves the share.

Deletion removes the local escalation and app-managed evidence copies. Original files you selected from other locations are not deleted.

Troubleshooting

Common issues

Sharing says iCloud is unavailable

Confirm the device is signed into iCloud, iCloud Drive is enabled, and the device has network access. Then reopen Share with Team.

An invitation opens but no packet appears

Confirm the invitation was sent to the account currently signed into iCloud. Ask the owner to verify the participant remains invited.

The app warns that the local revision is newer

Cancel the import, compare the two copies, and export the local JSON packet before replacing anything. Import only when you understand which changes will win.

A collaborator cannot open an evidence file

File bytes do not travel in the shared packet. Transfer the file through an approved channel or provide a location the collaborator can access.

A readiness warning will not clear

Read the warning detail and update the named section. Required checklist steps, unacknowledged handoffs, open high-priority actions, and incomplete closure verification can all keep the binder in Review.

You still need help

Email support@escalationbinder.com with the app version and build, device model, operating-system version, screen, expected result, and observed result. Do not send confidential escalation content unless it is necessary and safe.