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 decision.
A partition coordination decision log architects maintain is not a meeting minute. It is a controlled record of what was decided, what evidence supported it, and what remains unconfirmed. Panel handling and the operating sequence must be confirmed for the selected layout and project conditions. This guide offers an evidence-bounded framework for overseas project teams.
Why Partition Coordination Decisions Slip
Project review term: partition coordination decision.
Coordination rarely fails in one dramatic moment. It drifts. A finish is discussed in a design meeting, then referenced in a drawing note, then assumed in a contractor query. No single step is wrong, but the chain loses its evidence anchor.
Movable partition systems add a specific pressure: panels are individually movable, suspended from a top track, cross the opening without a floor track, and park at a planned stacking position. Each of those facts touches architecture, structure and operations. If any one is decided informally, later coordination becomes guesswork.
What Belongs in a Partition Coordination Decision Log
A useful log separates confirmed facts from open questions. The suitability of each route and parking arrangement depends on the approved layout, circulation, ceiling interfaces and operating sequence. The table below shows a compact structure that works for most project teams.
| Log field | What to record | Evidence boundary |
|---|---|---|
| Decision topic | Layout route, finish, pass-door, stacking position | Reference the drawing or query that triggered it |
| Status | Confirmed, pending, superseded | Do not mark confirmed without a named reviewer |
| Supporting note | Who raised it and what document was reviewed | No inferred performance or hidden engineering |
| Next action | Drawing update, sample review, structural check | Assign an owner and a review date |
This structure keeps the log honest. It also prevents a common failure: treating a finish selection as proof of acoustic, fire or durability performance. A finish is a finish. Performance requires separate project-specific evidence.
Logging the Movement Route and Stacking Position
Straight, turning and stacking routes are reviewed from the layout. That review is a coordination decision, not a default.
Record the proposed route as a line on the layout, not a verbal description. Note where panels are expected to park and whether that position remains clear of other building services. The exact route, junction arrangement, continuous overhead path and parking position must be confirmed from the coordinated project drawings. Every proposed movement path requires a continuous connected overhead route and project-specific support review.
Questions to log for every route
- Does the route remain within the reviewed layout boundary?
- Is the parking position coordinated with adjacent doors, glazing or fixed joinery?
- Has the structural support condition been confirmed by the responsible engineer?
- Has the finish or surface been checked against the intended application?
Finish and Surface Decisions Need Their Own Log Line
Confirmed finish options include laminate, melamine, fabric, leather, glass and other approved surfaces. Each option may raise different coordination questions about edges, reveals, cleaning assumptions or visual continuity. The log should record the selected finish and the reviewer who approved it.
Do not let a finish decision imply a performance outcome. A fabric surface does not confirm acoustic behavior. Those are separate questions that require matching evidence and project-specific confirmation.
Pass-Door and Documentation Coordination
Pass-door requirements and project documentation can be discussed with the supplier. In the log, treat pass-door decisions as coordination items: location, swing, hardware interface and review status. Avoid describing a pass-door as a standard inclusion unless the project documentation confirms it.
Documentation slips often happen when a drawing revision is issued without a corresponding log entry. The log should reference the drawing number, revision and date.
A Simple Process for Recovering Slipped Decisions
- List every partition-related decision that has changed since the last coordinated drawing issue.
- Mark each item as confirmed, pending or superseded, with a named reviewer.
- Attach the evidence that supports each confirmed item, or state the exact confirmation boundary.
- Identify which items affect route, stacking, finish or pass-door coordination.
- Issue a short decision note and update the drawing register.
- Schedule a review before the next coordination milestone.
This process is deliberately modest. It does not require new software. It requires discipline about what is known and what is not.
Evidence Notes for Acoustic and Dimensional Questions
Dimensional requirements follow the same rule. Panel height, stacking depth and route geometry must be confirmed against the actual layout. Do not infer dimensions from a photograph or a generic drawing.
Evidence note: a visible finish, photograph or drawing does not prove acoustic, fire, durability, load or commercial performance. Confirm project-specific support, acoustic and dimensional requirements before relying on any coordination decision.
FAQ: Partition Coordination Decision Logs
What is a partition coordination decision log?
It is a controlled record of partition-related decisions, their status, the evidence behind them and the next action. It helps architects and contractors trace why a layout, finish or route changed.
When should the log be started?
Start it as soon as movable partition coordination begins. Early entries are usually simple, but they establish the habit of recording evidence and review status.
Can the log include acoustic targets?
Yes, but record them as project-specific requirements rather than assumed outcomes.
How should finish decisions be logged?
Record the selected finish, the reviewer and the drawing reference.
What if a route or stacking position changes?
Mark the previous entry as superseded, add the new route or position, and confirm that the revised path has a continuous connected overhead route and project-specific support review.
Who should own the log?
The architect or lead coordinator usually maintains it, but each entry needs a named reviewer. Contractors, owners and suppliers can contribute, but the evidence boundary must remain clear.
Conclusion: Keep the Log Evidence-Bounded
A partition coordination decision log architects can rely on is not a marketing document. It is a working record that separates confirmed facts from open questions. When decisions slip, that record protects the project from unsupported assumptions about movement routes, finishes, acoustics or dimensions.
Review the movable partition wall product context, check relevant project references, and confirm project-specific support, acoustic and dimensional requirements before finalizing any coordination decision.
To discuss pass-door requirements, documentation or layout review, contact EBUNGE and share your project drawings for a focused coordination conversation.
Continue Exploring
More Movable Partition Guide Guides
- Newer guideHow Facility Teams Schedule Partition Changeovers Without Disrupting
- Earlier guideRoom Scheduling Rules That Decide When a Movable Partition Stays Open
- Related guidePhasing Movable Partition Work When Renovation Zones Swap Mid-Programme
- Related guideHow Architects Run a Partition Coordination Workflow Before Ceiling