Quick answer: architect coordination partition interface query
Review focus: architect coordination partition interface query.
An architect coordination partition interface query close-out is not a single meeting. It is a documented sequence that turns open questions about routes, parking, finishes and pass-doors into confirmed scope items before tender. The goal is not to answer every technical question in-house, but to separate maintained product facts from project-specific requirements that still need drawing review and written confirmation.
Movable wall panels are individually movable, suspended from a top track, cross the opening without a floor track, and park at a planned stacking position. That maintained description is the starting point. Everything beyond it — support conditions, acoustic expectations, dimensional tolerances and interface details — belongs to the project record.
Why Interface Queries Stall Before Tender
Project review term: architect coordination partition interface query.
Most tender delays around movable partitions come from unresolved interfaces, not from the partition itself. The suitability of each route and parking arrangement depends on the approved layout, circulation, ceiling interfaces and operating sequence. Each junction can generate a query if the drawing set does not state who owns it.
A second cause is evidence drift. It is not. Those are separate confirmations. The architect’s role is to keep the query list tied to what can actually be evidenced.
Separate maintained facts from project assumptions
Maintained facts describe how the system works in principle. Project assumptions describe how it will work in this building. Mixing the two creates tender risk. A clear close-out log should label each line as either a maintained fact, a project-specific confirmation, or an open item requiring further information.
Map the Movement Route Before Anything Else
Coordination scope: architect coordination partition interface query.
Straight, turning and stacking routes are reviewed from the layout. A route that looks simple in plan may cross a beam, a light cove or a service riser.
The exact route, junction arrangement, continuous overhead path and parking position must be confirmed from the coordinated project drawings. Every proposed movement path requires a continuous connected overhead route and project-specific support review. If the layout shows a break in the route, the query is not closed.
Route review checklist
- Confirm the full travel path from open position to parking position.
- Identify every turning point and confirm it is part of a continuous connected overhead route.
- Check that adjacent services, lighting and finishes do not obstruct the route.
- Record the parking position and confirm it is coordinated with the layout.
Parking and Stacking: Coordinate the Layout Early
Checklist focus: architect coordination partition interface query.
Parking style is customized to the customer layout and project requirements and may support compact stacking when the coordinated design permits it. The word ‘may’ matters. Compact stacking is not a default outcome; it depends on the coordinated design.
Architects should show the parking zone on the layout and confirm that it does not conflict with egress, furniture layouts or adjacent room functions. If the parking zone is tight, the query should be raised before tender rather than resolved on site.
Questions to resolve in the parking zone
- Where is the planned stacking position shown on the layout?
- Does the parking zone overlap any door swing, egress path or fixed joinery?
- Is the ceiling in the parking zone coordinated with the route review?
- Has the project team confirmed the parking style against the layout?
Finishes, Pass-Doors and Documentation
Review focus: architect coordination partition interface query.
Confirmed finish options include laminate, melamine, fabric, leather, glass and other approved surfaces. These are finish categories, not performance claims. A finish selection does not by itself confirm acoustic, fire, durability or cleaning performance. Those require separate project-specific evidence.
Pass-door requirements and project documentation can be discussed. If a pass-door is required, it should be identified as an interface item early, because it affects panel layout, route planning and the door schedule. The tender package should state whether a pass-door is included, excluded or still under review.
Evidence note for tender documents
Use maintained product facts for system description. Use project-specific drawings, calculations and confirmations for support, acoustic and dimensional requirements. Do not use a finish sample or a generic application example as evidence of performance.
Acoustic Concepts Without Invented Numbers
Visible references can support layout discussion but do not verify hidden construction or performance.
Instead, state the acoustic requirement as a project-specific confirmation item. The close-out log should record who is responsible for confirming the acoustic design and what evidence will be provided.
Acoustic query close-out steps
- State the acoustic requirement in the project’s own terms.
- Identify the adjacent construction and interface conditions that affect the assembly.
- Record any open acoustic item as a tender clarification rather than an assumption.
Build a Query Close-Out Log
It should list each query, its status, the responsible party and the evidence required to close it. The log should be reviewed before tender issue and updated as confirmations arrive.
| Query type | Typical interface | Evidence needed to close |
|---|---|---|
| Route | Ceiling, structure, services | Layout review and project-specific support confirmation |
| Parking | Adjacent rooms, egress, furniture | Coordinated layout and parking position confirmation |
| Finish | Adjacent wall, floor, ceiling | Approved finish selection and interface detail |
| Pass-door | Panel layout, door schedule | Written inclusion or exclusion in tender documents |
| Acoustic | Adjacent construction, assembly | Project-specific acoustic confirmation |
For product context, refer to the movable walls page. For general planning material, use the resources section. When a query needs project-specific input, contact the team with the layout and drawing set.
Frequently Asked Questions
What is an architect coordination partition interface query close-out?
It is a documented process for resolving open questions about how a movable partition meets the building before tender. It covers routes, parking, finishes, pass-doors and acoustic interfaces, and it records what evidence is needed to close each item.
Do movable partitions need a floor track?
No. EBUNGE movable wall panels are top-hung and move without a continuous floor running track or floor hardware along the partition line. The movement path still requires a continuous connected overhead route and project-specific support review.
Can I specify a finish and treat it as acoustic evidence?
No. Acoustic requirements need project-specific confirmation.
How should parking and stacking be shown before tender?
Show the planned stacking position on the layout and confirm it against adjacent rooms, egress paths and fixed elements. Parking style is customized to the customer layout and project requirements and may support compact stacking when the coordinated design permits it.
What documentation should accompany the tender package?
Include the layout, route review notes, finish selections, pass-door requirements and a query close-out log. Pass-door requirements and project documentation can be discussed with the project team as part of the close-out process.
Can acoustic performance be promised at tender stage?
No.
Conclusion: Close Queries with Evidence, Not Assumptions
Closing partition interface queries before tender is a discipline of separating maintained facts from project-specific confirmations. Map the route, coordinate parking, record finish and pass-door decisions, and keep acoustic expectations tied to project-specific evidence. A clear close-out log gives contractors, owners and design teams a shared basis for pricing and coordination.
Confirm project-specific support, acoustic and dimensional requirements before finalizing the tender package. For layout review and documentation discussion, contact EBUNGE with your drawings and query list.