Tomok, the AI workspace for heavy civil project control
- 13 daily reports
- Lookahead rev 12
- RFI-0217
- Weather log
7 days waiting on an RFI, 2 rain days, and 2 days with the crew pulled to the bridge deck. Completion holds. RFI-0217Weather logDR 09-15
Tomok is the AI workspace for heavy civil project control.
Update 23 of the demo project as Tomok prints it, the baseline behind the retaining wall and west paving, and one question answered from the record.
Trusted by teams from Kiewit, Skanska, and Fortune 500 companies.
An illustrated walkthrough of Tom investigating a missed start on the demo project. Tom reads the daily reports, the lookahead, the RFI log, and the weather record, explains the 11-day slip with a source for every cause, and drafts the update for the scheduler to accept.
We’re introducing Tomok, the AI workspace for heavy civil project control. One place for the schedule, the paper trail behind it, and the questions an owner asks.
A heavy civil job runs on a schedule with thousands of activities and a paper trail to match: daily reports, lookaheads, RFIs, submittals, change orders, specifications. Project controls is the work of holding all of it together, and of explaining every slip to an owner who wants to know why and what it does to the finish. Tomok reads all of it. It imports your P6 schedule, keeps every update, and answers schedule questions with the record that supports each claim.
Tomok starts with the schedule because that is where every question on a heavy civil job ends up. It draws print-ready linear schedules, investigates variances with cited evidence, and drafts the corrections, lookaheads, and narratives your team signs. Nothing changes in your schedule until a scheduler accepts it.
Update 23 of the demo project, in four numbers.
- Schedule updates, each kept as a version
- 23
- Daily reports read for one answer
- 13
- Retaining wall start, against baseline
- +11 d
- Substantial completion at P80, against contract
- +19 d
Total float by path
Demo project · weekly updates 12–23 · days
Total float on the three most critical paths of the demo project across twelve weekly updates. Tom flagged the bridge deck path in update 18, three weeks before its float went negative.
Each view answers a question project controls teams ask every week. Here they come from the demo project’s twelve updates and its daily reports; on your job, Tom builds them from the records your team already keeps.
“A schedule is a promise made in public. Project controls is the work of keeping it, and of explaining it honestly when it slips. We built Tomok so that work starts from the record instead of from memory.”
Start with the schedule
Import a P6 export and Tomok reads every activity, relationship, and date. Each update is kept as a version, so you can see what moved between data dates, and why.
From the same data, Tomok draws the linear schedule heavy civil teams plan with: stations across, time down, each crew’s production as a line you can read at a glance. Sheets print at 11×17 with your title block and legend, and share as view-only links.
Already planning in Excel? The Tomok add-in builds the same sheet inside your workbook, and the workbook opens in the web workspace when you’re ready.
| ID | Activity name | Start | Finish |
|---|---|---|---|
| CL-1010 | Clearing and grubbing, west | 02-Mar-26 A | 10-Apr-26 A |
| MS-0010 | Notice to proceed | 02-Mar-26 A | |
| CL-1020 | Clearing and grubbing, east | 16-Mar-26 A | 22-May-26 A |
| UT-1110 | Waterline relocation | 06-Apr-26 A | 31-Jul-26 A |
| EW-1220 | Mass excavation, cut section | 20-Apr-26 A | 25-Sep-26 A |
| BR-1310 | Cedar Fork Bridge substructure | 04-May-26 A | 04-Sep-26 A |
| EW-1210 | Embankment, west approach | 04-May-26 A | 28-Aug-26 A |
| EW-1230 | Embankment, east approach | 01-Jun-26 A | 30-Oct-26 |
| IC-1410 | Interchange ramps and bridge | 01-Jun-26 A | 30-Jul-27 |
| DR-1610 | Storm drainage, west | 06-Jul-26 A | 09-Oct-26 A |
| BR-1320 | Cedar Fork Bridge deck | 08-Sep-26 A | 02-Apr-27 |
| DR-1620 | Storm drainage, cut and east | 14-Sep-26 A | 26-Feb-27 |
| RW-1510 | Retaining wall, segment 3 | 17-Sep-26 A | 30-Nov-26 |
| BS-1810 | Aggregate base, west | 19-Oct-26 | 11-Dec-26 |
| WS-1700 | Winter shutdown, paving | 14-Dec-26 | 19-Mar-27 |
| BS-1820 | Aggregate base, east | 22-Mar-27 | 25-Jun-27 |
| MS-0050 | Traffic switch to new bridge | 05-Apr-27 | |
| PV-1910 | Paving, west | 05-Apr-27 | 11-Jun-27 |
| PV-1920 | Paving, east | 14-Jun-27 | 24-Sep-27 |
| BA-2010 | Barrier and guardrail | 02-Aug-27 | 29-Oct-27 |
| ST-2020 | Striping and signs | 04-Oct-27 | 19-Nov-27 |
| MS-0090 | Substantial completion | 30-Nov-27 |
Every answer cites its evidence
Ask Tomok what happened and it answers the way a good scheduler would: from the record. Tom reads daily reports, lookaheads, RFIs, submittals, meeting minutes, and the weather log, and ties each claim to the document and date behind it.
When an answer implies a schedule change, Tom drafts it as a correction: the activity, the new dates, the effect on float, and the sources. A scheduler reviews it and accepts it or doesn’t. Accepted corrections become project memory, so the next question starts from what your team already confirmed.
Tom traces float across twelve weekly updates, finds the path that is eroding, ties the loss to the daily reports and meeting minutes, and proposes a recovery for the project manager to weigh.
Your data stays yours
Schedules and project documents belong to the contractor that produced them. Tomok keeps each project’s records separate, shows the source behind every answer, and does not use your data to train models. Share links are view-only, and you can revoke them at any time.
Built by people who have run the schedule
Tomok is built by the head of schedule on a multi-billion-dollar rail tunnel program and a former Amazon tech lead. We are working with contractors on live schedules now. If you run project controls on a heavy civil job, we would like to hear what slows you down.
The operating system for heavy civil construction, starting with the schedule.