Triton Construction Builds a Standard on Safety Intelligence with BiltOn

Triton Construction Builds Safety Culture on BiltOn

Triton Construction is a New York City general contractor doing roughly $400 million in annual revenue. Over the past decade, the company has grown from managing ten- and twenty-story buildings to completing seventy-story build-ups, and in the last five years, Triton went digital on safety documentation, ahead of most contractors in the tri-state area. Despite the shift, they still ran into the problem that defeats most digital rollouts: lack of field adoption.

Triton moved to BiltOn on a full enterprise deal earlier this year and is already active on four projects, with more onboarding than they ever experienced from their subs. George Skelos, who ran safety at Triton for almost ten years, drove the switch to real safety intelligence through digitized, automated workflows.

The Challenge: Early to Digital, and Still Fighting the Field

Triton was not a holdout of a bygone era, they were first movers. The company started digitalizing safety documentation about five years ago with another platform, piloted it on a single project, and grew it to three, then five, then ten. Most contractors in the market were still on pen and paper. Triton had already proven to itself that the efficiencies were real.

The problem showed up at scale. The previous platform was browser based rather than a true app, and it carried an initial training burden that never really ended. On one project with a handful of users, a company can absorb that. Across five to ten projects it compounds into a permanent tax on the safety team.

Three specific failures pushed Triton to look elsewhere:

• Orientations ran long. A process that should take five or ten minutes was taking an hour to an hour and a half, which turned into phone calls from superintendents asking why the technology had made their day harder.

• Claims documents went missing anyway. Triton's paper process scanned records into a cloud sharing site, but a full audit found that a lot of documents had never actually been scanned. On claims that run for years, that gap surfaces at the worst possible moment.

• Observation data died on arrival. Safety teams logged unsafe observations on a paper template, reached out to the responsible contractor, and filed the sheet in a binder. The work got done once and then stopped generating value.

Worth sitting with the last one. The observations were being captured correctly by a team doing its job well. The system around them simply had no way to use what they collected.

The Solution: A Platform Nobody Had to Be Talked Into

Triton replaced its previous platform with BiltOn on a full enterprise deal. The deciding factor was not a feature comparison. It was whether a worker or a superintendent could open the product and know what to do next without being taught.

That distinction matters more in construction than in most industries. Crews arrive with different first languages and different levels of formal education, and they rotate between projects. Every minute of explanation is multiplied by the number of people on site, and the person absorbing that cost is usually the safety professional who should be walking the job instead.

George's benchmark for that quality was Apple, where the next click is wherever you already expected it to be. Applied to a jobsite, it means the initial training phase ends and does not come back. Once Triton's teams were through it, the daily hand holding stopped, and the calls from the field stopped with it.

The Results: Retrieval in Seconds, and Observations That Stay Alive

Triton has been on BiltOn for eight months.

Claims documentation moved from a search to a lookup. Before BiltOn, answering an attorney's request on a two or three year old claim meant reaching a project manager, who reached a superintendent, who reached an assistant superintendent, to hunt for paperwork that might be in a warehouse or locked in a job trailer. On BiltOn, the same request is answered directly from the app or the website in seconds, by the person the attorney called.

Observations became a dataset instead of a record. With every observation in one place, Triton can run trending analysis and see the issues repeating at a single job site, then bring the responsible parties in to address the cause rather than the instance. That is the difference between logging a hazard and preventing the next one.

Access control made headcount provable. Verified entry and exit gives Triton control over who is on the job, and digitalized pre shifts turn subcontractor headcount from a matter of argument into a matter of record. Claims administration that used to take George and his administrator a half hour to an hour now takes minutes, in his estimate, which frees both of them for work that needs judgment.

The Culture Shift: Why Accountability Landed Instead of Being Resented

New York is the hard case for safety accountability. State labor law and New York City regulation place effectively one hundred percent of the liability on the contractor, and every contractor working in the five boroughs feels that in the bottom line. A platform that surfaces every open item could easily read to a field team as surveillance.

At Triton it read as shared interest, for a reason worth naming. George connected claims spending directly to what the people on site care about: a company bleeding cash on claims is a company that does not give the raises it wants to give and does not grow the way it wants to grow. Accountability stopped being a compliance idea and became a paycheck idea.

The operating rule that came out of it is simple enough to repeat on a jobsite. If something happens on a Monday, it does not happen again on a Tuesday. Everyone closes out their items now, everyone has the same full view of what is actually happening on the project, and everyone is working toward the same result.

None of that is a software outcome on its own. George is direct about the sequence: technology follows culture, and the culture has to be established by upper management first. Without it, the checklists and the AI and the dashboards do not get used effectively by anyone.

What Comes Next: Reading the Data, Not Just Collecting It

Triton's next gain is not another capture workflow. George frames the ceiling on any platform honestly, and it is a useful thing for a vendor to hear: the platform is only as good as the data the contractor puts into it. Input discipline is the contractor's job, and adoption is what makes input discipline possible.

After that comes interpretation. The value is in analyzing what has been collected to drive better supervision and better behavior, and in using prediction to get ahead of incidents rather than document them. For a company running several projects at once, that includes learning across projects that would otherwise never share anything.

Projects normally run as islands. Without a layer sitting above them, the only way a problem at one site informs another is a phone call between project managers who are both busy, which is not something to build a safety program on. With a portfolio view, whatever is happening at project A becomes a warning for project B while there is still time to act.

Key Learnings: What Triton's Switch Says About Safety Technology

1. Usability is an adoption strategy, not a preference. A platform that needs constant explanation works on one project and fails across ten. Triton switched because the training burden never ended, not because features were missing.

2. Digitizing a document is not the same as using it. Paper observations filed in a binder and scans sitting in cloud storage both stop producing value the moment they are filed. Central, searchable, structured data is what makes trending analysis possible.

3. Retrieval speed is a claims defense. A claim that runs two or three years will outlive the memory of everyone involved. Being able to produce verified records directly, without a chain of phone calls, changes what a contractor can defend.

4. Culture comes first, and it comes from the top. Triton's teams adopted BiltOn because leadership had already established that safety discipline is a collective interest. Technology accelerated a culture that already existed.

5. The contractor owns the input. Data quality is a shared responsibility, and a contractor that treats it that way gets more out of the platform than one that expects the software to compensate.

"Our safety teams did a great job. When they would see an unsafe observation, we would have a template that they would write down on a piece of paper and log it and reach out to the contractor responsible. But after that, the data dies, because now it's in a binder, and now no one's really using it past that point." George Skelos, Safety Director, Triton Construction