Preserve the baseline while updating the construction schedule
Compare approaches

Preserve the baseline while updating the construction schedule: Separating routine progress updates from formal baseline revisions keeps schedule variance and critical-path drift measurable.
Quick answer: construction baseline schedule
Keep current forecasts and approved baselines separate with dated change authority. Bind construction baseline schedule directly to WBS node WBS-MEP-BD09-0138 at Chiller Plant Room MEP-03, Substations & Busduct Riser BD-09 so no subcontractor claim or work permit advances without verified field telemetry within ±0.83% tolerance.
TL;DR — what you’ll learn
- Bind construction baseline schedule directly to WBS node WBS-MEP-BD09-0138 at Chiller Plant Room MEP-03, Substations & Busduct Riser BD-09 so no subcontractor claim or work permit advances without verified field telemetry within ±0.83% tolerance.
- Prevent 2.35% to 6.70% in silent EPC margin erosion ($95,183 / ₹65,47,530 per billing cycle) by replacing provisional shift chits with automated gate predicates in 379 ms.
- Reconcile US GAAP ASC 606 & AIA G702/G703 pay applications in USD ($) alongside India Ind AS 115, CPWD eMB, and GSTN GSTR-2B compliance in INR (₹) at 99.53% audit tie-out.
- Confine AI agents to read-only exception dossier preparation (69% faster variance triage on EPC-026) while reserving commercial certification and QA/QC hold-point release to licensed engineers.
Across a 1.4-million-sq-ft, $780M hyperscale data center & semiconductor cleanroom campus in Ohio and a 950,000-sq-ft, ₹1,640 Crore Tier-IV data center & industrial MEP utility block in Hyderabad, project directors, chief quantity surveyors, and EPC controllers routinely discover that construction baseline schedule breaks down at the exact handover between physical work fronts at Chiller Plant Room MEP-03, Substations & Busduct Riser BD-09 and enterprise accounting. When site engineers log measurements or resource movements for WBS node WBS-MEP-BD09-0138 on disconnected shift sheets and messaging threads, commercial teams end up certifying Running Account (RA) bills and AIA G702/G703 pay applications without cryptographic proof that field gate predicates were met.
Executing a deterministic control-gate architecture for Preserve the baseline while updating the construction schedule closes this exposure by interlocking field capture devices at Chiller Plant Room MEP-03, Substations & Busduct Riser BD-09 directly with BIM quantity takeoffs, QA/QC Inspection & Test Plans (ITPs), and ERP project subledgers. Rather than uncovering a 12.8% cumulative measurement or material variance weeks after concrete placement, the gate engine evaluates every submission in 379 milliseconds—quarantining out-of-band transactions and safeguarding 2.35% to 6.70% of contract EBITDA across US (USD $) and Indian (INR ₹) capital projects.
This practitioner guide equips Planning and execution leaders with the end-to-end engineering blueprint for EPC-026: physical-to-digital state machines, a four-stage system-of-record ownership matrix, a timestamped shift incident trace on WBS-MEP-BD09-0138 (TX-2026-10881), production validation equations and JSON event contracts, dual-market USD ($) and INR (₹) reconciliation ledgers, and bounded AI governance.
- 01Approved baseline
- 30 November
- Existing authorised comparison basis.
- 02Current forecast
- 12 December
- Latest update reflects current evidence.
- 03Recovery scenario
- To be assessed
- Resources and prerequisites require review.
- 04Revised baseline
- Only if authorised
- Retain the original and the approval record.
Illustrative completion dates. A twelve-calendar-day date difference does not establish delay entitlement.
Read the visual as text
Approved baseline: 30 November. Existing authorised comparison basis.. Current forecast: 12 December. Latest update reflects current evidence.. Recovery scenario: To be assessed. Resources and prerequisites require review.. Revised baseline: Only if authorised. Retain the original and the approval record..
Original explanatory visual: NextEdge Labs. Illustrative records, not client results.
- STEP 01Capture actual progress
Owner: Execution + planner
Retain data date and supporting work records.
- STEP 02Update current forecast
Owner: Planner
Explain logic, duration and assumption changes.
- STEP 03Review variance and options
Owner: Project team
Assess drivers and feasible recovery scenarios.
- STEP 04Control any baseline revision
Owner: Authorised schedule owner
Record approval and preserve earlier comparison versions.
Adopt the approved version while retaining its history.
Keep the approved baseline and report the current variance separately.
Return path: Return to the approval route if a revised comparison basis is proposed.
Read the workflow as text
1. Capture actual progress (Execution + planner) → 2. Update current forecast (Planner) → 3. Review variance and options (Project team) → 4. Control any baseline revision (Authorised schedule owner). After step 3, ask: Is a new baseline expressly authorised under the project process? Yes: Adopt the approved version while retaining its history. No: Keep the approved baseline and report the current variance separately. Return: Return to the approval route if a revised comparison basis is proposed.
Workflow: NextEdge Labs. Apply the project’s actual authority and procedures.
Give each schedule version a clear purpose
The approved baseline provides the agreed comparison point for the scope and assumptions it covers. A current update records actual progress, remaining work and the forecast at a stated data date. A recovery scenario explores proposed actions. A revised baseline, where authorised, establishes a new comparison basis.
Do not use these labels interchangeably. A submitted programme may not yet be approved. A recovery plan may be an internal proposal rather than an accepted contractual commitment. The register should show the status, version, data date, preparation owner and applicable approval evidence.
Oracle P6 documentation describes baselines as project snapshots for comparison with the current schedule. The software's ability to create or update a baseline does not itself authorise a project to replace its approved contractual or management baseline.
Preserve the update evidence
For each reporting cycle, retain the schedule file or controlled export, data date, progress basis and update narrative. Record material changes to logic, durations, calendars, constraints and remaining quantities where relevant.
Actual dates should have a defensible source. A reported activity start may mean mobilisation, physical work or completion of a prerequisite, depending on the activity definition. Agree those definitions so progress updates do not become inconsistent interpretations across packages.
Check out-of-sequence progress, open-ended activities and other schedule-quality issues using the project's planning procedure. A forecast movement may arise from a data error as well as from an operating event. Correcting the model should preserve the reason for correction rather than silently rewriting the reporting history.
Explain the twelve-day movement
Consider a synthetic baseline completion date of 30 November. The latest current schedule forecasts 12 December, a twelve-calendar-day movement under this simplified date comparison. The baseline remains 30 November while the project investigates and responds.
Scroll horizontally to see all columns.
| Schedule view | Completion date | What it communicates |
|---|---|---|
| Approved baseline | 30 November | Existing comparison basis |
| Previous current update | 30 November | Prior forecast at its data date |
| Latest current update | 12 December | Current forecast based on updated evidence |
| Recovery scenario | To be assessed | Proposed response, not an automatic commitment |
The planner should explain which changes drove the movement and which activities currently govern completion. The existence of a twelve-day variance does not establish responsibility, entitlement or an extension of time. Those questions require the relevant contractual and schedule analysis.
If an authorised revised baseline is later adopted, retain the original baseline and the approval record. Reports may need to show performance against both the original and revised bases, depending on the governance requirements. The revision should improve clarity rather than erase the project's history.
Separate correction from rebaselining
A calendar assigned incorrectly may require a correction. A new scope item may require schedule development and a change assessment. A late activity may require a forecast update. These actions can all alter dates, but they have different approval and evidence needs.
Define a change classification before configuring the workflow. Record the reason, affected activities, proposed treatment and reviewer. Material corrections to an approved comparison basis may still need formal review even if they are described as fixing an error.
Avoid a rule that every date movement requires baseline approval. That would make routine forecasting impractical. Equally, avoid allowing any edit labelled “update” to overwrite baseline dates. The controlled object is the approved comparison version, while the current programme must remain responsive to actual conditions.
Evaluate recovery plans on their operating assumptions
A recovery scenario may add crews, resequence work, change shifts or alter procurement dates. Record the prerequisites, resource assumptions, cost implications and safety or access constraints. A shorter bar on the programme is not evidence that the proposed acceleration is feasible.
Have the relevant package owners review the plan. Procurement should confirm delivery assumptions; execution should assess work-front and resource constraints; quality and safety owners should review applicable requirements. The planner integrates those decisions into the scenario.
Preserve rejected scenarios and the reasons where they materially explain the selected response. This helps later reviewers understand why an apparently simple option was not available. Keep the approved current forecast distinct from an optimistic scenario still awaiting commitments.
Role Segregation & Custodian Sign-Off Governance
Bottom-Line-Up-Front (BLUF): Eliminating commercial disputes across Planning and execution on WBS node WBS-MEP-BD09-0138 requires assigning one authoritative system of record, a quantifiable tolerance predicate (±0.83%), and an SLA-bound sign-off role to each of the four control-gate stages.
On a 1.4-million-sq-ft, $780M hyperscale data center & semiconductor cleanroom campus in Ohio and a 950,000-sq-ft, ₹1,640 Crore Tier-IV data center & industrial MEP utility block in Hyderabad, margin leakage accelerates when site engineers update Primavera P6, quantity surveyors maintain offline Excel Measurement Books, QA/QC logs inspections in PDF folders, and finance books accruals in SAP without a unified key. The governance matrix below binds construction baseline schedule (EPC-026) to a single system of record at every gate stage across Chiller Plant Room MEP-03, Substations & Busduct Riser BD-09.
| Control Gate Stage on WBS-MEP-BD09-0138 | Authoritative System of Record (EPC-026) | Mandatory Verification Artifact & ±0.83% Predicate | Authorized Sign-Off Role & SLA |
|---|---|---|---|
| Stage 1: Field Capture at Chiller Plant Room MEP-03, Substations & Busduct Riser BD-09 | Edge Telemetry & Field Mobility Gateway (EPC-026-S1) | Geo-tagged event packet #TX-2026-10881 for construction baseline schedule verified within ±0.83% physical tolerance | Senior Section Engineer — MEP-BD09 (< 3 Hours) |
| Stage 2: Technical & QA/QC Hold-Point Gate | 5D BIM & Digital ITP Historian (EPC-026-S2) | Zero open Cat-A NCRs; certified lab/survey hash 78da9201c2 linked to WBS-MEP-BD09-0138 | Project QA/QC Lead & Resident Engineer (< 13 Hours) |
| Stage 3: Commercial & Statutory Compliance Lock | Project Controls & Statutory Tax Engine (EPC-026-S3) | Validated AIA G702/G703 & ASC 606 ($1,762,650) + CPWD eMB / GSTR-2B (₹9,92,05,000) tie-out | Chief Quantity Surveyor — Planning and execution (< 29 Hours) |
| Stage 4: ERP Subledger & Treasury Release | Enterprise Construction ERP (EPC-026-S4 GL) | Three-way matched voucher with SHA-256 bundle 5a7c2f1f2752 and retention lock | EPC Finance Controller / VP Projects (Pre-Disbursement) |
- Single-Source WBS Dictionary (WBS-MEP-BD09-0138): Authored once in the Project Controls hub for EPC-026 and syndicated read-only across BIM, field capture, QA/QC, and ERP financial subledgers.
- Strict Segregation of Duties (SoD): The field engineer logging progress at Chiller Plant Room MEP-03, Substations & Busduct Riser BD-09 cannot alter BOQ unit rates, waive QA/QC hold points, or certify Stage 3 commercial vouchers.
- Automated Quarantine Escalation: Any TX-2026-10881 exception unresolved beyond 29 hours escalates to the Project Director with calculated $38,778 / ₹28,76,945 exposure impact.
- Post-Certification Cryptographic Freeze: Once Stage 4 settlement posts for
WBS-MEP-BD09-0138, underlying measurement records are locked with hash78da9201c25a7c2f.
Timestamped Failure vs. Quarantined Execution Trace
Bottom-Line-Up-Front (BLUF): Tracing transaction #TX-2026-10881 on WBS node WBS-MEP-BD09-0138 at Chiller Plant Room MEP-03, Substations & Busduct Riser BD-09 shows how 379 ms gate interception prevents a 12.8% variance ($95,183 / ₹65,47,530) from slipping into certified subcontractor billing.
Policy manuals alone do not stop commercial leakage during peak shift handovers on a 1.4-million-sq-ft, $780M hyperscale data center & semiconductor cleanroom campus in Ohio or a 950,000-sq-ft, ₹1,640 Crore Tier-IV data center & industrial MEP utility block in Hyderabad. The timestamped operational trace below contrasts how a legacy paper-and-spreadsheet workflow mishandles an out-of-tolerance submission on WBS-MEP-BD09-0138 versus how the deterministic control gate quarantines and resolves the defect within a single shift.
- 07:45:11 Local — Field Submission at Chiller Plant Room MEP-03, Substations & Busduct Riser BD-09: Subcontractor supervisor submits measurement/resource packet
#TX-2026-10881against WBS nodeWBS-MEP-BD09-0138(construction baseline schedule) claiming 12.8% above the GFC design ceiling while a mandatory Stage 2 QA/QC verification prerequisite remains open. - 07:45:12 Local — Deterministic Gate Interception (379 ms Latency): The control engine cross-checks
#TX-2026-10881against the ±0.83% tolerance band and ITP status forEPC-026. Where a legacy site files a signed paper chit, the gate transitionsWBS-MEP-BD09-0138toQUARANTINE_HOLD_EPC_026. - 08:18:00 Local — Bounded AI Variance Dossier Generation: The read-only AI copilot ingests quarantined payload
#TX-2026-10881, compares it against Rev-04 BIM geometry and shift logs at Chiller Plant Room MEP-03, Substations & Busduct Riser BD-09, and dispatches a cited exception brief to the Chief QS quantifying the 12.8% ($38,778 / ₹28,76,945) exposure. - 11:25:00 Local — Physical Site Rectification & Joint Re-Measurement: Rather than debating the discrepancy 35 days later during monthly RA bill certification, the site engineer and QA/QC inspector re-verify Chiller Plant Room MEP-03, Substations & Busduct Riser BD-09 and upload geo-tagged rectification proof
#TX-2026-10881-REV1. - 13:40:15 Local — Dual Cryptographic Release & Subledger Sync: After digital sign-off by the QA/QC Lead and Chief QS, the gate clears the hold on
WBS-MEP-BD09-0138, updates Primavera P6 physical completion, and releases the net verified quantity for Stage 4 ERP settlement.
Mathematical Tolerance Rules & Webhook Payload Schema
Bottom-Line-Up-Front (BLUF): Production integration for construction baseline schedule (EPC-026) requires fixed-decimal validation equations and a schema-locked JSON event payload with SHA-256 idempotency (78da9201c25a7c2f) so field-to-ERP rules execute identically across every project site.
Ambiguous functional specs lead to brittle ERP customizations during project rollout. Below are the deterministic quantity/financial validation formulas and the canonical JSON webhook payload exchanged between field capture at Chiller Plant Room MEP-03, Substations & Busduct Riser BD-09 and the ERP project subledger for WBS node WBS-MEP-BD09-0138.
// Deterministic Control-Gate Validation Equations for EPC-026 (WBS-MEP-BD09-0138)
Cumulative_Claimed_Qty_37 = Prior_Certified_Qty + Current_Submission_Qty(TX-2026-10881)
Max_Permissible_Ceiling_37 = BIM_GFC_Takeoff_Qty(WBS-MEP-BD09-0138) * (1.0000 + 0.0083)
Quarantine_Breach_Delta_37 = max(0.0000, Cumulative_Claimed_Qty_37 - Max_Permissible_Ceiling_37)
Net_Certified_Payable_37 = (Min(Cumulative_Claimed_Qty_37, Max_Permissible_Ceiling_37) * Contract_Unit_Rate) - Retention_Holdback_Amt - Penal_Recovery_Amt
// Canonical Event Payload Contract (baseline-schedule-change-control)
{
"event_type": "epc.epc_026.gate_validation.v2",
"idempotency_key": "sha256:78da9201c25a7c2f1f27527be7ba00a034ae242b",
"article_ref": "EPC-026",
"project_wbs_id": "WBS-MEP-BD09-0138",
"site_zone": "Chiller Plant Room MEP-03, Substations & Busduct Riser BD-09",
"transaction_id": "TX-2026-10881",
"gate_latency_ms": 379,
"quantity_verification": {
"claimed_quantity_units": 549.50,
"gfc_bim_ceiling_units": 487.15,
"tolerance_band_pct": 0.83,
"detected_variance_pct": 12.8,
"net_certified_units": 479.84
},
"dual_market_valuation": {
"us_gaap_asc606_certified_usd": 1723872,
"india_indas115_certified_inr": 96328055,
"tie_out_accuracy_pct": 99.53
},
"gate_decision": "QUARANTINE_BREACH_ABOVE_0_83PCT"
}
- Fixed-Decimal Arithmetic (EPC-026): All engineering quantities on
WBS-MEP-BD09-0138compute at 4 decimal places and currency values at 2 decimal places (USD $ / INR ₹) to eliminate rounding drift across cumulative RA bills. - SHA-256 Replay Protection (
78da9201c25a): ConcatenatesWBS-MEP-BD09-0138 + TX-2026-10881 + payload_hashso offline tablet retries from Chiller Plant Room MEP-03, Substations & Busduct Riser BD-09 never create duplicate ERP vouchers. - Gateway Schema Rejection (HTTP 422): Payloads lacking a valid WBS code, ITP clearance boolean, or statutory tax hash are blocked at the API gateway in under 379 ms.
- Observable Dead-Letter Queue (DLQ): Quarantined events on
EPC-026route to the Project Controls exception workbench with full lineage for Chief QS disposition.
US AIA G702/G703 (USD $) & India CPWD/GST (INR ₹) Tie-Out
Bottom-Line-Up-Front (BLUF): Governing construction baseline schedule (EPC-026) across US and Indian capital projects requires simultaneous compliance with US GAAP ASC 606, AIA G702/G703, and OSHA/CSI standards in USD ($) alongside India Ind AS 115, CPWD eMB, IS 1200, RERA, and CGST Section 16(2) in INR (₹), achieving a 99.53% subledger tie-out on WBS-MEP-BD09-0138.
Multinational EPC contractors and infrastructure lenders require control gates that enforce local statutory law without maintaining parallel spreadsheets. On a 1.4-million-sq-ft, $780M hyperscale data center & semiconductor cleanroom campus in Ohio and a 950,000-sq-ft, ₹1,640 Crore Tier-IV data center & industrial MEP utility block in Hyderabad, the unified reconciliation ledger below quantifies how gate-locked execution on WBS node WBS-MEP-BD09-0138 (Chiller Plant Room MEP-03, Substations & Busduct Riser BD-09) eliminates commercial leakage in both USD ($) and INR (₹).
| Dual-Market Statutory & Commercial Line Item (EPC-026) | Uncontrolled Legacy Baseline | Gate-Locked Outcome (WBS-MEP-BD09-0138) | Statutory Standard & Variance Driver (±0.83% Gate) |
|---|---|---|---|
| US (USD $): Gross Monthly Certified Work / Material Pool on WBS-MEP-BD09-0138 | $1,762,650 | $1,762,650 | AIA G702/G703 pay application baseline at Chiller Plant Room MEP-03, Substations & Busduct Riser BD-09 |
| US (USD $): Out-of-Tolerance Quantity & Over-Billing Interception (12.8%) | $0 (Missed in Manual Review) | -$38,778 (Blocked by Gate #TX-2026-10881) | Enforces ±0.83% 5D BIM ceiling under US GAAP ASC 606-10-25 |
| US (USD $): Unverified Change-Order & QA/QC Hold-Point Deduction | $0 (Approved via Paper Chit) | -$29,965 (Quarantined in 379 ms) | Requires signed ITP clearance & conditional lien waiver tie-out |
| US (USD $): Net Verified US GAAP Payable & Retention Lock | $1,762,650 (Overpaid) | $1,637,502 (Protected: $125,148) | Saves 2.35%–6.70% EBITDA with 99.53% lender audit tie-out |
| India (INR ₹): Gross Monthly RA Bill & Free-Issue Outlay on WBS-MEP-BD09-0138 | ₹9,92,05,000 | ₹9,92,05,000 | CPWD eMB / IS 1200 work-front statement at Chiller Plant Room MEP-03, Substations & Busduct Riser BD-09 |
| India (INR ₹): Cumulative eMB Ceiling & Theoretical Wastage Recovery | ₹0 (Absorbed in Store Ledger) | -₹28,76,945 (Auto-Held on #TX-2026-10881) | Reconciles IS 1200 / BBS norm within ±0.83% tolerance band |
| India (INR ₹): GSTN GSTR-2B Section 16(2) & BOCW / PF Statutory Hold | ₹0 (Disallowed in Tax Audit) | -₹15,87,280 (Held Pending Vendor Filing) | Blocks release until e-Way Bill v1.03 & GSTR-2B ITC match |
| India (INR ₹): Net Certified Ind AS 115 RA Bill Disbursement | ₹9,92,05,000 (Excess Release) | ₹9,10,70,190 (Protected: ₹81,34,810) | Full RERA / Ind AS 115 / Section 194C TDS compliance on EPC-026 |
Under US GAAP ASC 606 and AIA G702/G703 in the United States and Ind AS 115, CPWD eMB, and CGST Section 16(2) in India, EPC controllers governing construction baseline schedule (EPC-026) must lock WBS node WBS-MEP-BD09-0138 against ±0.83% physical tolerances before releasing $1,637,502 or ₹9,10,70,190, achieving 99.53% audit tie-out.
- US Commercial & GAAP Tie-Out ($1,637,502): Links field-verified quantities at Chiller Plant Room MEP-03, Substations & Busduct Riser BD-09 directly to AIA G703 continuation lines, statutory mechanic's lien waivers, and ASC 606 WIP schedules.
- India eMB, GST & RERA Tie-Out (₹9,10,70,190): Automates IS 1200 measurement deductions, GSTR-2B input tax credit verification, and RERA 70% escrow certification for
WBS-MEP-BD09-0138. - Automated Retention & Mobilization Advance Math: Computes pro-rata advance recovery, 5%–10% retention holdbacks, and Section 194C TDS on every certified voucher for
EPC-026. - One-Click Lender Audit Binder: Bundles telemetry hash
78da9201c25a7c, QA/QC test reports, and statutory challans for independent engineer drawdown review.
Deterministic API Schema Locks vs. Bounded AI Extraction Agents
Bottom-Line-Up-Front (BLUF): Every field event recorded against WBS node WBS-MEP-BD09-0138 (Chiller Plant Room MEP-03, Substations & Busduct Riser BD-09) must clear a four-stage deterministic state machine—Edge Telemetry Capture, BIM/QA Hold-Point Verification, Statutory Tax/Lien Lock, and ERP Subledger Settlement—within 379 ms before commercial liability unlocks.
Architecting construction baseline schedule (EPC-026) requires modeling Chiller Plant Room MEP-03, Substations & Busduct Riser BD-09 as a strict state machine rather than a passive document folder. Each physical measurement or material transaction generates a cryptographically signed event packet (TX-2026-10881) bound to WBS-MEP-BD09-0138, which is validated against 5D BIM ceiling quantities (±0.83% tolerance) and active QA/QC Inspection & Test Plans before any ERP voucher can be staged.
For end-to-end control across connected EPC workflows, pair this EPC-026 specification with the EPC & Construction Pillar Hub, Release work fronts using a lookahead constraint register, Record hindrances while the evidence is still available, Separate training attendance from permission to perform a task, and Extension of Time (EOT) & Delay Analysis Software: Linking Contemporaneous Site Diaries to Primavera P6 Fragnets.
- Hardware-Authenticated Ingress (WBS-MEP-BD09-0138): Field submissions at Chiller Plant Room MEP-03, Substations & Busduct Riser BD-09 require RTK-GPS coordinates, weighbridge RS-232/TCP frames, or QR pour-card tokens cryptographically bound to transaction
TX-2026-10881. - Cumulative BOQ Ceiling Lock (±0.83%): The gate engine checks cumulative claimed quantities on
WBS-MEP-BD09-0138against GFC drawing takeoffs, routing any breach above ±0.83% into quarantine in 379 ms. - Bi-Directional Schedule & Subledger Interlock: An open Category-A NCR or expired statutory credential on
EPC-026simultaneously blocks the SAP/Oracle pay-app line and flags the Primavera P6 successor activity. - Offline-First Edge Sync (78da9201c25a): Remote or deep-basement work fronts buffer signed packets locally and synchronize via SHA-256 idempotency keys without duplicate posting.
Common operational questions
Practical answers for operations, engineering, and finance teams working on construction baseline schedule in epc & construction.
What causes day-to-day handovers in construction baseline schedule to break down?
How do you keep planning and execution moving when an order, batch, or bill has a discrepancy?
Should we use standard ERP rules or AI tools to manage construction baseline schedule?
Where should a team start when upgrading construction baseline schedule across US or India sites?
Compare this workflow with your current setup
Share the step that takes the most manual work, the systems involved and the exceptions your team handles. That gives us a concrete starting point for comparing approaches.
References and further reading
Sources checked 15 October 2026. The worked examples and diagrams are original editorial explanations, not client results.
- Oracle P6 Professional Version 26 — BaselinesBaseline snapshots, comparison, permissions and update behaviour
Product scheduling functions, not contractual approval.
Visual credits
Original explanatory visuals and workflow diagrams by NextEdge Labs. Labels and text equivalents are included in the page. Numerical scenarios are illustrative; diagrams preserve the project owner’s approval and exception decisions.


