Quick answer: interface assumption verification status board
Review focus: interface assumption verification status board.
An architect coordination interface assumption verification status board movable partition is a design-phase tracking tool, not a drawing set. It records which track, stack and ceiling assumptions each discipline has actually confirmed before those decisions are frozen. The board does not prove performance; it exposes where evidence is still missing. Used well, it prevents a coordination meeting from closing on assumptions that no one has verified against the current layout.
Why Interface Assumptions Drift Between Disciplines
Project review term: interface assumption verification status board.
Movable partitions sit at the boundary of several scopes. The architectural team controls the opening and the finished ceiling zone. The suitability of each route and parking arrangement depends on the approved layout, circulation, ceiling interfaces and operating sequence. The MEP team controls services that may cross the track route. The partition supplier reviews the layout and confirms what the product can do.
Each discipline may hold a different version of the same assumption. One team believes the track runs straight to a side pocket. The exact route, junction arrangement, continuous overhead path and parking position must be confirmed from the coordinated project drawings. A third has not checked whether the ceiling void can accept the suspension. None of these are product failures; they are unverified interfaces.
The status board makes those differences visible early, while changes are still inexpensive to coordinate. It is a working document, reviewed at each design milestone, not a one-time checklist.
What the Status Board Should Track
Coordination scope: interface assumption verification status board.
A useful board is narrow. It tracks assumptions that affect whether the partition can be built as drawn. Broader design questions belong elsewhere.
Track and route assumptions
- Proposed route: straight, turning, or a combination reviewed from the layout.
- Whether the overhead route is continuous and connected across the full movement path.
- Who has reviewed the route against the current architectural plan.
Stack and parking assumptions
- Planned stacking position and whether it is inside or outside the room envelope.
- Whether the stacking zone conflicts with doors, glazing, or fixed furniture.
- Whether the parking arrangement is customized to the project layout.
- Who has confirmed the stack position against the reflected ceiling plan.
Ceiling and support assumptions
- The ceiling zone available for the top track and suspension.
- Which discipline owns the supporting structure above the ceiling.
- Whether the support condition has been reviewed by the responsible engineer.
- Any unresolved question about services passing through the track zone.
A Simple Verification Status Model
Checklist focus: interface assumption verification status board.
Status labels should describe evidence, not confidence. A discipline saying “looks fine” is not the same as a discipline confirming a drawing.
| Status | Meaning | Next action |
|---|---|---|
| Assumed | Stated in a meeting or sketch, not checked | Assign an owner and a review date |
| Under review | Being checked against current drawings | Record the drawing revision being used |
| Confirmed by discipline | The responsible discipline has reviewed and accepted | Note the reviewer and date |
| Confirmed with supplier input | Reviewed with the partition supplier’s layout comments | Attach the reviewed layout reference |
| Open / blocked | Cannot be resolved until another decision is made | Name the blocking decision |
This model avoids the trap of treating a verbal agreement as a confirmed interface. It also shows a project owner where design risk is concentrated.
Running the Board Through Design Phases
Review focus: interface assumption verification status board.
The board changes character as the project moves forward. In early design, most rows are assumed. By the end of coordination, most rows should be confirmed or explicitly deferred with a named owner.
Concept and schematic phase
List every interface assumption that affects the partition concept. Include the opening width, the intended movement path, and the likely stacking zone. Do not attempt to resolve support details yet; record who will resolve them.
Design development
Review the board against updated plans and the reflected ceiling plan. Mark which assumptions have moved to confirmed and which remain open.
Pre-tender and construction documentation
Freeze only what is confirmed. Anything still open should be listed as a coordination item with a responsible discipline. The board becomes a handover record between design and delivery teams.
Evidence Notes and Boundaries
Project review term: interface assumption verification status board.
Confirm project-specific support, acoustic and dimensional requirements with the responsible disciplines and the partition supplier before freezing track, stack or ceiling decisions. A status board records coordination, not performance.
Treat acoustic requirements as project-specific and confirm them through the appropriate specification route.
Those questions require their own evidence and their own reviewers.
Common Coordination Failure Patterns
Most interface problems repeat across projects. Recognizing the pattern helps a team correct it before drawings are issued.
- Silent assumption transfer. A route is drawn by one discipline and treated as fixed by another without review.
- Stack position by default. The parking zone is placed where it fits graphically, not where the layout and ceiling allow.
- Ceiling void treated as empty. Services crossing the track zone are discovered late.
- Verbal confirmation. A reviewer agrees in a meeting but no drawing revision is recorded.
- Frozen too early. Track and stack decisions are locked before the responsible disciplines have reviewed them.
Each pattern is preventable with a status board that names an owner, a drawing revision, and a date for every row.
How to Keep the Board Useful
Keep it short enough to review in one meeting. One row per interface assumption, one owner, one status, one next action. Avoid duplicating the full drawing register.
Review it at every design milestone and after any significant layout change. A board that is updated only at the end of design development is a record, not a coordination tool.
Share it with the partition supplier early enough that layout comments can be incorporated. The supplier can review straight, turning and stacking routes from the layout, and can discuss pass-door requirements and project documentation.
For product context, see the movable wall systems page. Additional planning references are available in the resources library.
Frequently Asked Questions
Who should own the status board?
The architect or lead designer usually maintains it, because the board tracks interfaces across disciplines. Individual rows are owned by the discipline responsible for verifying that assumption.
When should the board be started?
As soon as a movable partition is proposed in the layout. Starting early keeps assumptions visible while they are still easy to change.
Does a confirmed status mean the partition will perform as required?
No. Confirmed means the responsible discipline has reviewed the interface assumption. Performance requirements still need their own project-specific confirmation.
Can the board include acoustic requirements?
It can record that an acoustic requirement exists and who is responsible for confirming it. It should not be used to claim a rating or infer performance from a drawing.
How does the board relate to the partition supplier’s layout review?
The supplier reviews straight, turning and stacking routes from the layout. Recording that review on the board helps the design team see which assumptions have supplier input and which do not.
What should happen to rows that remain open at tender?
They should be listed as coordination items with a named owner and carried into the construction phase, rather than being treated as resolved.
Conclusion
A design-phase interface assumption verification status board gives a project team a shared, evidence-based view of what has actually been confirmed. It does not replace drawings, engineering review, or supplier input. It simply prevents unverified track, stack and ceiling assumptions from being frozen as if they were decisions.
Used consistently, the board reduces late coordination surprises and gives every discipline a clear place to record its review. Confirm project-specific support, acoustic and dimensional requirements before finalizing any partition configuration.
To discuss your project’s layout, route and documentation requirements, contact the EBUNGE team.