Bridge Brothers

Bridge Brothers manufactures steel bridges in Greenville, South Carolina. A job starts when sales closes it and enters the details in a Google Form. From there it moves through engineering (a team of ten, each with a defined set of steps, with submittals back and forth until the customer approves), then detailing, where shop drawings and material requisitions are produced, then production, which covers cutting, fabrication and welding, and a finishing path that depends on the bridge. A galvanized bridge, a sandblasted and painted bridge, and a bridge that goes straight to decking each take a different route through the same stations, and jobs for a state department of transportation carry their own inspection requirements before processing can start.

All of that was tracked in five or more Google Sheets, one per department, each holding dates for when kickoff happened, when analysis and design would be done, when drawings were due, when internal review was scheduled. A red cell meant a promised date had passed. Handoffs were emails. Engineering changed a status to released, detailing got a notification, the shop lead got a notification, and each person re-keyed what the last person had entered. Data was hours or days behind, and when a job slipped it was hard to say where or why. The team had opened a ClickUp workspace on their own and drawn the whole process on a whiteboard inside it, but the projects themselves were not in ClickUp yet, and the first thing they had tried (a form that named its submissions correctly) had not worked.

This was a ClickUp implementation. We spent years implementing work management platforms, ClickUp among them, and this engagement is a compact example of that work.

Discovery ran as workshops with engineering, production, and QC to document the real flow, the fields, the finish variants, and the special-provisions list that comes off the sales form. From that we designed the ClickUp hierarchy (spaces, folders, and lists organized by department, scope, and type), a status model, custom fields for job number, finish, revision, due dates, and critical-path flags, and a permission matrix separating the internal team from subcontractors.

The intake form captures a new job with conditional sections, assigns a true job number in the company's format, and timestamps the request. Automations move the job through engineering, detailing, fabrication, QC, and shipping, and set the downstream path based on finish. A galvanized bridge picks up its galvanizing hold and notifies shipping, a painted bridge routes through blasting and paint. Standard checklists for weld inspections, finishing prep, and DOT documentation sit on the tasks where they belong, and photos or files must be attached before a status can move to the next stage, so the quality trail is built as the work happens rather than assembled afterward.

Dashboards show engineering WIP as a Kanban and burn-down, a production Gantt with critical path, a QC punch-list aging report, and an executive view of lead time and on-time percentage. The plan also covered cleaning and importing legacy rows from the engineering schedule, production resources, and project overview sheets so the team would not run two systems in parallel, and live recorded training with a coach-the-champion handoff so the team could make simple changes themselves.

Job status stopped living in five sheets and started living on the job. Each department sees the jobs at its station and nothing else, and a handoff is a status change rather than an email plus a re-key. Because the finish drives the route, a bridge does not get to the shop floor without its galvanizing or paint steps already sequenced. Quality evidence is attached to the task before it can move, which is what a DOT or customer review asks for. Leadership reads WIP, bottlenecks, and on-time delivery from a dashboard instead of stitching a report together in a spreadsheet. The engagement ran in 2025.

Given the same problem now, we would build Bridge Brothers a shop system of their own that holds jobs, stations, finish routing, checklists, machine capacity, and customer submittals in one database under their own accounts, with the sales form and accounting connected directly and no per-seat licensing for the shop floor. The ClickUp build gave them the structured workflow they asked for. A custom, client-owned build goes further on the things a general-purpose task tool cannot do well, such as capacity per machine and per station, which the team already wanted, and reporting that spans the whole life of a bridge without workarounds.