--- title: "Designing an engineering intake form · DeliverySheet" description: "Most intake forms are nets — they catch everything and decide nothing. What the form should actually ask, and the one property that makes it work." canonical_url: "https://www.deliverysheet.com/blog/the-intake-form-is-a-door" last_updated: 2026-08-07 meta: author: "Tan Gravam" "og:description": "Most intake forms are nets — they catch everything and decide nothing. What the form should actually ask, and the one property that makes it work." "og:image": "https://www.deliverysheet.com/_og/s/o_01f05beaacea11f8.png" "og:image:alt": "An intake form is a door, not a net — DeliverySheet essay card" "og:image:height": "600" "og:image:type": image/png "og:image:width": "1200" "og:title": "An intake form is a door, not a net — DeliverySheet" "twitter:description": "Most intake forms are nets — they catch everything and decide nothing. What the form should actually ask, and the one property that makes it work." "twitter:image": "https://www.deliverysheet.com/_og/s/o_01f05beaacea11f8.png" "twitter:image:alt": "An intake form is a door, not a net — DeliverySheet essay card" "twitter:title": "An intake form is a door, not a net — DeliverySheet" --- > Index of every page on this site: [llms.txt](https://www.deliverysheet.com/llms.txt) [← All writing](https://www.deliverysheet.com/blog) # **An intake form is a door, not a net** 7 August 2026 · 4 min read · by [Tan Gravam](https://www.deliverysheet.com/about) ## **What makes an engineering intake form work?** **The short answer ** An intake form works when it is a door with a bar, not a net that catches everything: it should ask the two questions that make a request decidable — what needs to change, and who is affected or why now — and it should be allowed to say "not yet" when the answers are missing. Every field beyond those two must earn its place at the moment of asking, because each one is paid by the requester while their patience is shortest; category pickers, priority dropdowns and sizing guesses belong to the team's later stages, not the door. The one property that makes any of it work is that requests which clear the bar visibly move — a door that leads nowhere teaches people to go around it. Sooner or later every engineering team builds an [intake](https://www.deliverysheet.com/glossary/intake) form, and almost every one of them builds a net: a dozen fields, a category picker, a priority dropdown, and a submit button that files the result somewhere nobody is obliged to look. The form was supposed to bring order to the door. What it actually does is industrialise the disorder — the same undecidable requests arrive, now with metadata. ## What the form is for A request is decidable when it says [what needs to change](https://www.deliverysheet.com/blog/what-makes-a-request-shapeable), and at least one of *who is affected* or *why it matters now*. That is the entire bar. A form earns its existence by holding that bar at the moment it is cheapest to hold — while the requester still has the context in their head — and by being allowed to say **"not yet"** when the answers are missing. Most forms cannot say not yet. Every field is optional in practice, because the team was afraid friction would push requesters away — so the form collects whatever arrives and the real questions get asked in week six, by an engineer, of a requester who has forgotten. The friction did not disappear. It moved downstream, where it costs ten times as much. ## Every extra field is paid by the requester The moment of asking is the worst possible time to demand taxonomy. A requester who wants to report "checkout is slow on mobile" does not know your category tree, cannot rank priority against a portfolio they can't see, and should not be guessing effort. Those are the team's questions, answered at the team's stages — shaping, deciding, [planning](https://www.deliverysheet.com/blog/quarter-planning-without-the-theatre) — by the people equipped to answer them. So the test for every field: *does the requester uniquely hold this information, and does the decision need it?* What needs to change — yes. Who is affected — yes. Deadline or trigger, if one exists — yes. Category, priority, T-shirt size, sponsor, OKR alignment — no. The two-question form with a bar beats the twelve-field form without one, every time. ## The property that makes it all work None of this survives unless requests that clear the bar **visibly move**. A door that leads to silence teaches requesters the same lesson a [slow maybe](https://www.deliverysheet.com/blog/saying-no-is-a-recorded-decision) teaches them: the form is where requests go to die, and the way to get something done is a DM to whoever owes you a favour. Then the side channels return, and the form's data describes only the requests nobody cared about. Visible movement does not mean fast delivery. It means every request gets a recorded state someone can check: shaped, parked with a reason, declined with a reason, planned, promised. The door works when going through it is the *best* way to get an answer — including when the answer is no. I'm Tan Gravam. I build **DeliverySheet** — it takes a vague work request to a clear delivery decision, so the shape, owner, capacity, dependencies and open questions are on the table before anyone commits people or a date. $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) [**See pricing **](https://www.deliverysheet.com/pricing) Not ready for that? Play [eight rounds of Request or topic?](https://www.deliverysheet.com/spot-the-request) It takes two minutes and needs no sign-up. ## **More on turning a request into a decision** [Read the overview: Turning a request into something you can decide on →](https://www.deliverysheet.com/topics/intake) - [Five honest alternatives to the intake spreadsheet](https://www.deliverysheet.com/blog/spreadsheet-intake-alternatives) Keep the sheet, move to Airtable or Notion, run a Jira intake project, add JPD, or adopt enforced states — the case for each, stated first. - [Demand management is deciding, not collecting](https://www.deliverysheet.com/blog/what-is-demand-management) An intake queue records wishes. Demand management shapes them, refuses some on the record, and commits the rest against capacity. - ["SSO" is a topic, not a request](https://www.deliverysheet.com/blog/a-topic-is-not-a-request) Half of what arrives in an intake queue is a subject area wearing the grammar of a request. The test that separates them takes five seconds. ```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/blog/the-intake-form-is-a-door#webpage","dateModified":"2026-08-07","datePublished":"2026-08-07","description":"Most intake forms are nets — they catch everything and decide nothing. What the form should actually ask, and the one property that makes it work.","name":"Designing an engineering intake form","url":"https://www.deliverysheet.com/blog/the-intake-form-is-a-door","@type":["WebPage","FAQPage"],"breadcrumb":{"@id":"https://www.deliverysheet.com/blog/the-intake-form-is-a-door#breadcrumb"},"isPartOf":{"@id":"https://www.deliverysheet.com/#website"},"mainEntity":[{"@id":"https://www.deliverysheet.com/blog/the-intake-form-is-a-door#/schema/question/1"}],"potentialAction":[{"@type":"ReadAction","target":["https://www.deliverysheet.com/blog/the-intake-form-is-a-door"]}],"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/blog/the-intake-form-is-a-door#breadcrumb","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","name":"Home","item":"https://www.deliverysheet.com","position":1},{"@type":"ListItem","name":"Writing","item":"https://www.deliverysheet.com/blog","position":2},{"@type":"ListItem","name":"An intake form is a door, not a net","item":"https://www.deliverysheet.com/blog/the-intake-form-is-a-door","position":3}]},{"@id":"https://www.deliverysheet.com/blog/the-intake-form-is-a-door#article","@type":"Article","dateModified":"2026-08-07","datePublished":"2026-08-07","description":"Most intake forms are nets — they catch everything and decide nothing. What the form should actually ask, and the one property that makes it work.","headline":"An intake form is a door, not a net","inLanguage":"en","thumbnailUrl":"https://www.deliverysheet.com/_og/s/o_01f05beaacea11f8.png","author":{"@id":"https://www.deliverysheet.com/about#person"},"image":{"@id":"https://www.deliverysheet.com/#/schema/image/1"},"isPartOf":{"@id":"https://www.deliverysheet.com/blog/the-intake-form-is-a-door#webpage"},"keywords":["intake","process design","forms"],"mainEntityOfPage":{"@id":"https://www.deliverysheet.com/blog/the-intake-form-is-a-door#webpage"},"publisher":{"@id":"https://www.deliverysheet.com/#identity"}},{"@id":"https://www.deliverysheet.com/blog/the-intake-form-is-a-door#/schema/question/1","@type":"Question","inLanguage":"en","name":"What makes an engineering intake form work?","acceptedAnswer":{"@type":"Answer","text":"An intake form works when it is a door with a bar, not a net that catches everything: it should ask the two questions that make a request decidable — what needs to change, and who is affected or why now — and it should be allowed to say \"not yet\" when the answers are missing. Every field beyond those two must earn its place at the moment of asking, because each one is paid by the requester while their patience is shortest; category pickers, priority dropdowns and sizing guesses belong to the team's later stages, not the door. The one property that makes any of it work is that requests which clear the bar visibly move — a door that leads nowhere teaches people to go around it."}},{"@id":"https://www.deliverysheet.com/about#person","@type":"Person","jobTitle":"Founder","name":"Tan Gravam","url":"https://www.deliverysheet.com/about","sameAs":["https://gravam.com","https://twitter.com/TanGravam","https://github.com/TanGravam"]},{"@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"},{"@id":"https://www.deliverysheet.com/#/schema/image/1","@type":"ImageObject","contentUrl":"https://www.deliverysheet.com/_og/s/o_01f05beaacea11f8.png","inLanguage":"en","url":"https://www.deliverysheet.com/_og/s/o_01f05beaacea11f8.png"}]} ``` ## Sitemap See the full [sitemap](https://www.deliverysheet.com/sitemap.md) for all pages.