Review meeting changes and request client confirmation
Compare a meeting excerpt with requirements v1, review the proposed change, then create v2 and request client confirmation.
By PLARO · Content date
Choose a baseline before comparing
Prepare the current requirements version and original meeting text. For a recording transcript, first check speakers and important wording.
Online store redesign example · From meeting to new version
An illustrative sample written by PLARO, not a customer case or a live AI result. Check AI suggestions against the source; results may vary between runs.
- Before
- REQ-02 · Admins can view orders.
- Meeting excerpt
- Client: Admins should be able to cancel orders too. PM: I will confirm the cancellation conditions and update the requirements. Client: I will check internally about courier integration.
- Manager review
- Review order cancellation as a proposed change. This sample assumes a later discussion agreed to cancel only orders not yet shipped. The manager adds this condition; it was not established by the excerpt above.
- After · v2
- REQ-02 · Admins can view orders and cancel orders not yet shipped. Customers also see the cancellation in their order history.
- Still open
- Courier integration is undecided. Keep it as a question to resolve instead of an agreed requirement.
- Client confirmation
- The manager sends v2 to the client, who can confirm it or request changes. Check the response and its content before deciding the next action.
Separate suggestions from agreements
Read supporting excerpts before deciding to apply, edit or ignore a finding. The sample below shows a manager refining a proposed change.
Record confirmation of the new version
After creating a version with the reviewed changes, the manager requests client confirmation. Review revision requests and never treat silence as confirmation. A confirmation record differs from an electronic signature.
Guides to requirements and meeting changes
PLARO compares client project requirements with meeting content, helps managers keep reviewed changes in new document versions, and records client confirmation.
Requirements document example and reusable template
Use an online store redesign sample to separate requirements, acceptance criteria and open questions, and keep document versions.
Review meeting changes and request client confirmation
Compare a meeting excerpt with requirements v1, review the proposed change, then create v2 and request client confirmation.