Approach · Espoo, Finland

Operating runbook

Illustrative resource · English

This is an illustrative document, not a client case or an offer. Any timelines, figures and terms belong to the example; actual project scope and commercial terms are agreed separately.

Sample

Kolosseum · Sample

Runbook · AP exception console

Your repoYour cloudSample · not an engagement

Deploy

CI green, including acceptance cases. Named owner runs the production pipeline. We watch. We do not hold the button.

Rollback

Previous release is one action. Tested in week 10 with a real failure injected, not a tabletop. RTO: the afternoon, not the quarter.

The three things most likely to page someone

  • ERP read timeout. Symptom: queue stops filling. Action: fail open to manual inbox, alert owner.
  • IdP outage. Symptom: nobody can decide. Action: do not bypass auth. Wait. Log the gap.
  • Document store rate limit. Symptom: attachments missing. Action: pause posting, do not post on headers alone.

Escalation

Business hours EET, two-hour written response from the named owner. Outside hours: next morning unless a payment file is in flight. Path written before signature. Not a 24/7 SOC.

Handover contents

Gold cases, eval harness, audit-trail export, this runbook, subprocessors list, dependency list. All in your repo. You could hand the lot to another vendor in thirty days.

Back to our approach