Construction data becomes a transfer problem when repeated capture and richer deliverables create more bytes than project connections, recipient tools, and handoff practices can absorb on schedule. The problem is not simply “large BIM files.” It is the combination of native models, linked dependencies, drone imagery, point clouds, derived products, many external recipients, and version-sensitive deadlines.
Capture creates source and derived data
A field visit no longer produces only notes and selected photographs. Depending on scope, it can produce hundreds or thousands of drone images, terrestrial scan setups, mobile-mapping trajectories, control records, panoramas, and video. Processing then creates registered point clouds, orthomosaics, elevation models, meshes, textures, reports, and BIM references. Teams may retain both source and derived data because they serve different purposes.
Point density, image resolution, overlap, number of scan positions, returns, attributes, and project duration all affect volume. There is no defensible universal “typical construction scan” size. USGS Lidar Base Specification 2025 revision A, released June 2025, defines 8 pulses/m² for public-program QL1 and 2 pulses/m² for QL2. Over the same area, that is a fourfold pulse-count multiplier before attributes and processing. These 3DEP quality levels do not describe every commercial scanner, building survey, or construction deliverable.
Device specifications show why field choices matter without proving a typical project. Leica's dated BLK360 G2 sheet lists up to 680,000 points/second, four resolution settings, and 104 Mpx raw spherical imagery per setup. DJI describes the Zenmuse P1 as a 45 MP full-frame photogrammetry payload and publishes a 3 km² single-flight claim under its stated conditions. These are product-specific ceilings and vendor claims, not cross-device benchmarks or construction file-size measurements.
Drone activity is also easy to overstate. The FAA's CY 2024 U.S. survey estimated 38.4 million recreational and Part 107 nonrecreational flights in 2024. Among surveyed Core Part 107 operators, real estate and construction was the most common activity category, with more than 500 respondents at least somewhat active. Those are U.S. survey facts, not construction adoption percentages, file-volume measurements, or 2026 fleet counts.
BIM adds dependencies and release pressure
Native models are only part of a coordination set. A useful handoff may include linked models, CAD references, point-cloud references, families, shared coordinates, IFC or NWC exports, clash reports, BCF issues, schedules, PDFs, and viewer packages. One visible RVT file can therefore understate the complete dependency tree.
Authoring platforms also distinguish live collaboration from packaged exchange. Autodesk's eTransmit guidance for Revit 2022, for example, describes collecting a model and associated files for transmission. That product-and-version-specific workflow should not be generalized to every Revit release, cloud-hosted model, ACC tenant, or non-Autodesk dependency. The sender still has to test the actual package and tell the contractor what was included.
Every coordination cycle can create another release. If teams overwrite folders or send links from personal storage, recipients can combine a current model with an old scan or clash report. At construction deadlines, version ambiguity can be more damaging than raw package size.
Platform capacity does not remove the time constraint. Autodesk's ACC/BIM 360 support page, as accessed August 2026, lists a 5 TB maximum per file, 10,000 items per folder, and cancellation for an upload that does not finish within 24 hours. Those limits are surface- and date-specific. They do not promise that a 5 TB file can cross either endpoint's connection within one day.
Field connectivity meets two network legs
Construction delivery often crosses an office, regional office, jobsite trailer, subcontractor, and owner environment. The sender's advertised download speed says little about upload capacity, and the recipient must still download the package. Local storage read/write, Wi-Fi, VPN policy, inspection tools, and concurrent traffic can become bottlenecks.
The FCC adopted 100/20 Mbps as a U.S. fixed-broadband benchmark in March 2024 and a long-term goal of 1,000/500 Mbps; the associated availability snapshot used December 2022 deployment data. It is a policy benchmark, not measured jobsite throughput or a service guarantee.
At 20 Mbps, a 750 decimal GB release takes about 93 h 20 m for one modeled upload. A recipient downloading at 100 Mbps adds about 18 h 40 m. The site's model uses decimal bytes and a 12% planning allowance. These are planning estimates, not observed performance; packaging, verification, and application ingest are additional.
External coordination multiplies the problem
The U.S. Census Bureau estimated June 2026 construction spending at a seasonally adjusted annual rate of $2,166.5 billion, with $1,046.9 billion in the first six months of 2026. That preliminary, revisable U.S. sector measure establishes economic scale only. It does not prove BIM adoption, data growth, or transfer demand.
The operational evidence comes from the workflow itself: many organizations need different subsets, permissions, formats, and deadlines. A federated model for coordination, a reduced viewer set for a trade, and source scans for a survey consultant should not automatically become one all-recipient package.
Treat delivery as a release process
First, inventory data by purpose: source capture, working data, coordination outputs, contractual deliverables, and archive. Send only what the recipient is authorized and equipped to use. Record software/version, units, coordinates, datums, relative paths, file counts, decimal byte sizes, and integrity values in a manifest.
Second, freeze an issue-stamped release and separate WIP from issued material. Grant identified recipients access for the required window. Estimate both network legs from measured rates, preserve a physical or hybrid fallback when the deadline requires it, and keep an owner watching exceptions.
Finally, require recipient confirmation: manifest matched, integrity checked, and representative files opened in the intended application. “Upload complete” is not the same as “contractor can work.”
The construction file-transfer workflow and BIM/VDC checklist provide a practical operating path.
Use the transfer-time calculator with measured endpoint rates, then compare physical-media timing in the shipping-versus-transfer calculator when the field connection cannot meet the handoff window.
Where TeraAirlift fits
TeraAirlift is a Windows-first desktop operations console for discrete online delivery. It provides queues, progress and ETA, cancellation, retry-friendly operations, history, diagnostics, recipient-controlled delivery, short-lived storage access, and SHA-256 verification. It can make a release observable, but it does not reduce capture volume, replace BIM collaboration or archives, guarantee speed, or establish contractual acceptance.
Sources
- FAA — CY 2024 Small UAS Survey Report
- FCC — 2024 broadband benchmark order
- U.S. Census Bureau — Construction spending release
- USGS — LiDAR base specification tables
- USGS — Lidar Base Specification online
- Leica Geosystems — BLK360 G2 specification sheet
- DJI Enterprise — Zenmuse P1
- Autodesk — Revit 2022 eTransmit
- Autodesk — BIM 360 and ACC upload limits
