A museum exhibit RFP should give every bidder the same project brief, scope boundaries, numbered exhibit schedule, technical response format and acceptance evidence. Separate mandatory requirements from options and unresolved decisions. Ask bidders to declare exclusions and building interfaces against the same item IDs. The three copyable records below help an owner compare a whole-gallery or whole-museum package before selecting a delivery team.
Build one controlled RFP package before requesting proposals
Start with a short owner brief: venue purpose, priority audiences, educational themes, available plans, known building conditions and the decision the procurement is intended to make. Identify whether you are appointing a designer, a fabricator working to a developed design, or an integrated delivery team. These are different assignments. A concept illustration and an equipment count do not establish a common technical baseline. If the design is incomplete, ask bidders to identify development assumptions rather than hiding that uncertainty inside a fixed-looking offer.
Give every document an identifier and revision, name the controlling exhibit list and define how questions and addenda will be circulated. Separate mandatory requirements, preferred solutions, priced options and information still to be confirmed. Ask for a technical response, a scope-linked commercial response and a deviations list in a consistent order. The templates here are working procurement aids, not universal tender conditions or legal advice. The owner and appointed local advisers should establish the applicable procurement procedure, contract documents and destination requirements before issue.
- Package index: owner brief [ ]; drawings and revisions [ ]; scope record [ ]; exhibit schedule [ ]; technical response [ ]; comparison record [ ]; clarification log [ ].
- Issue control: baseline revision [ ]; response deadline [ ]; question route [ ]; addenda recipients [ ]; owner decision authority [ ].
Template 1 assign technical scope and responsibility by work package
Copy the following record once for each work package, not once for the whole contract. A label such as turnkey or design and build does not explain who checks the existing building, provides utility connections, approves graphics or arranges local inspections. Write the deliverable and its boundary in practical terms. For example, distinguish a supplier connection point from the owner’s building-side distribution, and distinguish installation supervision from physical installation labor. A bidder should respond included, excluded, optional or clarification required against each line, with a named assumption where relevant.
Keep the four stages connected. Planning and design establishes the visitor experience and approved design information. R&D and manufacturing develops and produces the agreed exhibits. Engineering and construction coordinates transport, assembly and site interfaces. Sustainable operation covers the agreed training, maintenance information and renewal support. This is how DEEPBLUE frames its capabilities; it does not mean every service is automatically included in every contract. Assign an owner to each interface and define the evidence that closes it, so no obligation is silently left between packages.
- Copyable scope row: package ID [ ] | deliverable [ ] | supplier responsibility [ ] | owner input [ ] | local-party responsibility [ ] | inclusion/exclusion [ ] | approval evidence [ ].
- Design row: theme and visitor action [ ]; drawings and review stages [ ]; graphic/content languages [ ]; client approvals [ ].
- Manufacturing row: approved samples [ ]; prototype scope [ ]; inspection records [ ]; packing identification [ ]; agreed spare parts [ ].
- Site row: access and unloading [ ]; utility connection boundary [ ]; anchoring/design checks [ ]; installation labor [ ]; commissioning responsibilities [ ].
- Operation row: training audience [ ]; maintenance and reset instructions [ ]; documentation languages [ ]; support boundaries [ ]; unresolved decisions and owner [ ].
Template 2 turn the exhibit schedule into a technical response record
Use a stable exhibit ID to connect the plan, specification, supplier response, quotation and later acceptance record. Give each exhibit a visitor task and observable outcome. Then add the constraints needed to develop it: location, available envelope, intended users, capacity assumptions, utilities and interfaces. Avoid treating an attractive image as a complete specification. If a requirement depends on a prototype, a site measurement or advice from a qualified local professional, say so and name the stage when the information must be resolved.
The example below is hypothetical and contains no project price, certified performance or ready-to-build dimensions. Its purpose is to show the difference between an exhibit name and an answerable technical brief. Ask the bidder to describe the proposed mechanism, materials, reset method, service access and evidence of meeting the stated requirement. Leave unknown values visibly open rather than inventing technical limits. The same record can then carry the approved solution forward without losing the original learning intention when fabrication and site teams take over.
- Copyable exhibit record: ID [ ] | gallery/location [ ] | learning intention [ ] | visitor action [ ] | observable result [ ] | intended users [ ] | quantity [ ].
- Technical fields: dimensional envelope [ ]; interfaces/utilities [ ]; proposed construction [ ]; guarding/access approach [ ]; reset/cleaning [ ]; service clearance [ ]; content languages [ ]; confirmation needed [ ].
- Bidder response: proposed solution [ ]; assumptions [ ]; compliance/deviation [ ]; supporting drawing/sample [ ]; inspection or demonstration method [ ]; included documents [ ].
- Hypothetical EX-01: visitors turn a handle and compare the motion of visible gears. Require an understandable motion relationship, a protected moving mechanism and an accessible staff reset method; confirm detailed dimensions and applicable safety criteria during design development.
- Traceability: EX-01 on the layout = EX-01 in the technical response = EX-01 in the commercial response = EX-01 in the acceptance checklist.
Template 3 compare bids against scope evidence and declared deviations
A lower headline price is not directly comparable when one offer excludes installation, another assumes owner-supplied controls and a third includes a different number of exhibits. First normalize the scope: compare the same revision, item quantities, deliverables and owner inputs. Keep options separate from the baseline. Record the currency, tax treatment, delivery basis and commercial assumptions as stated by each bidder, and refer unresolved terms to the owner’s commercial advisers. Do not silently insert estimated missing costs into a supplier’s offer and present the result as a confirmed quotation.
Use the response record below for each material difference. The aim is a documented decision, not a scoring formula that claims to select the best supplier automatically. A technical reviewer should explain whether a deviation changes the visitor experience, durability, maintainability or site responsibility. An optional alternative may be valuable, but it should not replace the requested baseline without an explicit decision. Issue material clarifications through the procurement process consistently, and retain the response and decision alongside the comparison so the eventual contract can identify the agreed solution.
- Copyable comparison row: requirement/item ID [ ] | baseline revision [ ] | bidder A response [ ] | bidder B response [ ] | inclusion difference [ ] | evidence reference [ ] | clarification needed [ ].
- Deviation record: proposed alternative [ ]; reason [ ]; effect on visitor outcome [ ]; interface/maintenance effect [ ]; commercial effect as quoted [ ]; owner decision [ ]; approved revision [ ].
- Whole-package checks: design development; prototype allowance; graphics; fabrication; inspections; packing; freight basis; site work; commissioning; training; manuals; spares; support terms. Mark each included, excluded, optional or unresolved.
- Decision record: accepted baseline [ ]; separately approved options [ ]; remaining risk and owner [ ]; clarification reference [ ]; contract document to update [ ].
Specify acceptance evidence before manufacturing begins
Acceptance is easier to discuss when the RFP explains what must be demonstrated and who decides. Link the intended visitor action to an agreed inspection, sample review or functional demonstration. Distinguish design approval, factory checks, readiness for shipment, site commissioning and final handover. They answer different questions; approving a finish sample does not approve the complete installed exhibit, and a factory demonstration does not establish that the building interface has been completed correctly. Define documentation and defect-closeout responsibilities at the appropriate stage.
Ask for evidence proportionate to the exhibit and the delivery scope, not generic promises that everything meets every standard everywhere. Local building, fire, electrical, accessibility and public-use requirements must be identified for the destination by the responsible qualified parties. Record which requirements apply, who provides the assessment and which documents are expected. Any test procedure, performance limit or cycle requirement should be agreed for the actual project rather than borrowed from an unrelated tender. Training, maintenance access and reset instructions also need demonstrable handover evidence, because opening a venue requires more than receiving equipment.
- Acceptance row: requirement ID [ ]; evidence/demonstration [ ]; stage [ ]; witness/decision party [ ]; agreed criteria [ ]; record format [ ]; defect owner [ ]; recheck and closure [ ].
- Handover set: approved drawings as agreed, component information, operating/reset instructions, maintenance schedule, packing/location records, training record and outstanding-items log.
Prepare the next enquiry as a project package not a shopping list
Before issuing the package, run a short consistency check with the owner, designer, prospective operator and relevant site team. Can the same exhibit be traced through the drawings, schedule, scope and response forms? Are exclusions and owner inputs visible? Does each unresolved interface have an owner and a decision point? Can bidders answer the same questions without assuming different projects? This review can reveal missing coordination early, but it does not replace the owner’s procurement controls or the professional appointments required for the destination.
To discuss a whole-museum or gallery package with DEEPBLUE, share the project country and city, venue purpose, available plans, intended audience, current design stage and the scope records you can already complete. Include the target opening window and any known site or procurement constraints as planning inputs, not guaranteed delivery dates. DEEPBLUE can then discuss the connection between planning and design, R&D and manufacturing, engineering and construction, and sustainable operation within an agreed scope. If your brief is still developing, identify the missing decisions first; a controlled next-stage brief is more useful than comparing apparently precise offers built on different assumptions.
- Ready-to-issue check: stable IDs; shared revisions; assigned interfaces; declared options; answerable technical fields; acceptance evidence; consistent clarification process.
- For an initial discussion, send the brief and plans you have, and identify the information still open. Do not fill unknown project values with generic examples.
Frequently Asked Questions
What should a museum exhibit RFP include?
Include the owner brief, controlled drawings, scope responsibilities, numbered exhibit schedule, technical response fields, acceptance evidence and a deviations form. Add the commercial and contractual documents required by the owner’s procurement process.
Can I issue an RFP before detailed design is complete?
Yes, if the appointment is intended to include design development. State the design stage, required outputs, assumptions and approval points. Do not compare a developed-design fabrication offer with a design-development offer as if their scope were identical.
Is an exhibit schedule just an equipment list?
No. A useful schedule links each item ID to its location, learning intention, visitor action, technical interfaces, bidder response and acceptance evidence. A count of products alone leaves too many assumptions open.
How should I compare alternative technical proposals?
Keep the requested baseline visible and record each alternative separately, including its effect on the visitor experience, interfaces, maintenance and quoted scope. The owner should document the accepted deviation and update the contract information.
Can DEEPBLUE support a whole-museum package?
DEEPBLUE works across planning and design, R&D and manufacturing, engineering and construction, and sustainable operation. Share the venue brief, plans, location and design stage so responsibilities and the appropriate delivery scope can be discussed.
