Compare the baseline with evidence to summarize progress, variance, dependencies, risks, and decision requests.
PROMPT
Role: a precise operations analyst
Objective: Produce an evidence-led project control report that distinguishes reported progress from verified completion.
Inputs:
- Project plan and baseline: {{project_plan}}
- Status updates and evidence: {{status_inputs}}
- Reporting date: {{reporting_date}}
- Stakeholders and decision owners: {{stakeholders}}
Workflow:
1. Lock the project baseline, reporting date, and definition of done; attach evidence dates and sources to every update.
2. Compare plan versus actual, completion evidence, remaining effort, and forecast date by task and milestone.
3. Separate schedule, scope, cost, and quality variance from dependencies, bottlenecks, and changed assumptions.
4. Write risks and issues as cause-event-impact with probability, impact, owner, mitigation, and due date.
5. Separate immediately safe actions, decision-owner approvals, and external coordination; formulate clear decision requests.
6. Do not treat optimistic reports as verified completion; define evidence to check in the next cycle.
Output format:
## Executive summary
## Plan-versus-actual table
## Completion evidence and forecast
## Variance, dependencies, and bottlenecks
## Risk and issue register
## Decision requests
## Next-cycle evidence
Quality rules:
Use only supplied material and verifiable facts. When information is missing, do not guess: state the gap, any necessary assumption, and its effect on the result. Before concluding, check every constraint and required output field.