Before sending a revised quotation, read the sentence that caused the discussion. A resolved comment beside a delivery term does not tell the recipient whether the term was changed, deliberately retained or left as a proposed edit. The useful final check is the wording the buyer will receive, not the number of open comments remaining in the document.

This matters when an overseas salesperson and a supplier team in China review the same file at different times. One person may close a thread after answering a question. Another may read that action as confirmation that the requested edit has been made. Both can believe they have finished their part while the quotation still contains an unsettled condition.

Google's September 30 Docs API announcement makes comments and suggestions available for programmatic management. Its documentation treats resolving a discussion and accepting a suggested edit as separate operations. That distinction is useful beyond the interface: a discussion status describes the conversation, while the document text carries the commercial statement.

Read the decision, then locate its effect

A comment can request information without asking for a change. It can propose alternative wording. It can also record a decision to retain the original sentence. Closing each of these discussions may be appropriate, but the resulting document actions are different. An assistant that sees only the closing status cannot reliably reconstruct the intended outcome.

For material terms, a short decision should identify the outcome: retain the existing clause, accept a specified suggestion or replace the sentence with agreed wording. This need not become an elaborate approval process for punctuation. It is most valuable where a change affects the relationship between a price and its configuration, quantity, delivery basis or validity condition.

Compare the recorded decision with the final sentence. Unchanged text is correct when the team chose to retain the original, but a missed action when it approved a replacement. Check that distinction before asking a colleague to reopen a comment: an unchanged clause is not automatically an unfinished edit.

A buyer should not have to reconstruct the offer from internal abbreviations, deleted text and comments in the margin. Where the working document remains collaborative, produce a clearly identified sending version. That version should make the offered configuration and its conditions readable without access to the discussion that produced them.

A clean preview can still contain undecided content

Google Docs can return a preview that treats suggestions as accepted, or one that treats them as rejected. Those views are useful for examining the alternatives. Reading an accepted-suggestions preview does not itself accept the edits in the underlying document.

This creates a particular risk for AI summaries. An integration may generate a polished quotation summary from a preview containing every proposed change. The summary can look final even though the source still contains competing suggestions. A clean-looking extract is therefore not sufficient evidence that the terms have been settled.

The integration should identify which view it reads and why. A reviewer examining a disagreement needs the alternatives and their context. A process preparing an outgoing offer needs the actual agreed content. Choosing a reading mode because it produces tidier text is not a sound way to decide which commercial terms survive.

There may also be several suggestions about the same condition. Automatically accepting all of them is not a substitute for resolving the choice. The person responsible for the quotation must still determine which wording represents the intended offer; the automation can help locate the affected passage and carry out the specified change.

Keep the final check small and substantive

For a routine revision, concentrate on the passages that changed the buyer's understanding. Compare the previous wording, the recorded decision and the outgoing sentence. Then inspect the exported or shared version, rather than assuming the working editor and the recipient's copy show the same state.

That check differs from deciding whether a correction should become a general processing rule. Our discussion of purchase-order correction scope addresses future documents. A quotation review must first settle the present document. A closed thread should not be promoted into approval of the entire file.

Small teams may do this manually with little overhead. Repeated document flows may justify separate handling for comments, suggestions and final text. In either case, the practical question remains simple: does the sentence being sent say what the team decided? Close the relevant discussion when that answer is clear, not merely when the conversation has gone quiet.

Sources