Tomok, the AI workspace for heavy civil project control

  • 13 daily reports
  • Lookahead rev 12
  • RFI-0217
  • Weather log
Cedar Fork CorridorDemo project · Update 23West approachCedar Fork BridgeCut sectionInterchangeEast approach100+00120+00140+00160+00180+00200+00220+00240+00260+00280+00300+00320+00340+00100+00120+00140+00160+00180+00200+00220+00240+00260+00280+00300+00320+00340+00MarAprMayJunJulAugSepOctNovDecJanFebMarAprMayJunJulAugSepOctNovDec20262027MarAprMayJunJulAugSepOctNovDecJanFebMarAprMayJunJulAugSepOctNovDec20262027Data dateClearing and grubbing, westClearing and grubbing, eastWaterline relocationMass excavation, cut sectionEmbankment, west approachCedar Fork Bridge substructureEmbankment, east approachInterchange ramps and bridgeStorm drainage, westCedar Fork Bridge deckStorm drainage, cut and eastRetaining wall, segment 3Aggregate base, westAggregate base, eastPaving, westPaving, eastBarrier and guardrailStriping and signsLegendMilestonesClearingDrainage and utilitiesEarthworkStructuresRetaining wallsBase and pavingWinter shutdownBarrier and stripingBaselinetomokCHART TITLELinear schedulePRODUCED BYTomokDATA DATE2026-10-12RUN DATE2026-10-12REVISIONU23
tomtok

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.

See Tom work

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.

Cedar Fork Corridor
Data date 12-Oct-26
00:00 | 00:16

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

Bridge deckRetaining wallEast embankment
−606121824Negative floatU12U14U16U18U20U22FlaggedBridge deck −3dRetaining wall 6dEast embankment 17d

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.

tomtok
“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.”
Why we built Tomok

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.

InputP6 exportCFC_U23.xer
IDActivity nameStartFinish
CL-1010Clearing and grubbing, west02-Mar-26 A10-Apr-26 A
MS-0010Notice to proceed02-Mar-26 A
CL-1020Clearing and grubbing, east16-Mar-26 A22-May-26 A
UT-1110Waterline relocation06-Apr-26 A31-Jul-26 A
EW-1220Mass excavation, cut section20-Apr-26 A25-Sep-26 A
BR-1310Cedar Fork Bridge substructure04-May-26 A04-Sep-26 A
EW-1210Embankment, west approach04-May-26 A28-Aug-26 A
EW-1230Embankment, east approach01-Jun-26 A30-Oct-26
IC-1410Interchange ramps and bridge01-Jun-26 A30-Jul-27
DR-1610Storm drainage, west06-Jul-26 A09-Oct-26 A
BR-1320Cedar Fork Bridge deck08-Sep-26 A02-Apr-27
DR-1620Storm drainage, cut and east14-Sep-26 A26-Feb-27
RW-1510Retaining wall, segment 317-Sep-26 A30-Nov-26
BS-1810Aggregate base, west19-Oct-2611-Dec-26
WS-1700Winter shutdown, paving14-Dec-2619-Mar-27
BS-1820Aggregate base, east22-Mar-2725-Jun-27
MS-0050Traffic switch to new bridge05-Apr-27
PV-1910Paving, west05-Apr-2711-Jun-27
PV-1920Paving, east14-Jun-2724-Sep-27
BA-2010Barrier and guardrail02-Aug-2729-Oct-27
ST-2020Striping and signs04-Oct-2719-Nov-27
MS-0090Substantial completion30-Nov-27
OutputLinear schedule11 × 17 · Sheet 1 of 1
Cedar Fork CorridorDemo project · Update 23West approachCedar Fork BridgeCut sectionInterchangeEast approach100+00120+00140+00160+00180+00200+00220+00240+00260+00280+00300+00320+00340+00100+00120+00140+00160+00180+00200+00220+00240+00260+00280+00300+00320+00340+00MarAprMayJunJulAugSepOctNovDecJanFebMarAprMayJunJulAugSepOctNovDec20262027MarAprMayJunJulAugSepOctNovDecJanFebMarAprMayJunJulAugSepOctNovDec20262027Data dateClearing and grubbing, westClearing and grubbing, eastWaterline relocationMass excavation, cut sectionEmbankment, west approachCedar Fork Bridge substructureEmbankment, east approachInterchange ramps and bridgeStorm drainage, westCedar Fork Bridge deckStorm drainage, cut and eastRetaining wall, segment 3Aggregate base, westAggregate base, eastPaving, westPaving, eastBarrier and guardrailStriping and signsLegendMilestonesClearingDrainage and utilitiesEarthworkStructuresRetaining wallsBase and pavingWinter shutdownBarrier and stripingBaselinetomokCHART TITLELinear schedulePRODUCED BYTomokDATA DATE2026-10-12RUN DATE2026-10-12REVISIONU23
Update 23 of the demo project as a P6 export, and the linear schedule Tomok draws from it. The pale shapes behind the retaining wall and west paving are their baseline dates; the red line is the data date, 12-Oct-26.

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.

Cedar Fork Corridor
Data date 12-Oct-26
00:00 | 00:14

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.

Log in