ManagementIntermediateEngineeringManufacturing

Project Progress & Risk Management Prompt

Produces a progress-tracking and risk-register template for an engineering or systems project.

Audience: PM, project managers · Last updated 2026-07-17
Contents

Scenario

Produces a progress-tracking and risk-register template for an engineering or systems project.

Applicable Industry or Company Size

  • Engineering
  • Manufacturing

Preparation Before Use

  • The project charter or SOW.
  • Team member roles.

Variable Reference

VariableDescription
[Company Name]Your company's official name
[Project Name]This project's name
[Project Type]e.g., data-center cabling, ERP implementation
[Target Completion Date]e.g., launch by Q2, within 3 months

Full Prompt

Prompt
You are a senior PMO consultant. Produce a progress-tracking and risk-management framework for the following project.

[Background]
- Company: [Company Name]
- Project Name: [Project Name]
- Project Type: [Project Type]
- Target Completion Date: [Target Completion Date]

[Output]
1. The first two levels of a WBS.
2. Recommended milestones and deadlines.
3. A risk register: risk / impact / probability / score / mitigation / owner. List 10 initial risks.
4. A weekly progress-report format.
5. A communication plan (who, what, frequency, channel).
6. A change-control process.

[Judgment Criteria] Risk descriptions must include a trigger condition and quantified impact; avoid simply writing "delay."

[Handling uncertain information]
If any of the variables below have not been filled in or the information is insufficient, list the missing fields directly and ask the user — do not assume or fabricate data.

[Prohibited]
- Do not fabricate statistics, regulation numbers, certification names, or client case studies.
- When professional judgment is insufficient, explicitly mark "requires human confirmation" rather than inferring on your own.

[Final self-check]
After producing the output, list a self-check at the end covering: (1) whether any fabricated numbers, regulations, standards, or client names were used; (2) whether any unfilled but important variable was ignored; (3) whether assumptions are clearly labeled.

Usage Steps

  1. Fill in the variables.
  2. Confirm the WBS with the team.
  3. Include in the weekly project meeting.

Example

Common risks in data-center projects: site-access restrictions, delayed material delivery, power-window constraints.

Common Mistakes

  • Setting milestones to "finish as soon as possible."

Cautions

  • The risk register must be updated continuously.
Last updated 2026-07-17

Need further customization to fit your company's process and industry?

AEGIS POWER INTEGRATIONS offers AI adoption, process assessment, and systems integration consulting to help you turn prompts into a stable, working internal process.