HCSS Quarterly Product Release Webinar - Q1

All right, it looks like we are at 10 A.M. Central, so we'll go ahead and get started. My name is Reed Renfrow. Thank you for joining us today. Some of you don't know me, I'm the head of product marketing here at HCSS, and we're trying something out new this quarter. We're bringing all of our product releases for winter 2026 into one webinar. So we have one hour to cover everything from HeavyBid, HeavyJob, Fleet, Platform. So you're gonna get a lot of updates. We'll go through a number of different updates today. Be a little bit more condensed than maybe if you've been on our HeavyJob webinar in the past, but we think this will give everyone a good view of everything that we are releasing in just about one week. So with that, I'm going to jump in first to some updates we have to our product branding that you are going to see in the product next week. So one thing we tried to do is try to bring all of our products under three primary product brands, HeavyBid, HeavyJob and HCSS Fleet. And what that will really mean for you, the biggest changes are coming on the HeavyJob side. And so you're going to see some UI updates to safety, the plans to forms or bring all those products under the HeavyJob umbrella. Over the next month so, you're likely going to see some some UI changes. None of your logins change, none of your user information changes. So it's really more of a UI change and will change some of our marketing information as well. One thing to note, desktop products, we're not changing any of the branding, so HCSS Dispatcher is remaining the same. On the HeavyBid side, minimal changes, but you will see we have our HeavyBid beta is now out of beta and is our primary HeavyBid product. And then our HeavyBid product that you all know and love is now going to be referred to as HeavyBid desktop so that we differentiate it and it's distinctive from our HeavyBid web product and HeavyBid preconstruction. For those who using that product will remain the same. On the fleet side, we're we're we're adopting the HCSS fleet brands. You'll see HCSS fleet telematics, and we're renaming Maintenance Pro to HCSS Fleet Maintenance. But again, there does desktop products, Equipment360, Fueler Plus and then ELogs are remaining changed. So again, no big changes for you. The products will still work exactly the same way, but you might notice some UI changes, some color changes. You'll see products referred differently on our website as well. So these changes will probably be ongoing over the next few months, but they'll start rolling out with our release next Thursday. And with that, the last thing I want to mention before I hand it off to Andrew is we do have UGM coming up. It is early this year. There is still plenty of time to register though, though you need to get on that quickly. If you, we would love to see you join all of us here. All of us on this call will be down in Houston in a couple of weeks. So you can scan that QR code. You go search for HCSS UGM. You can find it on our website. Lots of options. It's not too late. Go ahead and register. And I know a lot of you on this call are already going. So we look forward to seeing you there. And with that, I'm going to turn it over to I said it was Andrew. It's actually me, Hayden. I got my order mixed up. Hayden, on to you. Thank you, Reed. Let's go ahead and talk about what's new and coming with HCSS Fleet. We will start with Equipment360. So the big thing that we're launching this month is going to be our pay adjustment story, and that's going to allow you to account for pay adjustments on your timecards. So things like per diem and rig pay or travel expenses, things that you kind of had to work around in the past. So we're really excited to solve build this product gap for you guys. And we have this configured in a way that you can configure as needed. So you can set up daily rates, hourly rates, quantity based rates, flat dollar value rates. And you can also actually override each of these pay adjustment rates at the employee level as needed. So should be quite customizable. The configuration of this is actually already out with Equipment360 2025.5. So if you want to get your manager system updated to start playing with these setups, that is available in your employee setups. There's a new section for pay adjustments. The E360 mobile site entry on the time card and the export to accounting side will be releasing by the end of the month. So again, you can see what we have in the screenshot right now, even in the time card screen. So if you want to get in, start playing with it, let us know any feedback, please do. We also did some back end work for you guys, and we got our Equipment360 personal alerting system integrated with the HCSS notifications system and service. So what does that mean? You probably know if you're using personal alerts in Equipment360 that that's going from an email setup to a text or to an SMS number. And carriers are starting to deprecate those messages more and more. So we've gotten our personal alerting system moved over to a true SMS service. A couple benefits of that. You will no longer have to set up carrier information for every employee, big one, And you do not have to worry about any delays or concerns about those carriers blocking messages since we're using a true SMS service. This is also integrated with the maintenance request web app. So whether you're setting up those personal alerts in E360 or you're using the maintenance request app, this will be live if you are updated to the latest version. One other big technical story we've been working on is pushing Equipment360 data to HCSS Insights. That mechanism, all the back end work that we did to actually send that data up for Insights consumption is also out in Equipment360 2025.5. Viewing the actual data in HCSS Insights will be available by end of month, and I believe Michaela will elaborate on that a little bit. But let's hop over to. Here we go. Fleet maintenance and the web. A couple updates for you guys on this end as well. So a lot of you might not be aware that this even exists. We do have a web based maintenance system that's built into our Fleet platform, or as you know today in the telematics website. So this allow you to stay on top of work orders, services, repairs, maintenance requests from field, documentation, all of your notes within work orders and so on. We did give this a little bit of a UI refresh. It looks a lot more modern using the latest HCSS UI components. And we did also implement auto saves here, which is really exciting. So hope to get more of you guys in here playing around with this. We had also a couple little quality of life improvements in this web based system. And one of those is when we trigger a PM alert, we get this new modal that you see at the top to where you can trigger multiple PMs in one step, get them all added to a particular work order. Along with any of our alert types at the bottom here, we did add another step to allow you to add those alerts to existing work orders. So makes it easier to manage, add things to existing work orders, create work orders in bulk, etc. We also released the work order functionality in our HCSS Fleet mobile app today, and I believe in the App Store, it's still called you probably know of this app as HCSS Telematics Connect. But as part of the rebrand, this will be HCSS Fleet mobile app. But this is available and live now. So if you're using any of these web based work orders, we have this work order functionality in the mobile app. So you can create and edit work orders, attach your PM services, requests, track repair workers on the fly, assign mechanics, do all your notes and documentation. A quick update on the HCSS Telematics side. We did add a new OEM integration for Case SiteWatch, and that is live and ready to go. So be on the lookout if you would like to start pulling SiteWatch information in. And that is all I have, so I believe I'm handing it off to Amanda. Thank you, guys. Hello. My name is Amanda Ayles, and I am the group product manager for estimating at HCSS. I am gonna take a moment to remind y'all as well that we do have the q and a feature running in the Zoom meeting, so please check that out at the bottom bar. If you have any questions during our presentation, please feel free to bring them up. So today we're going to be focusing on two products in the HeavyBid line. An update in HeavyBid preconstruction and our latest additions in the new HeavyBid basic software. So starting in pre construction, the new feature we are highlighting today is tied to estimate history in the HeavyBid desktop system. Estimate history was originally released as a new feature in HeavyBid desktop in 2017. And with estimate history, you can archive and sync estimates from your desktop system to the HCSS platform online. This provides a virtual backup of your estimate with many benefits. One, just having a backup outside of your business system in case anything happens. Two, the ability to increase your we increased your search ability for past estimates in the copy screen, that little first arrow up here on the HeavyBid screen. And then three, you can update your binoculars to utilize your past estimates to review the way you've thought about productivity on activities in the past. So if any of that sounds interesting to you, we'll be dropping a link to the support article for setting up estimate history in the chat. This feature is available for all versions of HeavyBid basic, advanced, and comprehensive and it's free to start using immediately. So now what we're emphasizing today is a new feature in pre construction that allows you to maintain that data. The data that you want your team to see when you search estimate history. So the ability to bulk update what estimates you want included or excluded has been a request from customers currently utilizing this feature, and they they use this to speed up their decision making process during bidding. So this update will be available in our winter release. Now moving into HeavyBid. We'll be focusing on the most recent updates to the new HeavyBid basic online. Our first update is a big picture list of the new features we've added since October 2025. And the primary feature I wanna call out is what we've built out this is that we've built out the standard estimate building workflow, but for a work breakdown structure tree instead of a pay item driven tree. Our goal here is to support the private work or unstructured work you may be getting from smaller public owners. In this estimate building process, you would select scopes of work to build out the activities and crews you'll need on this job. And then once you've built out that scope, you can go into arranging those activities into the pay items you're going to deliver your proposal in. This is a pretty major shift in how HeavyBid has traditionally locked down the estimate building so we want to keep highlighting this to spark conversations. Stay engaged with us via your account executive or the HCSS community forum. Next, we're going to highlight the work we've been doing around proposals because our goal is to bring these features to desktop customers as quickly as possible. So first up is a preview of our proposal template designer. This designer will provide a drag and drop experience for arranging a proposal with general block pieces. You can pull information from the libraries, the project, or the estimate to fill in the template. Again, in the designer, you're going to see generic data that gets filled in with live data when you view the proposal for a specific estimate. Next step, we'll see an example that with this proposal, of that with this proposal view in the One Pave estimate that is also demonstrating our ability to put subtotals into the proposal. And finally, a small preview of the new inclusions and exclusions library. This library creates a space for standardizing your setup that can be utilized on a project by project basis. So you can fine tune the scope of your inclusions and exclusions for each unique bidding opportunity you get. Overall those are the highlights from HeavyBid for the upcoming winter release. If you want to review what we released with the HeavyBid Desktop release at the end of last year, you can go check out our previous HeavyBid webinar where we went over the HeavyBid desktop release for two thousand and 2025.1. And you can find out more information about the release and these features at updates.hcssapps.com. So next up, I'm gonna hand this over to Michaela to take over on platform. Alright. Good morning, everybody. My name is Michaela Halliwell. I'm the senior product manager over our platform. So we're gonna get started this morning talking about all of the things that are winter release designed for our data analyst users, our admin back of house, our developers on the call. Starting with credentials, specifically API clients. This is really the foundation of a lot of what we're gonna be talking about today. Historically, in HCSS platform credentials, managing API clients required a lot of jumping back and forth between different tools. So we have centralized and brought that all in one place. So now what you will see is an API client list that will give you visibility into all of your API clients in one place. And from there, we've made a few things in the UI in the actual interface a little bit easier. For example, now you can copy a client ID using an actual copy button, so there's no more dragging and selecting and copying and missing different characters here and there. You can also view and copy all the scopes in a single action, which is really useful when you're setting up an integration. And then lastly, you can search a client by name, ID or scope. So finding things is even easier. On the creation side of that, we've also made scope selection a lot easier. There's now a select and unselect option. So combined with the organization of that scopes, that helps speed up setup and reduce some mistakes, especially when you're dealing with a client that requires a lot, a large number of permissions. Once that client is created, you can also immediately copy all of those details without having to navigate away or reload anything. And that's intentional so that we have faster handoffs between our admins, developers, and different partners. So from a customer's perspective, there is just less time managing, there's fewer errors when you're configuring everything and then just get your integration set up faster and on your way. Next thing that I wanna talk about is part of our some of the UI changes that you've been seeing over the last few quarters is our unified nav bar and why that matters. So as our product and our platform has grown, navigation naturally evolves at different times, and that can create friction when experiences are different, especially for customers who are navigating between HeavyJob and HeavyBid and Fleet throughout the day. So the goal of our unified nav bar is simple, it's just to make moving around HCSS feel more predictable, feel more effortless. So with that update, we've standardized our nav bar across the entire product suite, which means you're gonna get the same layout, the same options, the same behavior, model, no matter where you are. It's really going to be helpful to when you're hunting for things and just making things feel more cohesive. And so what that release looks like for this winter release is that now that that nav bar is in our h c s credentials on the back end, ultimately, just reducing cognitive load is the goal here. You don't have to think about how you're gonna navigate to what, you can just focus on moving effortlessly throughout the platform. Next, have migrated some of our reports and credentials to React, which might not sound like much, but it's what it means for you as customer is more consistencies consistency. Historically, our credentials and usage reports, things like subscription usage, mobile usage, HeavyJob data, were built on different times and different technologies with different teams, and sometimes with even different assumptions behind them. And so you might see a report in one place that doesn't quite line up with another or one that worked fine on desktop, but felt clunky or slow elsewhere. And so when you're trying to answer a question that friction really matters. Migrating these reports to react, the goal here was just to make things consistent, faster and easier for you to trust. They load faster, the UI is cleaner, it's easier to scan, you see more numbers across the reports, which means you don't have to scroll as much, everything is just right there. It really sets us up for the future. It's not really just about a UI refresh, but it's allowing us to ship things faster so that you have clearer visibility into your data. Next, I wanna talk about our identity and access management, which is specifically the company switching between products. So we have a lot of customers on the call that don't operate just as a single simple company. They have multiple entities, subsidiaries, joint ventures, operating companies, business units, and historically moving between those on the platform often means logging in, logging out, managing multiple sets of credentials, and that that friction is annoying. It adds up fast. So with this release, now users can switch between the companies that they're affiliated with with just a single login. So there's no reauthenticating. There's no switching outside of the app. It's just a smooth transition from one to another. So your workflows are not interrupted. There's no logging in and out, and you just get faster faster access, especially for those who manage multiple companies and multiple roles. Next, we have rebranded some of our permissions page. So historically, when you would go into permissions, you're not able to quickly view what permissions are accessible to the groups on your teams. Now it's just a little bit more visible, a little bit more clean. See what products and what suite and what features that you are able to view, eliminating the the need to just navigate to the group settings. So you can see it all there in one shot. Another thing that we have done, our APIs, we have been working on this, all the teams represented on the call have been working on this for over a year. Our original version of our setups API was built at a time when our primary goal was scale, not necessarily visibility, and so it relied heavily. On operations moving through something called a service bus and it works, but it comes with trade offs and those trade offs could be that data is inconsistent. Across different products, it could be that when you make an API call and setups that you get a failure, but you don't know why those errors aren't available to you. And there's no clear signal if or when something had partially failed or fully failed. So from user's perspective, from an experience perspective, it just shows up as uncertainty. You make a change, wait, and then have to guess whether things actually synced. And that lack of feedback is very painful at a small scale, but on an enterprise level becomes really unmanageable. And so something that we have done is we've changed the contract from fire and hope to confirm and trust. So our setups v two APIs will confirm a successful synchronization across our products before an operation is marked as complete. So that means that you get validation in real time. You get a clear understanding of what errors are firing off and then confidence that what you called actually stuck. And so one of the biggest improvements here that I want to highlight is bulk processing or our bulk endpoints. Instead of updating one record at a time, you can now update ten thousand records at a time across our employees, equipment, or location. And you get visibility into whether or not that has succeeded or failed, or if it has failed, what has failed and what you can do to remediate that and so that's where the intent of this really matters we're very intentionally supporting to API patterns here because. Not everybody operates the same way, so for more modern web based erp systems. The V one endpoints might work a lot better because they're real time they're more accurate they match the goods and give you more stronger guarantee that the system will stay in sync and then, on the other hand. V2 is more intentionally optimized for server based systems and so. These systems often can't change internal codes, they don't support web hooks and they're fine receiving large batches of data, so in those cases sending ten thousand records at a time. Is exactly the right solution, so the takeaway here isn't V1 is better than V2 or V2 is better than V1. It's that we are designing our integrations and our APIs based on the value it brings to you, not purely on just technical purity. Different systems have different constraints, and our job is to meet you where you are. And so that is what the purpose of v one and v two of our setups API is that will be released next week. Next, I wanna pause here. This is a really big one. This is the first time we are introducing AI directly into the HCSS product experience, not just as a demo or a bolt on, but something designed to sit inside your workflow. At the most basic level, yes, this AI Copilot search gives you a faster way to search, but you can also ask natural language questions, find pages, and navigate across the entire product suite without knowing exactly where something lives. That's not the most important part though. The big shift here is how you interact with the platform and how you interact with a question and a problem that you might have. Instead of clicking through menus or memorizing where things are, asking someone else on your team, hey how do I do this again, you can just ask Copilot. How do I import or export a time sheet what steps do I follow to set up a cost code in a new project, how do I approve this report? And Copilot will respond in context. We're also introducing functionality that will summarize things like the daily digest, for instance. This is the beginning of moving information from information overload and having too much information to synthesize to really distilling where the system can help show you what matters instead of just showing you a field. Another important design here choice here is that this isn't locked into one place. You can drag CoPilot around the experience with you. You can keep it open and treat it as your companion to work, not just a modal to open, read, close, and that is also very intentional. We want CoPilot to feel like it's part of your workflow, not a disruption to it. But one thing I want to emphasize here, this is just stage one, this is version one. We are starting with navigation discovery because those deliver an immediate value to you with little risk. But strategically, we are setting a foundation where the future of HCSS platform and AI unlocks functionality that not only helps you summarize, but helps you complete tasks, not just find screens, that knowledge lives within our platform, not as a group memory exercise. And it's a force multiplier that helps you from every role, in the field to folks on the back end, to executives to folks who are onboarding. When you look at Copilot search, don't want you to think of it as an AI search, even though that's what it's starting as. Think of it how work gets done inside of HCSS. Also, please know we're also always open to feedback on this. We wanna know what your experience is like interacting with this co pilot search and please reach out if you have any feedback, questions. Yeah, Alright, let's move on and talk a little bit about you heard a Hayden mentioned that the E360 team has moved data into insights. Historically, E360 data has been in insights if you were a beta user because it relied on a reporting database. And that reporting database is limited on the freshness of the data, the flexibility and the long term scalability so we actually built a new data model our company data model which ninety percent of our users are on the company data model as opposed to the reporting database. But the problem is that E360 data was not in that company data model so with this release, we are introducing that, and so this is a very foundational change this new model does not rely on the legacy reporting database, which allows us to deliver better reports. Faster. So to start, we have shipped three templated reports built on that new model. Those are designed to answer very common operational questions. One thing to call out here, you must be on version 2025 of E360 or later to use those reports. This from from a customer's perspective, this means you're going to get more trustworthy numbers better performance when you're working with large data sets, and a reporting foundation that we can actually extend over time. So it's not about adding more charts. It's about moving E360 reporting into our modern data backbone so we can continue to expand upon it. This is really a start of a whole new approach for customers on E360 when looking at your data. All right, last few things I want to talk about here because this is fundamental to how our integrations are discovered and adopted. Historically, finding integrations, what does HCSS connect to? How can I bring two systems that I work on together? Historically, that has been done on our marketplace and will continue to be, but it will look a little bit different. Right now, our marketplace is limited in terms of how many logos we actually integrate with, but we've restructured this experience and it's taken multiple teams a while to evolve and mature our processes and really showcase the decades of connections and relationships that HCSS has within this space, on this Heavy Civil utilities space. We've restructured this around a connection first mindset. So instead of starting with a logo and technical details, can browse by product category, business need, and quickly see what's available and what's supported. It's a a true new complete discovery hub for all of our integrations, and you're able to move from, hey, I'm interested in this or I'm curious to let me just connect right away. So this is really all about confidence, a well organized growing ecosystem that is extensible and it is about something bigger. It's a natural extension of our platform. It's integrations are not just an afterthought. They're just a natural part of how we do business. Alright. I think last thing for me here is the new developer portal. The developer portal, we are switching vendors on the back end is very minor that there will be no disruption to your actual integrations. There will be no disruption to how you're calling APIs. We've just simply rebuilt the interface to make it easier to discover and easier to use. One of the biggest upgrades, though, that I wanna point out that you see a little bit on the right of the screenshot is this ask AI functionality. We previously had had an API co pilot built on our current developer portal and hit or miss on whether you got the correct answer. I would say with a large amount of confidence that this new ask AI, since it is trained on our spec and across multiple programming languages, that if you have an API question, you can ask this Co pilot and you're almost certain to get a correct answer. And if it does not have a correct answer it will point you to the person who can answer your question. So from a day to day perspective for the developers on the call for the executives on the call that work with our api's there is way less time searching for answers, there are fewer mistakes when you're building an integration and a faster time to value and just getting up and running. Just like with our Co pilot, this isn't a one off. This really gives a foundation to continuously improve developer enablement, better guides, better tooling. So if you want to integrate with HCSS, it should feel very obvious how you do that. You're well supported on this new dev portal and well documented from day one. I believe that's all for me. I'm gonna hand it over to Andrew Fowler to talk about the winter releases with HeavyJob. You'll see some of that echoed throughout HeavyJob as well. Michaela's team really sets up as that platform side how we are going to use the rest of the the software. Let's jump into our first big feature. We're going to touch this a little bit more with Gen in just a moment, so we will go ahead and cover this very briefly. But we've done a lot of work with our map view component inside of HeavyJob. Right now, we do have the ability to view your photos and your telematics locations inside of the the map view inside of HeavyJob. We're adding in two new things this part of this winter release. The first big one is inspections. The best way to think about it for now until Gen tells you a bit more, we're taking that daily digest information and putting it into the map view. Alright. The other big one, one that I'm very excited about, adding in the plans sheet overlay inside of our map view itself. For those of you that have experience with HCSS plans with our docs and plans, you'll know this feature as being on iOS within the iOS app itself. Lots of value to the foreman and the workflows that they can do there. We are very excited now to add this into the map view on our desktop on our website as well, allowing you to now really get a full job context of where the pieces of equipment are, where that inspection happened, where all these other things that we plan to add into the map view are happening based upon how what the information is in the in the plan sheet itself. So as you can see, we've got the overlay in action here. It uses the actual location services set up in plans itself. And then from there, the default opacity is static right now. We've chosen one that really looks really well for seeing both the background and the data itself. But we do have a lot more improvements just in terms of usability plan for this. But again, just that idea of viewing your own information inside of our map view. And with that note, just as we get into UGM, we'll be asking quite a few questions about what other types of location data that you have, something that we are always interested in learning more about. More map view improvements. Again, for those of you using it today, you'll find that viewing your photos and that photo location has been really critical to to what we offer today. We've added in what we call a photo light box. I actually had to look up what a light box was. Apparently, it's an old term, but it's now new inside of new newer software development. But it's just a nice fancy way of displaying all of your photos directly inside of the view. We love our developers for the photos that they managed to find for us. But in this case, just being able to see the photos and really have just a very nice experience with it. As I go into our next slide, we'll see how within this inspection itself, I can open it up. I can go through the different photos themselves. I can do a nice zoom. I can see all the different inspection notes. So there we go zooming in. And last but not least, that info panel up in the corner. We can open that up and see all the information of it, when it was taken, where it was taken, who uploaded it, what project it was on, any notes that it was on. So all that information just really combined in one spot for you to be able to see those photos because of how important they are and to go through them very quickly. Alright. And back on some of the things that Michaela was referencing, we've done a lot of work to add in a new public portal, a DIG permit API. Any of you that have used our DIG permits project controls in the past know that it's a way to get all of that information directly into that field user's hand. And then you can also pin the specific location of those DIG permits inside of HCSS plans. So DIG permits really for how important they are, they go through all the different parts of of our HeavyJob platform. But what we heard from you and what we heard from several customers and and partners was that they they want to get that information in. You keep it updated somewhere else. So we've developed a public API that will now allow you to send that information in into the Heavyob project manager portal where those DIG permits live. You'll be able to fully upgrade and integrate all the information for that DIG permit, where it's at, when it expires, when it needs to be renewed. All the information that's inside of the DIG permit is available in that API to update it and just make sure that all of your information is as live as it really needs to be. And and we can do that back and forth as well. So if the integration is going the other way, something gets changed on the manager side, you can use another API to call that, see what the information is, and change it in whatever system you have. So just a great overall API experience to allow you to do everything you need in terms of data management and to make sure everything is flowing back and forth. Okay. Like Michaela mentioned before, again, like I said, they work on the platform side and work on rolling things out. There was an in app AI experience that has been rolled out on that side. We are also rolling out an in app AI experience inside of our daily digest as well. This is the start of how we are going to approach AI, really developing that model of what we can do with our AI tools and then putting it into places that make sense for your workflows inside of the applications themselves. The first one that made sense for HeavyJob was that daily digest summary. Whenever we talk about the information that's in there, it's text heavy, takes a lot of reading and processing to figure out what happened on a day. And so with that, we did the summarize daily digest as that quick magic command as we're calling it. So it's a preconfigured prompt for those of you that are familiar with how AI operates. It's a preconfigured prompt. It says how to, do the summarization of that daily digest and then spits back out the result, for what you're looking for. Like we said, it's it's this this is our model for how we want to do any feedback of how well it's doing, what we can improve, where else you'd like to see these types of summaries, where else you'd like to see different types of AI functionality would be greatly appreciated. Double click there. All right. Moving into a new feature within our time card adjustment tool. This one is titled labor rules. Any of our customers that have worked with unions, anybody that works in the states that have more strict labor laws and and things like that, will understand what this screen is doing for you. Within the rules section are really the rules that we see that apply to, to meals typically. And what we're going to use is the schedule information that you can input into the time card and that the field users in MyField can input as well. That schedule information will then be used to calculate things like, do they need premium pay? Do they need a subsistence or an additional valid an additional dollar amount applied to them? Because as the rule says, they do not take a thirty minute lunch break, and that is configurable. Or they did not take the lunch break every five hours as needed. And so what we see is in this case, what we're seeing on the screen, minimum meal duration of thirty minutes and require a meal break every five hours worked. We are going to apply a one hour premium meal. So you might have M1, L1 in this case is what was used. And we're also going to apply as another option, check or uncheck, an additional twenty dollars per meal that misses that violation. So if we're required to do two mils based upon that five hour five hour period, and both mils are skipped, we will give you m two or l two in this case and forty dollars total. We've also built in a lot of checks if you already have a process in place with the foreman already know to do this sort of thing. We will check the total amounts and make sure that the total amount is correct based upon, again, that schedule information from MyField, that schedule information inside of the time card itself. All right, keep on rolling here. This is our revenue quantity screen inside of web as well as APIs to back that up as well. This has been a feature for those of you that have used our our desktop system, maybe is is where you would have seen this before as an option inside of the configuration of HeavyJob Manager. This is what allows you to enter in revenue quantity directly against those pay items. Whenever you think about why you may want to do that, perhaps it's a a paving job where you're reporting the cost in a certain unit, and you're reporting revenue in a certain one, and you wanna make sure that those are getting aligned. So that's why you would use it, and that's why our other customers have used it in the past. But now we are adding this information and adding this ability to our web portal as well. You will see that we can add in that revenue quantity direct onto the screen. Whenever a configuration is checked, if this is something you want to use, please feel free to reach out to our support so they can help you with the configuration as well, just like in in desktop for those of you that had this configuration on the the mobile side on the website as well. But once that is set up, we can add in that revenue quantity reported directly, edit any information from the field as it comes in, but just using that within the workflow in order to get all the information that we need, how I how I want to gather revenue inside of our system as well. And then similar but different, we're looking at the pay item entry inside of our mobile screen. So this is if we're looking at how we use our pay item entry really for that short cycle and utilities work, what we're looking at is pay items are what is are driving what how the how the foreman thinks about selecting the individual work. And so within the configuration, we've what we found is there could be a lot of those pay items listed within the screen. And so just like we were doing cost code where that was the primary thing that the foreman needed to pick, within the pay item screen, we now have the ability to create those tag groups as well as the individual tags. On this particular screen, we see that we have a material group and a pipe size group. So that way, we can filter down to those pay items, select exactly what we need, and then be able to have that foreman enter in the information without having to worry about however many pay items that you have set up on your workforce. And then connecting that back into another pay item screen, again, that same workflow for what we're looking at whenever we have those MSA unit prices. This is a pretty standard operation across all of HeavyJob. Exporting that information to Excel, letting your macros run, letting you use Excel in a way that makes sense that that can do things much better as Excel than than what a web application could do, and then reimporting that information back into HeavyJob. So we've set that up for our paydowns as well. A number of reasons why you would want to do that, but overall, just making sure that it's complies and and follows the models that we've put up in other places. Export that information to Excel, modify it however you need to, and then bring it back in. Really great to make sure that your new quantities, your new unit prices are updated appropriately. And that sums up for the HeavyJobs side. I have one slide for docs and plans. This is a pretty exciting integration and feature that we've built out. We've actually been working through and building out a punch list functionality inside of HeavyJob using docs and plans as the way to enter in that information. So what you'll find inside of the project controls after our winter release is a new punch list section where you can enter in and view that information. When it comes time to enter in and view it in the field, this is part of the HCSS plans where we would open up the punch list module that would now be available and be able to see the information as well as place that new punch list item as well. So that way, by integrating it into Docs and plans, we now have a very nice sync up between where that punch list is or what sheet that it applies to. So that way we're really improving that accountability and also just being able to document it really thoroughly using plans as that hub for the field entry of your punch list items. All right. And as always, any questions that you have, feel free to send them in. I will go ahead and turn it over to Brittney. Thanks, Andrew. Hey, everybody. My name is Brittney Klosterman, and I'm the product manager of HeavyJob Resource Planner. For the folks on the call that have already heard about Resource Planner, hi, again, I have some updates to talk about. For anybody that is like, what is Resource Planner? I've never heard of it. I'd like to just introduce you guys to what this new product is, just so you guys have awareness. Then if you have questions, shoot me an email. There's a little typo in my name. So if you want to send me an email, my name is I'll just send it in the chat so you guys have it. But just what is Resource Planner? It's essentially a construction scheduling tool where you can effectively schedule your crews. It is different if you are familiar with our legacy product, HCSS Dispatcher, and that it's web based and it's built for your project managers. So it's very, very collaborative. You can create needs requests. Thanks, Adam. You can create needs requests. You can schedule crews as an entire group, you can go and look for your equipment and see is it available at the time I need it. What's really cool about Resource Planner is we are working to make it a seamless part of our platform. So things like your jobs, employees, and equipment, that in HeavyJob is gonna show up in Resource Planner. So that's a little primer. If this is the first time hearing about Resource Planner, feel free to reach out to me if you want to learn a little bit more or talk to your customer success rep to learn. But with that, we do have some exciting new developments in Resource Planner. So as we chatted with a lot of customers over the past few months, we heard that one of the most important things when it comes to scheduling is keeping the field in sync with the plan. So one of our first new features we've added is the ability to text your your schedule assignments to anybody that's assigned on a selected day. So think about this, if you already have a afternoon planning meeting every single day where you're deciding who goes where. If you're finalizing that plan and you wanna go ahead and tell everybody, hey, where where should you go tomorrow? This is the feature that you would use that. You can either say, tell everybody across all jobs, whichever matches your process best. And it's going to text each person as long as their phone number is in attached to their account. And when I see each person, this is each employee you're scheduling. It's going to send them their scheduled job, which is your code and description. It's going to send that job address, their foreman, and then also their foreman's phone number. So that way if that person is getting to site, they have any issues, they already have their foreman's phone number that they can give them a call. This is our first pass at this. So I am really eager to hear what you guys think because we anticipate that it could even be better. So looking for some ideas, we have some ideas on what we'd like to do. If you're looking for this functionality, it is not going to be released next week with the rest of the features that we're talking about today. It will be released before the end of January. So it's something that we're actively working on, but I'd be looking out for that. And then we didn't stop there. So for your foreman that already use the HCSS field app, we continued doing some work to provide better communication. So if your foreman are already checking out the work plan, I know we are really excited about that cost code list we did last year. We actually have that crew tab just below it, and your foreman can go and see live as long as their Internet is connected, the actual scheduled assignments, employees, equipment on the job that they're working on. That way your foreman can get an idea of who should they expect on-site. Now, you're probably wondering, okay, cool, but how can we help our foreman get their job done a little faster? And so they can also use this poll and crew functionality to get a head start on building their time card. So that way, whoever is scheduled in Resource Planner, they can go ahead and put those people and equipment on their time card. Something I've heard frequently is someone is scheduled but didn't show up. You want to see that person on the time card with an attendance code, whether it's absent or maybe they took paid time off. This is going to help prevent your foreman from missing employee. Linked equipment will also come over here with your operators. So that's all I've got. I'm very excited to talk more about Resource Planner with you guys, but for now, are the new features we have. We have a ton of stuff in store for 2026. So looking forward to chatting with you guys more. Oh, sorry, Gen. I clicked it a couple times. There we go. No. It's fine. Hey, guys. I am Gen Whatley. I'm the product manager for Safety and Forms. We'll be talking a little bit about both today. And for anyone who hasn't used Safety, it is our safety software that integrates directly with HeavyJob. It actually is in the same app, HCSS Field, and so it's a great way to just help your crews get that engagement, and just get involved in your safety program. So talking about some new things, Fowler did address this earlier, but I want to go just a little bit deeper on this, and I am mindful of time, so I won't spend too long. But essentially, we are adding in just a totally new way to view some of your data, and that is location on a map. And in the safety world, there are so many different things that are so much richer understanding once you put them on a map. So we decided to go after inspections first, because so many of you are using it every day, you've got a lot of thoughts on it, but we are hoping to hear from you what else we should be putting on maps like these. But what is coming up in this new release is essentially you can see on a map exactly where inspection happened in relation to your equipment, including your telematics data, as well as in relation to your hazards or just other locations. And so that's really going to make it easy for you to start understanding where some of these activities are happening, so you can maybe gently guide and say: Hey, I see that this is often you're starting a job walkthrough over here in this area, but really you should be going down this corridor or hey, we want to extend this walkthrough somewhere else and add this in. So this will hopefully give you some of that, some of that view. This also is really helpful for getting your PMs involved because they can see it right there next to some of their, some of their performance data, some of their photos, and so it's really easy to just toggle through and understand it. And of course, there are filters, as you can see on here, to filter out to look at specific inspection types, recorders, or other detail. And you might be wondering, how are we getting this location data? And so right now what it's set to is if you have location services turned on, it just is automatically pulling that location from your device when you start that inspection. But we also are allowing in the next release the ability to manually set your location. So this is great if maybe you are somewhere further away or if you work in dredging, you know, you're having those inspections under the water, you're not actually gonna go and walk out over the water and set that location. So a lot of options there and you can toggle between the two on this map. And there are some new improvements that are coming soon. So like I mentioned earlier, we're giving you the ability to really understand where people are on things like their drop site walkthrough inspections. So you can actually see on here for each inspection item, if your location services turned on or you're manually setting it, you can see exactly where it happened and the time it happened. So think about that. That is going give you so much more rich data to really understand the quality of your inspections. We also are giving a little extra in terms of you can see where your active follow ups are, and so this is in the office, is a great quick view to understand what is outstanding, and then also in the field you do have the ability to see in the follow-up where the location is, so that's really going to help in terms of helping people. They get a follow-up assignment and they say, alright, I need to fix this, where is this item? So super easy to help get them where they need to go. Less questions, less phone tag. So, moving on to JHAs, we have some more JHA work coming out in the future, but something you can look forward to is the ability to rename JHAs to whatever you want, and have that flow across the platform. It'll show up in the field app. It'll show up in your reports. It is a company wide configuration, which we heard from y'all is important, and historical records do remain intact. And so, this is really just gonna help if maybe you've been using a different term for JHA. Some of y'all use tail boards, or some of y'all call it pre task planning, and this just can definitely help if you're getting a lot of, new people on the job site, or if you just never fully made the switch. So expect more JHA customizations. And just one last item. So on the form side, there's three form types. There's fillable, there's custom and hybrid. So we're talking about fillable today. We're giving you the ability to say this is a required field. You cannot submit this unless this field has been filled out. And so that's in two thousand twenty five point two zero, so feel free to go and try that out. And it really should be simple, not too much here. I think it's straightforward, just mark it as required and away you go. And I think that's it for me. Thank you, Gen. I think we have about three minutes left, so we have a very short amount of time for maybe question. Michaela, I think you had a question about Insights you would like to address. So do you want to take that question and answer it for the group? Yeah, absolutely. There was a question in the Q and A around how to add Insights. If you do not have HCSS Insights it is free for you to add. If you are a company admin you can just go into HCSS Credentials and add insights as a product to your your company. There, you can add users, you can add reports, and this is at no cost as long as you have a valid HCSS subscription, Insights is free for you to use. So yeah hope you hope you do. And that's it. Michaela, thank you very much and thank all of you for joining today. Know this is a little bit different format. So if you have feedback on this, we're going to try to keep doing this every quarter around our quarterly release, and we always want to know what we could do better. Again, everyone who is on this call and anyone who's registered should receive an email soon with a link to the recording So you can go ahead and watch this, forward it on to other people in your company that this might be helpful too. So that will be available, be available on our website as well. But take a look out for that email. And lastly, look, hopefully we'll see a lot of you very soon at UGM. So thank you very much for joining us today, and we'll see you all shortly. Bye.