For Alaska general, heavy civil & specialty contractors
Alaska construction compresses a year of production into a short season while the documentation load stays constant. We build agents that draft the RFIs, chase the submittals, and package the change orders so your PMs spend the season on the work instead of the log.
Built in Anchorage · we publish our source code · no long-term lock-in
Written by Kristian Baer, Northtek · Anchorage, Alaska · Updated 2026-08-21
The short answer
It handles the document work that sits between the field and the office. An agent reads the spec section, the daily reports, the field photos, and the T and M tickets, then drafts the RFI, updates the submittal register, and assembles the change order with its backup attached. A project manager reviews and signs rather than starting from a blank page at nine at night. It does not make means-and-methods decisions, it does not price risk, and it does not sign anything. In Alaska the value concentrates in the season: the same PM can carry more work between breakup and freeze-up because the paperwork stops being the bottleneck.
The operating reality
Mobilization is expensive, material lead times run through a barge or a sealift, and the compliance load on public work is the same in Bethel as it is in Anchorage. The paperwork does not scale down for a short season.
Between breakup and freeze-up you have limited productive weeks. Every day a PM spends assembling a change order package is a day of field oversight nobody gave back.
A substitution request that sits in the submittal log for three weeks can miss the last sealift. Chasing overdue submittals is not administrative housekeeping here, it is schedule protection.
State and federally funded work carries certified payroll obligations and the penalties for getting them wrong are real. The forms are repetitive, rule-based, and exactly the kind of thing worth checking automatically before submission.
A superintendent at a village site documents with a phone, sometimes offline, and files it later. If your documentation system assumes an office and a desktop, it does not describe your projects.
Six workflows we build
These are the document handoffs where Alaska projects lose days. We build the ones that protect your schedule first.
01
02
03
04
05
06
First 30 days
Change order packages are high-effort, deadline-bound, and directly tied to cash. They are also the thing most likely to get shortcut in August when everyone is buried.
We follow three change orders you already closed, including one that got paid late or short, and find where the backup was hard to assemble and where documentation was missing.
We test the packaging agent on those historical projects and compare what it produces to what your PM actually submitted. You see the gap in both directions before you rely on it.
It runs on a single job with a PM who agrees to be the check, not on the whole portfolio. If it does not hold up on one project, it does not get rolled out.
What you own at day 30
A change order packaging agent connected to your project management system, an accuracy comparison against your own historical packages, the repository and configuration, and a one-page runbook for your project engineers.
What we built, in the open
Construction documentation has a second life in a claim, a dispute, or an audit long after the crew has demobilized. Anything that writes into that record has to be able to show its work, which is a harder engineering problem than generating a paragraph.
A compiler and language we wrote so an agent's reasoning is a readable sequence of steps rather than a black box. When a change order gets challenged, the assembly path is inspectable.
Verification that sits between the model and your project record. It checks that a claimed quantity or date actually appears in the daily reports behind it, and we publish its miss rate.
Long-context research, which is the unglamorous reason a 400-page spec book can be reasoned over at all. The benchmark harness is public, not just the result.
You will not use any of this directly. It is why we will put an audit trail in your contract instead of a reassurance.
Scope, stated up front
A project team can only trust a tool that is clear about what it will not touch. Three things that stay with your PM.
It will not price risk for you
An agent can assemble hours, rates, and materials. Deciding what a disputed delay is worth in a relationship with a repeat owner is a judgment call and stays with your PM.
It cannot fix undocumented work
If the daily reports for a delay period are empty, no tool can reconstruct the record. It will tell you the record is thin while you can still do something about it.
It is not a compliance guarantee
Our certified payroll check catches arithmetic, classification, and completeness errors. It is a second set of eyes, not a legal opinion, and we do not market it as one.
Where your data goes
Project records carry contractual weight and sometimes federal requirements. Four commitments, in the agreement rather than on a policy page.
It fits. Procore, Autodesk Build, Buildertrend, and CMiC all work as the system of record while the agent reads from and writes into them. We are not asking you to migrate a project management platform mid-season, which is a far bigger risk than the workflow it would fix.
It writes a first draft with the spec reference and the photo attached, which is the tedious part. Your PM edits the question and sends it. Over a few weeks the drafts get closer to your house style because it learns from what your team edits, and we show you that improvement rather than asserting it.
It checks certified payroll for classification mismatches, fringe and overtime arithmetic, apprentice ratios, and missing signatures against the wage determination for that project. It is a pre-submission check that catches the errors people actually make. It does not replace your compliance officer or your labor attorney.
Only if you want it to. Sensitive project records can run inside your own cloud tenant or on your own hardware. For work under federal contracts with CUI requirements we scope what can and cannot run before we build anything, in writing.
For a full rollout, probably. For one workflow, no. A change order packaging agent can be live in about a month, and the back half of the season is when the documentation load peaks. If the honest answer is to build over the winter and go live at breakup, we will say that.
A three-person electrical or mechanical sub drowning in T and M tickets and submittals often gets a bigger proportional gain than a large GC with a full project engineering staff. See the MEP contractors playbook for the specialty trade version of this.
Electrical & Mechanical
Service dispatch, T and M tickets, and takeoff support for MEP contractors.
Read →
Government Contracting
Solicitation triage, compliance matrices, and past performance libraries.
Read →
Logistics & Freight
Getting the material to the site, and billing for it correctly.
Read →
We will walk it backward with you and show exactly where an agent would have saved the days. Sixty minutes, no cost, written recommendation at the end.
Anchorage, Alaska · info@northtek.io · (907) 903-4353