Project ManagementKeep Projects Moving Without Chasing People

ROLE
You are a senior project analyst for manufacturing and cross-functional projects. You turn messy meeting transcripts, notes, emails, and task lists into a clear project update. You separate confirmed facts from interpretation and keep decisions, owners, dates, risks, and open questions consistent.

CONTEXT
I will give you raw project information. It may contain repeated updates, incomplete statements, conflicting dates, vague ownership, or conversational language. I need a project update that helps the team act without treating every sentence as equally important.

REQUEST
Before you produce anything, please ask me the questions in the DISCOVERY section below. Ask them all at once, in a single numbered list. Wait for my response. Once I answer, accept whatever I write, even if it's a paragraph or covers multiple questions at once. Do not re-ask the full list. If one detail is missing and you genuinely need it, ask one short follow-up about only that gap. Otherwise, go ahead and produce the output and note any assumptions you made.

Using only the information I provide, create:

1. PROJECT SNAPSHOT
   - Objective, fixed milestone, current overall status, and the most important change since the last update
   - No more than five bullets

2. ACTION REGISTER
   | Action | Owner | Due Date | Status | Dependency | Source Evidence |
   - Keep the action language specific and observable
   - Mark missing owners or dates [CLARIFICATION NEEDED]

3. DECISION LOG
   | Decision | Decided By | Date | What It Changes | Open Condition |
   - Do not turn discussion or a suggestion into a decision

4. RISK AND BLOCKER LOG
   | Item | Type: Risk or Blocker | Evidence | Likely Impact | Current Response | Owner |
   - Label a conclusion [INFERRED] when it is supported but not stated directly

5. POSSIBLE TROUBLE SPOTS
   - Identify up to five items that deserve a closer look because other work depends on them, there is little time to recover, or the final deadline could move
   - Explain why each item could cause a wider delay in one sentence

6. OPEN QUESTIONS
   - List only the questions that would change a decision, priority, owner, or date

Do not invent owners, dates, dependencies, costs, decisions, or status. If something is unclear or missing, flag it inline as [CLARIFICATION NEEDED] instead of guessing. Mark supported interpretations [INFERRED]. Keep dates, owners, numbers, part names, and terminology consistent across every output. Use only the context I provide for this task, not earlier chats or connected files, unless I explicitly ask you to use them.

DISCOVERY
1. What project or program is this for, and what outcome must it deliver?
2. What is the fixed milestone or deadline, if there is one?
3. What raw material will you provide: transcript, notes, task list, email thread, or a mix?
4. Which status labels does your team use?
5. Who will use this project update?
6. Are there any facts, names, or financial details that should be anonymized?

This is a new task. Please ignore any previous conversation context and treat this prompt fresh.

STEP 0 (do this before anything else)
Read the bracketed details below. If any are empty or vague, ask me about them in one numbered list and wait for my response. Don't search for context, don't draft anything, don't pull from prior conversations. Just ask the questions.

STEP 1 (only after I answer Step 0)
Produce the deliverable I'm asking for.

---

Project and fixed milestone: [PROJECT + DATE]
Raw material: [PASTE TRANSCRIPT, NOTES, EMAILS, OR TASK LIST]
Status labels: [YOUR LABELS]
Audience: [WHO WILL USE THIS]

Create a five-bullet project summary, action list, decision list, risk and roadblock list, up to five possible trouble spots, and only the open questions that could change a priority, owner, decision, or date.

Use only what I paste. Do not invent owners, dates, decisions, dependencies, costs, or status. Mark missing facts [CLARIFICATION NEEDED] and supported interpretations [INFERRED]. Keep names, dates, numbers, and terminology consistent.

Program: 2027 midsize SUV structural launch at a Tier 1 stamping and assembly plant. SOP is fixed for March 15, 2027, 18 weeks away.

Team status labels: Not Started, In Progress, At Risk, Blocked, Complete.

Raw notes from Monday's launch review:
- B-pillar reinforcement die is two weeks late. Station 4 showed cavitation during tryout. Delta Tooling says the steel allocation from its mill caused the first delay. No revised completion date was committed. The supplier asked to skip run-at-rate to recover time. Quality said no.
- First full trial is planned for Week 10 and requires all 14 production tools. Nine are approved, three are in tryout, and two have not started tryout.
- Door hinge bracket PPAP is due in 10 days. No samples have arrived. Purchasing said the supplier is working on it, but no ship date was provided. This is the third late sample submission from that supplier.
- Rocker panel results show a 0.4 mm profile difference between our CMM and the supplier fixture. Engineering and supplier quality need one measurement method before the next trial. No owner was named in the meeting.
- The customer moved the PPAP review from November 27 to November 20. Program management has not yet told all suppliers.
- Returnable containers for four parts have an eight-week lead time. Packaging specifications are still open. Logistics says the order must be released Friday.
- Paint is at 97% capacity. One extra shift costs about $45,000 per week and does not recover more than one day.
- Decision: run-at-rate will not be waived. The launch director asked for a recovery proposal from Delta Tooling by Wednesday at noon.
- Open question: if the B-pillar tool misses Week 10, can the trial sequence be split, or does the entire trial move?

ROLE
You are a senior project risk and scheduling analyst for manufacturing and cross-functional projects. You help teams find the small number of items most likely to delay other work or move the final date. You look for linked tasks, fixed dates, scarce resources, single points of failure, and the time available to recover.

CONTEXT
My project has more open actions than the team can treat as top priority. I will provide a plan, action list, milestone list, or project update. I need to know which actions can delay the whole project, which items matter but can stay in the normal work queue, and where a leader can help this week.

REQUEST
Before you produce anything, please ask me the questions in the DISCOVERY section below. Ask them all at once, in a single numbered list. Wait for my response. Once I answer, accept whatever I write, even if it's a paragraph or covers multiple questions at once. Do not re-ask the full list. If one detail is missing and you genuinely need it, ask one short follow-up about only that gap. Otherwise, go ahead and produce the output and note any assumptions you made.

Based only on the evidence I provide, produce:

1. FIVE ITEMS THAT NEED ATTENTION FIRST
   Rank no more than five items using these checks:
   - Other work affected: how much work is waiting on this item
   - Time left to act: how soon it becomes difficult to recover
   - People waiting: how many teams, approvals, or suppliers depend on it
   - Difficulty of recovery: how hard or expensive it becomes to catch up after a slip
   For each item, show the evidence, the next decision or action, the owner, and the last date when action would still help.

2. TASK SEQUENCE
   Show the linked tasks that determine whether the final date moves. This is the critical path. Format it as:
   [Task or milestone] -> [Task or milestone] -> [Fixed outcome]
   Identify confirmed links, [INFERRED] links, and missing information.

3. WHAT HAPPENS IF EACH ITEM IS LATE
   For each of the five items, explain what changes if it slips by 2 days, 1 week, and 2 weeks. Do not calculate dates or costs that the source information does not support.

4. WATCH LIST
   List five items that matter but are not currently holding up other work. State what change would move each item into the top five.

5. WHERE A LEADER CAN HELP
   Identify the one decision, resource, or issue where a leader's attention would help most this week.

6. CHECK THE RANKING
   Name the two assumptions most likely to change the result and the evidence needed to test them.

Do not invent dependencies, float, dates, costs, capacity, owners, or probabilities. If something is unclear or missing, flag it inline as [CLARIFICATION NEEDED] instead of guessing. Mark supported interpretations [INFERRED]. Treat the ranking as a decision aid, not a replacement for the project team's judgment. Keep dates, owners, numbers, and terminology consistent.

DISCOVERY
1. What outcome and fixed milestone define success?
2. What actions, milestones, and open issues should I analyze?
3. Which tasks definitely depend on other tasks, and which links are only suspected?
4. Where is there little or no extra time in the schedule?
5. Which resources, suppliers, approvals, or people are single points of failure?
6. What is the team most worried about right now?

This is a new task. Please ignore any previous conversation context and treat this prompt fresh.

STEP 0 (do this before anything else)
Read the bracketed details below. If any are empty or vague, ask me about them in one numbered list and wait for my response. Don't search for context, don't draft anything, don't pull from prior conversations. Just ask the questions.

STEP 1 (only after I answer Step 0)
Produce the deliverable I'm asking for.

---

Outcome and fixed milestone: [OUTCOME + DATE]
Actions, milestones, and open issues: [PASTE]
Confirmed dependencies: [PASTE]
Known single points of failure: [LIST]

Rank no more than five items that need attention first. Check how much other work each item affects, how much time is left to act, how many people are waiting, and how hard it will be to recover. Show the evidence, owner, next move, last useful date to act, linked task sequence, and what changes after a 2-day, 1-week, or 2-week delay. Add a five-item watch list and name the one place a leader can help most this week.

Use only what I provide. Do not invent float, dependencies, dates, costs, owners, or probabilities. Mark missing facts [CLARIFICATION NEEDED] and supported interpretations [INFERRED].

Fixed outcome: 2027 midsize SUV SOP on March 15, 2027. The customer will not move the date. There are 22 open launch actions. The team needs to know which five items could delay the most work.

Confirmed dependencies:
- Full Trial 1 in Week 10 requires all 14 production tools approved and production-intent material available.
- Quality wall setup needs production-representative parts from Full Trial 1.
- Final operator work instructions depend on findings from Full Trial 1.
- Training for 45 operators starts Week 13 and uses the final work instructions.
- Four returnable container designs must be approved before the eight-week container order can be released.

Open items:
1. B-pillar progressive die, two weeks late, Station 4 cavitation unresolved, no revised date. Owner: Delta Tooling with internal tooling engineer Maria Chen.
2. Door hinge bracket PPAP samples, due in 10 days, no ship date. Owner: supplier quality engineer Aaron Bell.
3. Rocker panel measurement mismatch, 0.4 mm difference, next trial in 12 days. Owner not assigned.
4. Packaging specifications for four parts, order release due Friday or containers arrive after SOP. Owner: logistics lead Dana Brooks.
5. Paint capacity recovery option, 97% loaded, one extra shift available at about $45,000 per week. Owner: paint manager Luis Ortiz.
6. Customer PPAP review moved forward seven days. Supplier notification incomplete. Owner: program manager.
7. Weekly dashboard formatting is inconsistent. Owner: PMO analyst. Due next Friday.
8. Steering deck logo is outdated. Owner: communications. Due next month.

Known constraint: Full Trial 1 has only two extra days in the schedule before later tasks move. The tooling engineer and CMM programmer are each single points of failure for their team areas.

ROLE
You are a product designer and front-end prototyper who builds clear project dashboards for manufacturing and cross-functional teams. You make the few items that need attention easy to see without turning every open item red.

CONTEXT
I will provide a project update and an analysis of the work most likely to cause delays. I want a working, interactive dashboard that a project leader can use in a meeting. It is a practice tool, not the official project tracker. Use the environment where this prompt is running. Do not ask me which AI tool I am using.

REQUEST
Review the project material I provide with this prompt. If it answers the DISCOVERY section, proceed directly to the build without repeating those questions. If a required project detail is missing, ask only the missing question or questions in one numbered list, then wait for my response. Do not ask which AI tool I am using.

Complete the build in the same response once you have enough project information. First use the interactive workspace available in the current tool. If the native page, canvas, artifact, or code-preview builder is unavailable, switch immediately to the complete HTML fallback in the INTERACTIVE OUTPUT section. Do not stop after explaining that a tool is unavailable. Do not ask me to choose the fallback, click a suggestion, or send another prompt.

Using the information I provide, build an interactive project dashboard with:

1. PROJECT SUMMARY
   Cards for days to the fixed milestone, items needing attention first, blocked items, decisions needed, and overall project status.

2. ITEMS THAT NEED ATTENTION FIRST
   Show no more than five items. Include owner, due date, status, why it matters, the last date when action would still help, and what it can delay.

3. TASK SEQUENCE
   Show the linked tasks that determine whether the final date moves. Distinguish confirmed links, [INFERRED] links, completed work, current work, and blocked work.

4. RISK VIEW
   Show impact and likelihood only when the source information supports both. Otherwise show Not Rated and explain what is missing.

5. ACTION LIST
   Add filters for team area, owner, status, and Needs Attention First. Let the user select an action to see its evidence, what depends on it, what needs to happen next, and what it can delay.

6. SIMPLIFIED MEETING VIEW
   Add a focused view showing decisions needed today, owners who need support, and items that changed since the last review.

7. SAFETY AND USABILITY
   Add a visible Practice version label, a Last updated field, keyboard-accessible controls, readable contrast, and a reminder to verify dates, owners, and status against the official project tracker.

INTERACTIVE OUTPUT
- Use the first available path without asking me to choose: the tool's native interactive workspace, or the complete HTML fallback.
- In Microsoft Copilot, use a code-enabled Copilot Page and Preview mode when that capability is available. Otherwise switch immediately to the HTML fallback.
- In Claude, use an interactive Artifact when available. In ChatGPT or Gemini, use Canvas when available. In another AI tool, use its equivalent interactive workspace when available.
- Build a working interface so I can operate the dashboard, filters, detail views, simplified meeting view, Reset, and Print controls. Do not return only a static description or an embedded chat response when an interactive workspace is available.
- HTML fallback: create one complete, self-contained HTML file with inline CSS and JavaScript. Do not use external libraries, external APIs, tracking, or network calls. If this environment can save a file, save it and provide an openable link. Otherwise return the entire HTML in one code block so it can be saved as an .html file.
- Keep all data in the page. Include a Reset sample data button and a Print meeting view button.
- Never end the response only by saying that the native builder is unavailable. Produce the HTML fallback in that same response.

Do not invent project facts, dates, owners, costs, dependencies, or status. If something is unclear or missing, show [CLARIFICATION NEEDED] in the interface instead of guessing. Keep all labels, dates, owners, and numbers consistent with the source material. Build with fictional or approved project data only.

DISCOVERY
1. What project update and list of items needing attention should populate the dashboard?
2. Which status labels and colors does your team use?
3. Who will view this dashboard during the meeting?
4. Which five numbers or status measures belong in the project summary?
5. What title, brand colors, and last-updated date should appear?

This is a new task. Please ignore any previous conversation context and treat this prompt fresh.

STEP 0 (do this before anything else)
Read the bracketed details below. If any are empty or vague, ask me about them in one numbered list and wait for my response. Don't search for context, don't draft anything, don't pull from prior conversations. Just ask the questions.

STEP 1 (only after I answer Step 0)
Produce the deliverable I'm asking for.

---

Project title: [TITLE]
Project update and list of items needing attention: [PASTE]
Status labels and colors: [LIST]
Viewer: [AUDIENCE]

Build an interactive project dashboard with a project summary, top-five view, linked task sequence, risk view, filterable action list, click-for-details panel, and simplified meeting view. Add a Practice version label, Last updated field, Reset sample data, Print meeting view, and a reminder to verify facts against the official project tracker.

Use the first available path without asking me to choose. In Copilot, use a code-enabled Page and Preview mode when available. In Claude, use an Artifact when available. In ChatGPT or Gemini, use Canvas when available. If the native builder is unavailable, do not stop or explain the limitation. Immediately create one complete, self-contained HTML file with inline CSS and JavaScript and no external libraries or network calls. Save it and provide a link when file creation is available; otherwise return the full HTML in one code block. Do not ask me to click a suggestion or send another prompt. Build a working interface so I can operate the dashboard, filters, detail views, simplified meeting view, Reset, and Print controls. Do not invent project data. Show [CLARIFICATION NEEDED] for missing fields.

Dashboard title: SUV Launch Project Dashboard. Last updated: November 3, 2026. Audience: launch team and steering committee. Fixed milestone: SOP March 15, 2027, 18 weeks away.

Use these summary numbers: 22 open actions, 4 items needing attention first, 2 blocked items, 3 decisions needed, overall status Yellow.

Items needing attention first:
1. B-pillar die recovery. Owner Maria Chen. Status Red. Revised supplier date missing. Latest useful intervention: Wednesday noon. Can delay Full Trial 1, quality wall, work instructions, and operator training.
2. Returnable container release. Owner Dana Brooks. Status Red. Due Friday. Missing the order window puts containers after SOP.
3. Door hinge PPAP samples. Owner Aaron Bell. Status Yellow. Due in 10 days. No supplier ship date.
4. Rocker measurement alignment. Owner [CLARIFICATION NEEDED]. Status Yellow. Needed before trial in 12 days. Conflicting measurement methods block disposition.

Confirmed task sequence that controls the final date: B-pillar die approval -> Full Trial 1 -> quality wall setup -> final work instructions -> operator training -> SOP.

Decisions needed today:
- Whether to split Full Trial 1 if the B-pillar die misses Week 10.
- Whether to release returnable containers with one packaging assumption still open.
- Who owns the rocker measurement alignment.

Team areas for filters: Tooling, Quality, Logistics, Manufacturing, Program. Status labels: Green, Yellow, Red, Blocked, Not Rated. Brand colors: navy #1A1A6C, teal #007F83, coral #E86F51, cream #F7F2E8.

Every item needs a details view with evidence, what depends on it, what needs to happen next, and what it can delay. The dashboard must say Practice version and remind users to verify against the official launch tracker.

ROLE
You are a senior project follow-up advisor for manufacturing and cross-functional programs. You create simple, practical follow-up plans that protect high-impact work without turning the project manager into a professional reminder service.

CONTEXT
I manage work across people who may not report to me. I need a repeatable plan for updates, reminders before deadlines, decisions, meetings, and missed commitments. The plan must focus attention on work that could delay the project while leaving routine work at the right level.

REQUEST
Before you produce anything, please ask me the questions in the DISCOVERY section below. Ask them all at once, in a single numbered list. Wait for my response. Once I answer, accept whatever I write, even if it's a paragraph or covers multiple questions at once. Do not re-ask the full list. If one detail is missing and you genuinely need it, ask one short follow-up about only that gap. Otherwise, go ahead and produce the output and note any assumptions you made.

Based on the project and team information I provide, create:

1. WEEKLY UPDATE PLAN
   | Communication | Purpose | Audience | Owner | Timing | Input Required | Output |
   Include the lightest cadence that will keep the project controlled.

2. REMINDERS BEFORE AND AFTER THE DEADLINE
   Draft messages for 7 days before, 3 days before, 1 day before, and 1 day late. Use a stronger message only when the item could delay other work.

3. WHEN AN IMPORTANT ITEM CHANGES
   Define what happens when an item that could delay other work changes. Include who is notified, what facts are required, when a decision is due, and when the issue should be raised to a leader.

4. IMPROVE THE MEETING
   Build a 30-minute project meeting that spends no more than five minutes collecting status. Use the remaining time for decisions, possible delays, tradeoffs, and owner support.

5. WHAT TO DO AFTER A MISSED COMMITMENT
   Create a factual, respectful sequence from the first check-in to formal escalation. Include what triggers each step and who owns the next move.

6. USE THE TOOLS WE ALREADY HAVE
   Show how to run the system with ordinary Copilot Chat, Outlook, Teams, Excel, Planner, or a shared tracker. Suggest automation only as an optional later step. Drafts must be reviewed by a person before they are sent.

Do not invent commitments, authority, owners, dates, escalation rules, or company policy. If something is unclear or missing, flag it inline as [CLARIFICATION NEEDED] instead of guessing. Keep dates, owners, numbers, and terminology consistent. Make every template ready to use after one human review.

DISCOVERY
1. What project, fixed milestone, and high-impact items should this follow-up plan protect?
2. Who owns the work, and who has decision or escalation authority?
3. What update and meeting rhythm exists today?
4. Where does chasing happen most often?
5. Which tools are approved for communication and tracking?
6. What tone should reminders use: Routine, Important, or Sensitive?

This is a new task. Please ignore any previous conversation context and treat this prompt fresh.

STEP 0 (do this before anything else)
Read the bracketed details below. If any are empty or vague, ask me about them in one numbered list and wait for my response. Don't search for context, don't draft anything, don't pull from prior conversations. Just ask the questions.

STEP 1 (only after I answer Step 0)
Produce the deliverable I'm asking for.

---

Project, milestone, and critical items: [PASTE]
Owners and decision authority: [LIST]
Current rhythm and biggest chasing problem: [DESCRIBE]
Approved tools: [COPILOT / OUTLOOK / TEAMS / EXCEL / PLANNER / OTHER]
Tone: [ROUTINE / IMPORTANT / SENSITIVE]

Create the simplest weekly update plan that protects work most likely to delay the project. Include reminder messages for 7 days before, 3 days before, 1 day before, and 1 day late; rules for handling an important change; a 30-minute decision-focused meeting; and clear steps after a missed commitment. Show how to run it manually first. Human review is required before any message is sent.

Do not invent policy, authority, commitments, owners, or dates. Mark missing facts [CLARIFICATION NEEDED].

I manage the same SUV launch with eight workstream leads across tooling, quality, manufacturing, logistics, purchasing, engineering, HR, and finance. None report to me. Functional directors own their priorities; the launch director and steering committee own escalation decisions.

Current rhythm: I send a status request Monday morning and ask for replies by Wednesday. Three leads reply on time, two reply Thursday or Friday, two respond after individual follow-up, and purchasing rarely replies without a call. Our weekly launch meeting lasts 60 minutes. About 30 minutes is spent going around the table collecting status that could have been submitted earlier. The rest is reactive problem-solving.

What is failing: routine actions and items that could delay other work receive the same reminder. People do not see which late item will affect several other tasks. When I copy directors, response improves for one week and then returns to the old pattern. I do not want to burn political capital by escalating every missed update.

What must be protected this month: B-pillar die recovery by Wednesday noon, returnable container release by Friday, door hinge PPAP samples within 10 days, and rocker measurement alignment before the next trial in 12 days.

Approved tools: Microsoft 365 Copilot Chat, Outlook, Teams, Excel, and Planner. We do not have Copilot Cowork. Drafts must be reviewed before sending. Tone should be Routine for normal status, Important for work that could delay the project and needs action soon, and Sensitive for a customer commitment or formal escalation.

I need a simpler weekly update plan, rules for handling important changes, messages before deadlines, a 30-minute meeting agenda, and clear steps after a missed commitment.

ROLE
You are a senior project communication advisor for manufacturing and cross-functional programs. You turn one set of verified project facts into the right message for each audience.

CONTEXT
I need to communicate a project change, serious risk, or decision without burying the headline, overstating certainty, or blaming a person. I will provide the verified facts, the likely effect on other work, and the audiences.

REQUEST
Before you produce anything, please ask me the questions in the DISCOVERY section below. Ask them all at once, in a single numbered list. Wait for my response. Once I answer, accept whatever I write, even if it's a paragraph or covers multiple questions at once. Do not re-ask the full list. If one detail is missing and you genuinely need it, ask one short follow-up about only that gap. Otherwise, go ahead and produce the output and note any assumptions you made.

Using the information I provide, create:

1. LEADER DECISION BRIEF
   - Headline in 12 words or fewer
   - Current status and what changed
   - Business or launch impact
   - Decision needed, options, recommendation, and decision deadline
   - Under 200 words

2. MESSAGE TO THE PERSON DOING THE WORK
   - The specific commitment, dependency, or support needed
   - Why the timing matters
   - One clear response requested by a stated date
   - Under 150 words

3. TEAM UPDATE
   - What changed, what stays the same, the items that need attention first, and next actions with owners and dates
   - Under 250 words

4. ESCALATION EMAIL, ONLY IF WARRANTED
   - Facts, prior actions, current impact, decision or support requested, and deadline
   - Focus on the issue and recovery path, not the person

5. 60-SECOND MEETING OPENING
   - A 60-second spoken update that starts with the decision or critical-path threat

Use the requested tone selector:
- Routine: normal coordination, no immediate threat
- Important means action is needed soon to protect the plan
- Sensitive: relationships, customer commitments, cost, or leadership attention require extra care

Do not invent facts, commitments, costs, customer positions, authority, or dates. If something is unclear or missing, flag it inline as [CLARIFICATION NEEDED] instead of guessing. Keep dates, owners, numbers, and terminology consistent across every version. If escalation is not warranted, say so and provide the next proportionate step.

DISCOVERY
1. What changed, and what evidence confirms it?
2. What can this affect if no action is taken?
3. What decision, commitment, or support is needed, from whom, and by when?
4. What has already been tried?
5. Who are the executive, functional, and team audiences?
6. Which tone fits: Routine, Important, or Sensitive?

This is a new task. Please ignore any previous conversation context and treat this prompt fresh.

STEP 0 (do this before anything else)
Read the bracketed details below. If any are empty or vague, ask me about them in one numbered list and wait for my response. Don't search for context, don't draft anything, don't pull from prior conversations. Just ask the questions.

STEP 1 (only after I answer Step 0)
Produce the deliverable I'm asking for.

---

Verified change and evidence: [PASTE]
Impact if no action is taken: [DESCRIBE]
Decision or support needed, from whom, by when: [DESCRIBE]
What has already been tried: [LIST]
Audiences: [EXECUTIVE / FUNCTIONAL OWNER / TEAM]
Tone: [ROUTINE / IMPORTANT / SENSITIVE]

Create an executive decision brief, functional owner message, team update, escalation email only if warranted, and a 60-second meeting opening. Start each version with what the audience needs to know or do. Keep facts, dates, owners, and numbers consistent.

Do not invent commitments, costs, customer positions, authority, or dates. Mark missing facts [CLARIFICATION NEEDED]. If escalation is not warranted, give the next proportionate step.

Verified change: Delta Tooling confirmed at 9:15 AM that the B-pillar progressive die will miss its revised completion date by another five business days. Station 4 still shows cavitation after the second tryout. Delta has not requested a third tryout date from the press shop. Maria Chen confirmed the update in the supplier call notes.

Fixed outcome: Full Trial 1 is scheduled for Week 10 with only two days of float. It requires all 14 tools approved. Quality wall setup, final operator work instructions, and training for 45 operators depend on production-representative parts from the trial. SOP remains fixed for March 15, 2027.

What has been tried: the team rejected Delta's request to skip run-at-rate. Maria requested a written recovery plan twice. The launch director set Wednesday noon as the deadline. Delta sent a partial plan with weekend work but no confirmed press time or completion date.

Decision needed: by 3 PM today, the launch director must choose whether to reserve an alternate press slot at an estimated $18,000, split Full Trial 1 around the B-pillar parts, or keep the current plan and accept the schedule risk. Engineering must confirm whether a split trial will produce enough representative parts for quality wall setup.

Audiences:
- Executive: plant manager and VP of operations. They need launch risk, cost exposure, options, and a recommendation.
- Functional owner: engineering director. She needs a decision on the split-trial feasibility and an owner by noon.
- Team: eight workstream leads. They need to know what changed, what remains fixed, and which downstream dates are now conditional.

Tone: Sensitive. Keep the message factual and recovery-focused. Do not blame the supplier contact.