Real Talk: The Questions You're Actually Asking

The best questions come from many places. They come at the booth, after the third coffee, when people stop being polite and start talking about what's actually slowing them down, from calls with prospects and clients, and even social media posts.

We compared those conversations and summarized seven questions that kept surfacing, about documenting the work, getting paid, and finding tools crews will actually use.

Here are our straightest answers. Some involve software. A few don't.

1. "After the Newark shutdown, what should my crew document on every dig?"

On September 21, the primary communications circuit at the air traffic control facility serving Newark failed. The backup should have taken over, but a construction crew in New Jersey had already cut the backup fiber line. Hundreds of flights were cancelled or delayed.

In its preliminary account, the transit agency running the project said the crew was working about 10 feet from the utility markings, and that it was still determining who had placed them.

Most strikes never make the news, but nearly every crew has lived a version of that day. We saw one up close on our road trip this summer.

Documentation alone won't prevent a strike. It helps establish what happened if one occurs, including who marked the line and where. At a minimum, every dig should capture the locate ticket number and its expiration, timestamped photos of the marks before anyone breaks ground, and who was on site.

The catch: if capturing that takes more than a minute, it won't happen on a busy day.

2. "What should 'accepted' actually mean?"

"It lit up" isn't acceptance. Neither is "the crew said it's done."

Acceptance should mean the work was checked against the design, tested where testing applies, documented with photos and records that stay with the as-builts, and signed off by a named person.

Write that definition down. Share it with every sub before the job starts, and make it the same checklist the field uses. When everyone works from one definition, acceptance stops being an argument.

3. "The job is done. Why haven't we been paid?"

This was the question we heard most. Even good work can sit unpaid when the closeout package is incomplete: one missing photo, or an as-built that doesn't match the staking sheet.

The work finishes on Tuesday. The paperwork finishes whenever someone chases it, and every gap in between becomes a phone call or a resubmission.

The fix is boring, and it works. Decide what the closeout package needs before the job starts, then collect it while the crew is still on site. When the field gathers exactly what billing needs, the package is ready for approval by the time the truck pulls away.

4. "How is a small sub supposed to carry 45 to 60 days of costs?"

That's how one splicing contractor put it. Payroll is weekly. Hotels, fuel and truck payments are due now. And the more work you win, the more cash you have to front.

Clean paperwork won't change that math. Even if every invoice is approved on the first pass, you're still carrying six to eight weeks of costs. That's a terms problem, and it's worth raising directly with primes, along with options like progress billing or shorter cycles for smaller subs.

What you can control is keeping 45 to 60 days from turning into 90. A rejected invoice, a quantity dispute or an approval stuck in someone's inbox can each push payment further out. Production data the prime can verify without calling you means fewer of those.

5. "Why won't my crews use the app we paid for?"

Too often, field software works better in the office than on site, where signal is spotty and nobody wants to hit a small button with gloves on.

On a site visit in Denver this summer, we watched a crew member tilt an iPad against the sun just to read the screen. It was a small moment, and it stuck with us.

Crews adopt tools that make their day shorter. If entering the data is slower than a clipboard, the clipboard wins. So when you evaluate anything, including us, hand it to your least patient foreman and watch.

6. "What actually causes delays: missing material, lack of visibility, or poor communication?"

Usually the last two, dressed up as the first.

A missing reel often isn't missing. It's in a yard across the county, allocated to a different project, and nobody told the crew. The ISP sees the schedule, the supplier sees inventory, and the contractor sees the field. Each view is accurate. None of them match.

You don't need everyone on one system to fix that. You need a shared picture that answers a few things for every job: what's done, what material is available and where, what's blocking the next step, and who needs to act. When those answers live in one place, fewer crews show up to a site they can't work.

7. "How do we use production data without it turning into finger-pointing?"

This one came from an operations leader, and it might be the most important question here.

Production data gets its bad reputation from how it's used. If the numbers only come up when a target is missed, crews learn that honest reporting gets them in trouble, and they stop.

Use the data to find problems, not people. A slow stretch might mean rock, a permit hold or a late material drop. Ask what the number is telling you before you ask who's responsible. Crews who trust the data report it accurately, and accurate data is the only kind worth collecting.

Your turn

Real Talk is going to be a recurring edition. If you've got a question, the kind you'd ask at the booth but maybe not on a sales call, hit reply and send it. We'll answer the best ones next time, and we'll keep you anonymous unless you tell us otherwise.

If you'd rather talk it through live, bring your hardest question to a quick demo.

Book a 20-minute demo

See you in the field,
The OciusX team