WORK BREAKDOWN STRUCTURE DICTIONARY
Original fictional BriefRelay client-intake release. Checked October 28, 2026.
The companion workbook supplies ten example records and twelve prepared slots. No deliverable is represented as implemented or accepted.

EXAMPLE HIERARCHY
1 Client intake release (Group)
  1.1 Intake experience (Group)
    1.1.1 Submission form (Work package)
    1.1.2 Receipt view (Work package)
  1.2 Operational handoff (Group)
    1.2.1 Exception runbook (Work package)
    1.2.2 Support handoff (Work package)
  1.3 User guidance (Group)
    1.3.1 Help article (Work package)
    1.3.2 Training walkthrough (Work package)

EXAMPLE WORK PACKAGE
ID: 1.1.2
Parent: 1.1 Intake experience
Deliverable: Receipt view
Owner: Engineering
Boundary: show the accepted submission reference to an authorized requester in the correct workspace.
Excluded: payment receipts, a cross-workspace administrator screen, and a new identity provider.
Completion definition: the requester sees its accepted reference; an unrelated workspace cannot retrieve that receipt; the reviewer has the relevant evidence.
Inputs: agreed receipt behavior, permitted synthetic account and brief data, and the recorded release candidate.
Related verification: link to the team's actual test case and evidence when executed.
Acceptance reviewer: Product, proposed in this fictional planning exercise.
Status: PLANNED. No test result or acceptance has been recorded.
Assumptions: the existing identity and submission-ID mechanisms remain in scope as dependencies, not new deliverables.

BLANK WORK-PACKAGE ENTRY
ID:
Parent ID and deliverable:
Deliverable name:
Owner:
Included output:
Explicit exclusions:
Required inputs/dependencies:
Observable completion definition:
Verification/evidence reference:
Acceptance reviewer:
Actual acceptance decision and date, when available:
Open questions:
Change trigger:

WORKBOOK CONVENTIONS
Use root ID 1, level 1, Group, with no parent.
Every other record names a unique Group parent exactly one numeric level above.
Levels are limited to 1, 2 and 3 in the prepared workbook.
Groups need children; work packages have no children.
IDs are identifiers, not estimates or dates. Keep them stable when referring to the work elsewhere.
The workbook does not infer parentage from dotted ID spelling. Parent ID and Level are authoritative.
The sheet checks structural inputs. Human review must determine whether the decomposition covers the agreed scope without overlap.
Do not sum group estimates and their child estimates together. The workbook deliberately supplies no time or cost total.
Use the related Gantt template for dates/dependencies and a RACI matrix for broader responsibility assignments.
Extend formulas and validations beyond row 21 before adding more records.