Architect Partition Interface Assumption Swap Before Tender
Quick project answer
An architect partition interface assumption swap before tender is a deliberate drawing review in which the design team replaces inherited beliefs about a movable wall with confirmed, project-specific information. The goal is not to add paperwork. It is to stop tender documents from carrying assumptions that bidders cannot price, coordinate or build against.
Movable partitions touch many interfaces: the head condition, the parking zone, adjacent finishes, the opening width and the routes panels follow when moved. Each interface deserves a named assumption, an evidence status and an owner. This article sets out a practical swap process for design teams working with contractors, owners and suppliers.
Why Interface Assumptions Survive Until Tender
Assumptions persist because they are rarely written down as assumptions. A ceiling detail may imply support without stating it. A plan may show a stacking position without confirming that the route to it works. A specification may list a finish without checking whether the substrate and edge treatment are coordinated.
By tender stage, these gaps become bidder risk. Different contractors may interpret the same drawing differently, and comparisons become unreliable. The swap process makes each interpretation visible before pricing begins.
Separate product facts from project decisions
Confirmed product facts describe how the system works in general terms. Project decisions describe how it will work in this building. Keep the two in separate columns or notes so reviewers can see which statements still need evidence.
Build the Assumption Register First
Start with a simple register rather than a revised drawing set. List every statement about the partition that currently appears in drawings, schedules or specifications. Include statements that seem obvious, because obvious assumptions are the ones most often left unexamined.
- Head condition: what the drawings show above the opening and how support is described.
- Movement route: the straight, turning and stacking paths shown on plan.
- Parking position: where panels are expected to rest when the opening is clear.
- Floor line: whether any floor track or floor hardware is shown along the partition line.
- Finishes: which surfaces are named and which remain open.
- Pass doors: whether a pass-door requirement is stated or still undecided.
- Acoustic intent: what the design team expects and what evidence exists.
Give every line an evidence status
Mark each line as confirmed by maintained product information, confirmed by project drawings, or still open. Open items are the real output of the register. They become the agenda for the swap meeting rather than hidden risk in the tender pack.
Run the Swap as a Numbered Review
A structured sequence keeps the review focused and gives the project team a record of what changed and why.
- Collect current documents. Gather the latest plans, sections, ceiling details, finish schedules and any draft specification text.
- Read the movement story. Trace each panel from the closed position to the parking position. Confirm the route is continuous and connected overhead, and flag any gap or turn that the drawings do not resolve.
- Check the floor line. Confirm whether the design shows a clear floor along the partition line, consistent with a top-hung system, and remove any contradictory floor hardware notes.
- Review the parking zone. Confirm that the planned stacking position is drawn, dimensioned and coordinated with adjacent services and finishes.
- Test finish statements. Replace generic finish language with the confirmed options under consideration, such as laminate, melamine, fabric, leather, glass or other approved surfaces, and note where approval is still needed.
- Record acoustic intent carefully. State the design intent and the evidence required. Do not convert an expectation into a promised result.
- Assign actions and reissue. Give each open item an owner and a date, then update the drawings and specification before tender release.
Use a Compact Comparison Table
The table below helps reviewers distinguish a safe statement from an assumption that needs project confirmation. It is a review aid, not a performance schedule.
| Drawing statement | Status | Action before tender |
|---|---|---|
| Panels are top-hung and cross the opening without a floor track | Supported by maintained product facts | Keep, and remove conflicting floor hardware notes |
| Panels park at the position shown on plan | Project-specific | Confirm route, stacking space and coordination with the layout |
| Finish is shown as a generic note | Open | Name the finish option under consideration and confirm approval |
| Acoustic outcome is stated as a result | Unsupported | Restate as design intent and request project-specific evidence |
| Pass door is implied but not scheduled | Open | Discuss the pass-door requirement and document the decision |
Handle Acoustic Language Without Overclaiming
The suitability of each route and parking arrangement depends on the approved layout, circulation, ceiling interfaces and operating sequence. Seals, junctions and adjacent construction all influence the outcome, so generic explanations should stay conceptual.
Before tender, replace any promised acoustic result with a clear statement of intent and a request for project-specific evidence. Ask what documentation will be provided, how it relates to the proposed configuration, and which interfaces remain the responsibility of other trades.
Evidence note: a finish name, a photograph or a plan view does not by itself demonstrate acoustic performance, structural capacity or cleaning compatibility. Those questions require matching project evidence and drawing review.
Coordinate the People Around the Interface
Architects and interior designers can confirm design intent and finish direction. Contractors can flag buildability and sequencing questions. Owners can confirm how the space must operate. Suppliers can clarify which statements are maintained product facts and which need project-specific confirmation.
Keep the meeting short and evidence-led. Review open items first, then confirm what has moved from assumption to decision. Record the outcome in the drawing revision notes so the tender pack tells one consistent story.
Questions to ask before reissuing
- Does every movement route read as continuous and connected overhead?
- Is the parking position drawn and coordinated with the surrounding layout?
- Are finish statements specific enough to price without implying unverified performance?
- Is the acoustic intent separated from any promised result?
- Has the pass-door requirement been discussed and documented?
Close the Loop Before Tender Release
The final step is a consistency check across the whole pack. Plans, sections, schedules and specification text should use the same terms for the same interface. Any remaining open item should be listed explicitly rather than buried in a note.
This approach does not remove every uncertainty, and it should not pretend to. It does give bidders a clearer brief and gives the design team a defensible record of what was confirmed and what still requires project-specific support, acoustic and dimensional review. For product context, see the movable wall systems page and the project resources.
Frequently Asked Questions
What is an interface assumption swap before tender?
It is a structured review in which the design team identifies assumptions about partition interfaces, checks them against confirmed information and project drawings, and replaces unsupported statements before the tender pack is issued.
Which drawings should be included in the review?
Include plans, sections, ceiling and head details, finish schedules, the parking layout and any draft specification text. The aim is to review every document that could influence how a bidder interprets the partition.
Can the design team rely on a finish name as evidence of performance?
No. Those questions need matching project evidence and drawing review.
How should acoustic intent be written before tender?
State the design intent and the evidence required, and avoid promising a result.
What should happen if a movement route is unresolved?
Flag it as an open item and resolve it before tender. The exact route, junction arrangement, continuous overhead path and parking position must be confirmed from the coordinated project drawings.
Who should attend the swap review?
Include the design team, a contractor representative, the owner or operator where relevant, and the supplier. Each participant can confirm a different part of the interface story and identify remaining evidence gaps.
Conclusion and Next Step
A disciplined assumption swap gives architects a clearer tender pack and gives bidders a fairer basis for pricing. Keep every statement tied to maintained product facts, visible evidence limits and project-specific drawing review, and confirm support, acoustic and dimensional requirements for each project.
To discuss pass-door requirements, finish options or project documentation, contact the EBUNGE team with your layout and drawing set.


