---
title: "Free engineering intake & planning templates · DeliverySheet"
description: "Free CSV templates for engineering managers: a project request form, an FTE-month capacity plan, a decision log and a RAID log, with how to use each."
canonical_url: "https://www.deliverysheet.com/templates"
meta:
  author: "Tan Gravam"
  "og:description": "Free CSV templates for engineering managers: a project request form, an FTE-month capacity plan, a decision log and a RAID log, with how to use each."
  "og:image": "https://www.deliverysheet.com/_og/s/o_c410b2994625936a.png"
  "og:image:alt": "Free engineering intake and delivery planning templates — card"
  "og:image:height": "600"
  "og:image:type": image/png
  "og:image:width": "1200"
  "og:title": "Free templates for engineering intake and delivery planning — DeliverySheet"
  "twitter:description": "Free CSV templates for engineering managers: a project request form, an FTE-month capacity plan, a decision log and a RAID log, with how to use each."
  "twitter:image": "https://www.deliverysheet.com/_og/s/o_c410b2994625936a.png"
  "twitter:image:alt": "Free engineering intake and delivery planning templates — card"
  "twitter:title": "Free templates for engineering intake and delivery planning — DeliverySheet"
---

> Index of every page on this site: [llms.txt](https://www.deliverysheet.com/llms.txt)

# **Free templates for engineering intake and delivery planning **

Four spreadsheet templates for the part of delivery that happens before any ticket exists: taking a request in, sizing it against what the teams can actually give, recording the decisions, and keeping the risks honest. Each is a CSV with a few fictional example rows — open it in Excel or Google Sheets, delete the examples, keep the columns. Each links to the essay that explains the method behind it.

- ## **Project request form**

  The intake form with two required questions and one optional date — a need, and who is affected or what happens if nothing changes. Each row also records who asked and when, and the triage decision that has to follow within the week: plan, discovery, park or decline, with a reason the requester can read.

  **Columns **
  - Requested by
  - Date received
  - What needs to change?
  - Who is affected — or what happens if nothing changes?
  - Is there a date this is tied to?
  - Date context (one line)
  - Decision (plan / discovery / park / decline)
  - Reason
  - Review date [**Download project-request-form.csv**](https://www.deliverysheet.com/templates/project-request-form.csv) [ How to use it: An intake form template with two required fields](https://www.deliverysheet.com/blog/intake-form-template)
- ## **Capacity plan in FTE-months**

  One quarter, per team and per craft — never an organisational total. A team-line row takes gross capacity down to the honest line; demand rows then walk down it in priority order, each with the figure the delivering team gave and its confidence, until the line is spent.

  **Columns **
  - Quarter
  - Team
  - Craft
  - Row type
  - Walk order
  - Item
  - Gross capacity (FTE-months)
  - Committed elsewhere (FTE-months)
  - Interruption reserve (FTE-months)
  - Honest line (FTE-months)
  - Demand figure (FTE-months)
  - Confidence (high / medium / low)
  - Figure given by (delivering team)
  - Remaining on the line (FTE-months)
  - Next step [**Download capacity-plan-fte-months.csv**](https://www.deliverysheet.com/templates/capacity-plan-fte-months.csv) [ How to use it: A capacity planning template that fits on one sheet](https://www.deliverysheet.com/blog/capacity-planning-template)
- ## **Decision log**

  For the decisions that would cost more than an hour to re-make. It records what was decided, what was rejected and why, who decided, and the condition that would reopen it — the field that turns a decision from something defended into something checkable.

  **Columns **
  - Date
  - Demand it belongs to
  - Decision question
  - Options considered
  - Chosen (what was decided)
  - Why, and why the other options lost
  - Decided by (a person)
  - Revisit if [**Download decision-log.csv**](https://www.deliverysheet.com/templates/decision-log.csv) [ How to use it: A decision without a record is a decision you will make again](https://www.deliverysheet.com/blog/decisions-need-a-record)
- ## **RAID log**

  Risks, assumptions, issues and dependencies, attached to a demand on every row rather than to a project document. "Assessed — none known" is a valid status, distinct from a blank nobody looked at; dependencies carry "asked, not confirmed" until the other team agrees; issues name the decision they need.

  **Columns **
  - Demand
  - Type (Risk / Assumption / Issue / Dependency)
  - Item
  - Owner
  - Status
  - Severity (risks only)
  - Next review date [**Download raid-log.csv**](https://www.deliverysheet.com/templates/raid-log.csv) [ How to use it: The RAID log, minus the theatre](https://www.deliverysheet.com/blog/raid-log-without-the-theatre)

## **Scripts and checklists to copy **

Not spreadsheets: wording and lists that live inside an essay, ready to copy as they stand.

- [**Request or topic? A one-page guide to print**](https://www.deliverysheet.com/request-or-topic)

  The three things a request has to say before anyone sizes it, the question to send back for each one that is missing, and two stamped examples. One sheet for the team channel or the wall.
- [**Seven emails for answering a request**](https://www.deliverysheet.com/blog/declining-a-request-email-templates)

  Decline, park until a review date, ask the two questions that are missing, offer a smaller yes, redirect to the right owner, reply to a date sales already promised, or tell a customer no. Replace the square brackets and send.
- [**A four-section status report**](https://www.deliverysheet.com/blog/engineering-status-report)

  Committed, closed since last time, at risk, and committed early — one table that says what goes on each line, and nothing about activity.
- [**A change request checklist**](https://www.deliverysheet.com/blog/change-request-process)

  Ten lines to run when someone asks to change a commitment: the baseline, what changes, the cost per team, the effect on the date, and the decision by the owner.
- [**A three-sentence lessons learned template**](https://www.deliverysheet.com/blog/lessons-learned-template)

  What you committed to and believed, what turned out, and what you will check before similar work — with six examples, each in a weak and a strong version.
- [**Five emails for a project that is running late**](https://www.deliverysheet.com/blog/telling-stakeholders-a-project-is-late)

  A new date, a choice between scope and date, a dependency outside the team, an estimate that was wrong, and stopping the work. Four parts each: what was promised, what changed, what you need, what happens meanwhile.

## When a spreadsheet stops being enough

These templates work in a spreadsheet, and for one person making the commitments on a list that fits on a screen, a spreadsheet is the right tool. What a sheet cannot do is refuse: any cell can be edited, so a row reading "committed" means someone typed it, and the reason a risky commitment was made early is overwritten by the next edit.

DeliverySheet is the same method with the rules enforced:

- **A capture floor.** A request enters the lifecycle only with a stated need plus an impact or a trigger — the two questions of the request form, checked at the door.
- **Enforced states.** A demand moves through capture, shape, decide, plan, commit, deliver and learn; parking and declining are recorded decisions with a reason, not rows that stop being updated.
- **A readiness verdict.** Dependencies, decisions, capacity and risks are read before commitment — each can honestly be "none known", which is different from "not assessed" — and a blocked dependency, an unresolved high risk or an open key decision keeps the demand from reading as ready.
- **Recorded exceptions.** Committing before a demand is ready requires an exception naming why it is early, what is missing, who accepts the risk, and what condition would change the decision.

[Where the sheet genuinely wins, and where it quietly fails](https://www.deliverysheet.com/vs/spreadsheets), is its own honest page. To check a real request against the need, the impact and why now — no account, nothing stored — paste it into the [free request check](https://www.deliverysheet.com/request-check). To see what a shaped demand looks like once it leaves the sheet, read the [example one-pager](https://www.deliverysheet.com/examples/one-pager). To write one yourself, there is a plain-text [one-page project brief template](https://www.deliverysheet.com/blog/one-page-project-brief) to copy.

$189/month per workspace, unlimited members. 7-day free trial — card required, cancel before it ends and you're not charged. I answer the support email myself.

[**Start 7-day trial **](https://www.deliverysheet.com/login?next=/app) [**Try the free request check **](https://www.deliverysheet.com/request-check)

```json
{"@context":"https://schema.org","@graph":[{"@id":"https://www.deliverysheet.com/#website","@type":"WebSite","description":"Turn raw work requests into structured, decision-ready demands before you commit people, budget, or a date. AI-assisted shaping, planning and commitment governance for engineering leaders.","name":"DeliverySheet","url":"https://www.deliverysheet.com/","publisher":{"@id":"https://www.deliverysheet.com/#identity"}},{"@id":"https://www.deliverysheet.com/templates#webpage","@type":"WebPage","description":"Free CSV templates for engineering managers: a project request form, an FTE-month capacity plan, a decision log and a RAID log, with how to use each.","name":"Free templates for engineering intake and delivery planning — DeliverySheet","url":"https://www.deliverysheet.com/templates","breadcrumb":{"@id":"https://www.deliverysheet.com/templates#breadcrumb"},"isPartOf":{"@id":"https://www.deliverysheet.com/#website"},"potentialAction":[{"@type":"ReadAction","target":["https://www.deliverysheet.com/templates"]}],"primaryImageOfPage":{"@id":"https://www.deliverysheet.com/#logo"}},{"@id":"https://www.deliverysheet.com/#identity","@type":"Organization","alternateName":"Delivery Sheet","description":"Turn raw work requests into structured, decision-ready demands before you commit people, budget, or a date.","name":"DeliverySheet","url":"https://www.deliverysheet.com","founder":{"@type":"Person","@id":"https://www.deliverysheet.com/about#person","name":"Tan Gravam"},"logo":{"@id":"https://www.deliverysheet.com/#logo"}},{"@id":"https://www.deliverysheet.com/templates#breadcrumb","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","name":"Home","item":"https://www.deliverysheet.com","position":1},{"@type":"ListItem","name":"Templates","item":"https://www.deliverysheet.com/templates","position":2}]},{"@id":"https://www.deliverysheet.com/#logo","@type":"ImageObject","caption":"DeliverySheet","contentUrl":"https://www.deliverysheet.com/logo.png","inLanguage":"en","url":"https://www.deliverysheet.com/logo.png"}]}
```

## Sitemap

See the full [sitemap](https://www.deliverysheet.com/sitemap.md) for all pages.
