Open logic: find the missing handoff
Turn an open-end flag into a traceable review decision, without adding artificial relationships.
An isolated activity can carry scope without carrying its consequences through the schedule. Start by asking what releases the work and what depends on its completion. The goal is a credible handoff, not simply a lower exception count.
Establish the review boundary
Export one project and record the data date. Identify the authorised start and completion milestones, external interfaces and approved exceptions before reviewing open ends. A single-project export can omit external dependencies; confirm those in the source programme.
Read both sides of the activity
For each flag, inspect incoming and outgoing logic, WBS, scope description and responsible party. Ask the package owner what must be complete before this work starts and which downstream work it enables. Do not assume that the nearest activity in the list is the correct predecessor.
Correct or justify the relationship
Document a real dependency, its type and any lag rationale. If the activity is an intentional interface boundary, record the exception and supporting reference. Recalculate in P6, export again and compare the effect on dates and paths as well as the finding count.
Close the review with evidence
Keep the old and new XER filenames, activity code, issue, decision, owner, target date and reviewer. A resolved flag is useful only when the underlying logic represents the work. Removing scope to clear the flag is a different decision and must be visible.
Try the North Terminal example
| Evidence | Before | Review action |
|---|---|---|
| A160 vendor review | 0 predecessors / 0 successors | Confirm the release and the downstream acceptance handoff |
| PP-101 / PP-102 / PP-103 | One activity appears in three finding groups | Count the activity once in your action register |
| Revised sample | A140 → A160 → A150 | Inspect the supplied teaching relationship; do not copy it into a real project blindly |
Three flags can describe one underlying issue. The revised sample demonstrates the mechanics, not an approved contractual logic decision.
Take this checklist into the review
- Authorized start and finish boundaries recorded
- External-project links checked in P6
- Every added dependency has a scope reason
- Owner and acceptance evidence recorded
- Recalculated dates and driving paths reviewed
Inspect the open-logic demonstration
Find A160, inspect all three findings, then download both sample inputs.
Open the free demonstration →Further reading
These guides describe PlanProof’s current implementation and a suggested review workflow. External references provide broader scheduling context; they do not endorse or certify this tool.
References checked 6 October 2026. PlanProof methodology · Scoring model