Planner AI Guide

Using Copilot With Primavera P6 Schedule Data

A practical workflow and prompt guide for project planners reviewing OHTL schedules exported from Primavera P6.

Audience: Project planners, schedulers, planning engineers, project controls teams, and managers.

Scope: Primavera P6 schedules exported as PDF, Excel, CSV, XER/XML summaries, and related reports uploaded to Copilot.

Core rule: P6 remains the official source of truth. Copilot supports analysis, reporting, risk review, and decision preparation.

1. Purpose

This guide explains how a planner can use AI, especially Microsoft Copilot, to analyze Primavera P6 schedule outputs after upload. It is written for OHTL projects, but the workflow can also be used for substations, infrastructure, EPC, and construction schedules.

Copilot should be used to speed up schedule review, summarize large reports, identify risks, prepare lookahead plans, draft management updates, and convert P6 data into action trackers. It should not replace Primavera P6 calculations, planner judgment, contractual delay analysis, or formal schedule approval.

Main principle: Primavera P6 is the planning engine and official schedule record. Copilot is the schedule analyst, reviewer, reporter, and risk assistant around it.

2. Recommended Workflow

Step	Planner Action	Copilot Use	Control Point
1. Maintain official schedule in P6	Update progress, data date, calendars, logic, constraints, baselines, resources, and activity status in Primavera P6.	Do not use Copilot to replace P6. Use it only after exporting reviewed data.	Confirm the P6 schedule has been calculated before export.
2. Export schedule data	Export PDF reports and Excel/CSV tables from P6. Include activity, relationship, milestone, baseline, and progress data where possible.	Upload the files to Copilot for analysis.	Use consistent file names with project, data date, revision, and report type.
3. Analyze, summarize, and report	Ask Copilot to summarize the schedule, identify critical path, low float, delays, risks, and required actions.	Use structured prompts and request tables with Activity ID, WBS, dates, float, risk, and action.	Ask Copilot to separate confirmed findings from assumptions and missing data.
4. Validate findings in P6	Check Copilot findings inside P6 before issuing reports.	Ask Copilot to create a validation checklist.	Planner confirms critical path, float, dates, logic, and baseline variance in P6.
5. Feed approved corrections back into P6	Make approved corrections manually in P6.	Use Copilot to prepare a correction log and change summary.	Recalculate P6 and compare previous versus revised exports.
6. Keep an audit trail	Save uploaded files, prompts, AI findings, validation notes, approvals, and final report versions.	Ask Copilot to create an audit trail table.	Human approval remains mandatory for official reports and schedule changes.

3. Best Files To Upload To Copilot

PDF reports are helpful for management-style review, but Excel/CSV exports are better for accurate activity-level analysis.

File Type	Recommended Content	Best Use In Copilot
PDF schedule report	Layouts, Gantt pages, milestones, WBS summaries, and printable P6 reports.	Executive summary, visual schedule review, narrative reporting.
Activity table Excel/CSV	Activity ID, name, WBS, duration, start, finish, float, percent complete, baseline dates.	Critical path review, variance, progress status, lookahead planning.
Relationship report	Predecessors, successors, relationship type, lag, activity IDs.	Logic quality review, missing links, high lag, sequencing risks.
Baseline comparison report	Baseline start/finish, current start/finish, start variance, finish variance.	Delay analysis, variance narrative, management reporting.
Milestone report	Contractual, internal, engineering, procurement, construction, commissioning milestones.	Milestone dashboard and key date tracking.
Schedule log	Warnings, constraints, open ends, out-of-sequence progress, calendar issues.	Schedule quality review and audit support.

Minimum Recommended Columns

Activity ID Activity Name WBS Original Duration Remaining Duration Start Finish Baseline Start Baseline Finish Actual Start Actual Finish Percent Complete Total Float Free Float Predecessors Successors Calendar Constraint Type Constraint Date Activity Status Resource or Discipline Location or Line Section

4. Master Copilot Instruction

Use this instruction immediately after uploading the schedule files.

You are a project controls analyst reviewing uploaded Primavera P6 schedule files for an OHTL project. Use only the uploaded files. Do not guess missing dates, float, relationships, resources, progress values, or delay causes. If information is not available, state "Not available in the uploaded file." Where possible, reference Activity ID, Activity Name, WBS, source file, and page or table. Separate confirmed findings from items that need validation in Primavera P6. Return important findings in tables.

5. Copilot Use Cases And Prompts

5.1 Data Availability Check

Review the uploaded Primavera P6 files and identify which schedule fields are available. Create a data availability checklist covering Activity ID, Activity Name, WBS, start date, finish date, baseline dates, actual dates, percent complete, total float, predecessors, successors, constraints, calendars, resources, and location. Mark each field as Available, Partially Available, or Not Available.

5.2 Schedule Summary

Summarize the uploaded Primavera P6 schedule for this OHTL project. Include project start date, finish date, data date if visible, total duration, major WBS areas, key milestones, and the overall construction sequence.

Create an executive schedule summary in 10 bullet points for a project manager. Focus on completion date, critical path, delayed areas, upcoming milestones, major risks, and decisions required.

5.3 Key Milestones

Extract all major milestones from the schedule. Show milestone name, Activity ID, WBS, planned date, baseline date if available, current date, variance if available, and whether it appears to be contractual or internal.

5.4 Critical Path And Float Review

Identify the critical path activities from the uploaded schedule. Provide Activity ID, Activity Name, WBS, Start, Finish, Total Float, and a plain-language explanation of how the activity drives project completion.

List all activities with zero, negative, or low total float. Use low float as less than 10 days unless the file defines another threshold. Show Activity ID, Activity Name, WBS, Finish, Total Float, risk comment, and recommended action.

5.5 Schedule Logic Quality

Review the schedule logic quality from the uploaded P6 files. Identify missing predecessors, missing successors, excessive lags, hard constraints, open-ended activities, out-of-sequence activities, and unusual sequencing. Provide Activity ID, issue, risk, and recommended P6 validation step.

5.6 OHTL Sequence Review

Check whether this OHTL schedule follows a logical sequence: survey, soil investigation, design approval, ROW clearance, access roads, foundations, tower supply, tower erection, conductor stringing, OPGW stringing, testing, commissioning, energization, and handover. Identify missing activities, wrong sequence, weak links, and major risks.

5.7 Baseline And Variance Analysis

Compare baseline dates with current schedule dates. Identify activities with start variance or finish variance. Show Activity ID, Activity Name, WBS, Baseline Start, Current Start, Start Variance, Baseline Finish, Current Finish, Finish Variance, and likely schedule impact.

5.8 Progress And Status Review

Analyze schedule progress from the uploaded files. Identify activities that should have started but have not started, activities that should have finished but are incomplete, in-progress activities with high remaining duration, and activities behind plan. Use the data date where available.

5.9 Lookahead Planning

Create a 4-week lookahead plan from the schedule. Include Activity ID, Activity Name, WBS, Location or Line Section if available, Planned Start, Planned Finish, Predecessor Requirement, Discipline, and Action Required.

Create a 90-day lookahead schedule summary for management review. Group the work by engineering, procurement, ROW, foundations, tower erection, stringing, testing, commissioning, and handover.

5.10 Procurement And Long-Lead Items

Identify procurement-related activities in the schedule. Include design approval, material approval, manufacturing, inspection, delivery, and site readiness activities. Highlight long-lead items such as towers, conductors, insulators, OPGW, hardware fittings, gantries, and protection equipment where visible.

5.11 Engineering And Approvals

Extract all engineering, design, drawing, approval, permit, and interface activities. Show Activity ID, Activity Name, WBS, Start, Finish, Float if available, and explain which site activities depend on them.

5.12 Risk Register

Create a schedule risk register from the uploaded P6 data. Include Risk ID, risk description, related Activity ID, cause, impact, probability, severity, mitigation action, owner placeholder, priority, and whether P6 validation is required.

5.13 Recovery And Mitigation Plan

Suggest schedule recovery actions for delayed, critical, and near-critical activities. Consider resequencing, parallel work fronts, additional crews, extended working hours, procurement expediting, approval acceleration, ROW resolution, and commissioning readiness. Show Activity ID, issue, recovery option, expected benefit, constraint, owner, and priority.

5.14 Reporting And Communication

Prepare a weekly schedule review report from the uploaded P6 files. Include executive summary, project status, critical path, delayed activities, upcoming milestones, 4-week lookahead, key risks, recovery actions, and decisions required.

Draft a concise email update to the project manager summarizing the schedule status, critical path, delayed areas, risks, and required actions. Use professional project controls language.

6. Validation In Primavera P6

Copilot output must be validated in Primavera P6 before being issued as an official schedule report.

Finding Type	Validate In P6	Reason
Critical path	Check total float, longest path setting, calendars, constraints, and relationship logic.	PDF or Excel reports may not show all calculation settings.
Low or negative float	Confirm total float values after schedule calculation.	Float depends on calendars, constraints, progress, and schedule options.
Baseline variance	Check assigned baseline and current schedule version.	Wrong baseline selection can distort variance.
Missing logic	Review predecessor and successor tabs for the activity.	Exported reports may omit some relationships or external links.
Delay cause	Check progress records, correspondence, site records, and approved delay events.	Schedule data alone may show impact but not contractual responsibility.
Recovery option	Model the change in P6 before approval.	Acceleration ideas must be tested against logic, resources, calendars, and constraints.

Validation Prompt

Create a validation checklist for the Copilot schedule findings. For each finding, tell me exactly what must be checked in Primavera P6 before it can be included in an official report. Group the items as Confirmed from uploaded data, Needs P6 validation, and Not supported by available data.

7. Feeding Approved Corrections Back Into P6

After human review, use Copilot to prepare a clear correction log. The planner should then update P6 manually, recalculate the schedule, and re-export the revised reports.

Based on the validated findings, prepare a Primavera P6 correction log. Include Issue No., Activity ID, Activity Name, current issue, recommended correction, reason for correction, priority, owner, and status.

Correction Type	Typical Planner Action In P6
Missing logic	Add predecessor or successor relationships after confirming the correct technical sequence.
Excessive constraint	Remove or revise constraints where logic can drive the date.
Long-duration activity	Break into measurable activities by location, section, or workfront.
Weak OHTL sequence	Link design, procurement, foundations, tower erection, stringing, testing, and energization correctly.
Missing milestone	Add contract, internal, engineering, procurement, construction, commissioning, and handover milestones as required.
Poor reporting structure	Improve WBS, activity codes, location codes, discipline codes, and filters.

8. Audit Trail

For controlled project environments, each AI-assisted schedule review should be traceable.

Audit Item	What To Save
Uploaded files	PDF, Excel, CSV, XER/XML reports, schedule logs, and baseline comparison reports.
Prompt record	Master instruction, analysis prompts, reporting prompts, and any follow-up prompts.
AI output	Findings, tables, risk register, report draft, and correction log.
Human validation	Planner comments, accepted findings, rejected findings, and P6 checks performed.
Approved actions	P6 corrections, schedule revision, report issue date, and approver name.

Create an audit trail table for this schedule review. Include uploaded file name, Copilot prompt used, key finding, whether P6 validation is required, planner validation comment, accepted or rejected status, action taken, reviewer, and date.

9. Quick Start Prompt Sequence

Upload the P6 PDF and Excel/CSV exports.
Run the master instruction prompt.
Ask for a data availability checklist.
Ask for a schedule summary.
Ask for key milestones.
Ask for critical path and low-float activities.
Ask for baseline variance and progress issues.
Ask for OHTL sequence review.
Ask for risk register and recovery plan.
Ask for weekly report, action tracker, and validation checklist.

10. Limits And Controls

Do not upload confidential project data to an unapproved AI environment.
Do not treat Copilot output as contractual proof without planner, project controls, and commercial validation.
Do not let Copilot invent missing dates, float, causes, or responsibilities.
Do not update the official P6 schedule based only on AI output.
Always validate critical path, total float, baseline variance, calendars, constraints, and logic in P6.
Keep a record of prompts, findings, validation notes, corrections, and approvals.

Best short instruction to use every time:

Use only the uploaded Primavera P6 files. Do not guess. Show Activity ID and source reference wherever possible. Separate confirmed findings from items that need validation in Primavera P6.

Prepared as a combined AI use guide for planners based on Primavera P6, Copilot schedule review, OHTL schedule analysis, validation, correction control, and audit trail practices.