Esc

↑↓ move↵ openIndex · Pagefind
Scheduling / Baselines, versions and conformance

Baselines, versions and conformance

Every save is an immutable, digest-verified version. Name baselines, overlay them on the Gantt, diff any two versions, compare against a baseline and retain contract conformance assessments.

On this page

A schedule is only as defensible as its history. In os.construction, every successful save creates an immutable version: the exact definition, a content digest, and the calculation saved with it. Baselines, comparisons, analyses, traces and reports all point at a specific version, so they still mean the same thing next year.

Versions

  • A version is created only by a successful calculation. Unsaved drafts never become versions.
  • Each version keeps a content digest. Before a version is used in a calculation, a comparison or a report, its digest is checked, and a stored definition that fails the check is refused rather than read.
  • Saved history lists earlier versions of activities and WBS summaries, so a removed item can be restored to its exact saved state in the Planner.

Named baselines

A named baseline is a frozen reference to one saved version. It records the name, a kind (for example project), who created it and when. It doesn’t follow later saves, approve the version, change field baseline dates or publish anything. See schedule baseline.

  1. Save the plan you mean to baseline. You can’t baseline an unsaved draft.
  2. Name it in the Planner’s baselines panel. Names don’t need to be unique; each baseline has a stable ID. Retrying the same request returns the same baseline instead of creating a duplicate.
  3. Use it. Overlay it on the Gantt, compare the current plan with it in the Planner, or choose its version in Schedule analysis for Earned Schedule and Compare.

The baseline timeline returns each activity’s start and finish from the baseline version’s original calculation, checked against the version’s digest. That’s what the Gantt overlay draws.

Compare and diff

Two tools answer two different questions:

Question Tool Returns
How did the calculated schedule move? Analysis › Compare Finish movement and why, criticality gained and lost, date and float deltas per activity
What did someone author differently? Version diff Activities added and removed, the exact fields that changed, relationships added and removed, changed project sections

The version diff ignores ordering noise (object keys, activity order, relationship order) but still counts duplicate relationships. It treats a missing field as different from an explicit null. It’s a read: it never moves the head, runs a calculation or publishes anything. Compare shows its relationship changes beside the engine’s comparison.

Conformance assessments

A conformance assessment checks a saved version against a governing profile: a specification or jurisdiction, named contracts, elected options, contract terms, and whether the version is the baseline submission. The report lists findings, evidence requirements, a score and coverage, which shows how many of the profile’s clauses were actually assessed.

  1. Pick a profile and declare whether this is a baseline submission. Advanced options take contract names, elections and terms.
  2. Run it on a saved version, including a historical one.
  3. Review the findings. Filter by text or status. The report warns you if its version is no longer the current plan.

Each assessment is kept immutably with its parameters, engine revision and input digest. Running it again creates a new assessment rather than overwriting the old one.

A baseline you can defend

  • The baselined version passed a health check, and any exceptions are explained.
  • Its data date is the planned start or the agreed status cutoff.
  • The name says what it is, for example “Contract baseline, NTP 2026-03-02”.
  • A conformance assessment against the contract profile is retained with it.

Limits

  • An old version can’t be restored as the head. Rebuild the change, or restore individual activities from saved history.
  • Baselines can’t be deleted, and they have no approval workflow.
  • Assign Baselines sets a shared project baseline and your own primary, secondary and tertiary baselines. Up to three baseline bars draw on the Gantt, with BL1, BL2 and BL3 columns. See Baselines in views and layouts.
  • Conformance reports can’t be exported as PDF yet. Download the retained JSON through the API.

Keep exploring

Related across os.construction

Run it on your own project.

Start a 14-day free trial. Want a say in what ships next? Join the founding program.

Your role (optional)

14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →

Ask the OS

Reading this page

Ask anything about this page. Answers use what you're reading as context.

Suggested

    AI · may be imperfect · sample data where shown

    Open file