Distinguish the source model from its deliverables
A native model and an issued drawing serve different purposes. The model may contain building elements and structural relationships, while the drawing records a particular view, issue or approval state. Linked models, calculations and other documents may be held separately.
IFC is an exchange format for building information. What an export contains depends on the system and settings used. For example, Autodesk's Revit IFC export options describe choices involving linked files. An IFC export should therefore not be assumed to contain the entire original project.
Give the project a workable boundary
| Archive layer | Useful information for the discussion | What should not be assumed |
|---|---|---|
Source models |
Known system, version and project grouping |
Every discipline is contained in the main model |
Discipline models |
Which disciplines contributed and how links are organised |
One organisation can license every contribution |
Issued drawings |
Types of issue and their relationship to project stages |
Every file has a complete revision history |
Construction and as-built records |
Related fabrication, installation or record documents |
The planned and constructed conditions are identical |
If several projects or stages have become mixed in the same storage area, a broad grouping is sufficient initially. A technical contact can explain the detail later. There is no need to reconstruct the archive before making contact.
Revisions can explain how a design developed
A final plan answers different questions from a sequence of design changes and associated decisions. Revision notes, responses and recorded approvals can help establish that sequence where they exist. Their presence does not mean that every project has a complete or commercially relevant history.
Consider a fictional façade package with an initial concept, a revised fixing arrangement and a corresponding fabrication drawing. A useful overview would identify the released state and whether the same elements can be followed across those documents. It would not need to identify the building owner or disclose the site address.
Separate contributors, permissions and project identity
Architecture, structural engineering and building services may have been produced by different organisations. Being able to open a combined project does not settle who can authorise a further use. Appointments, customer obligations, contributors' rights and confidentiality need to be considered separately.
Project identity may also be apparent from geometry, location information or a distinctive combination of features. Removing a title block is not automatically enough. The anonymisation review guide covers indirect identifiers, while the confidential engineering data guide helps frame the related rights and disclosure questions.
Start with a description rather than a drawing set
Share known systems, approximate project years and the kinds of records available. Volumes can be estimated or left unknown. If a sample is appropriate later, its project sections, dependencies and required approvals are agreed before any transfer.
The archive types overview can help you describe a mixed technical collection. Please keep project links, access credentials and source files out of the initial enquiry.