Why the Brief Comes Before the Quotation
A factory can only respond to the project it has been asked to understand. If one buyer writes “six cabins for staff” and another supplier receives a room list, climate notes and a site sketch, the resulting quotations may describe different products even when both suppliers use the same headline label. The comparison problem begins before the quotation is issued: it begins in the request.
A useful brief is not a complete architectural specification. It is a controlled statement of what the buyer knows, what the buyer needs, and what remains open for technical review. Its purpose is to give every invited supplier the same starting information and to make missing information visible. A short, structured document is often more useful than a long email chain because it gives suppliers a common reference number, revision date and response format.
Keep the brief focused on the project definition. It should not become a second article about customs classification, Incoterms or landed-cost modelling. Those questions belong in the commercial and logistics review. Here, the task is to describe the cabin requirement so that suppliers are quoting the same scope rather than filling gaps with different assumptions.
Identify the Project and Its Decision Context
Start with a project name, destination country and locality, the buyer's organisation or project role, the person coordinating technical questions, and the date on which the brief was issued. Add a short description of the project purpose: workforce accommodation, a remote operations base, temporary classrooms, a hospitality cluster, site offices or another defined use. A location should be specific enough to identify the relevant climate and local project context, but sensitive personal details do not belong in a general supplier brief.
State the procurement stage. Is the buyer testing feasibility, collecting budgetary quotations, preparing a tender, or seeking a proposal against a developed design? Suppliers need to know whether they are being asked for an indicative configuration or a response against fixed requirements. Identify the intended decision date and the date by which questions should be submitted, while avoiding promises about production or site completion.
Define Quantity and Configuration Precisely
Quantity should be written as a count, not left inside a general description. State the total number of units and, where the project contains different types, give a separate count for each type. For example, list sleeping cabins, accessible cabins, ablution units, kitchens, laundry rooms and offices separately rather than asking for “a camp package.” If the exact mix is not decided, show a base quantity and clearly labelled options. Do not let an optional unit become part of the base scope in one supplier's response and disappear from another's.
Describe the configuration using room functions and relationships. Identify the expected number of bedrooms, bathrooms, shared rooms, storage areas and service spaces. Clarify whether each cabin is standalone, joined to another module, arranged in a row, or connected by a covered walkway. State whether the buyer expects one repeated model or several layouts. Where dimensions are known, identify whether they refer to the external module, internal usable area or a site planning envelope. Do not invent dimensions merely to make the form look complete.
Describe Use, Occupancy, and Operating Pattern
A room schedule is not a complete use description. Explain who will occupy the cabin, how many people are expected to use it at one time, whether occupancy is continuous or intermittent, and whether the building will be used during the day, overnight or around the clock. A staff rest cabin, a permanent residence, a seasonal guest cabin and a security post can have similar floor plans but different requirements for privacy, sanitation, ventilation, durability and maintenance access.
Describe the operating pattern in practical terms. Will shifts overlap? Will users cook inside? Is there a need for accessible circulation, a quiet room, secure storage, a reception point or a place for wet clothing and equipment? Will cleaning be performed by an on-site team, a contractor or the occupants? Are there peak periods when the cabin cluster must accommodate more people than usual? These details help suppliers understand the intended arrangement without asking them to make assumptions about the buyer's operations.
Translate Climate into Usable Project Inputs
Avoid describing a site only as “cold,” “hot” or “tropical.” Give the destination locality and provide the climate information available to the project team: seasonal temperature patterns, wind exposure, rainfall, humidity, snow or ice exposure, solar exposure, dust, coastal conditions and any known flood or wildfire context. If the buyer has not obtained reliable site data, label the information as preliminary and ask the supplier to identify which additional inputs are needed for a technical proposal.
Explain when the cabins will operate. A building used only in a mild season may need a different envelope and service strategy from one occupied through winter. Note whether heating, cooling, dehumidification, freeze protection or shading is expected. For cold locations, identify whether water services will remain active during periods when the cabins are unoccupied. For hot and humid locations, note whether doors may remain open, whether wet equipment will be stored inside, and how ventilation is expected to work.
Record Utility Conditions Without Guessing
Utility information should be recorded as a site condition, not as an assumed feature of the cabin. For electricity, state the known supply type, available capacity, phase and frequency only where confirmed by the utility provider or project engineer. Identify whether a generator, battery system or other independent source is being considered. If the electrical supply is unknown, write “to be confirmed by destination-side electrical professional” rather than inserting a convenient standard value.
For water, identify whether the site has a municipal connection, borehole, delivered water or another source. Record known pressure, quality or treatment information only when supported by current documentation. For wastewater, state whether the project expects a public sewer connection, septic system, treatment plant, holding tank or another arrangement, and mark the responsible local designer. Add information about stormwater disposal, fuel, data, communications and fire-service interfaces when relevant to the intended use.
Assign Destination-Side Responsibilities Explicitly
A brief should include a responsibility paragraph that is direct enough to prevent scope drift. State that foundations, site preparation, local installation, utility connections, permits, inspections and final approval are destination-side responsibilities of the buyer's project team and its appointed local professionals, unless a separate written agreement expressly allocates a defined task differently. The factory can provide product information and coordinate technical interfaces within its agreed supply scope; it does not determine local site suitability or replace the authorities and professionals who control the project.
Break the boundary into tasks rather than relying on a single sentence. The destination-side team arranges site surveys, geotechnical review, grading, drainage, foundations, access roads, lifting areas, local trades, utility applications, local code review, permits, inspection scheduling and occupancy or operational approvals where applicable. The buyer should also identify who will receive the modules, check transport condition, coordinate lifting, complete module connections and maintain records of local work.
Ask the supplier to list what it includes and excludes for factory design, production drawings, packing, export documentation, lifting points, connection details, installation guidance and after-sales technical support. The buyer should not infer that a drawing package includes local engineering or that factory assembly includes site completion. Local rules differ by jurisdiction and project type. A modular unit is not automatically approved, certified or compliant for a particular site or use because it has been manufactured elsewhere. Local professionals and authorities make those determinations.
Explain Site Access and Installation Interfaces
A supplier needs to understand how the units will reach their final position. Attach a site plan if available and describe the route from the public road to the proposed installation area. Note gate widths, overhead obstructions, turning constraints, gradients, soft ground, bridge or axle restrictions, seasonal closures and any known restrictions on vehicle movements. If these details have not been surveyed, label them as unknown and assign an owner to obtain them. A map screenshot can orient the supplier, but it is not a substitute for a measured access survey.
Describe the planned unloading and placement method only to the extent it has been assessed. The project may anticipate a crane, forklift, telehandler or another method, but equipment selection depends on module weight, lifting points, reach, ground bearing conditions and local safety review. Ask the supplier for shipping dimensions, gross weights, centre-of-gravity information where available, lifting-point details and any handling restrictions needed by the transport and lifting teams. Do not ask a supplier to confirm that an uninspected route or site can accept the load.
Ask for Evidence and Identify Its Status
A request for evidence should be specific. Ask for the proposed floor plan, elevations, material schedule, wall and roof build-up, door and window schedule, service-point diagram, module dimensions, shipping information and a description of the proposed structural system. The exact package will depend on the stage of procurement. At an early stage, a representative drawing may be sufficient to explain a concept; before design freeze, the project will need documents developed for the actual configuration and reviewed by the appropriate professionals.
Ask suppliers to label each document as a standard product document, project-specific proposal, preliminary drawing, controlled production drawing, third-party document or item still to be developed. Record the revision, date, author or issuing organisation where available. A brochure image is useful for orientation but does not establish hidden construction details. A material name without thickness, location or assembly context is not a complete envelope description.
Do not request or imply a certification claim that has not been established for the product and destination. Instead, ask what evidence exists, what product or configuration it covers, who issued it, what jurisdiction or standard it refers to, and whether it remains current. The buyer's local professionals and authorities decide which evidence is relevant and whether the proposed unit can be used at the site. Evidence requests should help those reviewers do their work; they should not pre-empt their conclusion.
Make Supplier Responses Comparable
Send the same brief and attachments to every invited supplier, and ask each to return its response against the same headings. A useful response schedule includes: offered model or configuration; quantity; room and component schedule; dimensions; stated climate assumptions; proposed envelope and services; drawings supplied; documents still required; factory scope; exclusions; destination interfaces; deviations; open questions; and validity or revision information. Keep commercial schedules separate where the buyer needs them, but ensure every supplier is responding to the same defined technical requirement.
Ask suppliers to mark each line as “complies with brief,” “alternative proposed,” “not included,” or “information required.” Require an explanation for every alternative. This makes it harder for a visually attractive proposal to conceal a missing bathroom, a different window arrangement or a reduced service scope. If a supplier cannot answer because a site input is missing, the response should say what information is needed and why it matters.
Control Unknowns, Questions, and Revisions
Unknown information is normal at the beginning of a project. The mistake is to let an unknown become an invisible assumption. Use a short register with four fields: the question, current status, person responsible for answering it, and date by which an answer is expected. For example, “available electrical capacity” may be marked pending with the local electrical consultant as owner. “Final room finish” may be marked buyer decision. A supplier should not silently decide either item.
Separate a supplier clarification from a buyer change. A clarification explains how the supplier has interpreted an existing requirement. A change alters the requirement itself, such as adding accessible accommodation, changing the number of units or moving the service entry. Changes should be issued to every supplier still in the comparison so that no bidder works from an obsolete version. Record the revision number, date, summary of change and attachments affected.
A One-Page Brief Template and Issue Process
The following structure can fit on one page if the buyer uses concise entries and attaches drawings separately. It is a starting form, not a substitute for design documents.
Project: name, destination locality, buyer contact and brief revision/date.
Purpose and users: intended use, occupancy pattern, operating season and any accessibility or security needs.
Quantity and types: total units, count by type, base scope and separately identified options.
Configuration: room schedule, layout relationship, known dimensions and required/optional components.
Climate: location, seasonal exposure, wind, rain, humidity, snow/ice, dust and operating conditions; identify data source or mark pending.
Utilities: electricity, water, wastewater, drainage, communications and other services; state confirmed facts, unknowns and local owners.
Site and access: site plan status, route constraints, proposed placement area, lifting assumptions and information still required.
Responsibility boundary: foundations, local installation, utilities, permits, inspections and final approval are destination-side responsibilities.
Supplier response: proposed model, drawings, scope, exclusions, deviations, evidence status, questions and document revision.
Issue the brief with a clear response deadline and one channel for questions. Attach only documents that are relevant, legible and labelled with their status. Ask suppliers to acknowledge the revision they used. When the buyer updates a requirement, circulate a numbered revision and withdraw obsolete copies. Before comparing responses, check that every supplier received the same package and answered the same base quantity.
The one-page format is valuable because it disciplines the request. It does not make the project simple, remove the need for engineering or decide local approval. It makes the first conversation more precise, gives the factory a fair basis for proposing a configuration, and gives the buyer a practical record of what has and has not been defined.
Sources
Sources reviewed on November 13, 2026.
- U.S. General Services Administration, Pre-engineered and Prefabricated Buildings Ordering Guide: https://www.gsa.gov/buy-through-us/purchasing-programs/multiple-award-schedule/preengineered-and-prefabricated-buildings-ordering-guide — procurement questions covering intended use, site preconditions, utilities, foundations and installation scope.
- U.S. Department of Housing and Urban Development, Factory-Built Home Checklist: https://www.huduser.gov/portal/publications/pdf/factbuilt_2.pdf — a lifecycle checklist covering manufacturer selection, site preparation, foundations, utilities, delivery, installation and closeout.
- MK Mobile House, The First-Time Importer's Checklist for a Modular Housing Order: https://mkmobilehouse.com/blog/first-time-importer-checklist-modular-housing-order/ — related buyer-side planning topics and project handover questions.
- MK Mobile House, Writing a Winning Modular Tender Response: Evidence, Scope and Review: https://mkmobilehouse.com/blog/writing-winning-modular-tender-response-evidence/ — related guidance on evidence and response structure.
- MK Mobile House, Technical Resources: https://mkmobilehouse.com/technical-resources/ — company resource index for planning and installation interfaces.
