How Architects Can Run a Track Zone Interface Query Log Through Design
Quick project answer
Review focus: track zone.
A movable wall rarely fails at the drawing review because the panel is wrong. The suitability of each route and parking arrangement depends on the approved layout, circulation, ceiling interfaces and operating sequence. An architect track zone interface query log design stages workflow fixes that by turning open questions into dated, owned entries that travel with the project from concept to handover.
This guide sets out a stage-by-stage method for maintaining that log.
Why the Track Zone Deserves Its Own Query Log
EBUNGE movable wall panels are individually movable and suspended from a top track. They cross the opening without a floor track and park at a planned stacking position. That single sentence already touches several disciplines: structure above the ceiling, ceiling and soffit detailing, floor finish continuity, adjacent joinery, and the parking zone.
A general RFI register tends to bury these items. A dedicated log keeps the overhead route, the parking position and the opening geometry visible as one connected subject, so a change to the ceiling zone does not silently invalidate a movement route.
Set the Log Structure Before Concept Design
Agree the log format at project kickoff, not after the first clash. A simple spreadsheet or issue tracker is enough, provided each entry carries a unique reference, the drawing or room affected, the question, the decision owner, the date raised, the target response date and the evidence needed to close it.
Fields that earn their place
- Route type: straight, turning or stacking, because each is reviewed differently from the layout.
- Interface discipline: structure, ceiling, floor, facade, services or joinery.
- Evidence required: drawing, layout confirmation, finish approval or project-specific engineering review.
- Status: open, answered, superseded or closed with a reference to the revised drawing.
Keep the log in one controlled location. Duplicate copies in email threads are how decisions get lost between stages.
Stage One: Concept and Feasibility Queries
At concept stage the log should capture intent rather than detail. Record where flexible division is wanted, which rooms combine, and where panels are expected to park when the space is open. The exact route, junction arrangement, continuous overhead path and parking position must be confirmed from the coordinated project drawings.
Note the finish direction too. Confirmed options include laminate, melamine, fabric, leather, glass and other approved surfaces, but the log should record the question, not a premature answer. Finish choice interacts with adjacent materials and with how the client expects the wall to read in the room.
Stage Two: Design Development and Drawing Review
Design development is where the log does most of its work.
Drawing review checklist
- Mark the full overhead route on plan, including turns and the approach to the parking position.
- Overlay the route against ceiling and soffit drawings and record any conflict as a new log entry.
- Confirm the parking zone is shown at the planned stacking position and does not block circulation or escape routes.
- Check that the opening width and height shown on plan match the architectural setting-out drawings.
- Record whether a pass-door is required within the run, and raise it as a query if the requirement is unclear.
- The exact overhead route and support arrangement must be confirmed by the responsible project team from coordinated drawings.
Where acoustic separation matters, record the requirement and ask for project-specific confirmation.
Stage Three: Tender and Specification Queries
Before tender, convert open design questions into specification statements or explicit exclusions. The log should show which items are settled and which remain subject to project-specific review.
| Log entry type | Close when | Do not close on |
|---|---|---|
| Route geometry | Route is drawn and reviewed against the layout | Verbal assurance |
| Support and structure | Project-specific structural review is recorded | Assumption from a similar project |
| Finish selection | Approved surface is named and referenced | A photograph of a similar room |
| Acoustic objective | Requirement and evidence route are documented | Inferred performance from a drawing |
Project documentation and pass-door requirements can be discussed with the supplier, so route those queries through the contact channel and log the response reference.
Stage Four: Construction and Handover Closure
During construction the log becomes a change tracker. Close an entry only when the revised drawing is issued and referenced.
At handover, retain the closed log with the as-built information. It gives the facilities team a clear record of what was confirmed, what was excluded and which items remain subject to future project review. The resources section is a sensible place to point owners who want background reading.
Evidence note: a visible finish, drawing or photograph does not demonstrate acoustic performance, structural capacity, cleaning compatibility or a application reference. Each of those requires matching project-specific evidence.
Keeping the Log Honest Across Stages
Review the log at every design gate and at each contractor coordination meeting. Assign one owner for the track zone interface so entries do not drift between disciplines. Where a question cannot be answered with available evidence, record the boundary explicitly rather than filling the gap with an assumption.
For product context on the movable wall range, see the movable walls product page, and confirm support, acoustic and dimensional requirements for your specific project before finalising drawings.
Frequently Asked Questions
Who should own the track zone interface query log?
One named owner prevents duplication.
When should the log be started?
At concept stage, before routes are fixed. Early entries are broad, but they establish the habit of recording evidence requirements.
Can a route include a turn or a gap?
Turns and stacking routes are reviewed from the layout.
How should acoustic questions be logged?
Record the design objective and the evidence needed to support it.
What closes a finish-related entry?
A named approved surface from the confirmed options, referenced to the relevant drawing or schedule, rather than a verbal preference.
Does the log replace project-specific engineering review?
No. It records and routes questions; it does not substitute for the review that answers them.
Conclusion
A disciplined query log keeps the overhead track zone visible from concept through handover, so route geometry, parking, finishes and acoustic objectives are confirmed rather than assumed. Start the log early, review it at every gate, and close entries only on documented evidence.
To discuss pass-door requirements, project documentation or a specific layout, contact the EBUNGE team and confirm your project-specific support, acoustic and dimensional requirements.


