Search

Starlink Mini for Construction Sites Without Fixed Internet

Starlink Mini panel on a tripod beside a dusty white dual-cab ute on an Australian civil construction site at late afternoon, with an excavator and shipping-container site office behind.

On most civil and commercial projects the internet arrives last. The earthworks happen, the pad goes down, the footings pour, the steel goes up — and somewhere near the end, a subcontractor turns up to pull a fibre cable through a trench that someone else was supposed to dig in month two. Until that day, the site is expected to run on mobiles and optimism.

That gap is where construction projects quietly lose time. Not in the big, obvious ways that show up on a programme, but in the small ones: the RFI that sits in someone's drafts because the drawings are too big to send, the crane camera that only works in the site office, the daily diary that gets typed up at home because there is nowhere to upload the photos. A Starlink Mini does not fix a site's connectivity permanently, and it is not meant to. It closes the gap between mobilisation and the day the trench finally gets dug.

Why fixed connectivity arrives last on site

There is a logic to it, even if it is a frustrating one. Fixed connectivity is a permanent asset on a temporary footprint. Nobody wants to trench 400 metres of conduit into ground that will be cut and filled again in six months, and nobody wants to own that asset at practical completion. So the trench gets deferred, and deferred again, and the site runs on whatever it can borrow.

The result is a project phase that everyone treats as temporary and almost nobody plans for properly. Yet on a typical build, that phase can run for a third of the programme. Getting it wrong does not stop the job. It just makes the job slower and more expensive in ways that are hard to point at later.

The trenching order of operations

Fibre and copper need a path, and the path needs to exist before the cable does. On a greenfield site that means the civil works have to reach the point where a comms conduit can be laid without being destroyed by the next pass of an excavator. On a brownfield site it is worse — you are threading new services through ground that already has stormwater, sewer, gas and someone's forgotten 1970s telephone line in it.

Add the commercial layer and the delay compounds. The developer does not want to fund permanent infrastructure for a tenant who has not signed. The head contractor does not want to carry the cost. The telco has its own lead times, which are measured in weeks and sometimes quarters. Everyone is waiting for someone else to commit, and the site keeps working in the meantime.

None of that is a criticism of how projects are run. It is simply the reason a temporary link is not a nice-to-have on a construction site. It is the only communications infrastructure that is actually going to be there during the phase when the most expensive plant and the most people are on the ground.

What actually needs the link

Ask a site team what they use the internet for and you will get a list that sounds modest until you add it up. Email and drawings come first. Then the project management platform, the safety system, the daily diary, the photo records that increasingly form part of contractual evidence. Then the things that only exist because there is a connection: the crane camera feed, the time-lapse upload, the environmental monitoring dashboard.

The shape of that traffic matters more than the total. Most of it is small packets — text, forms, metadata — and a lot of it is upstream. Photos from a phone go up, not down. Site diaries go up. Time-lapse frames go up. Which is why a link that benchmarks beautifully on download and collapses on upload is worse than useless on a construction site: it will pass the speed test and fail the job.

There is also a category of traffic that is genuinely latency-sensitive and often overlooked. Live camera feeds for crane operations, remote support sessions where a supplier is walking a site supervisor through a fault, and any tool that holds a session open rather than transferring a file. Those do not need enormous bandwidth. They need consistency, and consistency is the thing a congested site network is worst at providing.

Interim is not temporary

The word "interim" does a lot of damage on construction projects. It implies a solution that does not need to be thought through, because it will be replaced. In practice the interim system is the one that carries the project through its riskiest phase, and it gets replaced on a date that moves.

Treat it as production infrastructure and the decisions change. You stop asking whether the dish can sit on the ground and start asking where it can be mounted so it does not get hit. You stop running a single cable across a trafficable area and start thinking about how the power gets there safely. You stop assuming the site manager's phone hotspot is a backup and start treating it as what it is: a single point of failure with a battery.

That shift in framing is worth more than any particular piece of hardware. A site that has decided its temporary link is real infrastructure will specify it, install it properly and hand it over between supervisors. A site that has decided it is temporary will improvise it three times and wonder why it keeps failing.

What a construction site needs from a satellite link

Satellite internet has a reputation problem on construction sites, and most of it was earned by the previous generation of geostationary services. High latency, hard data caps, and a dish the size of a wheelbarrow. The current generation of low-earth-orbit services behaves differently enough that the old assumptions do not transfer, but it is not magic either. It has specific strengths and specific limits, and both matter when you are specifying it for a project.

The useful way to think about it is not "is this fast" but "does this fit the traffic shape we actually have". A site with four people sending drawings and photos has a very different requirement from a site running a live camera feed and a cloud-backed safety system. Getting that match right is most of the work.

Upstream is the number that matters

Site connectivity is asymmetric in a way that home connectivity is not. On a residential connection, most of the traffic comes down — streaming, browsing, updates. On a construction site, a surprising proportion goes up. Photo evidence, diary entries, marked-up drawings, time-lapse frames, drone captures, automatic backups of the project platform. All of that leaves the site.

This is where a cheap mobile-based solution quietly fails. A phone hotspot will report a healthy signal and then take twenty minutes to push a batch of site photos, because the uplink is the constrained direction and nobody specified it. Files queue, the platform syncs late, and the person holding the phone concludes the software is slow.

When you size a link for a site, size the uplink first. Ask what leaves the site on a heavy day — not on an average one — and design for that. If the answer includes drone imagery or time-lapse, the number is bigger than most people expect, and the practical response is usually scheduling rather than more bandwidth: push the big transfers overnight rather than during the working day.

Latency, jitter and the tools that notice

Low-earth-orbit latency is good enough for almost everything a site does, including video calls and remote support. What causes trouble is not the average latency but the variation — jitter — and the occasional drop when the dish's view of the sky is interrupted. A file transfer does not care. A live session does.

The practical implications are about placement rather than hardware. A dish with a clean, unobstructed view of the sky is stable. A dish tucked against a container, under a tree, or beside a structure that will soon be clad is unstable, and the instability will show up as video calls that freeze and remote sessions that drop at the worst moment.

It is also worth being honest about what satellite cannot do well on a site. Real-time control of heavy plant over a satellite link is not something to design around, and any tool that assumes a fixed, low-jitter connection should be tested before the project depends on it. Where those tools exist, the usual answer is to keep them local and let the satellite handle the reporting.

Treat the temporary link as production infrastructure and the decisions change. Stop asking whether the dish can sit on the ground, and start asking where it can be mounted so it does not get hit, does not get stolen, and does not lose its view of the sky when the scaffold goes up.

Plan limits and the data you did not budget for

Every satellite service has a data model, and construction sites are unusually good at generating traffic that nobody planned for. Automatic cloud backups of the project platform, phone photo libraries syncing over the site network, software updates pushed to every laptop on a Monday morning — individually reasonable, collectively expensive.

The fix is rarely a bigger plan. It is a small amount of traffic management, applied early. Turn off background sync on site devices. Schedule large transfers outside working hours. Keep a separate connection decision for anything that streams continuously, like a camera, rather than letting it share the link with the site office by default.

A site that has done this properly will run comfortably on a modest plan. A site that has not will burn through a large one and still complain that the internet is slow. The difference is not the hardware, it is whether anyone owns the traffic.

Power, mounting and security on a live site

The connectivity decision gets all the attention, and the installation is what actually determines whether it works. A Starlink Mini on a construction site has three problems to solve that a domestic installation does not: power that does not depend on a wall socket, mounting that survives a site, and a link that stays private on a site full of subcontractors.

None of these are hard, but all of them are easy to get wrong in a way that only shows up after a few weeks of dust, vibration and weather.

Power from plant, not a generator

The default instinct is to run an extension lead from the site shed, and on a project with reliable mains that is fine. On early works, the shed may not exist and the generator may be a shared asset that gets shut down at the end of the shift. A dish that loses power overnight is not a disaster, but a dish that loses power mid-transfer is.

Running the unit from the vehicle is usually the more robust option on a moving site, because the vehicle is already there, already has a battery, and already moves with the supervisor. A 12V to 30V power supply with an Anderson plug handles the voltage range a working vehicle actually delivers — including the sag on start and the spike on a jump start — without needing a separate inverter.

If the unit is going to live on a vehicle long-term, plan for the cable run as well as the power. A cable that crosses a tray or a cabin door is a cable that will be pinched, and a pinched power cable on a moving vehicle is a fault that presents as an intermittent reboot nobody can explain.

Mounting for wind, dust and theft

A tripod on the ground works for a day. It does not work for a month on a site where plant moves around it. The practical options are a magnetic mount on a steel surface — a tray, a bonnet, a container roof — or a fixed bracket where the unit is going to live permanently for the duration of the project.

Magnetics are popular on construction sites because the unit can be moved between vehicles without tools. A good magnetic mount with a shield, like the Alloy Magnetic Mount with Shield for Starlink Mini, gives you that flexibility while protecting the panel from the knocks that come with vehicle mounting. What it does not do is stop someone walking off with the unit, so a mount is only half the answer.

The other half is the routine. Unit goes on at the start of the shift, comes off at the end and goes into the cab or a hard case. That habit, applied consistently, is more effective than any lock. A hard protective travel case also solves the transport problem: a dish that lives loose in a tray gets damaged by its own cable and whatever else is sliding around next to it.

Keeping the link private

A site network with an open password is a site network that will be used by everyone, including people who are not on your project. That is not a security lecture, it is a capacity problem: a link sized for a site office will behave very differently when forty subcontractor phones have joined it.

The practical controls are simple. Give the site network a strong password and change it when the trade mix changes. Keep a separate guest network for visitors if the link can support one, or decline politely if it cannot. Turn off the default network name where the hardware allows it, so the unit does not advertise itself to everyone in the car park.

If the site needs to share data between devices — a printer, a camera, a local drive — a wired adapter is usually the cleaner answer than putting everything on Wi-Fi. Keeping fixed devices on cable also reduces the number of things competing for airtime, which is the constraint most site networks actually hit.

Frequently asked questions

Can a Starlink Mini replace a site's permanent internet connection?

No, and it is not designed to. It is the right tool for the phase between mobilisation and the day fixed services arrive, and for the sites where fixed services will never be economic. Use it to keep drawings, diaries, photo records and safety systems flowing during early works, then hand over to the permanent connection when it lands.

How much data does a construction site office actually use?

Less than most people fear and more than most people plan for. A site office running email, drawings, a project platform and photo uploads sits in a modest range, but automatic cloud backups, phone libraries syncing and continuous camera feeds can multiply it. Measure for a week before choosing a plan, and schedule the heavy transfers outside working hours.

What is the most common installation mistake on a construction site?

Placing the unit where it has a partial view of the sky. A dish tucked against a container or under a tree will work well enough to look fine in a speed test and then drop live sessions at the worst moment. Give it a clean horizon, mount it high enough to stay clear of plant and stock, and take it down at the end of the shift rather than leaving it out to be hit.

Where this leaves the temporary site

The connectivity gap on a construction site is not going to close on its own. Fixed services will keep arriving late, because the commercial and civil logic that delays them is not going to change, and projects will keep mobilising onto sites with no infrastructure. The only real variable is whether the temporary link is planned or improvised.

Planned looks unremarkable: a unit mounted where it has a clean view, powered from the vehicle that carries it, on a plan sized to what actually leaves the site, with a routine for locking it away at the end of the shift. Improvised looks like a hotspot taped to a window and a supervisor who has become the unofficial IT department.

If you are specifying connectivity for early works, the hardware is the easy part. A vehicle-mounted unit, a power supply that handles a working vehicle's voltage, a mount that can move between machines and a case that survives the tray — that is a complete kit, and it can be installed in an afternoon and moved to the next project when this one finishes. The Outcamp range covers magnetic mounts for site vehicles, 12V power supplies built for Anderson wiring and hard cases for transport between sites, which is most of what a temporary site installation needs.

Leave a comment (all fields required)

Turtle season opens at Mon Repos and the sand south of Bundaberg empties out. A late-spring guide to the beaches, the bush camps and the reef beyond.

No sealed roads, no servo, and a barge that will not wait. Here is how to do Mulgumpin properly in spring, from permits to the best camp on the western beach.

Hard sand under the tyres, humpbacks resting in the bay beyond the headland — a spring run to K'gari is the trip that earns its place on the calendar.

Frosty mornings, granite boulders and a fireside cellar door at every turn — Queensland's highest wine region is at its best when the rest of the state is in shorts.

Towing all day should put real charge back in. Usually it barely does, and the trailer plug is the reason why. Here is the diagnostic order that finds it.

A big number on the box does not mean a big night of power. Here is how usable capacity, inverter loss and surge ratings decide what your caravan can actually run.

A fridge that copes fine in winter can fail badly at 40 degrees. Most of the fixes cost nothing — and one of them is a five-minute check behind the vent.

No bars at the free camp doesn't have to be part of the deal. Here's how to mount and power a Starlink Mini on your van so it works every time you stop.

Search