How to Write a Museum RFP

A practical guide for museum staff: what goes in a request for proposals, how to order it, what to check before it goes out, and a template outline you can copy.

For
Museum staff who buy outside services
Last updated

This guide describes common practice. Your institution’s purchasing policy, your board, and any rules that apply to your funding come first. Nothing here is legal advice, and posting on Museum Vendors does not meet any public-bid or notice requirement.

What a museum RFP is

A request for proposals (RFP) is a written invitation for qualified vendors to propose how they would do a piece of work, and at what price. A museum uses one when the work is complex enough that the museum wants to compare approaches, not only prices: exhibit fabrication, exhibit and graphic design, audiovisual and media systems, conservation, or consulting.

A museum procurement RFP is the same document seen from the purchasing side. It tells vendors what you need, how you will choose, and how to respond, and it gives your institution a clear record of how the choice was made.

RFP or RFQ?

Use an RFP when you want vendors to propose a solution. Use a request for quotation (RFQ) when the scope is already fixed and you mainly want comparable prices, for example a set of cases built to your drawings. If you are unsure, an RFP that states the scope clearly and asks for a price breakdown covers both.

Before you write

Most weak RFPs are weak because a decision was left open. Settle these first, with the people who will sign off.

  • Read your own purchasing rules. Ask your finance or procurement office whether there is a dollar threshold for formal bids, a required template, a required number of quotes, or a list of terms that must appear.
  • Name the goal in one sentence. What should be true when the project is finished that is not true today?
  • Set a budget range, or decide to say it is not set. Vendors respond better to a range than to silence. If you cannot share it, say so and ask for a price breakdown they can scale.
  • Fix the dates that cannot move. An opening, a grant deadline, a season, a loan return. Work backwards from them.
  • Decide who evaluates. Name the roles on the review team, and agree on the criteria before any proposal arrives.
  • Choose one contact for questions. One person, one email address, one rule for how answers are shared.

Structure of a museum RFP

A museum RFP template works best in this order. Each part answers a question a vendor will otherwise have to guess at.

1. Summary

Two or three sentences: who you are, what you need, the response deadline. A vendor should know within ten seconds whether to keep reading.

2. About the museum and the project

Your mission in a sentence, the audience, the space or collection involved, and why the project is happening now. Keep it factual and short.

3. Goals and scope of work

List what the vendor will do, and say what is out of scope. Describe the outcome you want, and leave room for vendors to propose how. Name any fixed constraints: dimensions, load limits, accessibility requirements, security, climate, existing systems, install access and hours.

4. Deliverables

Each thing you expect to receive: drawings, prototypes, finished pieces, documentation, training, maintenance manuals. Say what format each takes.

5. Timeline

Dates for issuing the RFP, the deadline for questions, any site visit, the proposal due date, when you expect to decide, and the project start and finish. Give a time and a time zone for the due date.

6. Budget

The range or ceiling, what it includes, how and when payments are made, and any funding conditions the vendor needs to know about.

7. What to include in a proposal

List exactly what you want to receive and in what order, so proposals can be compared side by side: company background, relevant past projects, the team and who does what, approach, schedule, a priced breakdown, and references. Set a page limit.

8. How proposals will be evaluated

List the criteria, and if you can, the weight of each. Common ones are fit with the brief, relevant experience, approach, schedule, price, and references. Tell vendors whether you may hold interviews or ask for revisions.

9. How to submit

Where to send the proposal, the accepted file formats and size, and what happens to a late submission. Say how and when vendors will hear the result.

10. Terms and conditions

Insurance, contract terms, ownership of the work and of any drawings, confidentiality, and anything your institution requires in every contract. Have your own procurement or legal contact supply and review this part.

Checklist before you send it

  • The first paragraph says who you are, what you need, and the due date.
  • Your purchasing office has seen the draft and the terms section.
  • Scope says what is included and what is not.
  • Every deliverable has a format and a date.
  • A budget range or ceiling is stated, or the RFP says plainly that it is not set.
  • The due date has a time and a time zone, and the question deadline is earlier.
  • Evaluation criteria are listed, and match what you ask vendors to submit.
  • The proposal requirements are specific enough that two proposals can be compared line by line.
  • One named contact handles questions, and the answers will be shared with every vendor.
  • Site details are included: access, hours, load limits, security, and any visit date.
  • Nothing private is in the document: no personal phone numbers, no confidential donor or collection details.
  • Someone outside the project has read it start to finish and could explain the job back to you.

Common mistakes

  • Hiding the budget entirely. Vendors then guess, and proposals come back too far apart to compare. A range is enough.
  • Describing the solution instead of the problem. If you already know the exact answer, write an RFQ. Otherwise describe the outcome and let vendors show their thinking.
  • A short response window. Good proposals take time to prepare. Give vendors enough days to visit, ask questions, and price the work properly.
  • Criteria that appear only after proposals arrive. Decide how you will judge before you see anything, and tell vendors.
  • Vague scope. Phrases like “as needed” and “and related work” turn into disagreements later. Name the work.
  • Leaving out install and site conditions. Access, hours, elevators, floor loads, and security affect price. Say what they are.
  • Asking for too much in the proposal. A fifty-page response costs vendors a lot and costs your team more to read. Ask for what you will actually use.
  • Answering questions privately. Share each answer with every vendor, so no one has an advantage.
  • No named owner. If nobody is responsible for questions and for the decision date, both slip.
  • Treating terms as an afterthought. Check contract terms with your own procurement or legal contact before the RFP is released.

Copyable museum RFP outline

Use this as a museum RFP template. Replace the bracketed parts, delete what does not apply, and have your purchasing office add the terms your institution requires.

REQUEST FOR PROPOSALS: [PROJECT TITLE]
[Museum name] | Issued [date]

1. SUMMARY
[Museum name] is seeking proposals from qualified vendors to [what you need].
Proposals are due [time, time zone, date].

2. ABOUT THE MUSEUM AND THE PROJECT
- Museum: [one-sentence mission and audience]
- Project: [what is being made, changed or bought, and where]
- Why now: [opening, grant, season, or other driver]

3. GOALS AND SCOPE OF WORK
- Goal: [the outcome, in one or two sentences]
- Included: [list the work]
- Not included: [list what is out of scope]
- Constraints: [dimensions, loads, accessibility, security, climate, existing systems, install access and hours]

4. DELIVERABLES
- [Deliverable, format, date]
- [Deliverable, format, date]

5. TIMELINE
- RFP issued: [date]
- Questions due: [date]
- Site visit: [date, or none]
- Proposals due: [time, time zone, date]
- Decision expected: [date]
- Project start and finish: [dates]

6. BUDGET
- Range or ceiling: [amount, or "not set"]
- Includes: [what the budget covers]
- Payment terms: [schedule]
- Funding conditions: [if any]

7. WHAT TO INCLUDE IN YOUR PROPOSAL (in this order, [number] pages maximum)
- Company background
- Relevant past projects
- Team and roles
- Approach
- Schedule
- Priced breakdown
- References

8. HOW PROPOSALS WILL BE EVALUATED
- Fit with the brief: [weight]
- Relevant experience: [weight]
- Approach: [weight]
- Schedule: [weight]
- Price: [weight]
- References: [weight]
- Interviews or revisions: [may / will not be requested]

9. HOW TO SUBMIT
- Send to: [name, email]
- Format and size: [for example PDF, maximum size]
- Questions: send to [name, email] by [date]. Answers are shared with all vendors.
- Late submissions: [how they are handled]
- Notice of result: [how and when vendors will hear]

10. TERMS AND CONDITIONS
[Supplied by your purchasing or legal contact: insurance, contract terms, ownership of work and drawings, confidentiality]

Sending it to vendors

Once your RFP is ready, you can post it on Museum Vendors. Posting asks for the same things this guide covers: a title, the type (RFP or RFQ), a category, your institution and location, a budget range, a description of the scope, a deadline, and how to respond. A person reviews every RFP within 2 business days before it is published. Vendors can then view it and register interest.