Bidder Track Interface Assumptions Hidden Scope
Quick answer: track interface
Review focus: track interface.
When a tender package includes movable walls, the bidder track interface assumptions hidden scope is often the first place where submissions quietly diverge. Two bidders can quote the same panel count and the same finish schedule, yet describe very different ideas about what the track connects to, who supplies it and what must be verified before fabrication. The suitability of each route and parking arrangement depends on the approved layout, circulation, ceiling interfaces and operating sequence.
This article sets out an evidence-bounded review method. It does not judge any bidder’s competence and it does not supply engineering conclusions. It shows where to look, what to ask and which items must be confirmed against project-specific drawings and support review.
Why Track Assumptions Matter More Than Panel Descriptions
Project review term: track interface.
EBUNGE movable wall panels are individually movable, suspended from a top track, and cross the opening without a floor track. They park at a planned stacking position. That operating concept means the overhead route carries the movement, so the interface between the partition system and the building structure is central to the scope.
Panel descriptions are comparatively easy to compare: dimensions, finish and quantity are visible on the schedule. Track interface assumptions are harder, because they describe a boundary between packages. The exact route, junction arrangement, continuous overhead path and parking position must be confirmed from the coordinated project drawings. Neither assumption is wrong in itself, but each one transfers work or risk somewhere.
What the interface actually covers
In tender terms, the interface includes the route the panels follow, the points where that route is supported, the transitions at corners or turning sections, and the parking location. Straight, turning and stacking routes are reviewed from the layout, so the layout drawing is the document that should anchor the discussion.
Reading a Bidder’s Assumptions Line by Line
Coordination scope: track interface.
Assumptions are usually written as short qualifications. Read them as scope statements rather than as caveats. The table below shows typical assumption wording and the question a reviewer should ask. It is a review aid, not a statement about any particular bidder.
| Assumption wording | What it may leave open | Question for the bidder |
|---|---|---|
| Overhead support by others | Who designs, verifies and installs the supporting structure | Which drawing shows the support, and who signs it off? |
| Continuous track route assumed | Whether the route is connected across the full movement path | Can you mark the complete route on the layout? |
| Parking area by others | Location, size and readiness of the stacking position | Which plan defines the parking zone and its clearance? |
| Finishes per schedule | Which surfaces are confirmed and which remain open | Which finish options are priced, and on what basis? |
| Site conditions as drawn | Whether the drawings reflect current site conditions | Which drawing revision was used for the bid? |
Watch for assumptions that travel between packages
The most expensive gaps are rarely inside one bidder’s price. They sit between packages, where each party believes the other has covered the item. Track support, route continuity and parking readiness are common examples. A short written clarification is usually cheaper than discovering the gap after award.
A Practical Review Sequence for Project Teams
The following numbered process keeps the review grounded in documents rather than impressions. Adapt it to your procurement stage.
- Ask each bidder to mark the proposed movement route, including straight, turning and stacking sections, on the same layout.
- Ask each bidder to state in writing which interface items are included and which are assumed to be provided by others.
- Compare the marked routes and inclusion statements side by side, not the headline prices alone.
- List every difference and route it to the responsible design party for confirmation.
- Record the confirmed position in the tender clarification or contract documents before award.
This sequence does not resolve engineering questions. It exposes them early enough for the right party to answer. For general product context, see the movable wall product overview.
Where Hidden Scope Usually Appears
Hidden scope is not necessarily concealed on purpose. It appears where documents are silent, where responsibility is shared, or where a bidder has made a reasonable but unstated working assumption. Reviewers should look in four places.
Route continuity and transitions
Every proposed movement path requires a continuous connected overhead route and project-specific support review. If a bidder’s drawing shows panels crossing an opening but does not show how the route continues through a turn or into the parking zone, that is a scope question, not a detail to settle later.
Support and structure
Top-hung operation places the interface at the structure above. The tender should make clear which party is responsible for verifying that support. Do not infer capacity from a drawing or a photograph; capacity and fixing design require project-specific confirmation.
Parking and stacking
Parking style is customized to the customer layout and project requirements and may support compact stacking when the coordinated design permits it. The bidder’s assumption about where panels park, and whether that space is available, belongs in the comparison.
Finishes and pass doors
Confirmed finish options include laminate, melamine, fabric, leather, glass and other approved surfaces. If a bidder prices a finish without stating the basis, ask. Pass-door requirements and project documentation can be discussed with the supplier and should be written into the scope where required.
Comparing Submissions Without Overreading Them
A comparison matrix helps, provided it records only what bidders actually wrote. Avoid scoring bidders on inferred quality. Instead, record the presence or absence of a written position on each interface item.
- Route marked on the same layout revision by all bidders
- Written statement of included and excluded interface items
- Named drawing revision used as the bid basis
- Finish basis stated for each scheduled surface
- Parking position identified on plan
- Open questions listed with an owner for each answer
Evidence note: a marked route or a written assumption is a coordination record, not proof of structural capacity, acoustic performance or dimensional fit. Those items require separate project-specific confirmation.
Acoustic Language: Keep It Conceptual
Seals and acoustic concepts can be explained generically, but any acoustic requirement must be confirmed for the specific project, assembly and opening.
Ask for the confirmation path instead.
Documentation to Request Before Award
The aim is a tender record that shows what was agreed, not a promise about outcomes. Request the marked layout, the written inclusion and exclusion list, the drawing revisions used, and a schedule of open items with named owners. Where pass doors are required, include the requirement in the same record.
Additional planning material is available in the EBUNGE resources section. Keep every statement tied to a document revision so that later changes can be traced.
Frequently Asked Questions
What does a bidder’s track interface assumption usually mean?
It is the bidder’s written or implied position on how the overhead route connects to the building and which party provides each part. It should be read as a scope statement and confirmed against drawings.
Does a marked route prove the system will fit?
No. A marked route is a coordination record. The exact overhead route and support arrangement must be confirmed by the responsible project team from coordinated drawings.
Can panels cross an opening without a floor track?
EBUNGE panels are top-hung and cross the opening without a floor track. Every proposed movement path still requires a continuous connected overhead route and project-specific support review.
How should parking be handled in the tender?
Parking style is customized to the layout and project requirements. Ask each bidder to identify the parking position on plan and state whether that space is included or assumed.
Which finishes can be discussed?
Confirmed options include laminate, melamine, fabric, leather, glass and other approved surfaces. The basis for each scheduled finish should be stated in the bid.
Can STC or Rw be compared directly between bids?
These are rating concepts, and any acoustic requirement must be confirmed for the specific project and assembly.
Conclusion and Next Step
Bidder track interface assumptions are a useful early-warning system. Review them as documents, record the answers, and confirm every project-specific requirement before award.
To discuss pass-door requirements, finishes or project documentation for your layout, contact the EBUNGE team with your drawings and tender questions.


