Key Takeaways
- Construction back offices lose money on paperwork, not on concrete. An expired insurance certificate, an unsigned change order or a late pay application costs more than any field inefficiency that week.
- The work is documents plus deadlines plus chasing. That combination is exactly what an AI employee handles well, because none of it needs a person on site.
- Start with subcontractor compliance. It is the highest risk item, it is pure record keeping, and it is the one job where nobody notices the gap until an incident happens.
- Change orders and RFIs are a chasing problem. Somebody has to know what was sent, who has not answered, and how long it has been sitting. That somebody does not have to be human.
- Keep the field out of it. An AI employee belongs in the office, in your channels and your files, not between a foreman and a crew at 6am.
- Review-first is the only sane default. Anything that goes to an owner, a lender or a sub comes back as a draft for a human to approve.
The concrete pour went fine. The problem is that the sub who did it had an insurance certificate that expired eleven days ago, nobody caught it, and now the general contractor's risk manager has a question that costs more to answer than the pour did.
That is the construction back office. Not the exciting part of the business, but the part that decides whether a job closes at margin or bleeds out in retention, disputed change orders and unbilled work. Most of it is documents with deadlines attached, chased by two or three people who are also doing four other jobs.
This is a guide to handing that work to an AI employee: what to give him first, what to keep human, and where it goes wrong.
Why construction back office work suits an AI employee
Three properties make a job a good fit for delegation, and construction admin has all three.
It is document shaped. Certificates of insurance, W-9s, lien waivers, submittals, RFIs, change orders, daily reports, pay applications. Every one of them is a file with fields, a date and a counterparty.
It has hard deadlines that arrive on a calendar. Pay application windows, notice periods, certificate expiries, RFI response times. Missing them is expensive and completely preventable.
Most of the effort is chasing, not deciding. The decision on a change order takes a project manager five minutes. Finding out that it has been sitting unanswered for nine days takes longer than the decision.
An AI employee like Viktor sits in Slack or Microsoft Teams, reads the channel for a job, and works across 3,200+ integrations with real read and write access. He can open the shared drive, read the certificate, check the expiry, post in the job channel and draft the email to the sub. He is not on site, he is not in a truck, and he never was going to be.
Where to start: five jobs, in order
1. Subcontractor compliance tracking
Pick every active sub, every required document, and every expiry date. Have your AI employee keep one live table of what is on file, what expires within 30 days and what is missing, refreshed on a schedule, posted in the channel every Monday.
The email to the sub asking for the renewal is drafted, not sent. You approve it. Trades remember who sends them a polite reminder and who sends them a legal letter after the fact.
2. Change order and RFI chasing
Every change order and RFI has a sent date, a required response date and an owner. Ask for one weekly table: item, job, days outstanding, who owes the answer, dollar exposure if it is a change order. Then have him draft the follow-ups for the ones past due.
This is the single highest return job on the list, because unanswered change orders turn into unbilled work, and unbilled work turns into a dispute at closeout.
3. Pay application assembly
Progress billing is assembly work. Pull the schedule of values, the current period costs, the lien waiver status for each sub, and produce the package draft with the exceptions flagged: which waivers are missing, which line items moved more than expected, which retention math does not tie.
A human signs it. A human always signs it. The three hours of assembly before the signature are the part you get back.
4. Supplier invoice and purchase order matching
Take the invoice, find the purchase order, compare quantity and unit rate, flag anything that does not match, and route the exceptions to the person who ordered it. The same pattern that finance teams use, applied to lumber and equipment rental. The mechanics are covered in AI for bookkeeping.
5. Job cost reporting for the owner
One report per job per week, assembled from the accounting system and the field reports, written in language a non-accountant reads in ninety seconds: committed, spent, remaining, what moved this week and why. The reporting pattern is in replace weekly reporting with AI.
What to keep human
Being honest about the limits matters more in construction than in most industries, because the downside is not an awkward email.
| Work | Give it to an AI employee | Keep it human |
|---|---|---|
| Tracking insurance and licence expiries | Yes, this is pure record keeping | Deciding whether to let a non-compliant sub work |
| Change order paperwork and chasing | Yes, assembly and follow-up drafts | Costing the change and negotiating it |
| Pay application packages | Yes, assembly and exception flags | Signing and certifying |
| Safety documentation filing | Yes, filing and gap reports | Any incident response or investigation |
| Daily report collation | Yes, collecting and summarizing | Field judgment about what actually happened |
| Bid comparison spreadsheets | Yes, normalizing scope into one table | Choosing the sub |
The pattern: the AI employee owns the paperwork and the deadline, a human owns the risk and the relationship. Nothing goes to an owner, a lender, an insurer or a sub without an approval step, which is the default described in how to verify your AI employee's work.
How the setup actually looks
Create a channel per active job. Connect the tools where the documents already live: email, the shared drive, the accounting system, the spreadsheet where somebody has been tracking subs since 2019. Guidance on picking the first ones is in choosing your first 3 integrations.
Then hand over one recurring job and let it run for two weeks before adding the second. The first one is almost always compliance tracking.
Every Monday at 7am, check the subcontractor folder in the shared drive against the active subs list. Post a table of every sub whose insurance certificate, licence or W-9 is missing or expires within 30 days, sorted by expiry date, with the job they are working on. Draft a reminder email for each one and leave them for me to approve.Once a job runs cleanly for a few weeks, write it down as a procedure the whole office can edit, so the next project manager inherits it instead of rebuilding it. That is the argument in how to turn a recurring task into a shared skill.
Where it goes wrong
Starting with the field. Foremen do not want another app and they are right. Keep the AI employee in the office, working on the documents the field already produces.
Handing over a broken process. If nobody knows which subs are active, an AI employee will produce a confident table built on a stale list. Fix the source list first.
No approval step on external mail. Construction relationships are long and local. A wrong reminder to a sub you have used for twelve years costs more than the ten minutes it saved.
Assuming the accounting system is the truth for field progress. It is the truth for money. Percent complete usually still comes from a person walking the job.
Frequently Asked Questions
What is an AI employee in a construction company?
An AI employee is software you message like a colleague, in Slack or Microsoft Teams, that connects to your real tools and does back office work: tracking documents, assembling billing packages, chasing responses and producing reports. Viktor works this way, with read and write access across 3,200+ integrations, and returns real files rather than suggestions.
Can it work with our project management software?
It depends on what you run. An AI employee reaches systems through their integrations or their exports, so the practical test is whether your system has an API or a scheduled export. Email and shared drives always work, which is why most construction offices get value on day one without touching the project management system at all. See which integrations your AI employee actually needs.
Is it safe to give it access to job financials?
Access should be scoped per channel and per tool, so an AI employee sees the jobs you put him in and nothing else. Viktor maintains SOC 2 Type I, and anything financial or external comes back as a draft for approval. The full access model is in how to control what your AI employee can access.
What about lien waivers and notice deadlines?
Tracking them is a good fit: dates, documents, counterparties. Deciding to file a notice is not, because that is a legal decision with a relationship attached. Have the AI employee surface every deadline inside its window and draft the paperwork, then have your controller or counsel make the call.
Will it replace our office manager?
No, and the offices that get the most out of this are usually the ones where the office manager runs it. The work that disappears is the collating, the chasing and the assembly. What is left is judgment, relationships and exception handling, which is most of the job anyway.
How long before it is useful?
One recurring job set up properly is useful the first week it runs, because compliance gaps show up immediately. Broad usefulness across a portfolio of jobs takes a few weeks of adding one job at a time. The ramp is described in your first 7 days with an AI coworker.
Does this work for specialty trades, not just general contractors?
Yes, and often faster. A mechanical or electrical contractor has fewer counterparties and a tighter document set, so the tracking table is simpler and the payoff on chasing change orders is just as large.
