7 min reading · Practice at your pace
Review, Revise and Finish an AI Work Task
Review a Work result, ask for one useful change and check the complete revision. Learn how to catch an introduction or conclusion that no longer agrees with an edited table.
Use a short feedback loop with a clear check
Inspect the delivered file against the brief, name one useful correction and compare the whole revision. Keep earlier versions available. A smaller edit can still leave contradictions in content it preserves.
A real correction that finished a proposal brief
A change to one part of a document can affect another. This example narrows the budget comparison, then updates Purpose so the introduction agrees with the revised table.
This brief considers whether a small community group should run a Cedar workshop without optional printing. It sets out the proposed figures from the group's notes for that scenario. Nothing here has been approved, and the workshop is not a confirmed plan.What changed and stayed
| Item | Details |
|---|---|
| Corrected | Purpose now describes considering the workshop without optional printing. |
| Preserved | Every other paragraph and the native table stayed unchanged from the preceding revision. |
| Known figures | USD 370 cost, USD 480 proposed income, USD 110 remaining; tax/delivery unspecified. |
| Status | The brief still says this is a proposal, not an approved or confirmed workshop. |
1. Review against the brief and source
Check each supplied figure, required section, claim and unknown. Distinguish a requirement the result missed from a new requirement you are now adding. Inspect the actual artifact and relevant checks, not only the completion message.
2. Check preserved content for contradictions
Preservation is valuable, but the parts you keep must still make sense after the requested change. Read the earlier and final paragraph below alongside the narrowed comparison table.
This brief is a proposal to help a small community group decide whether to run a Cedar workshop. It sets out the proposed figures from the group's notes and compares two scenarios. Nothing here has been approved, and the workshop is not a confirmed plan.This brief considers whether a small community group should run a Cedar workshop without optional printing. It sets out the proposed figures from the group's notes for that scenario. Nothing here has been approved, and the workshop is not a confirmed plan.Read the corrective request
This follow-up was sent during the earlier real document task; it was not newly generated for this lesson.
Create a separate final Word file named cedar-workshop-brief-final.docx from cedar-workshop-brief-revised.docx. Change only the Purpose paragraph so it accurately says the brief considers the workshop without optional printing; remove its obsolete claim that the document compares two scenarios. Preserve the title, all Source facts, Cost comparison, its native one-row table, Decision to confirm and both separate tax/delivery questions exactly. Keep the unapproved-proposal and unspecified tax/delivery boundaries. Retain the original and prior revised files. Deliver the actual editable DOCX and inspect the resulting paragraphs and native table; no visual/design check is requested.3. Name the change, preservation and checks
Name the file or version, describe the change, say what must stay the same and explain how to check the result.
In [ARTIFACT/VERSION], change only [SPECIFIC TARGET] to [REQUESTED CHANGE].
Preserve [NAMED CORRECT FACTS/SECTIONS/FORMULAS/INTERFACES].
Check [KNOWN ANSWERS] and reread the complete result for contradictions.
Keep the original and return a separate revision if needed.
State which checks actually ran and what remains incomplete.4. Verify both changed and unchanged behavior
Review the result in the way that fits the task: read a document’s claims, recompute a budget’s totals or run relevant tests for code.
5. Recover from incomplete work without losing context
Reopen the same task and inspect its current status, messages and outputs. Supply missing information, answer a requested decision or name the failure and expected result. If the run was interrupted, distinguish resuming it from starting a duplicate. Stop only the intended run when needed; never assume a new chat knows an earlier file.
6. Check the version you will actually use
Open the final artifact, confirm the specific correction and review the surrounding output. For a direct edit, verify the saved change after reopening. If you need an in-app export or another client, inspect that result too. A successful generation does not prove every save or conversion path.
Check a revision across the whole document
Use the meeting brief below. After changing the introductions, confirm the agenda still totals 45 minutes and the facts table, introduction and conclusion remain consistent.
Continue the task you already started
Send the revision in the same Work conversation. Work requires Plus and uses applicable credits. Follow-ups do not count as new hourly task launches; resuming still needs an active-session slot.
Work review questions
Make the requested improvement and verify the complete result.
How do I tell Work what not to change in a file?
Name the exact facts, sections, formulas or interfaces to preserve, then compare them in the delivered revision. A preservation instruction is something to check, not a guarantee.
What if a correct revision makes another paragraph outdated?
Read the surrounding output and request a focused coherence correction. The real proposal kept an obsolete Purpose paragraph after its comparison changed, then corrected only that paragraph.
Should I start a new task after every failed attempt?
Inspect the existing task, its errors and delivered outputs first. A focused follow-up or supported resume can preserve relevant context; starting another task can duplicate work and usage.
Guides and resources
Find more detail and choose your next step.
Your turn
Revise a document and check its coherence.
Create the meeting brief, then change the introductions to 10 minutes. Check the revised agenda total and any surrounding explanation before using the file.
Write a draft and review the checklist.
Your draft saves in this browser. You can leave and come back.
Take the brief into Work
Copy the brief, open Gab AI and choose Work before pasting and sending it. Open the delivered file and check it against the brief.
These buttons open the product and copy your draft. You choose the mode and send the request yourself.
Open Gab AI for WorkMake one change and check the whole result
Review the first answer, then send this follow-up in the same conversation.
Revise the meeting brief so introductions take 10 minutes. Adjust the other suggested agenda durations to keep the total at 45 minutes. Preserve Saturday at 10:30, 12 adult volunteers, the garden entrance and all missing details. Update any surrounding explanation that no longer agrees with the table. Return the complete revised file.Check that the requested change happened and the correct facts, format and missing details survived. For a file, open the revised artifact and inspect nearby paragraphs or formulas too.