From 888b71f486027de14d9cd94799d2ffd2bebccaad Mon Sep 17 00:00:00 2001 From: Matthew Paver <30728931+MatthewPaver@users.noreply.github.com> Date: Sat, 24 Oct 2026 18:20:49 +0100 Subject: [PATCH] fix: explain flagged schedule changes in the existing help --- docs/change-assurance.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/change-assurance.html b/docs/change-assurance.html index 2ebebbe..727e2ea 100644 --- a/docs/change-assurance.html +++ b/docs/change-assurance.html @@ -102,7 +102,7 @@

Follow one complete review.

Clear evidence. Clear limits.

ProjectLens compares the fields in your exports. A person interprets them and makes the decision.

Read the method
Do my schedule files leave this browser?

The 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.

-
Does a flagged change mean the project is delayed?

A later scheduled finish is an observed difference between exports. These checks do not recalculate the critical path or establish cause, contractual entitlement or the right decision.

+
Does a flagged change mean the project is delayed?

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.

What can I compare?

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.