When Customer Requirements Change, Keep the Handoff Clear with ZGI

Description and use

When customer requirements change, use ZGI to compare the baseline brief and update, classify changes, and produce a draft with unresolved decisions for human review.

Problem

Customer updates change scope, audience, and timing, risking loss of earlier requirements and misinterpretation of commitments.

Outcome

A clear, traceable change brief that maintains baseline requirements, flags new and deferred items, and keeps unresolved decisions visible for human approval.

Workflow

• 1. Identify and label baseline brief (B1) and customer update (U1).
• 2. Paste both texts into ZGI agent with instruction to compare and classify changes.
• 3. Request a comparison table first to catch misinterpretations.
• 4. Review table for correct classification and missing dates or scope.
• 5. Ask agent to produce a concise revised draft brief, keeping unresolved items and source labels.
• 6. Perform human review of the draft, confirm dates, audience, and open decisions.
• 7. Approve or reject the revised brief; if approved, replace baseline version.
• 8. Store both versions and record review notes for traceability.

Evidence

Use an agent in ZGI with a model available in your deployment and instructions focused on one task: prepare a reviewable account of what changed.

Source

Ask for the comparison table first. It is easier to catch a bad interpretation there than inside a smooth paragraph.

Source