Synthetic walkthrough · records exist only in this tab until reload. Exit to full ProjectLens
Compare two project schedules from Primavera P6 planning software with the project update. See the evidence behind the movement, then record a human decision.
Runs in your browser. Your schedule files stay with you.
“The key completion date is unchanged.”
Scheduled finish moves by 73 days.
What explains the revised finish?
Review what moved, see the evidence, then record your decision and any follow-up conditions.
Add the previous and current XER exports and the accompanying narrative.
Read finish dates, constraints, relationships and reported float beside the source fields.
Keep a factual movement distinct from its explanation. Name an owner and due date for missing evidence.
Record a human outcome and rationale. Export the evidence, then track any conditions.
ProjectLens compares the fields in your exports. A person interprets them and makes the decision.
Read the methodThe standard review reads your files locally. Saving a draft or decision stores it on this device. Downloads give you a copy to keep or share. Optional public-record research is separately configured and receives narrative text, never XER files.
A flagged change is a difference that needs review. Check its source and ask the owner to explain it. A later finish does not by itself prove why a project is late or who is responsible. These checks do not recalculate the critical path (the tasks that determine the finish), decide contractual rights or approve the change.
Two supported, single-project Primavera P6 XER exports from the same source project. ProjectLens checks their identity, dates and field coverage before comparing them. Missing fields and unsupported inputs are reported.
Start with the example, or review your own two schedule exports.
XER is the schedule export format from Primavera P6 planning software. Export both schedules (File → Export → Primavera XER): the previous submission and the current one. Your browser reads the files and uploads nothing. Add the narrative if you want ProjectLens to check what the update claims.
No XER files to hand? Download a synthetic pair from either example project and choose the files below: Northstar previous · Northstar current · Riverside previous · Riverside current. Optional narrative: Riverside narrative.
Choose 2 XER files to begin.
Resolve the blockers below or record why the decision authority accepts them.
Recheck a revision against these same schedules. The first checked narrative stays in the record. Unchecked edits do not change the decision evidence.
Each question keeps the finding that produced it. Add an owner and due date, then save the request.
ProjectLens saves the evidence version and any unresolved blockers with your decision. You make the decision; ProjectLens does not.
Mark Use or Ignore on every card before you save the decision.
Run a review to retrieve precedents.
Use attaches the case and its sources as context. Ignore records that you considered and dismissed it. Untouched cards stay not reviewed. Bundled records are illustrative context, not matched causal precedents. The XER comparison runs in this browser with fixed rules. Live retrieval, if configured, receives only narrative text and filters.
Open the full schedule evidence review ↗ How precedent retrieval works ↗Evidence review only. It does not establish contractual entitlement, causation or a probability of failure.
This demo stores decision records in this browser only.
Close or formally waive each condition attached to an approval.