Request for Proposal: [project / service]
RFP – scope, requirements, scoring, terms
Cómo usar: Procuring vendors. Precise requirements produce comparable proposals; vague ones produce sales decks.
Vista previa
Request for Proposal: [project / service]
What we need, how we will score you, and the rules. Precision here determines the quality of what comes back.
| Field | Value |
|---|---|
| RFP ID | RFP-YYYY-NNN |
| Issuer | [organization] |
| Contact | @name, [email] |
| Issued | YYYY-MM-DD |
| Proposals due | YYYY-MM-DD 17:00 [TZ] |
1. Background
[Who we are and the context vendors need to propose intelligently.]
2. Scope of work
- Required: [deliverables and acceptance criteria]
- Optional: [nice-to-haves priced separately]
- Out of scope: [explicit exclusions]
3. Requirements
| # | Requirement | Mandatory? |
|---|---|---|
| R-01 | [requirement] | Yes |
| R-02 | No |
4. Proposal contents
- Company profile and relevant experience (max N pages)
- Approach and methodology
- Team – named people, not "resources"
- Timeline and milestones
- Pricing – itemized; state assumptions
- References – N similar engagements
5. Evaluation
| Criterion | Weight |
|---|---|
| Technical approach | N% |
| Relevant experience | N% |
| Price | N% |
| Team | N% |
| References | N% |
Lowest price does not automatically win; scoring follows the weights.
6. Timeline
| Event | Date |
|---|---|
| Questions due | YYYY-MM-DD |
| Answers published | YYYY-MM-DD |
| Proposals due | YYYY-MM-DD |
| Shortlist interviews | YYYY-MM-DD |
| Award | YYYY-MM-DD |
7. Terms
- Proposals remain valid for N days
- Late proposals are not considered
- This RFP does not obligate award; costs of proposing are yours
- Confidentiality: [terms]