← Back to the guide

A project proposal with a clear boundary

Make this with my agent

Fictional worked example · Not a published customer artifact. You review the draft; nothing is published without your approval.

What we started withThe same facts, as a wiki page

Fictional team wiki

Maple Support — five-article pilot proposal

Context

Prepared September 7, 2026, by Sam for Lee. We want clearer help instructions. Clearer content and reduced support demand are hypotheses: there is no support-demand baseline or agreed reduction target.

Decision and scope

Decision requested by September 11: approve a five-article pilot and the proposed staff effort. Nothing is approved yet. Scope is to audit five selected help articles, draft revisions and run an editorial review. Article selection needs confirmation. Publishing, site redesign, software changes, the remaining help library and full rollout are excluded.

Deliverables and review

Deliverables are five revised drafts and a review log. An as-yet-unassigned reviewer must verify product steps, flag missing evidence and record unresolved issues. Review is not automatic acceptance or permission to publish.

Estimated effort and duration

Sam estimates 24 writer hours plus 6 reviewer hours, totaling 30 staff hours. Availability is unconfirmed; there is no monetary rate, cost estimate or available budget. Proposed duration is two weeks after approval and authorized source access, with no agreed calendar start.

Dependencies and next decisions

Noor owns the pending authorization request for sanitized support examples. No actual customer material is included. Before starting, confirm article selection, reviewer, staffing, approval and source access. At the end Lee reviews the drafts and issues; publication or rollout needs a separate recorded decision in the existing project workflow. No savings or reduction in support demand is promised.

Inspect the HTMLOne self-contained file

The example is sanitized and isolated from this site. No scripts, forms, or live data.

<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1"><title>Maple Support · Five-article pilot proposal</title><style>
*{box-sizing:border-box}html{color-scheme:light}body{margin:0;background:#faf7f0;color:#242b28;font:17px/1.65 system-ui,sans-serif}main{max-width:960px;margin:auto;padding:clamp(20px,5vw,64px)}h1,h2,h3,p{margin:0 0 18px}h1{font:500 clamp(32px,5vw,58px)/1.12 Georgia,serif;letter-spacing:-.025em;overflow-wrap:anywhere}h2{font:500 29px/1.25 Georgia,serif}h3{font-size:18px;line-height:1.4}.label{font:700 12px/1.5 system-ui,sans-serif;letter-spacing:.12em;text-transform:uppercase}.intro{font-size:20px}.lead{background:#214c3e;color:#fff;padding:24px;margin:28px 0}.lead p:last-child{margin:0}.grid{display:grid;grid-template-columns:repeat(auto-fit,minmax(min(100%,220px),1fr));gap:20px;margin:24px 0}.card{background:#fff;border:1px solid #c8d2c5;padding:24px}.metric{font:500 40px/1.1 Georgia,serif;display:block;margin-bottom:12px}section{margin:36px 0}ul,ol{padding-left:22px}li{margin-bottom:12px}.note{color:#46594f;font-size:14px}.pending{border-left:5px solid #946116;padding-left:20px}footer{border-top:1px solid #bac8bf;padding-top:24px;margin-top:40px;font-size:14px}@media print{body{background:white}.card,.lead{break-inside:avoid}}
</style></head><body><main>
<header><p class="label">Fictional example / Maple Support / September 7, 2026</p><h1>Five better drafts. Not a full rollout.</h1><p class="intro">A bounded pilot to improve help instructions, with the work, effort, and unanswered questions visible before anyone commits.</p><p class="note">Prepared by Sam · Decision owner: Lee</p></header>
<aside class="lead"><p class="label">Proposed · not approved</p><h2>Approve the five-article pilot and proposed staff effort.</h2><p>Lee is asked to decide by September 11, 2026. This request does not include publishing or a full rollout. Nothing is approved yet.</p></aside>
<section><h2>The boundary of the work</h2><div class="grid"><article class="card"><p class="label">Included</p><h3>Audit, revise, review</h3><ul><li>Audit five selected help articles.</li><li>Draft revisions.</li><li>Run an editorial review.</li></ul><p class="note">Article selection still needs confirmation.</p></article><article class="card"><p class="label">Excluded</p><h3>No wider commitment</h3><ul><li>Publishing the articles.</li><li>Site redesign or software changes.</li><li>The remaining help library.</li><li>A full rollout.</li></ul></article></div></section>
<section><h2>What the pilot must produce</h2><p>Five revised drafts and a review log showing unresolved issues.</p><p>The reviewer must verify product steps, flag missing evidence, and record unresolved issues. The reviewer has not yet been assigned. Review is not automatic acceptance or permission to publish.</p></section>
<section><h2>Effort is estimated. A start is not booked.</h2><div class="grid"><article class="card"><span class="metric">30 staff hours</span><h3>Sam’s estimate</h3><p>24 writer hours plus 6 reviewer hours. Staff availability is unconfirmed.</p><p class="note">No monetary rate, cost estimate, or available budget is supplied.</p></article><article class="card"><span class="metric">Two weeks</span><h3>Proposed duration</h3><p>After approval and authorized source access. No calendar start date is agreed.</p></article></div></section>
<section class="pending"><p class="label">Dependency · approval pending</p><h2>Authorize the source examples first.</h2><p>Noor owns the request to use sanitized support examples. That authorization is still pending. No actual customer material is included in this example.</p></section>
<section><h2>What we cannot promise yet</h2><p>Clearer instructions and reduced support demand are hypotheses, not measured results. There is no support-demand baseline or agreed reduction target. This proposal makes no savings claim.</p></section>
<section><h2>Before work starts</h2><ol><li>Confirm the five articles and assign the reviewer.</li><li>Confirm staff availability.</li><li>Obtain the pilot approval and authorized source access.</li></ol></section>
<section class="card"><p class="label">At the end of the pilot</p><h2>Review the drafts. Decide separately what follows.</h2><p>Lee reviews the drafts and unresolved issues. Any publication or rollout requires a separate decision. Record approval in the existing project workflow; this page does not collect it.</p></section>
<footer>Fictional worked example by share/artifacts. Names, dates, and figures are invented for demonstration. Source: the fictional pilot notes accompanying this example. Static snapshot; no live data or automatic updates.</footer>
</main></body></html>