Construction

Field and office on the same page

Vic coordinates crews, equipment and subs across your project software and phones, so superintendents run the job, not the paperwork.

The old way

The site runs on texts the office never sees

Crew changes, equipment faults, sub no-shows, deliveries, RFIs, change orders. It all lands on the superintendent, usually by text.

The new way

Pick a use case.

Watch Vic run the work, start to finish.

Crews

Crews placed. Changes caught.

Vic builds tomorrow's crew plan, confirms it by text and reshuffles when someone calls out, with the super approving.

  • Drafts daily crew assignments
  • Confirms by text and catches call-outs early
  • Proposes swaps and flags shortfalls
Vic Construction
Working
VicTomorrow: Crew A to Riverside for the pour, Crew B to Oak St. Confirmations sent 17:00.
VicTwo from Crew B called out. Proposed moving J. Ortiz and M. Lee from Riverside after the pour.
crew-plan_0113.pdfPDF · 2 call-outs · swap proposed
Plan draftedAwaiting your OK
Equipment

Iron tracked. Downtime caught.

Vic watches telematics for faults and hours, schedules PMs around the job and lines up rentals when a machine goes down.

  • Reads fault codes and hours from telematics
  • Schedules PMs around the pour schedule
  • Sources rental backups
Vic Construction
Working
VicExcavator 3 threw a hydraulic code at 08:12, on the trench for Thursday's pour.
VicMechanic booked for 10:00. Same-day rental quoted from United if it isn't fixed by noon.
equipment_EX3_fault.pdfPDF · mechanic booked · rental quoted
Mechanic dispatchedBackup ready
Subs & suppliers

Subs confirmed. Deliveries tracked.

Vic confirms every sub and delivery for the week, sends scope and access reminders and chases paperwork.

  • Confirms weekly sub schedules and delivery windows
  • Sends scope, access and safety reminders
  • Chases COIs, lien waivers and delivery tickets
Vic Construction
Working
VicElectrical sub confirmed Thursday rough-in, crew of 4. Their COI expired Monday.
VicAsked for the updated certificate and held the confirmation until it lands.
sub-schedule_wk03.pdfPDF · 6 subs · 1 COI pending
5 confirmed1 COI to clear
Safety

Toolbox talks logged. Certs current.

Vic collects daily safety checks by text, tracks certifications and inspections, and files it all to the project.

  • Collects daily safety checks by text and photo
  • Tracks certifications and expiries
  • Schedules inspections and files results
Vic Construction
Working
VicToolbox talk logged for Riverside, 11 of 12 signatures. J. Ortiz arrived at 07:10.
VicSent him the sign-off, filed the talk, flagged two OSHA 10 cards expiring this month.
safety-log_Riverside_D42.pdfPDF · 12 signatures · 2 certs expiring
Talk filed2 certs to renew
Change orders

Questions answered. Changes priced.

Vic drafts RFIs from field questions, chases responses and turns owner requests into priced change orders.

  • Drafts RFIs from field questions with photos
  • Chases architects and engineers
  • Drafts change orders with cost and schedule impact
Vic Construction
Working
VicRFI #118 on the stair landing has been open 9 days. Followed up with the architect.
VicOwner wants a second floor drain in the mechanical room. CO #14 drafted with pricing and a 2-day impact.
change-order_CO-14.pdfPDF · priced · schedule impact shown
RFI chasedCO drafted
The result

One live view across every crew, machine and sub

Vic watches crews, equipment, deliveries and subs across your sites, flags what is slipping, and works the routine ones to done.

Questions

What construction leaders ask first

Yes. Vic connects to your project management software, telematics, telephony and email through existing integrations and works inside them: reading schedules, logs, hours and fault codes, writing daily logs, schedule changes and RFIs, and logging every action back where your team expects to find it. There's no new portal to adopt and no data migration.

Rules and macros fire an alert and then wait for a person to act. Vic completes the task: it logs the change, confirms the sub, books the mechanic, drafts the RFI, and only escalates the calls that need judgment, with the full context attached. It's a teammate that does the work, not another notification in the queue.

You define the guardrails: what Vic handles on its own, what it must escalate, and who it routes to. Anything past those limits, like a change order above a threshold or a schedule move, goes to the right person on your team with the history and a recommendation. Once you decide, Vic carries out the action and updates the record.

Most teams connect their systems and start shadowing within the first couple of weeks, then expand coverage as trust builds. You stay in approval mode for as long as you want. Vic takes more of the routine queue only as you sign off on the patterns.

Put Vic on the jobsite.

Bring a week of field texts. See what Vic would have logged and chased.

Your systems stay put. Your people sign off. Running in days.