Mutual action plan for deal progression

Create a buyer-facing document called **Mutual Action Plan: [account name]** using the deal information below.

Source information:
[paste call notes, opportunity notes, agreed actions, stakeholder list and target dates]

Use these document fields:
- Deal outcome: the business result the customer expects
- Decision date: the date the customer expects to confirm a decision
- Milestone: a buyer-understandable stage required before the decision
- Target date: date in DD Month YYYY format
- Customer owner: named customer person and role, or `Customer owner to confirm`
- Supplier owner: named seller or supporting colleague and role, or `Supplier owner to confirm`
- Evidence needed: the document, meeting outcome, approval or demonstration that proves the milestone is complete
- Dependency or risk: anything that could prevent the target date
- Status: `Not started`, `In progress`, `At risk`, or `Complete`

Format the answer as:
1. A two-sentence purpose statement written for the customer.
2. One Markdown table with the fields above. Put milestones in date order.
3. A section titled `Open points to validate` with only unresolved owners, dates, dependencies and assumptions.
4. A final line: `Decision date to validate: [date or To confirm]`.

Include only actions that materially affect evaluation, commercial approval, procurement, security review, contracting, implementation readiness or the decision. Combine duplicates. Do not invent customer commitments, names, dates, approval steps or requirements. Where notes conflict, use the most recent dated source if one is available. Otherwise mark the item `To confirm` and explain the conflict in `Open points to validate`.

Review the document **Mutual Action Plan: [account name]** and produce a corrected buyer-facing version.

Current plan:
[paste the current mutual action plan]

Supporting evidence:
[paste dated call notes, email commitments, meeting notes and internal forecast notes]

For every milestone, check these fields:
- Milestone
- Target date
- Customer owner
- Supplier owner
- Evidence needed
- Dependency or risk
- Status
- Source confidence: `Confirmed with customer`, `Supported by notes`, or `Unconfirmed`

Return exactly three sections:
1. `Revised mutual action plan`, a Markdown table in milestone date order.
2. `Date and dependency issues`, a table with columns `Item`, `What conflicts or is missing`, `Question for customer`, and `Impact on decision date`.
3. `Customer validation questions`, a numbered list of no more than seven direct questions.

Keep customer language neutral. Treat an internal forecast date as unconfirmed unless the source says the customer agreed it. Do not move a date merely to make the plan look healthier. If a prerequisite has no owner, date or evidence, label the affected milestone `At risk`. If sources disagree and neither is clearly newer or more authoritative, retain both positions in the issues table and set the plan field to `To confirm`.

Strengthen the document **Mutual Action Plan: [account name]** by assigning clear owners and completion evidence to each milestone.

Current plan:
[paste the mutual action plan]

Account and buying-group information:
[paste stakeholder roles, names, meeting notes, approval process and account team details]

Create a buyer-facing Markdown table with these columns:
| Milestone | Customer owner | Supplier owner | Joint action | Evidence needed to complete | Target date | Dependency or risk | Status |

Apply these rules:
- Use a named person only when the source names that person and role.
- If responsibility belongs to a function rather than a known person, use the function, such as `Customer security team`, and add `Named owner to confirm` in the risk field.
- Write one observable proof point per milestone. Examples include `Security questionnaire accepted`, `Executive sponsor confirms business case`, or `Procurement confirms contracting route`.
- Separate customer actions from supplier actions. A joint action must state what each side contributes.
- Keep the plan focused on the path to a decision, not general relationship activity.

After the table, provide:
1. `Ownership gaps`, listing milestones without a confirmed customer owner.
2. `Evidence gaps`, listing milestones where completion cannot yet be verified.
3. `Questions to settle at the next customer meeting`, with the exact question for each gap.

Do not assign decision authority based on job title alone. Do not assume procurement, security, legal review or executive approval is required unless the source identifies it. Mark uncertain details as `To confirm`.

Turn the source material into a customer-shareable document called **Mutual Action Plan: [account name]**.

Source plan and notes:
[paste the current plan, relevant call notes and confirmed customer commitments]

The audience is [customer company] and the shared goal is [desired business outcome].

Write the document in this format:
- Title: `Mutual Action Plan: [account name]`
- A short opening paragraph stating the shared outcome and that dates and owners are proposed for joint validation.
- A Markdown table with columns `Stage`, `Milestone`, `Customer action and owner`, `Supplier action and owner`, `Evidence needed`, `Target date`, and `Status`.
- A section titled `Items to confirm together` containing unresolved dates, owners, dependencies and decision criteria.
- A final section titled `Decision checkpoint` with these fields: `Target decision date`, `Decision participants`, `Decision criteria`, and `Next review meeting`.

Use plain, collaborative language. Keep stages limited to the actual deal path, such as business validation, technical validation, commercial alignment and decision, only where supported by the source. Remove internal forecast labels, probability estimates, account strategy, deal risk scores and commentary about individual stakeholders. Do not claim an action is agreed unless the notes say it was agreed. Where a detail is missing, write `To confirm together` rather than guessing.

Before returning the document, check that every milestone has an owner, evidence, a target date or an explicit `To confirm together` label.

Review the document **Mutual Action Plan: [account name]** and create a decision-readiness update for the next customer meeting.

Current plan:
[paste the mutual action plan]

Latest customer interactions:
[paste recent call notes, emails and meeting outcomes]

Return these sections in order:
1. `Decision checkpoint summary`, with four fields: `Proposed decision date`, `Customer decision participants`, `Decision criteria`, and `Current confidence`. Set confidence to `Confirmed`, `Partially confirmed`, or `Unconfirmed`, based only on the source material.
2. `Remaining milestones`, a Markdown table with columns `Milestone`, `Owner`, `Evidence needed`, `Target date`, `Dependency`, and `Effect if late`.
3. `Customer meeting agenda`, a numbered list of up to six items, starting with the decisions or confirmations needed.
4. `Follow-up record`, a table with columns `Question or action`, `Owner`, `Due date`, and `How it will be confirmed`.

A decision date is valid only if the source identifies the customer decision process, the required participants or approving group, and the remaining proof points. If any of these are absent, write `Decision date to validate with customer` instead of presenting the date as committed. Do not infer that a successful demonstration, proposal submission or verbal interest equals a decision.