Honestly, the thing I like best about WORKetc is how it wraps CRM, project tracking, document control, and billing all in one place, so I don’t have to bounce between three separate tools every single day. Before I started using it, we ran our Cambridge construction projects with a patchwork setup: QuickBooks for costs, a separate CRM spreadsheet for subcontractors, and a shared Google Drive folder stuffed with change orders and draw packages. That mess blew up on us last spring with a drywall vendor out of Worcester. We had a verbal change order for extra soffit framing that only lived in an email thread, no formal log anywhere. Our foreman signed off on the extra work on site, but accounting never got the update, so the vendor’s invoice came in 18% over our original budget line. We spent three whole days digging through email chains, site photos, and text messages just to validate the charge, and we nearly delayed the whole progress draw because the paperwork trail was scattered. Once we moved that workflow into WORKetc, I can attach every single email, site photo, subcontractor quote, and change order form directly to the project record the second it lands on my desk. I tag the change order status, lock in the draw payment terms, and assign a notification to accounting the minute I log it. That Worcester vendor issue is the exact headache this tool stops from repeating.
I also really appreciate how flexible the custom fields are, which is huge for construction document control work. I spend a ton of time importing CSV vendor and project datasets, and I need fields tailored to our phases: pre-construction, rough-in, enclosure, finishes, closeout. A few months back, we brought on a new plumbing subcontractor from Lowell, and their team submitted their submittal logs using their own internal spreadsheet format. Our old system couldn’t map those custom columns cleanly, so I had to manually retype every submittal ID, revision date, and approval status for over 70 line items. That took me almost an entire workday, and I still fat-fingered three revision numbers, which almost caused us to approve an outdated material submittal for bathroom fixtures. With WORKetc, I built out custom fields specifically for submittal revision, material spec reference, andreview deadline. When that same Lowell plumbing team sent their next CSV batch, I mapped their columns straight to my custom fields during import. The upload took ten minutes, and the data populated correctly on the first pass. I don’t waste hours on manual data entry anymore, and I cut down those silly transcription errors that can snowball into costly material delays on site.
Another big win for me is how smoothly it handles internal training and shared visibility for our site office crew. A lot of our project superintendents aren’t naturally comfortable with SaaS tools, and they used to skip updating logs because they found the old systems clunky. Last summer, we had a framing subcontractor from Salem who submitted a pay application marked as “pending review,” but our superintendent forgot to update the status in our old sheet. Accounting assumed the payment was still waiting for site sign-off and held the draw, which made the Salem crew pause work for two days waiting for their check. It created tension with a vendor we rely on for a lot of our residential builds. Now inside WORKetc, every pay application and draw package lives on the shared project dashboard. I set up simple status dropdowns, and I ran quick 30-minute on-site training sessions for the superintendents to teach them how to flip a status and drop a quick note when they sign off. The superintendent can update it from their phone while they’re walking the site, and accounting gets an instant alert. We haven’t had a hold-up like that with the Salem framing team since.
It’s not perfect, but for a small construction firm like ours with 11–50 staff, it solves the exact gaps we keep running into. I don’t need a dozen disconnected platforms anymore. All our subcontractor coordination, job cost tracking, change order logs, and client communications sit tied together on one record. It keeps the whole team aligned, cuts down those messy, avoidable vendor disputes, and saves me so much time that I can focus on actual project coordination instead of chasing loose paperwork across a dozen different apps. Review collected by and hosted on G2.com.
To be straight up, the biggest thing I dislike about WORKetc is the clunky CSV import handling, especially when I’m uploading our subcontractor and change order datasets. I rely on bulk imports every week to push over vendor lists, draw schedules and submittal logs, and it’s crashed on me more than once when the file has German umlauts or special characters, even though we only work with US-based subs now. Last month we onboarded a new HVAC subcontractor out of Brockton, and they sent over their standard pay schedule CSV with ampersands and special notes in the description column. I mapped all the columns to my custom fields like I always do, hit import, and half the rows just failed silently. There was no clear error message telling me which lines were bad, I just saw partial data pop into the project record. I spent close to two hours stripping out special characters one by one, reuploading in chunks, and cross-checking line by line to make sure I didn’t miss any of their payment milestone dates. That whole mess pushed back my change order log update, and I almost missed sending the client their weekly cost summary before EOD. It’s frustrating because I do this exact same routine in other construction SaaS tools and they flag bad rows upfront so you can fix just the broken lines instead of rebuilding the whole file.
I also run into consistent pain points with permission granularity, which is a real headache for our small site team. We have superintendents, office admins and subcontractors that need limited access, but the permission tiers in WORKetc feel too broad. A few weeks back, our electrical sub from Quincy needed to view only their own pay applications and submittals for the current project. I tried locking their role down so they couldn’t see other vendor cost data or confidential client budget notes. No matter how I toggled the settings, they still got visibility into the full project job cost breakdown, including markup numbers we absolutely can’t share with trade partners. I had to scramble to export just their relevant documents and send them over via email instead, which defeats the whole point of housing everything inside the system. I was worried that if they scrolled too far, they’d see pricing for other trades and kick off a messy negotiation. We ended up reverting to email sharing for that sub, which brought back the scattered document trail we were trying to get rid of in the first place. Review collected by and hosted on G2.com.