That distinction matters when colleagues are already reviewing one document. A polished new file does not correct the paragraph they are reading in the original.
Identify the source and the exact change
In this fictional example, an event brief has a section titled “Arrival.” It says volunteers should arrive at 8:00 a.m. The organizer has approved 8:30 a.m.; the event start and venue should remain unchanged.
Open the source in Google first and confirm the account can edit it. Then use a bounded request:
Use this existing Google Doc: [EXACT GOOGLE DOC URL].
First identify the document title and quote the current Arrival
sentence so I can confirm you have the right document.
The approved correction is volunteer arrival at 8:30 a.m.
Propose the replacement for that sentence only. Keep the event
start time, venue and other sections unchanged. Do not create a
new document, change sharing permissions, move or delete the file.
Wait for my confirmation before making the edit.
Compare the quoted sentence with the source. If the document has two “Arrival” sections, identify the intended one before approving any change. A title match does not resolve an ambiguous paragraph.
Enable editing and inspect the destination
From + > Connectors, enable Google Docs. A Team or Enterprise Owner may need to allow the connection first. Existing Google permissions still determine which files Claude can change.
The editing pane works on Claude's web app in Chrome and on Claude Desktop with its built-in browser enabled. When the pane is unavailable, use Open in Google on the file card. The pane also needs a Google session; inspect an account-mismatch prompt rather than assuming the connected account and displayed account match. Live-editing setup
After confirming the proposed sentence, authorize that specific edit. Open the file card's Google link and inspect the Arrival section in the original document. Check the event start and venue too: they are the facts you explicitly wanted preserved.
Separate a missing pane from a failed edit
A file card that opens in a regular browser may still lead to the correct maintained document. Conversely, a visible pane does not prove the intended sentence changed. Check the destination text itself.
If Claude supplies a downloaded file, stop and clarify: “Edit the existing Google Doc at this URL; do not make a local copy.” If you lack edit permission, ask the document owner for the appropriate access instead of changing who can read the file.
For a read-only lookup, checking a Drive source before summarizing it explains a related verification habit. This task goes further because the result must be an actual change to the maintained Google Doc.
Leave one clear working copy
In the example, the finished source says 8:30 a.m. for volunteer arrival while preserving the event start and venue. Tell the organizer which sentence changed and provide the existing document link. Keep the conversation's proposed replacement separate from the text you actually verified in Google.