Design RFPs

A design RFP belongs to an opportunity and a practice organization. The proposal coordinator can record the site address, submission due date, estimated area and project budget as the bid takes shape. These values help the team judge the commission in context without creating a separate pipeline record. The RFP’s revision and status show whether the submission is still in draft, has been submitted, or has reached a later decision state.

Submission is a controlled operation. It checks that the RFP is Draft and that its revision matches the version the coordinator inspected. On success, the submission freezes that revision and writes an operation receipt. If another person changed the proposal in the meantime, the coordinator must review the current record before trying again. This is useful when the proposal package and budget are changing near a deadline.

• Pursuit link. Every design RFP points back to the fee opportunity that prompted it.
• Submission version. Revision and status keep the submitted proposal distinct from the draft the team was editing.
• Review trail. A review decision captures the source revision, reviewer, decision date and reason.

Agree who prepares the proposal, who confirms the submission package and who records the independent review. Decide how the practice identifies a revised proposal after submission. Agree whether the site address and project budget come from the client request or the practice’s bid assumptions. Identify where the team keeps the actual delivered package and how it will link its file evidence to the opportunity. Practice one last-minute change while a coordinator has the prior revision open.

A library commission moves into proposal work. The coordinator creates a design RFP under the opportunity, records the site address and submission due date, and adds the project budget. An attachment holds the current proposal document on the parent pursuit. The coordinator reviews the RFP’s revision, submits it and checks the operation receipt. The practice reviewer then records a reasoned decision with the source revision identified on the parent pursuit.

If the reviewer returns the proposal, the reason points the coordinator to the work that needs attention. If a colleague had edited the draft just before submission, the revision check prevents the coordinator from treating the older version as the submitted one. The principal can read the RFP decision beside the customer pursuit, while keeping the internal review separate from a Won or Lost customer outcome.

• Draft design RF ps — Proposal submissions still being prepared and their due dates.
• Submitted design RF ps — Submissions ready for a reviewer to inspect.
• Design RFP decision queue — Submitted and decided proposal records with their parent pursuits.

Design RFP submission follows the draft through submission. Proposal review and evidence shows the review handoff.