TeraAirlift
Delivery checklist
demo@rcparker.co
https://teraairlift.com/demo
BIM/VDC Package Delivery Checklist
Who it's for: VDC managers, BIM leads, coordination leads, and project engineers owning model handoffs before meetings and bid deadlines.
When to use: Use before sending RVT/IFC/NWD packages, clash reports, bid sets, owner handoffs, or scan-to-BIM datasets ahead of a coordination meeting or bid window.
TeraAirlift
Delivery checklist
BIM/VDC Package Delivery Checklist
Who it's for: VDC managers, BIM leads, coordination leads, and project engineers owning model handoffs before meetings and bid deadlines.
When to use: Use before sending RVT/IFC/NWD packages, clash reports, bid sets, owner handoffs, or scan-to-BIM datasets ahead of a coordination meeting or bid window.
01Before the meeting clock starts
- ☐Confirm the coordination meeting / bid deadline and required arrival buffer
- ☐Name a delivery owner who will confirm downloads before the call
- ☐List packages by audience (GC, architect, trades, owner) — don’t send one mega-dump to everyone
- ☐Align agenda language with the exact model version string you will send
- ☐Decide what happens if transfer slips past the meeting buffer
02Package & version
- ☐Confirm model version / federated set name in the folder root
- ☐Include issue/date stamp matching the meeting agenda
- ☐Strip stale WIP that should not go to subcontractors
- ☐Include clash reports, BCF, or issue lists that belong with this set
- ☐Note package size and expected download time for attendees on jobsite Wi-Fi
- ☐Verify a sample model/viewer package opens before upload
03Meeting-driven queue
- ☐Set the hard deadline relative to the coordination meeting (not “sometime Friday”)
- ☐Queue critical packages first; archive and photo sets second
- ☐Assign someone to confirm recipient download before the call starts
- ☐Prepare contingency if overnight bandwidth is constrained
- ☐If multiple trades need different subsets, queue separate controlled deliveries
04Jobsite & regional constraints
- ☐Check whether recipients are on trailer Wi-Fi or office fiber
- ☐Warn attendees if download will take longer than the pre-meeting buffer
- ☐Avoid last-minute “can you grab this from my personal Dropbox” paths
- ☐If drives are Plan B, confirm courier ETA still beats the meeting
05Stakeholder communication
- ☐Tell each recipient group what they are getting and what they are not
- ☐State clearly whether this is WIP coordination or issued-for-construction
- ☐Provide the access window end time with the send notice
- ☐Confirm who must reply “received and opened” before the meeting
06Failure / retry plan
- ☐If transfer slips past the meeting buffer, notify attendees early with a new ETA
- ☐Do not mix an outdated model into a new uncontrolled share to “save time”
- ☐Escalate when shipping drives would miss the meeting entirely
- ☐Capture root cause (version confusion vs bandwidth vs access) for the VDC postmortem
- ☐If you must re-send, bump the version string so nobody works from the wrong set
- ☐Park failed transfers — don’t leave half-synced folders labeled as the meeting set
07Recipient / access plan
- ☐Grant subcontractor access only for the packages they need
- ☐Expire access after the review / bid window
- ☐Keep owner vs trade packages on separate controlled deliveries when needed
- ☐Record who received the package and when
- ☐Revoke temporary consultant access after the coordination cycle
- ☐Avoid eternal shared-folder invites that outlive the trade’s involvement
08Verification plan
- ☐Confirm the recipient can open the model/viewer package
- ☐Verify version string matches the meeting agenda
- ☐Log delivery time relative to the meeting start
- ☐Have at least one trade confirm download before the call when critical
- ☐Archive the send record for RFI / change disputes later
- ☐Only then mark the coordination set as “issued for this meeting”