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 project answer
Review focus: partition coordination assumptions.
Before a design freeze, the partition coordination assumptions log architects maintain becomes the shared record of what is known, what is assumed and what still needs project-specific confirmation. For movable partitions, that log should capture the overhead route, parking strategy, finish direction and any acoustic or pass-door questions without turning early assumptions into final performance claims. The goal is not to close every item early; it is to make open items visible so the design team, contractor and supplier can review them against the same drawings.
Why a Coordination Assumptions Log Matters Before Freeze
Project review term: partition coordination assumptions.
A movable partition is not a single product choice. It is a spatial system that depends on the opening, the surrounding construction and the way panels are expected to move and park. If those dependencies stay in separate emails or sketch notes, they can be lost when the design is frozen.
A structured log gives every discipline a place to record assumptions. It also separates confirmed product facts from project-specific requirements that still need review. The suitability of each route and parking arrangement depends on the approved layout, circulation, ceiling interfaces and operating sequence.
What the Log Should Capture About the Overhead Route
Coordination scope: partition coordination assumptions.
EBUNGE 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. The log should therefore record the intended straight, turning and stacking routes as reviewed from the layout.
Route questions to record
- Where does the opening begin and end, and how does the partition line relate to adjacent walls or columns?
- Does the proposed route remain continuously connected overhead, including any turn or transition?
- Where is the planned parking position, and does the layout show enough coordinated space for it?
- Are there conflicts with ceiling features, structural elements or other services that need review?
These are coordination questions, not engineering conclusions. The project team should confirm support, acoustic and dimensional requirements against the actual drawings before relying on any assumption.
Parking, Stacking and Clear Floor Strategy
Checklist focus: partition coordination assumptions.
Because panels are top-hung and do not require a continuous floor running track along the partition line, the floor can remain clear in the open position. That does not mean every parking arrangement is automatically suitable. Parking style is customized to the customer layout and project requirements and may support compact stacking when the coordinated design permits it.
The log should state where panels are expected to park, whether that position is inside or outside the room, and what adjacent activities or circulation routes might be affected. If the design team assumes a compact stack, that assumption should be marked for review rather than treated as a fixed outcome.
Finish and Surface Assumptions to Record
Review focus: partition coordination assumptions.
Confirmed finish options include laminate, melamine, fabric, leather, glass and other approved surfaces. A finish direction can be logged early, but the log should distinguish between a visual preference and a confirmed specification.
Finish coordination notes
- Record the intended finish family and where it appears in the room.
- Note any edge, frame or junction conditions that need design review.
- Flag whether the finish is being selected for appearance, durability expectations or another reason.
- Do not treat a finish choice as evidence of acoustic, fire or maintenance performance.
If the project requires a specific surface approval, that should be confirmed through the proper project documentation rather than assumed from a generic finish name.
Acoustic and Seal Concepts Without Overclaiming
The log should record the acoustic intent and the need for project-specific confirmation, not a promised result.
However, the actual performance depends on the complete assembly, the surrounding construction and the installation conditions. The log should mark acoustic requirements as items to be confirmed with the supplier and the project team.
Pass Doors, Documentation and Review Status
Pass-door requirements and project documentation can be discussed with the supplier. The log should record whether a pass door is anticipated, where it might be located and what documentation the project team expects to review.
Evidence note
This article uses maintained EBUNGE product facts and generic coordination concepts. It does not provide project-specific engineering, acoustic or commercial conclusions. Confirm support, acoustic and dimensional requirements for each project.
A simple status column can help: open, under review, confirmed by project team or not applicable. That prevents an early assumption from being read as a final decision.
A Practical Log Template for Project Teams
The following checklist is a starting point. Adapt it to the project’s drawing set and review process.
| Log item | What to record | Status |
|---|---|---|
| Opening and route | Straight, turning and stacking routes reviewed from layout | Open / Review |
| Parking position | Planned stacking location and adjacent impacts | Open / Review |
| Finish direction | Laminate, melamine, fabric, leather, glass or other approved surface | Open / Review |
| Pass door | Anticipated need and documentation expectations | Open / Review |
| Acoustic intent | Requirement to confirm with project-specific evidence | Open / Review |
Use the log during coordination meetings and update it as drawings develop. The aim is to keep assumptions visible, not to replace formal submittals or engineering review.
How to Keep the Log Useful Through Design Freeze
A log becomes less useful if it mixes confirmed facts with wishful thinking. Keep a clear distinction between product facts, project assumptions and items requiring evidence.
Review habits that help
- Assign an owner for each open item.
- Review the log at each coordination milestone.
- Mark items as confirmed only when the project team has the supporting information.
- Carry unresolved items into the design freeze notes rather than closing them silently.
For product context, refer to the movable partition wall page. For project examples and documentation discussions, see projects. If the team needs to discuss pass-door requirements or project documentation, contact the supplier directly.
FAQ: Partition Coordination Assumptions
What is a partition coordination assumptions log?
It is a working record of the assumptions, open questions and confirmed items that affect a movable partition design before the design is frozen. It helps architects, contractors and suppliers review the same information.
Does a top-hung partition need a floor track?
EBUNGE movable wall panels are suspended from a top track and cross the opening without a floor track. The overhead route still needs to be continuously connected and reviewed for the project.
Can the log record acoustic requirements?
Yes, but it should record them as project-specific requirements to be confirmed.
How should finish options be logged?
Record the intended finish family, such as laminate, melamine, fabric, leather, glass or another approved surface, and note that final selection and performance require project confirmation.
When should the log be updated?
Update it at each coordination milestone and before design freeze. Unresolved items should be carried forward rather than closed without supporting information.
Can pass doors be included?
Pass-door requirements and project documentation can be discussed with the supplier. The log should note the anticipated need and the documentation the project team expects to review.
Conclusion: Keep Assumptions Visible Before Freeze
A partition coordination assumptions log architects can rely on is not a promise of performance. It is a disciplined way to record routes, parking, finishes, pass doors and acoustic questions before the design is frozen. By separating maintained product facts from project-specific requirements, the team can reduce confusion and keep the right items open for review.
Confirm support, acoustic and dimensional requirements for each project. To discuss movable partition coordination, pass-door requirements or project documentation, contact EBUNGE.
Continue Exploring
More Movable Partition Guide Guides
- Earlier guidePhasing Movable Partition Work When Renovation Zones Flip Mid-Project
- Related guideHow Architects Keep Partition Interface Decisions Visible Between
- Related guidePhasing Movable Partition Work Around a Building’s Seasonal Shutdowns
- Related guideHow Architects Run a Partition Coordination Workflow When the Design