Skip to main content
Guardian IT

Industries · Construction

IT that works in the office and on the job site.

General contractors and specialty trades run two environments at once: a back office that looks like any other business, and a field where connectivity is unreliable and hardware takes a beating.

Most IT providers are set up for the first one. We plan for both, because the estimate, the submittal and the change order all have to move between them.

Schedule a Free AssessmentRequest a Consultation

Who this is for

  • General contractors
  • Specialty and trade contractors
  • Civil, site and utility contractors
  • Design-build firms
  • Engineering and construction organizations
  • Companies with seasonal or fluctuating crews

Typically 5–50 office and field staff, often across multiple active projects.

What's different here

Two environments, one business.

The office side is familiar: estimating, accounting, project management, email and a file server or cloud drive full of drawings. The field side is not. It's phones and tablets on cellular, a laptop in a truck, a trailer with marginal internet, and people who need a document right now and can't wait for IT.

On top of that, crews change. Seasonal hiring, project-based staffing and normal trade turnover mean accounts are created and should be removed far more often than in a typical office business — and offboarding is usually the first thing that slips when a job is busy.

What we handle

What contractors actually need from IT

Drawn from the problems that come up repeatedly in construction businesses running an office and a field at the same time.

Office and field employees

The challenge

Office staff need full workstations and business applications. Field staff need fast access to a handful of things from a phone or tablet, usually with one hand and no patience.

How we handle it

  • Different device standards for office and field roles, both centrally managed
  • Field access focused on the few systems that matter: plans, photos, time, daily reports
  • Support that can help someone who is standing outside, not sitting at a desk
  • Training kept to what's genuinely needed, delivered in minutes rather than hours

Laptops, tablets and mobile devices

The challenge

Hardware lives in trucks and on sites. It gets dropped, dusty, left behind and occasionally stolen — and it holds project data either way.

How we handle it

  • Every device enrolled in management, whether it's a workstation or a tablet
  • Full-disk encryption so a lost device isn't a data exposure
  • Remote lock and wipe when hardware goes missing
  • Rugged or semi-rugged hardware recommended for field roles where it earns its cost
  • Replacement planning based on realistic field service life, not warranty length

Employee turnover and crew changes

The challenge

Seasonal and project-based staffing means frequent onboarding and offboarding. Access that outlives employment is one of the most common gaps we find in this industry.

How we handle it

  • Role templates so a new hire is set up in minutes from a known-good baseline
  • Accounts provisioned with an end date where the role is seasonal or project-bound
  • Same-day offboarding: sign-in blocked, sessions revoked, company data pulled from personal phones
  • Device return tracked, then wiped and re-provisioned for the next person
  • A written record of every grant and removal

Microsoft 365 and cloud applications

The challenge

Project management, estimating, accounting and document control are increasingly separate cloud services, each with its own logins and its own idea of who you are.

How we handle it

  • Microsoft 365 administered properly — accounts, licensing, mail security, file structure
  • Single sign-on where the application supports it, reducing password sprawl
  • A business password manager with shared vaults for the rest
  • Vendor coordination so we chase the software company, not your project manager
  • License counts reconciled against actual staff, which matters when headcount swings

Project files and drawings

The challenge

Drawings, submittals, RFIs and photos are large, numerous and version-sensitive. Working from the wrong revision is expensive in a way most IT problems aren't.

How we handle it

  • File structure and permissions designed around how projects actually run
  • Reliable sync so field and office are working from the same current set
  • Access for subcontractors and architects that doesn't mean opening everything
  • Archive strategy for closed jobs, so active storage stays fast and costs stay sane
  • Backup covering project data independently of the platform storing it

Unreliable job-site connectivity

The challenge

A site trailer might have decent internet, bad internet or none. Field work can't stop while someone waits for a connection to come back.

How we handle it

  • Cellular-first setups for trailers, with fixed internet where it's available and worth it
  • Offline-capable applications identified so critical work continues through an outage
  • Realistic expectations set per site rather than one standard that fails half of them
  • Temporary site networking for longer projects, including segmentation from company systems
  • Guidance on what genuinely needs bandwidth and what doesn't

Security that holds up in the field

The challenge

Construction businesses move substantial money and deal with many outside parties, which makes invoice and payment fraud a live risk. Field conditions make security that depends on perfect behavior unrealistic.

How we handle it

  • MFA enforced for everyone, configured to be workable on a phone in the field
  • Managed endpoint protection on every device, office and field alike
  • Email filtering plus domain authentication to reduce spoofing of your company name
  • A verification step for changes to payment or banking details
  • Controls that don't assume a quiet desk and an undivided minute

Vendor and subcontractor access

The challenge

Architects, engineers, subs and suppliers all need something. Access gets granted quickly during a job and almost never gets reviewed after it.

How we handle it

  • Guest and external access scoped to specific projects rather than whole systems
  • Access tied to the job, with removal at closeout as a standard step
  • Shared credentials eliminated in favor of individual accounts where possible
  • A current record of which outside parties have access to what

Common questions

What contractors ask us first

Didn't find your question?

Ask it directly — you'll get a straight answer from someone who does the work.

contact@guardianitutah.com
Contact us
Can you support our estimating and project management software?

We support the environment those applications depend on — devices, operating systems, network, permissions, file access, backups and connectivity — and we act as your technical contact with the vendor.

Deep questions inside the application go to the people who build it, but we open and manage those tickets and handle anything infrastructure-related, including upgrades and new-user setup.

What do you do about job sites with bad internet?

We start by being realistic: some sites will never have good connectivity, and planning around that is better than pretending otherwise. For trailers we typically go cellular-first, with fixed service where it exists and is worth the install.

We also identify which applications work offline and sync later, so a dropped connection doesn't stop a daily report or a set of photos from being captured.

How quickly can you set up a new hire during a busy season?

Field roles are usually same-day once we have the request, because the setup runs from a role template rather than being assembled from scratch. Office roles needing specific hardware depend on whether a device is already in stock.

We'll keep a small buffer of pre-configured devices if your hiring pattern justifies it — that's a conversation worth having before the busy stretch, not during it.

What happens when a device is lost or stolen on a site?

Because devices are enrolled and encrypted, the data on them isn't readable without credentials. We can lock or wipe the device remotely and revoke its sessions, then provision a replacement from the same baseline.

We also log it, because a pattern of losses in one area is usually a process problem worth fixing rather than a run of bad luck.

We have multiple offices and a shop. Does that complicate things?

Not materially. Multiple locations mainly affect network design and how you handle on-site visits. Each location gets its own firewall and wireless configuration with consistent standards, and company systems are kept separate from guest and shop-floor devices.

Management and support are centralized, so a user's experience is the same at every location.

Our crews aren't going to sit through security training.

They shouldn't have to. Field training should be a few minutes on the things that actually reach them: a text claiming to be from a supervisor, a fake delivery notice, a request to change payment details.

The heavier controls belong in the technology rather than in people's attention — enforced MFA, managed devices, email filtering. The goal is that someone making an honest mistake doesn't cause an incident.

Do you come to job sites?

Yes, across the Wasatch Front, for work that needs someone physically present — trailer setup, site networking, hardware deployment and new-location installs.

Day-to-day support is remote-first because it's faster, and we can reach a phone or tablet in the field the same way we'd reach a desk.

Get your office and your field on solid footing.

A free assessment reviews your Microsoft 365 setup, device protection, backups, employee access and job-site connectivity — then tells you what to address first.

Schedule Your Free AssessmentRequest a Consultation

(385) 270-4733Serving businesses throughout Utah.