Quick project answer
Review focus: track zone interface.
A track zone interface handover documentation record is the written bridge between the movable partition system and the building structure it depends on. For overseas contractors, architects, interior designers, owners and renovation teams, this record matters because the panels are top-hung, travel without a continuous floor track and park at a planned stacking position. The interface zone is where the overhead route, the supporting structure and the surrounding construction meet. If that zone is documented only in conversation, later coordination becomes guesswork. This article sets out what to record, what evidence to attach and where project-specific confirmation is required.
Why the Track Zone Interface Deserves Its Own Record
Project review term: track zone interface.
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 operating logic means the overhead route is continuous and supported along its full length, including straight runs, turning sections and parking areas.
The track zone interface is therefore not a single point. It is a corridor of coordination between the partition system and the building. Handover documentation should describe that corridor clearly enough for a future reader to understand what was reviewed, what was confirmed and what remains subject to project-specific verification.
What the Handover Documentation Record Should Contain
Coordination scope: track zone interface.
A useful record is structured, not narrative. It should allow a reviewer to trace each interface item back to a drawing, a coordination note or a confirmation request. The following checklist covers the core content categories.
- Drawing references: the layout drawings that show straight, turning and stacking routes, with revision numbers and dates.
- Route description: how the panels travel from the closed position to the parking position, including any turns.
- The suitability of each route and parking arrangement depends on the approved layout, circulation, ceiling interfaces and operating sequence.
- Parking zone record: where panels stack, how that position was coordinated and what clearance was reviewed.
- Finish schedule: the approved finish for each panel face, such as laminate, melamine, fabric, leather, glass or another approved surface.
- Pass-door requirements: whether a pass door is required and how that requirement was communicated.
- Open items: any interface question that still needs project-specific confirmation before handover.
Drawing and Route Evidence to Attach
Handover documentation should not rely on a single general arrangement drawing. The exact route, junction arrangement, continuous overhead path and parking position must be confirmed from the coordinated project drawings.
Straight, turning and stacking routes
Straight, turning and stacking routes are reviewed from the layout. The documentation should identify which drawing shows each route segment and note any point where the route changes direction. The exact overhead route and support arrangement must be confirmed by the responsible project team from coordinated drawings.
Continuous overhead route
Every proposed movement path requires a continuous connected overhead route and project-specific support review.
Support and Structural Coordination Notes
Support conditions are project-specific. A practical approach is to log each interface question, the party responsible for answering it and the current status.
Evidence note: this article describes documentation categories only. It does not confirm structural capacity, support spacing, fixing methods or engineering outcomes for any project. Those items require project-specific review and matching evidence.
Where a support question remains open at handover, the record should say so plainly.
Parking Zone and Clearance Records
Parking style is customized to the customer layout and project requirements and may support compact stacking when the coordinated design permits it. The handover record should describe the planned parking position, the route into it and any coordination notes about adjacent construction.
Clearance is a coordination topic, not a performance claim. The documentation should reference the drawings used to review the parking zone and identify any dimension that still requires project-specific confirmation.
Finish, Pass-Door and Acoustic Interface Notes
Confirmed finish options include laminate, melamine, fabric, leather, glass and other approved surfaces. The handover record should list the approved finish per panel or per elevation, linked to the finish schedule.
Pass-door requirements can be discussed as part of the project documentation. If a pass door is included, the record should note where the requirement appears in the layout and how it interacts with the track zone.
Evidence Boundaries and Open Items
A responsible handover record distinguishes between what has been confirmed and what has not. The following table suggests how to classify interface items.
| Item | Record as confirmed when | Record as open when |
|---|---|---|
| Route drawing | A revision is referenced and dated | Only a verbal description exists |
| Support coordination | A written response is attached | The question is still with the structural team |
| Parking position | The layout shows the stacking zone | The stacking zone is not yet dimensioned |
| Finish schedule | Approved surfaces are listed | Finishes are still under selection |
| Acoustic requirement | The project requirement is stated | No project-specific target has been set |
This classification prevents the documentation from drifting into unsupported conclusions. It also gives the project team a clear list of items to close before final handover.
How to Coordinate the Record Across Project Teams
Contractors can supply installation sequencing notes. Architects can confirm drawing revisions. Owners can confirm operational expectations. Distributors can confirm the product documentation available for the project.
- Agree the interface register format and the drawing revision convention.
- Collect route, support, parking and finish information against that format.
- Mark each item as confirmed, open or requiring project-specific confirmation.
- Attach the evidence referenced by each confirmed item.
- Review the register with the project team before handover.
For maintained product context, see the movable walls product page. Additional planning material is available in the resources section.
Frequently Asked Questions
What is a track zone interface in handover documentation?
It is the documented relationship between the movable partition’s overhead route and the building structure, including straight, turning and stacking sections. The record should reference the drawings and coordination notes that describe this zone.
Does the record need to confirm structural capacity?
No. The documentation should not imply a capacity that has not been verified.
How should parking positions be described?
Parking style is customized to the customer layout and project requirements. The record should reference the layout drawing that shows the planned stacking position and note any dimension still requiring confirmation.
Can the documentation state an acoustic rating?
Only where a project-specific acoustic requirement and matching evidence exist. This article does not state a rating for any configuration.
What finish information belongs in the record?
List the approved finish per panel or elevation, using confirmed options such as laminate, melamine, fabric, leather, glass or another approved surface, and link each entry to the finish schedule.
How are pass-door requirements recorded?
Pass-door requirements can be discussed as part of the project documentation. If included, the record should note where the requirement appears in the layout and how it relates to the track zone.
Conclusion and Next Steps
A track zone interface handover documentation record should be specific, evidence-linked and honest about open items.
Before final handover, confirm project-specific support, acoustic and dimensional requirements with the responsible parties. To discuss documentation expectations for your project, contact the EBUNGE team.