Free Engineering Team Operating Manual Template

An engineering team operating manual is one page that describes how the team works. Not how the company works. Not how engineering as a discipline works. How this team works — the meetings, the norms, the defaults, the decision flows, the on-call setup, the things that would be on a poster on the wall if the team were in a single office. The reason most teams don't have one is not that the information doesn't exist; it is that it's scattered across forty pages of wiki nobody reads. The manual is the index.

The template below is structured to fit on one screen, deliberately. The constraint is the point. If your operating manual is longer than one screen, the team will not read it, and the manual becomes a fiction nobody updates. Linking out to detail is fine. Trying to inline the detail is what kills the document.

When to use it

• You are forming a new team and want to set norms explicitly rather than discover them by accident.
• An existing team is large enough that new hires are not absorbing norms by osmosis.
• You have heard new hires say "I didn't know we did that" more than three times this quarter.
• The team has merged with another team and the norms diverge.

The template structure

This is the structure of the template. Copy it into a Notion page, a Linear doc, or a markdown file in your repo — it works in any of them.

[TEAM NAME] — OPERATING MANUAL
Last reviewed: [date]   Next review: [date]   Owner: [name]

WHAT WE OWN
  - [system/area]
  - [system/area]
  - [system/area]

PEOPLE
  Manager:             [name]
  Tech lead:           [name]
  On-call rotation:    [link]
  Decision authority map: [link]

WORKING HOURS
  Core overlap window: [hours] in [timezone]
  Default expectation: response within [N] hours during local workday,
  not during others'.
  No-meeting day(s):   [day]

MEETINGS
  Sync each week:
    [meeting] — [day/time] — [agenda owner]
    [meeting] — [day/time] — [agenda owner]
  Default policy: meetings have agendas, sent 24h ahead. No agenda,
  no meeting.

ASYNC RITUALS
  Wrap / EOD handoff:  [policy — link to template]
  Decision records:    [where they live]
  RFCs:                [where they live]

REVIEWS
  PR review SLA:       [link]
  Required reviewers:  see SLA
  Safety areas (two reviewers): [link]

ON-CALL
  Rotation cadence:    [weekly / 2-week / etc.]
  Compensation:        [explicit — money, time off, neither]
  Hand-off ritual:     [link to checklist]

INCIDENTS
  Sev definitions:     [link]
  Declare incident:    [link to runbook]
  Postmortem cadence:  every Sev-1 within [N] days

ONBOARDING
  New hire plan:       [link to onboarding template]
  Buddy assignment:    [policy]

DECISIONS
  Default: engineer doing the work decides.
  Exceptions: [link to decision authority map]
  Decision record format: [link to template]

REVIEW SCHEDULE
  This manual is reviewed every [6 months] by [owner].
  Last review:  [date]
  Next review:  [date]

How to use it well

• Link out, do not inline. The manual is the index. Detail belongs in the linked documents (decision authority map, on-call runbook, PR review SLA). Trying to be both index and detail is what makes operating manuals too long to read.
• Review every six months. Twice a year is the right cadence. Annually is too rare for a growing team; quarterly is too often and the manual becomes ceremony.
• Pin it in the team channel and link from the new-hire onboarding doc. The manual that nobody finds is useless.
• Be explicit about the no-meeting day. Teams that say "we try to keep Fridays clear" do not actually keep Fridays clear. Teams that write "No meetings on Fridays" and enforce it usually do.
• State the working-hours expectation explicitly. "Response within X hours during your local workday, not during others'" is the most important sentence in the manual for a distributed team. It sets a default that respects timezones.

What to skip

Skip values statements. "We are a high-trust team" is a vibe, not a default. The manual should describe behaviors, not aspirations. If the team has a value worth stating, encode it as a default ("PRs from any teammate get the benefit of the doubt") rather than a slogan.

Skip restating company-wide policy. The manual is for what is specific to your team. Everything that is true company-wide belongs in the company handbook, not here.

Frequently asked questions

Is this template free?

Yes. The structure above is the manual. Fill in your team's specifics and pin it.

Can I edit it?

Yes — most teams will. The skeleton is the part that recurs across teams; the content varies.

Do I need to give my email?

Not for the template. The download is a Notion-formatted version; the email is for our newsletter.