Design, review and controlled publication

Prepare changes in a separate design workspace, review their impact and publish them to the base project after approval.

Last updated: 10 November 2026

Separate the design from the base project

A design is a separate workspace created from the base project's records at a particular moment. Changes in it do not reach the base project until Publish completes. You can work on several designs and track the differences and decision history of each.

Creating a design requires editing permission across the whole project. Review, approval and publication options depend on project role and design status. Project membership determines writable scope.

Create a design

1. Open Designs in the base project's Project panel.
2. Select New design.
3. Enter Design name and an optional Description.
4. Select Create design, then Open or Open branch for the resulting design.
5. Make map, equipment, connection and circuit changes in this workspace.
6. Use Report and details for the design record, or Return to base for the base project.

Assess differences and impact

1. Select Verify in the design record.
2. Under Difference, inspect added, changed and deleted records. Use Compare for record details.
3. Under Conflict, check changes to the same records in the base project. Where offered, select Design or Baseline, then Save selections.
4. Resolve connection and policy issues under Violations.
5. Under Impact, read effects on circuits, optical calculations, measurements, outages, outputs and quantities.
6. After corrections or conflict selections, use Verify again.

Baseline advanced means the base project changed while the design was being prepared. Review the current report before deciding. An impact reported as unassessable or unavailable in detail does not mean there is no impact.

Submit for review and publish

1. If validation supports a decision, select Submit for review.
2. An authorised reviewer assesses the report and selects Approve or Reject. Rejection requires Rejection reason.
3. If changes are required, use Withdraw or Return to draft as the state allows, then repeat editing and validation.
4. For an approved design, an authorised administrator selects Publish, reviews the publication summary and selects I approve publishing the design changes to the base.
5. For construction tracking, select Open a work package when publishing and enter Work package name, Start and End.
6. Complete with Publish and check Published status.

Self-approval differs from the default process; an administrator can explicitly enable Allow submitters to approve their own designs. If a new conflict appears during publication, return to draft, resolve it and resubmit for review. For an uncertain operation result, follow Verify pending save result.

See Work packages and as-built records for construction tracking, or Offline field work for field submissions.

Distinguish conflicts from dependencies

Difference shows your changes in the design. Conflict identifies where those changes disagree with current base-project records. A changed design record is not automatically a conflict; later modification or deletion of the same base record affects the assessment.

On a selectable conflict row, Design retains the design change; Baseline retains the base-project record. After Save selections, use Verify again. Saving selections does not publish. You must also resolve connection or policy violations arising after a conflict choice.

Caution: The base project may change again during review. Do not assume an earlier acceptable report remains valid for later publication; use the current validation result.

Read the impact report

Impact shows how changes relate to the recorded network. In Circuits, review each affected circuit and its state; in the Impact column, inspect Will disconnect, Will be refreshed, Anchor, Path element or To be deleted. Reassessment and deletion of a circuit are different outcomes.

Optical calculations and Measurements show technical records linked to the changed path. Read the calculation reasons; do not assume an earlier optical calculation remains valid for new topology. Under Outage, assess affected records alongside endpoint, building and circuit counts. A skipped calculation or unavailable detail is not an empty result.

Exports and Previous generations identify technical schedules and earlier files related to the change. Regenerate field documents from the published records. Compare count and length differences under Bill of quantities (BoQ) with the design scope; a total difference alone does not determine which record is correct.

Follow decisions and publication outcomes

The reviewer selects Approve or Reject; Rejection reason records the explanation where required. Withdraw or Return to draft is available for corrections according to current state and permissions. Do not look for a separate return-for-changes button; use the offered action to resume editing.

A work package opened with publication moves planned scope into construction and handover tracking. Use Open work package to reach it. Assess the published record against actual field changes in the work package.

To roll back publication, inspect the relevant publication operation in the base project's History. Later changes or dependent records may block undo; assess the stated dependencies. After successful undo, design details show This publication was rolled back. The design history is retained. Undo does not erase the design's review history.