Scheduling & the Integrated Master Schedule
Almost every cost overrun begins as a schedule problem nobody wanted to report. This page states how the schedule is built, how the critical path is derived, where margin lives, and what happens at each status cycle.
Schedule Architecture
A schedule is a model of how the work actually happens. It is built from the work breakdown structure so that scope, budget, and schedule describe the same program rather than three different ones.
- Integrated master schedule containing all authorized work, including subcontractor and customer-dependent activities
- Traceable to the work breakdown structure and to the milestones the contract obligates
- Vertical traceability from the detail schedule through the intermediate to the summary level, with no divergence
- Horizontal traceability across handoffs so a delay in one path is visible in the paths that depend on it
- Subcontractor schedules integrated at the interface milestones rather than tracked separately by email
Network Logic and Critical Path
The critical path is calculated by the network, not chosen by the program manager. That only works if the logic is honest.
- Activities logically linked predecessor to successor, with open ends limited to the project start and finish
- Constraints minimized and each remaining constraint justified in a documented note
- Lags and leads used sparingly, with negative lags avoided
- Durations estimated from the resource actually assigned rather than from the date desired
- Critical path recalculated each status cycle and reported with its drivers
- Schedule health checked against the GAO Schedule Assessment Guide practices, including float, logic, and constraint metrics
Resource Loading and Realism
A schedule that assumes people are available in numbers the institution does not have is a fiction with dates on it. Resource realism is verified before a baseline is accepted.
- Key resources loaded where the schedule's credibility depends on their availability
- Resource conflicts across concurrent programs identified before commitment, not after
- Long-lead procurement, facility availability, and test slot reservations reflected as real constraints
- Government-furnished property and customer-dependency dates shown explicitly with the responsible party
- Learning curve and staffing ramp reflected honestly on new scope
Schedule Margin and Risk
Margin is a planned resource held at the level that can allocate it. Hiding margin inside task durations destroys the institution's ability to see where the risk actually is.
- Schedule margin held as identified tasks before key milestones rather than padded into activity durations
- Margin consumption tracked and reported; a decision is required to spend it
- Schedule risk assessment performed with duration uncertainty and discrete risk events modeled
- Confidence level associated with committed dates where the customer requires it
- Risks with schedule consequence linked to the affected activities in the schedule itself
Status Discipline
Weekly status is where schedule integrity is either preserved or quietly abandoned. Progress claimed must be progress made.
- Fixed status cycle with a defined status date, applied consistently across the program
- Progress claimed against objective completion criteria rather than perceived effort
- Actual start and finish dates recorded; no activity progresses without having started
- Forecast dates updated for remaining work, not left at baseline for appearance
- Baseline versus current comparison retained so slip is visible over time
- Baseline changes processed through the change control process with documented authorization
Where This Connects
Schedule discipline feeds performance measurement and earned value, cost control and overrun prevention, the systems engineering process, and the contract surge model, where staffing ramps are planned.
Alignment Disclosure
Monarch Space Systems describes its program planning, scheduling, performance measurement, and reporting practices as aligned with the cited federal regulations, agency directives, and consensus standards. Alignment is not a determination. The institution does not claim a validated or government-accepted earned value management system, a compliant system determination under DFARS 252.234-7002, a scheduling assessment result, or any specific contract cost or schedule performance. Program schedules, cost data, and reports are contract-controlled and are not published.
Policy documentation, procedures, and control descriptions are available to customers and prospective teammates through the confidential engagement pathway or by request through institutional contact.