Planning: Turn Approved Scope Into a Structured, Fully Resourced Plan
Once work is funded or won, PACE turns it into an executable plan — a work breakdown structure, a schedule, assigned resources, and a detailed budget built from the estimate that got it approved. One structure carries it all, for both contract work and capital investment.
Value Proposition
A Plan Is Only as Good as What It’s Connected To
A plan built in isolation — a schedule in one tool, a budget in a spreadsheet, resourcing decided in a meeting nobody wrote down — starts drifting from reality the moment execution begins. The schedule doesn’t know what the budget assumes. The budget doesn’t know what the estimate promised. Nobody can say, with confidence, whether the plan is still the plan.
PACE builds the plan directly on top of what was approved at Initiation. Scope becomes a work breakdown structure. The structure carries the schedule. The schedule and the approved estimate carry the budget. Nothing gets re-typed, and nothing drifts from what was actually funded or won.
Common Planning Challenges
• Scope, schedule, and budget live in separate tools, so nobody can see how a schedule slip changes the numbers until it’s too late
• Resource assignments are made informally, with no link between who’s assigned and what it costs
• The budget that goes into execution isn’t traceable back to the estimate that got the project approved
• Planning decisions — cost codes, resourcing method, funding source — get locked in informally, and nobody notices until execution exposes the gap
• Contract-funded and capital-funded projects get planned in the same generic template, even though what has to be set up first — a contract or a funding source — is fundamentally different
Common Elements — Every Project Starts Here
1. Define Scope with Unlimited WBS and Deliverables
Break the approved scope into a work breakdown structure with no depth limit, then attach deliverables to the tasks that need to prove physical progress. Cost codes can only be assigned at the lowest, most granular level of the structure — actual cost can never post against a summary node by mistake.
Inside PACE: PACE’s Forward Pass Engine derives every task’s start and end dates automatically from its dependencies, and new projects can launch from predefined WBS templates for rapid baseline creation. Deliverable progress isn’t estimated — Percent Complete is calculated automatically as Actual Quantity divided by Planned Quantity, rolling up from individual deliverable elements to the deliverable, and up to the WBS above it.
2. Schedule Your Tasks Using Dates and Dependencies
Set predecessors between tasks and let the schedule calculate itself — early start and late finish windows update automatically as dependencies change, instead of every date needing to be re-entered by hand.
Inside PACE: tasks can be reorganized on the fly — indent or outdent to reshape the parent-child hierarchy — without breaking the dependency chain or the dates the Forward Pass Engine has already calculated.
3. Assign Resources to Project and Tasks
Assign labor and non-labor resources at the task level, using either rate-based resources (quantity × rate calculates cost automatically) or resources with cost entered directly, depending on what the task requires.
Inside PACE: resource, cost, and revenue planning levels are locked permanently once the project is approved — a structural decision that keeps the plan’s financial architecture consistent for the life of the project. Cost and burden rates can still be refreshed from current corporate rate lists at any time, cascading the update through every dependent line without rebuilding the plan.
4. Develop Detailed Budget Based on Approved Estimate
Model the budget from the estimate that was already validated and approved during Initiation — not a new set of numbers built from scratch. Multiple alternative estimates can be modeled before approval; the one marked Original becomes the baseline the detailed budget is built from.
Inside PACE: approving the project automatically freezes the Current Working Budget into a fixed baseline layer, opens a new working version for operational tracking, and triggers an automated integration that pushes the approved project structure and its baseline budget directly into your connected corporate ERP system.
Contract Projects
Setup Contract and Contract Lines
Structure the contractual basis the project will be measured against — the contract and its lines — before planning goes further. Revenue budgeting is tied directly to what’s actually been contracted.
Inside PACE: PACE enforces this at the data level, not just as a guideline: a project’s revenue budget cannot be built to exceed the amount actually agreed with the client. The same discipline PACE applies when a Program’s agreements roll down to its sub-projects applies here — the number the team plans against is never allowed to drift past what was actually signed.
Asset Development / Internal Work
For Owners planning capital investment.
Setup Funding Sources
Define where the money for this project actually comes from — reserves, grants, debt — before the detailed budget is built, so every dollar planned has a documented, traceable source.
Inside PACE: funding sources are defined by planning year and business line as part of the same Organization Budget that governs which projects get funded across the whole capital portfolio — planning at the project level and funding governance at the portfolio level share one dataset, not two.
Optionally Define Assets to Be Developed/Retired
Link the project’s planning structure directly to the physical capital assets it creates or affects — asset type, in-service date, location, and the task the asset is tied to — so the connection between capital spend and the resulting asset is established during planning, not reconstructed afterward.
Why Planning Connects to Everything Around It
The Plan Doesn’t Get Rebuilt at Execution — It Gets Executed
Because the WBS, schedule, resourcing, and budget are built on the scope and estimate approved at Initiation, and because approval pushes that baseline straight into your ERP, Planning isn’t a separate exercise that gets reconciled against Initiation and Execution later. It’s the same connected structure, one stage further along — which is exactly what makes Execution tracking meaningful: actuals get measured against a plan that was never re-typed.
Outcomes — What Organizations Gain
- A budget that’s traceable back to the estimate that justified the project in the first place
- Schedules that recalculate themselves instead of requiring manual date maintenance
- Cost data that can only post at the correct level of the financial structure — never at a summary node
- A planning baseline that reaches your ERP automatically the moment it’s approved