--- title: "Project one-pager example for leadership · DeliverySheet" description: "A filled-in project one-pager: problem, committed outcome, scope in and out, owner, stakeholders and why now — for a fictional engineering demand." canonical_url: "https://www.deliverysheet.com/examples/one-pager" meta: author: "Tan Gravam" "og:description": "A filled-in project one-pager: problem, committed outcome, scope in and out, owner, stakeholders and why now — for a fictional engineering demand." "og:image": "https://www.deliverysheet.com/_og/s/o_a7588ec2a80c1611.png" "og:image:alt": "Project one-pager example — card" "og:image:height": "600" "og:image:type": image/png "og:image:width": "1200" "og:title": "Project one-pager example" "twitter:description": "A filled-in project one-pager: problem, committed outcome, scope in and out, owner, stakeholders and why now — for a fictional engineering demand." "twitter:image": "https://www.deliverysheet.com/_og/s/o_a7588ec2a80c1611.png" "twitter:image:alt": "Project one-pager example — card" "twitter:title": "Project one-pager example" --- > Index of every page on this site: [llms.txt](https://www.deliverysheet.com/llms.txt) # **Project one-pager example ** A one-pager is the page you forward when someone outside the team needs to understand a piece of work without opening any tool: a VP deciding whether to back it, a finance partner checking what is in and out, a stakeholder who missed the meeting. In DeliverySheet every shaped demand has one, generated from the demand's own fields — so nothing is written twice — printable to PDF and copyable as plain text for people outside the workspace. Below is what it looks like for a committed demand. The demand, the company and the people are invented. **Example — fictional demand ** **Example workspace** Generated Sep 30, 2026 ## **Move quarterly finance reports off the legacy data warehouse** **In delivery** Rebuild the six quarterly finance close reports on the new analytics platform, so the legacy warehouse is no longer needed for the Q4 close. **Timeline** **Oct 5, 2026 → Dec 18, 2026** **Start quarter** **Q4 2026** **Est. effort** **4.5 FTE-months** ### **Problem ** Finance's six quarterly close reports still run on the legacy data warehouse. Each close, two analysts spend most of the first week re-running failed overnight jobs and reconciling totals by hand before the numbers can go to the CFO. Vendor support for the warehouse ends in March 2027, and these reports are its last business-critical consumer. ### **Committed outcome ** For the Q4 2026 close, the six quarterly finance reports run from the new analytics platform, reconcile to the legacy output within the tolerance Finance agreed, and no quarterly finance report depends on the legacy warehouse. ### **In scope ** - Rebuild the six quarterly close reports on the new analytics platform - Migrate the general ledger, receivables and payables tables they read - Run old and new side by side for the Q4 close and reconcile - Hand report support to the data platform team's on-call ### **Out of scope ** - Monthly and ad-hoc finance reports (a separate demand) - New metrics or report redesigns - Switching off the legacy warehouse itself (Infrastructure) - Other departments' reports on the warehouse **Owner ** Priya Raman, Engineering Manager, Data Platform **Stakeholders ** Finance (Controller, FP&A), Data Platform, Infrastructure, Internal Audit **Why now ** Warehouse support ends March 2027. Moving after the Q4 close would leave no quarter to run old and new side by side before it lapses. ## How to read it - **The top row appears only once the demand is committed.** Timeline, the quarter it starts in, and estimated effort in [FTE-months](https://www.deliverysheet.com/glossary/fte-month) — the three things leadership decides on. Before a commitment, the page has no dates to show and does not invent any. - **"Committed outcome" is the promise as made.** Before the commitment, the same slot prints the outcome as shaped, labelled "Outcome / success metric". After it, it prints the outcome as refined at Commit, so a forwarded page never promises more than the team did. - **"Owner" means confirmed.** Until the owner is confirmed at Decide, the label reads "Likely owner" — a hypothesis should not travel to a VP looking like an accepted responsibility. - **Out of scope sits beside in scope,** at the same size. It is the half that prevents the argument later; [scope is what you are not doing](https://www.deliverysheet.com/blog/scope-is-what-youre-not-doing). Writing one from a blank page, field by field, with a weak and a strong line for each, is covered in [how to write a one-page project brief](https://www.deliverysheet.com/blog/one-page-project-brief). ## What it deliberately leaves out The one-pager is the summary, not the file. Per-team capacity, dependencies, decisions, risks and any commitment exception stay in the workspace, where the people answering for them can see and update them. For the regular update to leadership across all demands, see [reporting delivery to leadership](https://www.deliverysheet.com/blog/reporting-delivery-to-leadership). Most requests are nowhere near one-pager shape when they arrive. The [free request check](https://www.deliverysheet.com/request-check) reads a pasted request for the need, the impact and why now, and lists the questions to send back — no account, nothing stored. $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) [**Check a request for free **](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/examples/one-pager#webpage","@type":"WebPage","description":"A filled-in project one-pager: problem, committed outcome, scope in and out, owner, stakeholders and why now — for a fictional engineering demand.","name":"Project one-pager example","url":"https://www.deliverysheet.com/examples/one-pager","breadcrumb":{"@id":"https://www.deliverysheet.com/examples/one-pager#breadcrumb"},"isPartOf":{"@id":"https://www.deliverysheet.com/#website"},"potentialAction":[{"@type":"ReadAction","target":["https://www.deliverysheet.com/examples/one-pager"]}],"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/examples/one-pager#breadcrumb","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","name":"Home","item":"https://www.deliverysheet.com","position":1},{"@type":"ListItem","name":"Project one-pager example","item":"https://www.deliverysheet.com/examples/one-pager","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.