Skip to main content

2026, July 17th – What’s New July Updates

Skip to main content
How can we help you today?

Our Knowledge Base contains the answers to more than 500 previously asked questions.

Create a Ticket Schedule a Training

July 17th, 2026
Hosted by: Taha, Trainer at Contractor Foreman
Topic: What’s New in Contractor Foreman — Quarterly Updates and Open Q&A

Webinar Description

In this advanced training session, Taha takes a deliberately different approach from the rest of the series: instead of walking through a single workflow, he tours the most notable features released as part of Contractor Foreman’s latest quarterly update, and opens the floor for questions on anything at all. The result is a looser, more conversational session driven as much by attendee questions as by the agenda.

Taha opens with a point he returns to throughout: these updates come directly from customer suggestions. Feedback submitted through the in-app suggestion button, raised during one-on-one training sessions, or passed along through CSMs and trainers is collected and acted on each quarter. Several of the features demonstrated in this session were suggestions Taha submitted himself. His message to attendees is simple — the more vocal you are, the more the roadmap reflects what you actually need.

The tour begins with the redesigned Roles settings. The previous interface presented permissions as a single list of roughly two hundred line items; the new version groups them by category (project management, documents, people) and makes them far easier to navigate. Taha highlights two additions in particular: the ability to restrict a role to the mobile app, the web browser, or both — useful for keeping field staff focused on the tools they actually need — and a view of exactly which users are assigned to each role, which becomes valuable as headcount grows. He also clarifies a distinction that regularly causes confusion: full access, all data lets a user see and edit every record in the system, while own data limits them to records they created themselves.

Next is the Cost Codes interface, also rebuilt. Adding, editing, and archiving codes is now more manageable, and the library of pre-built industry standards has been expanded — NAHB and CSI lists can be browsed and selectively imported rather than built from scratch. Two new downloadable templates were added: a CSI 2020 template and a blank template. Taha also pauses to clarify the parent/child structure, since it trips people up constantly: a parent code is a group name, not a real cost code. The child codes beneath it are the actual cost codes. Concrete is the parent; reinforcing bars and cast-in-place concrete are the codes you assign transactions to.

On the AI side, the session covers two features. The first is AI-generated safety meeting topics, which lets a foreman produce a relevant, job-specific safety topic in seconds rather than choosing from a pre-built list that may not fit the work being done. Taha demonstrates it with an intentionally unusual example — welding at an offsite oil rig — to show how specific the output can get. The second is AI safety analysis on daily log photos, which reviews uploaded job site photos and flags visible hazards, missing PPE, and improper equipment storage. Taha draws on his own experience reviewing hundreds of site photos weekly to make the case for it, framing the feature less as a time-saver and more as a way to protect the most important asset a construction company has: its people. Notably, Taha believed this feature was still pending release — César confirmed live that it had gone live the day before.

The session closes with several quality-of-life improvements that are easy to miss but change day-to-day workflow. Language settings can now be assigned to a user at the moment access is granted, so a Spanish- or Russian-speaking crew member sees the interface in their language on first login rather than having to navigate an unfamiliar UI to change it. Terms and conditions on estimates can now be dictated by voice memo and cleaned up automatically, or generated from a written prompt. The estimate preview now opens in a resizable, draggable pop-up window — a small change that matters considerably on a laptop screen. And a Print PDF button has been added across all modules, so a PDF of whatever record you are viewing is always one click away.

Taha closes the AI segment with a caution consistent with previous sessions in the series: these tools exist to speed up your workflow, not to replace your judgment. Whatever the AI produces — a safety topic, a terms and conditions clause, a hazard analysis — still needs to be read and verified before it goes out.

César Macedo co-hosted the Q&A throughout, fielding questions alongside Taha and taking several items offline for follow-up. The discussion covered choosing between the Safety Meetings and Forms & Checklists modules for daily toolbox meetings, supported file upload formats, generating a scope of work document for field crews without exposing pricing, estimate template defaults, handling zero-value line items on invoices, markup inheritance from the cost item database, and which subscription plans include Service Tickets. Several attendee suggestions raised during the session were logged for the product team.

Attendees were offered a complimentary one-on-one training session to go deeper on any of the new features or discuss their specific workflow.

This session is ideal for:

  • Existing Contractor Foreman users who want a fast orientation to what changed in the latest quarterly release
  • Administrators managing user permissions who have found the previous Roles interface difficult to navigate
  • Teams responsible for job site safety documentation who want to see what the new AI tools can and cannot do
  • Anyone who has submitted a feature suggestion and wants to understand how that feedback makes its way into the product
Was this article helpful?
0 out of 5 stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
5
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.