# Send a proposal for review

URL: https://engiprose.com/help/review-and-approval/send-for-review
Updated: 2026-09-02
Audience: member

Send your draft to reviewers, check the readiness heads-up first, and confirm who gets it.

This article applies only when your admin has turned on in-app review. Review
is off by default for every new organization; if you do not see a Send stage
in your proposal, ask your admin about [lifecycle
options](/help/set-up-your-firm/lifecycle-options).

:::checklist title="What you'll do"
- Read the readiness heads-up before you send
- See who your reviewers are and where to change them
- Add an optional review-by date and a note, then send
:::

## Before you send

The Send stage opens with a heads-up, not a blocker: nothing here stops you
from sending.

:::figure src="/help-figures/review-and-approval/send-for-review-1.png" srcDark="/help-figures/review-and-approval/send-for-review-1-dark.png" alt="The Send for review screen with a Worth a look before you send banner listing limited prior content in two sections, the Reviewers card showing one reviewer, and the review-by date and note fields" caption="The Send for review screen" route="/proposals/$proposalId/write/send"
:::

"These don't block sending. They're a heads-up so reviewers see your best
draft." Two kinds of items can show up here:

- **Unresolved comments** on the draft, with a link to resolve them before
  sending.
- **Limited prior content in some sections**, the marker described in [Novel
  RFP and thin prior content](/help/write-with-ai/novel-rfp-and-thin-prior-content).

When neither applies, the banner is replaced with "This proposal looks ready
to send. No open comments or thin sections."

## Reviewers

"Reviewers come from this proposal's Approvers. To change them, edit
Approvers in Step 2 (Details), not here." The Send screen only shows who is
already set: it is not where you add or remove a reviewer.

If no approver is set on the proposal, the card reads "No approvers
configured. Organization Admin(s) will review." instead of a name list.

## Review by and a note

"Please review by" is an optional target date you type in here. It is
informational for your reviewers and is not persisted anywhere they can see
later: nothing in the product tells a reviewer when you asked them to finish.
"Note for reviewers" is a free-text field for anything they should know
before they start.

## Confirm and send

::::steps
:::step
Add a review-by date or a note if you want to, then select **Send**.
:::
:::step figure="/help-figures/review-and-approval/send-for-review-2.png" figureDark="/help-figures/review-and-approval/send-for-review-2-dark.png" alt="The Submit for Review confirmation dialog listing the approver by name, with Cancel and Submit buttons" caption="The submit confirmation" route="/proposals/$proposalId/write/send"
A confirmation lists exactly who will review this proposal. Select **Submit**
to send it, or **Cancel** to go back and change your date or note first.
:::
:::step
Your proposal moves to **In Review**. You land on a quick, optional
confidence check ("How confident are you in this proposal?"), which you can
skip.
:::
::::

::::faq title="Common questions"
:::q question="Can I still edit the proposal after I send it for review?"
No. Once a proposal is in review, editing happens inside the reviewer's
tracked changes on [Review a proposal](/help/review-and-approval/review-a-proposal),
not back on the Edit stage.
:::
:::q question="What if my proposal has no approver set?"
Sending still works. Review falls back to your organization's admins, who
can act on it from their own Reviewer view.
:::
::::