A studio in one country wins a project in another. The design is theirs, the client is theirs, and the architect of record will be a local practice because that is what the law requires. What travels between them is not drawings. It is information, and somebody has to be responsible for it.
This is the part of architectural work that crosses borders most easily, and it is the reason BIM coordination is bought as often by other firms as by building owners. Licensing does not travel. Model coordination does.
Three kinds of firm ask for it, and they are asking for different things.
A design studio at capacity needs production and coordination it does not want to hire permanently. The work is delivered behind their name, to their templates. What they are buying is elasticity, and the reason they buy it rather than subcontract locally is that the standard has to match the one they already run.
An engineering consultancy needs the disciplines reconciled before construction documentation is issued. Architecture, structure and building services each hold part of the truth, and the conflicts between them are cheap to fix in a model and expensive to fix in a wall. What they are buying is a federated model and a clash cycle that closes.
A contractor or construction manager needs to know the model can be trusted before pricing from it. What they are buying is a review, and quantities that stay consistent with the version that was approved.
What actually changes across a border
Less than people expect on the model, more than they expect on the process. Geometry is geometry. What differs is who approves what, which authority reads which document, what a permit set must contain, and at which point in the calendar the local architect of record takes responsibility.
The practical consequence is that a cross border BIM scope has to be written down before it starts. Not as bureaucracy, but because the alternative is discovering in month four that two teams held different assumptions about who models the services and to what level.
ISO 19650 is the shared language
ISO 19650 provides an international framework for managing information across the life of a built asset. It does not make a project good on its own. What it does is remove the argument about naming, status, revision and approval, so that a team in Athens and a team in Madrid mean the same thing by the same file.
Wolfblanc works informed by ISO 19650, alongside ISO 9001 quality principles and ISO 14001 environmental principles. In practice that means three things are agreed in the BIM Execution Plan before modelling starts: the level of information needed per discipline and phase, the exchange and approval routes, and where the Common Data Environment lives. Where the client already runs a CDE, we work inside it rather than beside it.
Open formats are not a preference, they are a condition
On a project with four firms in three countries, no party should be locked to another party's software. Production happens in Revit and coordination in Navisworks, but exchange happens in IFC, because the model has to outlive the licence that drew it and has to be readable by a team that never bought the same tools.
What to ask before appointing anyone
Ask who owns the federated model and who closes a clash. Ask what the level of information need is at each stage, in writing. Ask what happens to the model at handover, and in which format. Ask whether the coordinator has worked with a local architect of record before, because the failure mode in cross border work is almost never modelling skill. It is an unowned decision sitting between two firms who each assumed the other had it.
