The product

WriCon Construction Agents.

Specialist AI agents that run construction operations — live in production today, moving real iron. This page is the honest breakdown of what’s shipped: what each piece does, who uses it, and what it saves. Dispatch is first; the suite grows from here.

/01   WAIN · DISPATCH

Dispatch — the day, run properly

Wain keeps the whole lowbed day in one queue — moves, conflicts, drivers, and the field's asks — and catches problems while they're still cheap.

The dispatch module is where the suite started, because it’s where the money leaks: a lowbed day is a chain of small commitments — this machine, that trailer, this driver, that window — and one broken link ripples through all of them. Wain holds the whole chain, checks every change against it, and keeps the plan honest as the day moves.

What it does
  • Builds and maintains the daily move queue — every haul, in order, per driver
  • Detects real conflicts: missing permits on oversize loads, timed drops that can't be made, machines still committed to another site
  • Walks each driver's day serially, so nothing double-books by construction
  • Takes field requests — "I need a packer at the highway job" — and holds them against the queue until they're scheduled
  • Tracks material asks the same way: what's needed, where, by when, and whether it's been ordered
Who uses it
  • Dispatchers
  • Superintendents
  • Foremen (requests in, updates back)
What it saves

One person can run a fleet's worth of moves without the whiteboard, the sticky notes, or the 6 a.m. phone tree — and the expensive misses (a permit gap found at the scale, a machine promised to two jobs) get flagged the evening before instead.

Worked example — demo data

Monday at Tamarack Ridge

The Cat 336 has to get from the yard to the Highway 16 overlay, and it's oversize — Wain flags the missing permit before the truck is loaded. The D6 was promised to the subdivision by 10:00, but the queue says its driver can't make that drop — flagged, moved, solved at 6:40 a.m. Meanwhile the grading foreman's packer request from last night is already sitting in the queue with a want-by date attached.

The dispatch board on a Monday morning at Tamarack Ridge Contracting: Merv Kowalski's lane with a timed drop flagged won't-make-time, an oversize excavator flagged for a missing permit, and the field's open requests on the rail.
/02   WAIN · CHAT & VOICE

Talk to it like a dispatcher

Plain language in, dispatcher-grade answers out — typed or spoken, on whatever device is in reach.

Every agent in the suite is reachable the same way: a conversation. The door is a chat that behaves like your best dispatcher on their best day — it already knows the context, it proposes rather than assumes, and when something needs your sign-off it puts a card in front of you instead of a wall of text.

What it does
  • Web chat with full operational context — it knows the fleet, the sites, and today's queue
  • Live form cards inside the conversation: a proposed move arrives as a structured card you confirm, not a paragraph you decode
  • Full-duplex voice — talk to it hands-free from the truck
  • Push notifications carry updates back out to whoever needs them
  • Replies written the way a dispatcher would actually say it — route, timing, and what needs attention, no filler
Who uses it
  • Dispatchers
  • Foremen and field crews
  • Drivers
What it saves

Nobody learns new software. The training course is one sentence — "just tell it what you need" — which is why it actually gets used from day one, in the office and from the cab.

Worked example — demo data

"Get the 336 out to the highway job"

One sentence from the dispatcher. Wain answers with a move card: unit 4520 from the South Yard to the Highway 16 overlay, lowboy and driver suggested from the standing rotation, permit flag raised because the 336 runs oversize. One tap to confirm — the move is queued, the driver gets briefed, and the site contact is on the card.

A dispatch proposed in Wain chat: the haul mapped pickup to drop-off, the oversize permit warning carried on the card, and the dispatcher's approval stamped before anything moved.
/03   DASHBOARD

The ops surface

A live dashboard shaped to each role — the dispatcher's board, the admin's controls, and the audit trail, all in one place.

The dashboard is the suite’s shared surface: the same live state the agents work from, rendered for humans. It’s deliberately field-grade — high contrast, fast, readable on a phone in sunlight — because that’s where operations actually look at it.

What it does
  • Live day queue and move board — what's rolling, what's next, what's stuck
  • Role-shaped chrome: a driver sees their day, a dispatcher sees the fleet, an admin sees the levers
  • Fleet, sites, and roster management with managed vocabularies — types and options stay consistent
  • Admin surface with a full audit viewer: every proposal, confirmation, and override, attributed and timestamped
  • Installs as an app (PWA) — one tap from home screen to the board
Who uses it
  • Dispatchers
  • Coordinators & admins
  • Owners who want the 30-second overview
What it saves

The answer to "where are we at?" becomes a glance instead of three phone calls — and when something looks wrong, the audit trail answers "who changed this and when" in seconds instead of an argument.

Worked example — demo data

The 7 a.m. board at Tamarack Ridge

Six moves on the board: two complete, one in transit, one flagged — the D6's drop time won't be made — and two waiting on confirmation. The open-requests rail shows the packer ask for Highway 16 and a culvert order for the grid-road job. The superintendent reads the whole morning in under a minute, from the truck.

The WriCon ops console command deck as dispatcher Joan Norquay sees it — one tile for each module her company's instance runs.
/04   MOBILE

In every pocket on the crew

The agents, the board, and the day's briefs on the phones the crew already carries — installable from the browser today, with native iOS and Android apps on the way to the stores.

The suite meets the field where it lives: the phone. Today that’s an installed web app with push; the native iOS and Android apps — same instance, same agents, same live state — are in the store pipeline. Either way, the loop between office and field closes without anyone chasing anyone.

What it does
  • Installs to the home screen today (PWA) — one tap to the board, no app store required
  • Native iOS/Android shell with a bottom bar built for gloved, sunlit, jobsite use — in the store pipeline now
  • Push notifications that actually arrive — move briefs, changes, and confirmations
  • Driver flows on the phone: today's queue, map pins at the gate, delivery instructions, status stamps
  • The same private instance as the dashboard — nothing new to set up per user
Who uses it
  • Drivers
  • Foremen & field crews
  • Anyone away from a desk (which is everyone)
What it saves

The gap between "dispatch decided" and "the field knows" drops to zero. No printed run sheets, no morning phone tree, no "nobody told me" — the brief is on the phone before the coffee's poured.

Worked example — demo data

A driver's morning

Merv opens the app at 6:15: two moves today. First card — the 336 to the Highway 16 overlay, pin at the west tie-in, "flag the site super on arrival." He taps rolling when he's loaded, dropped when it's off the trailer, and the board updates itself. The only radio call is the one he didn't have to make.

A driver's day on the phone: two hauls with live ETAs, the 10:00 drop flagged won't-make-time, and the permit flag riding with the load.
/05   DOCUMENTS

Reads the paperwork so you don't

Feed the instance your specs, contracts, and drawings — then ask questions and get answers grounded in your actual documents.

Construction runs on documents nobody has time to read twice. The document module gives each instance a working memory of its own paper, so the answer to a spec question is a lookup, not an archaeology project.

What it does
  • Ingests the project paper: specs, contracts, standards, drawings, manuals
  • Answers questions from those documents, with the source to back it up
  • Works through the same chat door as everything else — ask in plain language
  • Per-client document store on your own instance — your paper stays yours
Who uses it
  • Project managers & estimators
  • Superintendents
  • Anyone who's ever said "it's in the spec somewhere"
What it saves

The twenty minutes spent hunting a clause becomes a ten-second question — and the answer comes with the section it came from, so you can trust it enough to act on it.

Worked example — demo data

"What's the compaction spec on the subdivision?"

Asked in chat, answered from the project's own spec book: the required density, the lift thickness, and the section reference — pulled from the documents Tamarack loaded, not from the model's imagination. The PM reads the cited clause without leaving the conversation.

The fleet-list importer: drop a spreadsheet, PDF, photo, or Word doc and the extracted trucks and trailers come back for review — nothing saves until a person confirms.
/06   TRUST & CONTROL

Agents propose. People confirm.

The suite is built human-in-the-loop from the ground up: role-based authority, confirm-by-default writes, and an audit trail on everything.

AI in operations only works if you can trust it on a bad day. The suite’s answer is structural: agents never act alone on anything irreversible, authority follows roles, and the audit trail is a first-class surface — not a log file someone has to go digging for.

What it does
  • Two-tier roles: what a driver can do, a dispatcher can do, and an admin can do are different — by design, not by convention
  • Confirm-by-default: anything that changes the real world arrives as a proposal a person approves
  • Every action lands in the audit trail — who asked, who confirmed, what changed, when
  • Per-client instances keep every company's data, users, and history fully separate
Who uses it
  • Owners & managers who answer for the operation
  • Admins
  • Anyone who's been burned by "the system did it"
What it saves

You get the speed of automation without handing it the keys. When something needs explaining — to a client, an insurer, or yourself — the trail is already written.

Worked example — demo data

The override, on the record

The dispatcher pushes a move through even though Wain flagged the timed drop as tight — their call, and the audit viewer shows exactly that: the agent's flag, the human's confirmation, the timestamp. Three weeks later, when someone asks why the drop ran late, the answer takes thirty seconds and settles the question.

The append-only audit log: account provisioning, sign-ins, and a denied capability call — every event recorded at the store, nothing editable after the fact.

All worked examples and screenshots on this page use synthetic data from Tamarack Ridge Contracting Ltd. — a fictional demo company. No client data appears on this site, ever.

Start here

See it running.

Start with a call — one conversation, no prepared sales deck. We’ll show you the agents working a real dispatch day, talk through what your operation looks like, and tell you honestly whether this fits it.

Book a demo → (204) 960-2934
✉ cwright@wricon.ca ◍ Grande Pointe, MB ● Curtis Wright · Founder