Workflow template

Incident Response Board for Nextcloud Deck as a normal Nextcloud Deck board.

An incident board for small teams that runs from the first signal through triage, mitigation, and monitoring to a blameless review. Severity is set early, and mitigation comes before root cause.

Last verified

Board preview

Incident Response

Reported1

Capture the first signal

Write what you observed before you start guessing why. The first note anchors the timeline.

  • What is broken, from a user's point of view
  • When did it start, as precisely as you can tell
  • What changed recently
  • Who is currently looking at it
Customer Impact

Triage1

Decide severity within five minutes

Severity decides who you wake up. Guessing low to avoid the call is the expensive mistake.

  • Is data being lost right now
  • Can users complete the core task
  • Is there a workaround they can use today
  • Escalate if you cannot answer within five minutes
Sev1Sev2

Mitigating1

Stop the impact before finding the cause

Roll back, fail over, or disable the feature. Root cause is a review task, not an outage task.

Customer Impact

Monitoring1

Watch before declaring it over

Give the system a full traffic cycle at normal load before you close the incident.

Follow-up

Review1

Run a blameless review

Look for the missing guardrail, not the person who typed the command.

  • Write the timeline from the cards on this board
  • Name what made detection slow
  • Name what made recovery slow
  • Create one concrete follow-up with an owner
Follow-updue in 5 days
Sev1Sev2Customer ImpactFollow-up
View the portable v1 template JSON
{
  "schema": "deckloud-template-v1",
  "schemaVersion": 1,
  "slug": "incident-response-nextcloud-deck",
  "locale": "en",
  "title": "Incident Response Board for Nextcloud Deck",
  "description": "A calm path from first signal to blameless review, with severity decided early and mitigation before root cause.",
  "category": "software",
  "tags": [
    "incident",
    "on-call",
    "postmortem"
  ],
  "quickCreateStackKey": "reported",
  "compatibility": {
    "requiresBoardCreate": true,
    "includesAttachments": false,
    "includesComments": false
  },
  "board": {
    "title": "Incident Response",
    "color": "DC2626"
  },
  "labels": [
    {
      "key": "sev1",
      "title": "Sev1",
      "color": "B91C1C"
    },
    {
      "key": "sev2",
      "title": "Sev2",
      "color": "F59E0B"
    },
    {
      "key": "customer-impact",
      "title": "Customer Impact",
      "color": "EF4444"
    },
    {
      "key": "follow-up",
      "title": "Follow-up",
      "color": "3B82F6"
    }
  ],
  "stacks": [
    {
      "key": "reported",
      "title": "Reported",
      "order": 1
    },
    {
      "key": "triage",
      "title": "Triage",
      "order": 2
    },
    {
      "key": "mitigating",
      "title": "Mitigating",
      "order": 3
    },
    {
      "key": "monitoring",
      "title": "Monitoring",
      "order": 4
    },
    {
      "key": "review",
      "title": "Review",
      "order": 5
    }
  ],
  "cards": [
    {
      "stack": "reported",
      "title": "Capture the first signal",
      "description": "Write what you observed before you start guessing why. The first note anchors the timeline.\n\n- [ ] What is broken, from a user's point of view\n- [ ] When did it start, as precisely as you can tell\n- [ ] What changed recently\n- [ ] Who is currently looking at it",
      "labels": [
        "customer-impact"
      ]
    },
    {
      "stack": "triage",
      "title": "Decide severity within five minutes",
      "description": "Severity decides who you wake up. Guessing low to avoid the call is the expensive mistake.\n\n- [ ] Is data being lost right now\n- [ ] Can users complete the core task\n- [ ] Is there a workaround they can use today\n- [ ] Escalate if you cannot answer within five minutes",
      "labels": [
        "sev1",
        "sev2"
      ]
    },
    {
      "stack": "mitigating",
      "title": "Stop the impact before finding the cause",
      "description": "Roll back, fail over, or disable the feature. Root cause is a review task, not an outage task.",
      "labels": [
        "customer-impact"
      ]
    },
    {
      "stack": "monitoring",
      "title": "Watch before declaring it over",
      "description": "Give the system a full traffic cycle at normal load before you close the incident.",
      "labels": [
        "follow-up"
      ]
    },
    {
      "stack": "review",
      "title": "Run a blameless review",
      "description": "Look for the missing guardrail, not the person who typed the command.\n\n- [ ] Write the timeline from the cards on this board\n- [ ] Name what made detection slow\n- [ ] Name what made recovery slow\n- [ ] Create one concrete follow-up with an owner",
      "labels": [
        "follow-up"
      ],
      "dueOffsetDays": 5
    }
  ]
}

01

When to use this board

For small teams that carry a pager and want the outage to follow a written path instead of improvisation. Severity is decided within minutes, mitigation comes before root cause, and the review looks for the missing guardrail rather than the person who typed the command.

02

How to run this board

  • Record the first signal.

    Write what you observed and when in a card in Reported before you start guessing at causes.

  • Set severity within five minutes, then mitigate.

    Use the triage checklist to decide who to call, then roll back, fail over, or disable the feature.

  • Monitor, then review without blame.

    Watch a full traffic cycle before closing, and run the review within five days to find the missing guardrail.

03

What this creates

5 stacks, 4 board labels, and 5 starter cards carrying 12 checklist steps. Attachments and comments are intentionally omitted so the template stays portable.

04

Why it fits Deckloud

The template is just a recipe for standard Deck objects. No hosted workflow account, no relay backend, and no Deckloud-only object model.

05

Safe import rules

IDs are not stored. Stack and label keys are remapped at creation time, due dates use relative offsets instead of stale fixed dates, and checklists are written into the card description as ordinary Markdown task lists.

FAQ

Practical questions

Does this change my Nextcloud server schema?

No. It creates ordinary boards, stacks, labels, and cards through the normal Deck model.

Does the template include comments or attachments?

No. V1 templates are text-only because comments imply authorship and attachments vary by server/version.

Can I edit the board after creating it?

Yes. After creation it is just a normal Nextcloud Deck board.

Why mitigate before finding the cause?

Users care that it stopped, not why it started. Roll back or fail over first; root cause is a review task with no clock on it.

What makes a review blameless in practice?

Asking what made detection and recovery slow, rather than who acted. The output is a guardrail with an owner, not a name.

Get Deckloud

Work with your Nextcloud Deck boards natively

Get Deckloud for iPhone and iPad, or the desktop app for Mac, Windows, and Linux. Your boards, cards, and due work stay on your own server.