Thank You for Submission and Request for Revision Template

In plain language: Names both parties — the recipient issuing the letter and the party that submitted the document — and identifies the specific submission being addressed, including its title, version number, and submission date.

Common mistake: Referencing only a general project name rather than the specific document version. If the submitting party has sent multiple drafts, the absence of a version number or submission date creates ambiguity about which document is under review.

In plain language: Formally confirms that the recipient has received and reviewed the submission, establishing a clear record of the date and method of receipt.

Common mistake: Omitting the non-acceptance qualifier. Without language expressly stating that receipt does not equal acceptance, the acknowledgement may be construed as partial agreement in some jurisdictions.

In plain language: Explicitly states that the Recipient is not accepting the submitted document in its current form, preserving the Recipient's legal position and preventing an inadvertent binding agreement.

Common mistake: Failing to include this clause at all and proceeding directly to the revision list. Courts in several jurisdictions have found that acknowledging receipt of a contractual proposal and requesting minor changes, without expressly withholding acceptance, can constitute a modified acceptance — creating an unintended binding contract.

In plain language: Lists each specific change required in numbered or lettered format, referencing the relevant section or clause of the submitted document and describing exactly what must be changed and why.

Common mistake: Writing revision requests as vague general commentary rather than numbered, section-specific instructions. Vague requests like 'the pricing section needs work' give the submitting party no clear direction and lead to a second round of non-compliant revisions.

In plain language: Explains the contractual, regulatory, or business justification for each requested revision — establishing a documented reason that protects the requesting party if the matter is later disputed.

Common mistake: Omitting the basis entirely and listing only the desired outcomes. Without documented grounds, the submitting party may dispute whether the revisions are legitimately required, especially in procurement or regulated contexts.

In plain language: States the specific date by which the submitting party must deliver a revised version, and describes the consequence of missing that deadline — typically the right to decline the submission or reopen the process to other parties.

Common mistake: Using relative time language like 'within a reasonable time' instead of a specific calendar date. 'Reasonable' is interpreted differently by each party and is frequently litigated. A fixed date eliminates the ambiguity.

In plain language: Confirms that issuing this letter does not waive any rights the Recipient holds — including the right to reject the revised submission, negotiate further, or terminate the process — and does not constitute a commitment to contract.

Common mistake: Positioning the reservation-of-rights clause at the end of the letter where it is less likely to be read carefully. Because this clause is legally the most protective, it should appear prominently — ideally both near the top and at the end of the letter.

In plain language: Establishes that the contents of this letter and any revision-related communications are confidential and, where applicable, made without prejudice to the parties' legal positions.

Common mistake: Skipping confidentiality language when the submission involves pricing, proprietary methodology, or sensitive commercial terms. Without it, the submitting party may share the revision requests — and the reasons behind them — with competitors or the press.

In plain language: Specifies how and to whom the revised document must be delivered — the named contact, accepted formats, and the submission portal or email address — to prevent the revised version being sent to the wrong recipient or in a non-reviewable format.

Common mistake: Accepting revisions in any format from any channel, then discovering the revised document was sent to a former employee's email or submitted without tracked changes, making it impossible to identify what was altered.

In plain language: Specifies which jurisdiction's law governs interpretation of the letter and provides signature lines for the authorized representative of the Recipient, making the letter an official record of formal communication.

Common mistake: Issuing the letter without a signature or on plain letterhead without any governance reference. An unsigned revision request carries no formal authority and may be treated by the submitting party as informal feedback rather than a binding procedural step.

A Thank You For Submission And Request For Revision letter is a formal written document that acknowledges receipt of a submitted proposal, contract draft, application, or report, and formally requests specific changes before the recipient will accept or execute the document. It creates a written record that receipt has occurred but acceptance has not, protecting the recipient's legal position while giving the submitting party clear, actionable revision instructions.

In contract law, acknowledging receipt of an offer or proposal without expressly declining or modifying it can, in certain circumstances, be interpreted as implicit acceptance — particularly when the requested changes are minor. Including explicit language withholding acceptance preserves your right to reject or renegotiate the submission entirely if the revised version is still unsatisfactory, without being bound by the original terms you acknowledged receiving.

It can, depending on the jurisdiction and the substance of the revisions. Under common-law contract principles, a response that changes the material terms of an original offer is treated as a counter-offer, which rejects the original and substitutes new terms. If your revision requests alter price, scope, duration, or other material terms, consider consulting a lawyer to ensure the letter is drafted in a way that preserves negotiating flexibility rather than inadvertently locking in a counter-offer position.

Yes. The template is most commonly used in procurement contexts where a vendor's proposal contains incorrect pricing, out-of-scope deliverables, non-compliant terms, or missing certifications. The letter acknowledges the submission — which is good practice for vendor relationship management — while formally requesting the corrections needed before a purchase order or contract can be issued.

Each item in the revision list should reference the specific section, clause, or exhibit of the submitted document that requires change, describe exactly what must be changed (not just that change is needed), and briefly state the reason — whether it conflicts with a regulatory requirement, a prior agreement, or your organization's standard terms. Numbered items with section references are far more actionable than narrative commentary and reduce the number of revision rounds needed.

For straightforward revisions to a short proposal, 5–10 business days is standard. For complex contract redlines or technical document revisions, 15–20 business days is more appropriate. The deadline should be realistic enough that the submitting party has a genuine opportunity to comply — an unrealistically short deadline can give rise to a dispute about whether the process was conducted in good faith, particularly in regulated procurement environments.

Yes. The letter should be signed by an authorized representative of the recipient organization — typically the procurement officer, contracts manager, or department head responsible for the submission review. An unsigned letter lacks formal authority and is difficult to rely on as an official procedural record. For high-value submissions, the signatory should hold authority to bind the organization on the subject matter.

The letter itself is generally not a binding contract — it is a procedural communication that withholds acceptance and requests revision. However, it creates a documented record of the parties' pre-contractual communications, which courts and arbitrators rely on to interpret the intent of the parties if a dispute arises later. Its legal weight depends on the jurisdiction, the underlying transaction, and how it is drafted — which is why legal review is recommended for high-value or complex submissions.

The letter should specify the consequence clearly — typically the right to withdraw from the process, reopen bidding to other parties, or terminate discussions without liability. If no consequence is stated, your ability to act on the missed deadline may be limited, especially in jurisdictions or regulated procurement contexts where good-faith negotiation obligations apply. Always include an explicit deadline consequence clause rather than leaving it implied.