Reviews and evidence

A review decision names its parent opportunity, the reviewer and the source revision. The reviewer chooses Approve, Reject or Return, records a reason and dates the decision. That structure matters when a proposal changes: the practice can identify the version the reviewer considered. The decision is an internal practice record, separate from the client saying whether the firm won the commission.

Supporting files also belong to the opportunity. An attachment has a title, evidence type, upload date, uploader and a visibility setting of Internal or Shared. The proposal team can keep the relevant package, client instruction or internal evidence near the pursuit and make its intended audience clear. The file record supports a review, but the reviewer still needs to inspect the right version and record a reasoned decision.

• Independent decision. The reviewer is named separately from the pursuit owner and the person who uploaded a file.
• Version context. A source revision and operation key preserve the decision context on the parent pursuit.
• File audience. Visibility helps the team distinguish internal working material from evidence marked for sharing.

Decide who may review an opportunity and how to prevent a preparer from acting as the independent reviewer. Agree what evidence type labels mean in the practice. Define who may see Internal files and who may mark a file Shared. Decide how the team identifies the source revision when a design RFP and opportunity are both changing. Rehearse an approval, a return with a correction request and a Reject decision with an explicit reason.

The proposal coordinator uploads the draft package for a civic library pursuit and marks the file Internal. A reviewer examines the submitted design RFP and the attached evidence, then records Return against the reviewed source revision. The reason says the project budget needs reconciliation with the client request. After the coordinator corrects the proposal, the reviewer can make a new decision against the new revision. The earlier decision remains part of the pursuit history.

The principal reads the decision and the file metadata before discussing the bid. A Shared attachment is treated as a deliberate audience choice, so the team checks the title and contents before changing visibility. The review record tells the principal who decided and why; it does not stand in for the client outcome.

• Review decision history — Approvals, rejections and returns with reviewer, source revision and reason.
• Pursuit files — Files grouped with their parent opportunity and visibility.
• Design RFP decision queue — Proposal submissions and their decision status.

Proposal review and evidence gives the review sequence. Review access describes the handoff between preparer and reviewer.