Skip to content

WBS

Build the deliverable hierarchy once, drag unassigned activities onto it, and save the whole structure as a reusable template for the next project.

Who it is for. Teams who need five planners to produce structurally comparable schedules, and consultants who want the structure that took a week to agree to survive into the next tender.

What it is for

Scope structure is the one thing every downstream report rolls up to, and it is the thing most teams rebuild from scratch every job — usually in Excel, then re-keyed. The result is inconsistent coding, orphan activities nobody notices, and no way to reuse the structure.

Against the incumbents

Two things. Deleting a populated branch refuses to proceed until you decide what happens to the activities. And WBS templates are a shared, database-backed library editable centrally, rather than a file on one planner’s machine.

What it does

Every line below is in the product today.

  • Deleting a populated branch is a decision

    You must say whether the activities inside die with it or move to a named surviving node. P6 and MS Project will happily take them with the branch.

  • An activity inbox you drag from

    Every unassigned activity is listed in a side panel; drag one onto a branch to assign it.

  • Structural moves that keep codes stable

    Move among siblings, indent to become a child, outdent to sit after the parent — from a side rail and the ribbon.

  • Roll-up on every node

    Activity count for the node, a total across the whole subtree, and the subtree’s earliest start to latest finish.

  • Templates shared across the organisation

    Save the current WBS as a named template stored in the database, editable in the Library — not a per-machine file or a whole project you clone.

  • The tree saves atomically

    One transaction, client ids preserved, and activities on a removed node are unassigned rather than cascade-deleted.

  • Duplicate a branch, with or without its work

    Structure only, or structure plus activities, with the id and code remap done atomically.

See it on your own schedule.

Send an XER before the call and we will import it and show you WBS running against your data.