|
||||||||
|
||||||||
|
MICROSOFT 365 COPILOT / WEEK 34
PLAN.
|
||||||||
|
||||||||
BUILD THE HISTORY
|
|
USE CASE
Gather delay discussion history to support formal delay analysis documentation.
|
FOR
Planner, Claims Analyst, Project Controls
|
| PROMPT / COPY-READY |
|
Search project correspondence for discussions about delays to [milestone/activity]. Compile: - When the delay was first reported - Causes mentioned by different parties - Recovery proposals discussed - Any schedule impact assessments referenced This is research for delay analysis documentation - requires formal analysis. |
| FORMAL ANALYSIS REQUIRED | Use the result as a research input. Confirm the chronology, source correspondence and contractual interpretation before relying on it. |
| DOCUMENT CONTROL / FOLLOW-UP | 07 / STATUS |
TURN OVERDUE EMAIL
INTO A STATUS LIST.
Surface late deliverables, reasons, commitments and named owners before the next document status meeting.
|
USE CASE
Identify overdue documents and their causes from email discussions.
|
FOR
Document Controller, Project Administrator, Engineering Administrator
|
| PROMPT / COPY-READY |
|
Search my emails from the past 2 weeks for discussions about overdue documents or late deliverables for [Project Name]. List: - Documents mentioned as late - Reasons given for delays - Commitments made for delivery dates - Who is responsible (as mentioned) I need this to prepare for the document status meeting. |
| KNOWLEDGE MANAGEMENT / CLOSE-OUT | 08 / EXPERIMENTAL |
FIND RECURRING
SCHEDULE LESSONS.
Review project communications for patterns worth discussing with the planning team during project close-out.
|
USE CASE
Identify schedule-related lessons from project communications for close-out.
|
FOR
Planner, Project Controls Manager, PMO
|
| PROMPT / COPY-READY |
|
Review project emails for [Project Name] and identify recurring themes related to schedule performance: - What caused delays repeatedly? - What worked well for recovery? - Any recommendations mentioned? Compile as input for project close-out. Requires validation with project team. EXPERIMENTAL: May miss context or misinterpret technical schedule discussions. Always validate with the planning team. |
| EXPERIMENTAL | Copilot may miss context or misinterpret technical schedule discussions. Always validate the output with the planning team. |
Replace every bracketed field, narrow the project or timeframe where possible, and check the result against its original sources.
| ALL THE PROMPTS AND TIPS HERE → |
| OPEN MICROSOFT 365 COPILOT → |
|
WEEKLY COPILOT TIPS
PRACTICAL AI SUPPORT FOR Y.CO TEAMS
|
PLANNING & PROJECT CONTROLS |