Skip to content

Specs, runbooks and postmortems, next to the work.

Engineering teams write a lot and trust little of it. Folio keeps specs reviewable, runbooks verified every quarter and postmortems open until the last follow-up is done.

SEdited by SamVerified until Dec 31For teams of 5 to 500 engineers

Engineering

Runbook: Export queue

Owner
SSam
Verified until
Dec 31
Alert
export-queue-depth

If the queue passes 500 jobs, start here. Customers notice at around 2,000.

First checks

Fix

Add a second worker pool from the deploy menu. It takes about four minutes to drain 2,000 jobs.

An engineering space in the sample workspace. Open a page, tick a to-do, open a toggle.

Three jobs Folio does for engineering teams

  1. 01

    Specs people finish

    Problem first, decisions at the bottom, reviewers sign. A spec is short because the template asks the right questions.

    Product spec template · 22.1k uses

  2. 02

    Runbooks you trust at 3 a.m.

    Every runbook is verified until a date. An expired one shows a banner nobody can miss.

    Verified pages on Plus and Business

  3. 03

    Postmortems that close

    Follow-ups live in a database with owners, and the page stays open until the last one is done.

    Follow-ups roll up per team

Spec review

From draft to shipped, on one page.

A spec moves through review on the page itself. Reviewers tick their part, the status changes for everyone, and the decision log keeps what was agreed.

Spec: Rate limits for the public API

  1. Draft
  2. In review
  3. Approved
  4. Shipped

Before “In review”, these must be true:

0 of 2 done

Ask Folio

What engineering teams ask it.

Real questions from the pages above. Each answer names the page it came from, so the person asking can check it in a click.

How Ask Folio works
  • Which runbook covers the export queue?

    Runbook: Export queue, owned by Sam and verified until Dec 31. Start with the two first checks.1

    1 Runbook: Export queue

  • What did we decide about rate limits?

    600 requests a minute per key with a burst of 100, signed by Theo and Sam on Nov 18 and 20.1

    1 Spec: Rate limits

  • Anything odd in this week’s handover?

    Search indexing lags about three minutes after big imports, and the disk alert on worker-7 is flaky.1

    1 On-call handover · Nov 22

Pallet’s story

“At 3 a.m. you don’t want a search engine, you want the one runbook that’s right. Verified pages gave us that, and Ask Folio points straight at it.”
EElena VargaHead of Platform, Pallet
PALLET

0 minon-call handover, down from forty

Read Pallet’s story

Templates

Start from pages engineering teams use.

Four templates engineering teams copy most. Use one as it is, or change it until it fits how you work.

Browse all templates
  • Product spec

    Problem, proposal, open questions and a decision log reviewers can sign.

    Engineering · 22.1k uses

  • Incident postmortem

    Timeline, impact, causes and follow-ups, written without blame.

    Engineering · 8.7k uses

  • Runbook

    Symptoms, first checks and the exact commands, for 3 a.m. readers.

    Engineering · 6.4k uses

  • Architecture decision

    One decision per page: context, options, the choice and its cost.

    Engineering · 5.3k uses

Questions

Engineering, answered.

The questions we hear on every call.

Ask us anything else

Write the runbook once. Trust it at 3 a.m.

Start with the spec and postmortem templates. Your first 14 days of Plus are free.