Guides · Delivery operations · 6 min read

    Turning a signed SOW into a delivery plan

    The gap between a signed document and a working plan is where projects quietly start going wrong. A practical sequence for closing it in a day.

    Projects rarely fail at kick-off for dramatic reasons. They fail because the signed scope and the working plan were built separately, by different people, and only stop agreeing three weeks later.

    Start from the agreement, not a template

    Take the deliverables and phases as written and turn them into the plan's structure. A template gives you a tidy plan for a project you are not delivering; the agreement gives you a rough plan for the one you are.

    The sequence

    1. Create phases from the agreed stages, with the dates the document commits to.
    2. Break each deliverable into tasks small enough to estimate — a few days, not a few weeks.
    3. Put an estimate on every task, even a rough one; demand and forecasts are derived from these.
    4. Assign owners, and check the assignment against what those people are already committed to.
    5. Set the commercial baseline: contracted value, rates, and the budget each phase assumes.
    6. Record assumptions and exclusions as risks or open decisions rather than leaving them in the document.

    Resolve the conflicts now

    The moment estimates and assignments exist, the plan will disagree with reality somewhere: a phase that needs someone finishing elsewhere, or effort that does not fit the fee. Both are far cheaper to fix in the first week than the fourth.

    Then keep it alive

    A plan built once and left becomes a document again. Update it when phases move and when scope changes, and let the forecast and the capacity view read from it rather than from anyone's recollection.

    See how this works in Aria

    Bring a live project and a real question. That is the quickest way to tell whether any of this holds up.