How to use the Mutual Action Plan Generator.
A mutual action plan is useful only when both sides recognize the steps. Keep proposed dates distinct from milestones that have actually been agreed.
Make the workflow fit your task.
List the buyer and seller actions required for the agreed decision, including owners and dependencies. Mark proposed dates separately from confirmed milestones and give each step an observable completion condition.
- What you provide
- Agreed buying steps, owners and dates.
- What you get
- Shared close plan with dependencies and acceptance milestones.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Buyer Alex and seller Sam agreed: Sam sends an anonymized sample by 10 October 2026; Alex reviews by 13 October. A decision meeting has not been scheduled.
Completed example
Milestone 1: sample delivery — owner Sam — due 10 October 2026 — agreed. Milestone 2: buyer review — owner Alex — due 13 October 2026 — agreed; depends on sample delivery. Milestone 3: resolve review questions — owners to confirm — proposed. Milestone 4: decision meeting — date and attendees to confirm — proposed. Completion evidence: delivered sample, buyer review notes and an agreed decision record.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
When is an action plan genuinely mutual?
Both sides need to recognize the responsibilities and milestones. A seller's internal checklist becomes mutual only after the relevant agreement.
Why are milestones slipping despite clear dates?
Check whether prerequisites and owners were confirmed. A date alone cannot resolve missing source material or an unmade buyer decision.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑