html body.single-post main#content.site-main{box-sizing:border-box!important;width:calc(100% – 32px)!important;max-width:900px!important;margin-left:auto!important;margin-right:auto!important;padding-left:0!important;padding-right:0!important}
Quick answer: movable partition
Review focus: movable partition.
A movable partition handover file index structure is the table of contents that tells every party where each interface record lives. On a project with top-hung panels, a parking zone and several adjoining trades, the index is not paperwork for its own sake. It is the map that lets a contractor, architect, owner or facility team find the right drawing, the right confirmation and the right open question without guessing.
This guide sets out a practical way to build that index. It stays within what can be confirmed about EBUNGE movable partitions: panels are individually movable, suspended from a top track, cross the opening without a floor track, and park at a planned stacking position. Straight, turning and stacking routes are reviewed from the layout. Finish options include laminate, melamine, fabric, leather, glass and other approved surfaces. Pass-door requirements and project documentation can be discussed. Everything else must come from your own project evidence.
Start With the Interface, Not the Folder Tree
Project review term: movable partition.
Most weak handover indexes are organised by file type: drawings here, certificates there, correspondence somewhere else. That structure hides the thing that actually matters at handover, which is the interface between the partition system and the building around it.
Begin by listing the interfaces the partition touches. The overhead route and its support arrangement are the first, because the panels hang from a top track and every movement path must be continuous and connected. The opening and adjacent wall returns are next. The parking position is a third, since panels must be able to stack where the layout intends. Finishes, pass doors and adjoining ceilings or services complete the list.
Once the interfaces are named, the index can be built around them. Each interface becomes a section, and each section holds the records that prove that interface was reviewed, coordinated and accepted.
A Register-Based Index That Reviewers Can Follow
Coordination scope: movable partition.
A useful index is more than headings. It should point to registers that carry status, revision and ownership, so a reader can see whether a record is current or superseded.
| Index section | What it holds | Status field |
|---|---|---|
| Layout and routes | Straight, turning and stacking route drawings | Revision and review date |
| Overhead interface | Top-track coordination and support review references | Confirmed or open |
| Parking position | Planned stacking location and clearance notes | Confirmed or open |
| Finishes | Approved surface selections and sample references | Approved or pending |
| Pass doors | Pass-door requirements discussed with the supplier | Discussed or outstanding |
| Open items | Questions awaiting project-specific confirmation | Owner and target date |
Keep the register short enough to be read in one sitting. A long index that nobody opens is worse than a lean one that is maintained.
Drawing Control for Straight, Turning and Stacking Routes
Checklist focus: movable partition.
Route drawings deserve their own control because they change as layouts evolve. A straight run, a turning arrangement and a stacking position each raise different coordination questions, and the index should make it obvious which drawing version was reviewed.
What each route drawing should identify
- The opening or openings the panels serve.
- The overhead route the panels follow, shown as continuous and connected.
- The planned parking or stacking position.
- The revision number, date and the party that reviewed it.
The exact route, junction arrangement, continuous overhead path and parking position must be confirmed from the coordinated project drawings. If a route is unresolved, record it as an open item rather than issuing a drawing that looks settled.
Evidence Notes: What the File Can and Cannot Prove
Evidence note. A handover file records what was specified, reviewed and confirmed for this project. It does not create performance. Visible shapes, finishes or drawings do not by themselves demonstrate acoustic, fire, durability, load or maintenance outcomes. Where a project needs those outcomes, the corresponding project-specific evidence must be obtained and indexed separately.
This boundary matters for acoustic language in particular. The suitability of each route and parking arrangement depends on the approved layout, circulation, ceiling interfaces and operating sequence. If acoustic requirements are part of your brief, confirm them for the specific project and record the basis of that confirmation in the index.
Finish and Pass-Door Records in the Same Index
Finishes are easy to lose at handover because they are chosen late and often change. Give each selected surface its own record: laminate, melamine, fabric, leather, glass or another approved surface, with the room or zone it applies to and the approval status.
Pass doors are similar. Where a pass-door requirement exists, record that it was discussed, which layout it affects and what was agreed. The index should make it clear that pass-door provisions are project-specific rather than assumed.
Review Gates Before Handover
Build two or three review gates into the index rather than leaving everything to the final week. A first gate can confirm that route drawings and the parking position are coordinated. A second can confirm finishes and pass-door records. A closing gate confirms that open items are either closed or explicitly carried forward with an owner.
- Confirm the interface list matches the current layout.
- Check that every route drawing is at its latest revision.
- Verify finish and pass-door records are approved or flagged.
- Review open items and assign owners.
- Issue the index with a clear date and version.
Coordinating the Index Across Project Teams
Contractors typically hold route and interface drawings, designers hold finish selections, and owners or facility teams hold acceptance records. Naming a single index owner prevents duplicated or conflicting versions.
For product context, refer readers to the movable partition wall page, and for examples of how documentation is handled across installations, see the projects section. Where your team needs to confirm pass-door requirements or discuss project documentation, contact the EBUNGE team directly.
Frequently Asked Questions
What should a movable partition handover file index contain first?
Start with the interface list: overhead route and support, opening and wall returns, parking position, finishes and pass doors. Then attach registers with revision and status fields.
Does the index need to include acoustic ratings?
Only if acoustic requirements form part of your project brief. Where they do, record the project-specific basis for confirmation. Do not treat a generic rating as evidence for your installation.
How should route drawings be controlled?
Give straight, turning and stacking routes their own register entries with revision numbers, review dates and the reviewing party, and flag unresolved routes as open items.
Can the index list finish options generically?
It can list the approved surface categories, such as laminate, melamine, fabric, leather, glass or other approved surfaces, but each entry should identify the zone and approval status.
Who should own the handover index?
One named party should own the index and its version control, with contractors, designers and owners contributing to defined sections. This avoids conflicting copies at handover.
What if a route or support detail is unresolved?
Record it as an open item with an owner and target date. Do not issue a drawing that implies a settled route when the overhead connection or support review is still pending.
Conclusion and Next Step
A well-structured index turns handover from a document dump into a readable record of interfaces, decisions and open questions. Build it around the partition interfaces, control route drawings by revision, keep finish and pass-door records visible, and state clearly what the file can and cannot prove. Confirm project-specific support, acoustic and dimensional requirements with your supplier and design team before relying on any record.
To discuss pass-door requirements, finish selections or project documentation for your layout, contact EBUNGE and share your drawings for review.
Continue Exploring
More Installation and Maintenance Guides
- Earlier guidePartition Track Datum Ceiling Grid Reconciliation
- Related guideHow to Hand Partition Coordination Notes to the Next Design Stage
- Related guideHow to Plan Movable Partition Lifting Routes Before Panels Arrive
- Related guideWhat Should a Handover File Index Prove About Partition Interfaces?