Quick answer: architect coordination partition interface query tracking design stages
Review focus: architect coordination partition interface query tracking design stages.
Architect coordination partition interface query tracking design stages is the discipline of logging every unresolved question about how a movable wall meets structure, ceiling, adjacent finishes and adjacent trades, then closing each item before the next design milestone. On top-hung systems, panels are individually movable, suspended from a top track, cross the opening without a floor track and park at a planned stacking position. Those four facts generate most interface queries, because each one touches another consultant’s scope.
This article offers a register structure, stage gates and evidence boundaries. It does not supply project performance figures. Confirm support, acoustic and dimensional requirements for each project with the responsible engineers and the partition supplier.
Why Interface Queries Drift Between Disciplines
Project review term: architect coordination partition interface query tracking design stages.
A movable partition sits at the seam between architecture, structure, MEP and interior fit-out. The suitability of each route and parking arrangement depends on the approved layout, circulation, ceiling interfaces and operating sequence. When a query is answered verbally, the answer rarely reaches the drawing set.
Query drift is not a documentation failure alone. It is a scope failure. If nobody owns the question, the default answer becomes an assumption, and assumptions about support or route geometry are the expensive kind.
Build a Single Query Register Before Concept Design
Coordination scope: architect coordination partition interface query tracking design stages.
Start the register at concept stage, even when the partition type is not yet fixed. One spreadsheet or issue-tracker board is enough, provided every row has an owner and a due milestone.
Minimum register fields
- Query ID and date raised
- Room or opening reference and drawing number
- Discipline raising the query and discipline answering it
- Interface category: support, route, parking, finish, adjacent trade, documentation
- Design stage gate by which the answer is required
- Status: open, answered, incorporated into drawings, closed
- Evidence reference for the answer
Keep the register visible in coordination meetings. A query that is answered but not incorporated into the drawings should stay open, because the drawing is the instruction the site team will follow.
Stage Gates for Partition Interface Query Tracking
Checklist focus: architect coordination partition interface query tracking design stages.
Different stages ask different questions. The register should be filtered by stage so the team is not trying to resolve construction detail during concept options.
Concept and schematic design
Confirm the operational intent: which rooms combine, how often, and where panels should park. Straight, turning and stacking routes should be reviewed from the layout at this stage, because route geometry affects adjacent room sizes and door positions.
Design development
Convert intent into coordinated geometry. The overhead route must be continuous and connected wherever panels are expected to travel. The exact route, junction arrangement, continuous overhead path and parking position must be confirmed from the coordinated project drawings.
Technical design and tender
Freeze the interface schedule: opening sizes, parking zone, finish direction, pass-door requirements and the documentation package expected from the supplier. Pass-door requirements and project documentation can be discussed with the supplier before tender so the specification reflects what will actually be issued.
Construction and handover
Track site queries against the same register. A site query that changes route geometry should trigger a drawing revision, not a verbal instruction.
Evidence Boundaries Architects Should State Explicitly
Review focus: architect coordination partition interface query tracking design stages.
Every register row should distinguish between confirmed product facts and project-specific requirements. Confirmed finish options include laminate, melamine, fabric, leather, glass and other approved surfaces. Visible references can support layout discussion but do not verify hidden construction or performance.
Actual performance depends on the complete assembly, the surrounding construction and the installation condition.
Evidence note: if a claim about support, acoustics, dimensions or finish behaviour is not in the maintained product documentation or the project’s own engineering information, record it as an open query rather than a specification statement.
Route and Parking Review Checklist
Project review term: architect coordination partition interface query tracking design stages.
Use this checklist at each stage gate. It is deliberately about geometry and coordination, not about performance.
| Check | Question to close | Typical owner |
|---|---|---|
| Overhead route | Is the route continuous and connected across every position the panels must reach? | Architect with structural engineer |
| Support condition | Has the supporting structure been reviewed for the proposed configuration? | Structural engineer |
| Parking zone | Does the planned stacking position fit the layout without blocking circulation or services? | Architect with interior designer |
| Adjacent trades | Do ceiling, lighting, sprinkler and containment layouts respect the route and parking zone? | MEP and ceiling contractors |
| Documentation | Is the required drawing and submittal package defined for tender? | Architect with supplier |
Running the Register Through Coordination Meetings
Give the register a fixed slot in the agenda. Review open items by stage gate, not by discipline, so cross-scope questions surface early. Close items only when the answer appears in an issued drawing or an approved submittal.
Where a query depends on supplier input, raise it through the project’s formal channel and reference the drawing it affects. The movable wall product page and the resources library provide maintained context for those discussions, but they do not replace project-specific review.
Frequently Asked Questions
When should the partition query register start?
At concept design. Even before the system is selected, operational intent and route geometry generate questions that affect room sizes and door positions.
Who owns interface queries between the architect and the partition supplier?
The architect typically owns the drawing coordination, while the supplier answers configuration questions. Each register row should name one owner and one required stage gate.
Can panels travel across a gap in the overhead route?
No.
Do finish selections prove acoustic performance?
No. Finish options such as laminate, melamine, fabric, leather and glass are surface choices. Acoustic behaviour depends on the complete assembly and must be confirmed for the project.
How should pass-door requirements be tracked?
As a distinct register category with its own drawing reference, because pass-door positions affect panel layout, route geometry and adjacent room planning.
What closes a query?
Incorporation into an issued drawing or approved submittal. A verbal answer alone should leave the item open.
Conclusion and Next Step
A query register turns scattered interface questions into a managed design record. Keep it stage-gated, evidence-referenced and visible in coordination meetings, and confirm support, acoustic and dimensional requirements for each project before specification.
To discuss pass-door requirements, documentation expectations or layout review for a specific project, contact the EBUNGE team.