AURONAHelp Center
Kenta / Using Kenta

Maintain stage prerequisites and review delivery changes

Link delivery stages, inspect unresolved prerequisites and retain decisions about changed commitments.

Current Revision 2 Reviewed Oct 25, 2026

Applicability

Current Kenta guidance; implementation-source applicability 0.3.0, evaluation scope. Source review does not establish customer production acceptance.

Download PDF (141 KB)Contact support
On this pageBefore you beginHypothetical synthetic delivery exampleProcedureVerify the resultWhat happens nextTroubleshooting

Before you begin#

  • Project management permission for stage and dependency changes; review authority for review decisions.
  • Named stages with owners and retained sources supporting recorded dates.

Hypothetical synthetic delivery example#

Consider an illustrative Equipment delivery stage with baseline and target 2027-02-18, forecast 2027-02-28 and no actual date. A required earlier service-confirmation stage remains unresolved. A new supplier assertion of 2027-03-04 flags an impact review; it does not move the baseline, target or forecast automatically. Inspect the blocker and retained source, record the review, and use a separately authorized date-change decision if justified. These sample dates do not certify commissioning readiness.

Procedure#

  1. Inspect the stage

    Open Schedule and select a stage. Read its target, baseline, forecast, actual date and unresolved prerequisites.

    Expand prerequisite details and follow linked actions, findings, earlier stages and source records.

  2. Maintain an explicit relationship

    Choose Link dependency or Relationship rules. Select the required earlier stage and the dependent stage.

    State the finish-to-start rule, supported calendar and lag where offered. Review the relationship before saving; do not infer unsupported calculation behavior.

  3. Review material changes

    When a supplier commitment or proposal changes, open its impact review and compare the current stage revision.

    A different reviewer records the proposal disposition; an authorized manager separately applies an approved date assertion. Record reasons and source versions.

  4. Record coordination completion

    Inspect every unresolved prerequisite before authorizing coordination completion. If the workflow permits an exception, retain the explicit rationale and accountable person.

Verify the result#

Dependencies and changes retain their source, owner, review and application history. Existing dates do not silently move when a commitment changes.

What happens next#

The timeline displays recorded dates. Explicit calendar relationships do not establish a critical-path calculation or physical readiness authorization.

Troubleshooting#