Many timber-building enquiries lose clarity at the same point: a factory package is discussed as if it automatically includes the full local project. It does not. A well-scoped brief does not make the offer smaller; it makes it possible to understand what has been requested, what can be assessed by the factory and what must be led by the locally responsible project team.
This is useful for dealers, developers, architects and private buyers alike. It turns a vague “What is included?” question into a project map that can be reviewed before a proposal is compared or an order is agreed.
Start with the desired factory package
Describe the building use, approximate configuration, known dimensions, layout direction, openings, visual references and any agreed documentation needs. These are the inputs Eurodita can assess for a potential factory package. If the project is at an early stage, state what is open and what needs clarification rather than inventing a finished scope.
The appropriate commercial route may be a selected product family, a bespoke discussion, a private-label programme or a project-specific configuration. The brief should name the route because it determines the relevant next questions.
Map the local project responsibilities
Separately identify the people or businesses responsible for local design coordination, approvals, site access, groundworks, foundations, utilities, installation, weather protection, connections and handover. The exact list depends on the project, but assigning an owner to each interface is more important than pretending the responsibilities do not exist.
If a role is not yet appointed, mark it as an open action. This gives the buyer a practical pre-proposal checklist and avoids treating a missing local party as an automatic factory obligation.
Why scope separation improves comparisons
Two proposals cannot be compared fairly when one refers to a factory package and another combines product, local labour, groundworks or other site services. Before comparing figures, confirm the basis: which drawings and assumptions were used, which components are included, what documentation is named and which tasks are outside the quoted factory package.
Clarity is also important for a dealer speaking with an end customer. The dealer can explain which questions belong to the building configuration and which need confirmation by the customer’s local project team.
Use a simple responsibility record
- Factory discussion: proposed configuration, factory package and agreed documentation based on the supplied brief.
- Buyer or dealer: customer qualification, commercial route and coordination of the correct local parties.
- Local project team: site design, approvals, foundations, services, installation and destination-market coordination unless a written order expressly changes that scope.
- Open items: facts not yet confirmed, named with an owner and next action.
This is not a contractual document by itself. It is a disciplined way to prepare for an accurate discussion and to highlight the items that need to be agreed in writing later.
Ask the questions in the right order
Before requesting an order-specific proposal, confirm the intended use, location, approximate layout, visual and functional requirements, project route and local interface owners. Then ask what further information is required to assess the factory package. The dealer resources and construction guides are useful supporting paths for this stage.
Do not treat a general blog article, reference image or model name as a final scope. They are starting information, not a replacement for the project-specific brief.
Keep the order stage separate
The scope becomes binding only through the relevant written order and agreed documents. Until then, it is good practice to distinguish confirmed facts from preferences, questions and local assumptions. This allows the factory, buyer and local team to resolve gaps without turning an early enquiry into an unintended promise.
A better first message
Send the intended use and market, an annotated layout or reference, the desired factory-package discussion, a list of local responsibilities already allocated and the questions that remain. The result is a clearer route from first enquiry to a proposal that everyone can read in the same way.
Use one scope line for every proposal input
For each important element, note the requested result, the party expected to supply or coordinate it, and the evidence needed before it can be treated as confirmed. A layout is not the same as a foundation design; a desired door position is not the same as local installation planning; a reference image is not the same as an agreed specification. Keeping those distinctions visible removes ambiguity without slowing the project down.
Before accepting a quotation for internal comparison, ask whether this scope record was used. If it was not, update the record and request clarification rather than filling the gap with a guess. This is how a buyer retains control of a multi-party project while keeping the factory conversation fair and focused.