Find the Gaps Before Bid Day: A Smarter Way to Review Drawings and Specs

  • Document Crunch
Find the Gaps Before Bid Day: A Smarter Way to Review Drawings and Specs

Webinar

Experienced estimators know where scope gaps, conflicting requirements, and costly surprises tend to hide. But with hundreds of drawing sheets, lengthy specifications, and tight bid deadlines, even the best estimators can't catch everything.
How can preconstruction teams make sure that expertise is applied consistently across every project?

Join Document Crunch's Maegan Spivey and a guest speaker (TBD) to discuss how contractors are rethinking document reviews to catch potential issues earlier, standardize their approach, and give teams more time to clarify scope before bid day.

Through real-world insights and a live demonstration, explore how AI can help teams review drawings and specs, apply their own standards, and turn findings into actionable bid questions.

What You'll Learn

  1. How to make experienced estimators' knowledge repeatable across project reviews
  2. How to identify potential scope gaps and conflicting requirements across drawings and specifications
  3. How to turn findings into RFIs and bid questions while there's still time to clarify scope

Speakers

  1. Mackenzie Putici Webinar Moderator Future B2B
  2. Maegan Spivey Project Manager Document Crunch
  3. Jeff Kirk VP Preconstruction Hill & Wilkinson General Contractors
Full Transcript Mackenzie Putici Hello, everyone, and welcome to today's webinar, Find the Gaps Before Bid Day, a Smarter Way to Review Drawings and Specs. Today's session is brought to you by DocumentCrunch, a Trimble company, and produced by Smartbrief. My name is Mackenzie Putisi with SmartBrief, and I'm excited to be your moderator for this fireside chat style discussion today. Now before we dive in today's topic and get our speakers up on stage, let's cover a quick bit of housekeeping to make sure you get the most out of today's webinar, and then we'll get this show on the road. Alrighty. I've already seen several of you piping up in the chat as we've, started settling in here. But if you're just joining us and just getting in the door, if you look to the right hand side of your audience console, you should see a chat interface. And at the top, you're gonna see a few different tabs, chat, docs, and q and a. So let's quickly do a audience console tour together, and then we'll, keep on moving on. So first things first, introductions are always great. Thanks already for those who are saying hi's, hellos. Looks like we got people in from Virginia, Wisconsin, Texas, Southern California, Pittsburgh, Montana, Wisconsin. Great. So, Colorado coming on in. Hey there, Ashley. Landis from Bethlehem, Colorado, New Jersey. So if you're just coming in again, feel free to look to the right, find that, and pipe in there in the chat. Let us know where you're tuning in from. This is also the perfect place, throughout the session to let us know what you're thinking, what you're feeling, have you had similar experiences? We love to know how the information is landing, so please do participate, in the chat. We love to know what you're they gonna feel in as I said. Now the chat is also the perfect place to let us know if you have any technical issues during today's session. Hopefully, that's not the case. But if video, slides, audio, anything's not loading, not syncing up, feel free to reach out in the chat. Myself and Deanna, our webinar coordinator, who's running things here smoothly in the background will be here to help. That said, a quick browser refresh usually does help with any issues, so try that as a first line of defense. And if you're having persistent, bugs there, we'll we'll be there and we'll be able to troubleshoot. A couple other things you can do to enhance your viewing experience, if you hover over your viewport in the bottom right, you will see a closed captions button. You can put that on in several languages. We've also got a toggle if you're on a mobile device, which is light mode just to help pair down the console for a better, small screen viewing experience. And a couple other things, there are some emoji reactions. If you guys wanna use those during the session, feel free. And there's also a catch up feature if you get interrupted or if you're coming in late here, that'll give you a quick summary of what happened over the last ten minutes. So you can click that at any time and get a a little bullet point version of what's been going on in the conversation. Alright. A couple of other things. We have in the q and a tab, space where you can ask any and all questions. We are gonna be holding some time for live q and a, which is one of the great things about these webinars. So feel free to ask those questions, and we'll do our best to cover those here, on the session today. In terms of getting your questions answered, if you're looking for any additional information about DocumentCrunch, there is a one pager linked in the docs tab there. So feel free to grab that, and there's also a link to a free trial. So if you're listening in, if this sounds like something you definitely wanna try out for yourself, feel free to hop in there and and grab that link. Aside from that, last bit of fun, we have a $250 Amazon gift card up for grabs today. You do need to be live and present for the duration of this webinar to qualify for that prize, and you also need to meet the price terms and conditions, which are linked in the docs tab there. So if you wanna check those out, feel free. Alright. So the the last thing I'm gonna do before we get our speakers up on stage is we're gonna be using a couple polls today. And amongst those tabs, we've just talked about the chat docs q and a. You're gonna see a new tab open up, and that is the poll tab. So in there, you should see a poll asking you, when does your team usually find conflicts between drawings and specs? So we'd like to get a sense of of where you're at. So is it during bid review, after award, during construction, or it varies? Feel free to fill that out, and then we're gonna put those results up in just a second here with our speakers and see what they think about that. Alright. So to set the stage on today's discussion, pre construction is where contractors have the most leverage. Before the bid goes in, there's still time to price a risk, clarify it, qualify it, or walk away. Afterward, that same risk becomes your cost. But bid week moves fast, and as experienced estimators retire, more of that responsibility falls on the next generation. Today, we are gonna be exploring what the best preconstruction teams do differently to catch risks early, make better decisions, and set projects up for success long before work begins. So with that, we are gonna bring up on the stage here in just mere seconds, Jeff Kirk. Jeff is VP of pre construction services at Hill and Wilkinson, where he manages risk, sets estimating standards, and develops new estimators. He's worked in every major role in construction, so he sees precon from every side. And we've also got Megan Spivey. Megan is product manager at DocumentCrunch. She works with pre construction and estimating teams across the country and brings what she's hearing from contractors about how they review drawings and specs. So with that, you too, welcome to the stage. Excited to have you here. Maegan Spivey Hello? Mackenzie Putici Hello. Hello. Maegan Spivey There. Mackenzie Putici How you doing there, Jeff? Welcome. Jeff Kirk Good morning. Good morning. I wonder, does that translator translate for redneck? Mackenzie Putici I guess we'll see. I guess we'll see. We'll have to try it out. Perfect. Well, you too. This is great. We have got our poll open. And why don't we throw up the results to get a sense of is this what you expected? Looks like we've got about 18, 19% saying, their team usually finds conflicts between drawings and specs during bid review. That's hopped up here a little bit to 24, 27. Alright. These are moving fast. So let's maybe leave this up for another thirty seconds. And then once we've got some consolidated, data here, we can see what we're thinking. So far, no one's saying after award, though. So is that surprising to either of you two? Jeff Kirk That… It does. It does. I was, our our whole role in preconstruction is to move these things back to the during bid review category. That 17% during construction, those are usually the most painful ones. Maegan Spivey Yeah. Mackenzie Putici So it looks like most people are saying it varies. So, Jeff, I know you lead a team of experienced estimators. Why do issues still slip through? Jeff Kirk Usually, it's because of where they hide. Details… Those gaps hide in the details. And, one of the things that we're finding about, using… These in document crunch is it helps us find things that are not there. We find those to be, what's not there is as important as what is there, and it helps us, find that. It also helps us find where they conflict, where it says, something in one place and it's dangerous because then you could assume you have the answer when you really don't. And then things that are not in their usual place. We had a project a year or so ago that we we looked for where is the maintenance of the landscape for this park project. And we looked in the usual places, and it wasn't there. Had we had this document crunch at that time, we would have found that it was a small note on the landscape drawings. So that was before DocumentCrunch, so we're glad to have it here now. Mackenzie Putici Excellent. Megan, I know you work with a lot of different contractors, through DocumentCrunch. Is this kind of a pattern that you're hearing from other other contractors as well? Maegan Spivey Yeah. What I hear a lot across, the industry and, is, you know, there's just these compressed timelines, so there is less time to review the documents. Maybe you check your usual spots and it's not where it normally is. And somehow it's in the project, it's in the bid documents, it's in your bid package, but it's not anywhere, that you're used to looking. And, you know, there's these, I hear the the phrase copy and paste a lot. You know, these specs get pasted in, you know, not not maliciously, but, you know, just from a time perspective. There's less time, you know, all the way, you know, upstream and downstream to review, excuse me, review more and more documentation. And so, you know, they're spending a lot of time. Contractors are, you know, GCs and trade partners are spending a lot of time going through the documents just kind of doing, like, a hygiene, you know, basic thing. They they kind of have a good understanding of what the work needs to be. But, again, it's it's making sure that the documents, like, align with it. And I would say that that is kind of, you know, those are kinda like the things that we're hearing is is that, you know, maybe they've updated the specs, but not the drawings or something like that, so they conflict a lot. So there's just kind of this, overall kind of crunch, in these timelines that the… And more and more documentation to stay on top of, and then just a lot of room for human error as you move. You try to get things to complement each other, and you just might miss something. Mackenzie Putici That makes sense. So there's more data, more documents, everything's moving faster, less time to review and catch mistakes. So I'd be curious, you know, how how big of a difference is that, Jeff? You know, if you catch something in week one versus week three, how does that really play out? Jeff Kirk You catch it in week one, you can get a better answer for it, And you can take more time with it. The design team can take more time with it. And then you can get those responses out to the subcontracting community a lot quicker. You catch it late, everybody's adding contingency because they're afraid of the issue. So we we find that not only do earlier questions and answers get better results, but we're also seen as being more proactive both to the subs and to the architectural community. We're seeing, like, we're on top of the game better. Mackenzie Putici So it was good. So we… We've talked a little bit here about where where the gap hides in reality. So I wanna move into talking to you too about making expertise repeatable. And all of you in the audience, you were so gracious, to answer our first poll. We're gonna launch a second poll here quickly. That's gonna open up where you saw before. In theory, here we go. Perfect. Alright. So everyone, the question here at hand is how does your team make sure every estimator reviews to the same standard? So we're using shared checklists of some kind. Are you having a senior review of every bid? Do you have each estimator's own method? Or perhaps you're not sure you're not sure if if you are doing this consistently. So, again, let's leave this up for just a second and see what you guys are saying. And then, Jeff, we've mentioned in your intro, you've you've kind of done everything in the industry, and, I think one of those things is training new estimators. How how does how does that look in this day and age, and and what's maybe changed in the last while? Jeff Kirk You know, it it has changed. The personalities have changed, but some of the tools that we have now kind of, help accelerate the process. I I think that AI is gonna do to preconstruction kinda what three d models did earlier. We used to spend a lot of time trying to visualize a project in our head and build it in our head, and and, models help shorten that learning curve. And I'm finding that using tools like the document crunch helps us shorten the learning curve and spend more time talking about important issues than sending them off to count doors and hardware and toilet partitions and those sorts of things. You know, they're gonna pick that up. My grandson could do it. What we're looking for is to train them how to find issues. And and we're finding that it it kinda creates better conversations earlier. Mackenzie Putici I like that. Okay. Hold that thought just a second. Looks like we've got a pretty good set of votes in here. So it looks like about 23% are saying there's, they're using a shared checklist. About 50% have said they're getting a senior review of every bid. About nine saying each estimator's own method. 17% not sure. What's your take on that? Is that surprising? Is that a good use of resources, having a senior review of every bid? Do you feel that's essential? Jeff Kirk You you know, you're not going to eliminate a senior review. That that will, in my mind, always be important. It's just how long does it take that senior to do the review? As far as the shared checklist, we kinda started out with that. We created… We got with all of our supers and PMs and all of our estimators and started… We created a really robust checklist. But then it was like, okay. Who's gonna run through this checklist? Who who takes it through each project? And, Megan has done a really good job of importing those into, this program, and and, it makes it much faster, much quicker that we can get to the big issues and talk about those rather than just spending days digging for things. Mackenzie Putici I love that. Perfect. Okay. I'm gonna close this poll out. And then, Jeff, to continue this question about sort of training and and prepping new estimators, I wanna ask you, you know, it sounds like a lot of people believe that new estimators need to do the work by hand to learn it. Where do you land on this opinion? Jeff Kirk I think they do. It is… It kinda like I was talking about earlier about learning by counting doors and hardware versus learning about… Let's talk about the big issues. Let's talk about the things that, are hidden and get that experience to them sooner. We've… We found that we can get them into DocumentTrance and get them to chatting with the drawings, and it also allows them to chat with general AI about, how things go together and why things are done the way they are that, they actually come away smarter, sooner. And it fits the way kids today learn. Mackenzie Putici So is it true that old dogs don't learn new tricks? Jeff Kirk Oh, no. Oh, no. You better learn your tricks. You better. Mackenzie Putici And, Megan, what are you seeing in terms of estimators? Do you find that, you know, like, newer estimators are learning faster with these new tools? Maegan Spivey You know, actually, what I'm finding is there's a lot of experienced, people who are testing, putting it through its paces… Putting, you know, new technology through its paces. They're really trying to evaluate, what they, you know, roll out to their organizations. And, you know, Jeff's a great example. He he is an innovator on his… He's just, like, always thinking of new things to try, and I see that, in many other contractors too is that they're… They understand what good looks like, and they are able to, you know, do that first pass because that's, you know, part of part of, you know, any sort of evaluation of some new tool or technology that you put in. And so they're really able to combine their experience. And, you know, once they get a comfort level, I think that, you know, traditionally in construction, a lot of construction technologies maybe don't totally fit everything. But with AI, there's a lot of ability to have flexibility and, you know, customization. And so being able to really kind of, they can kind of spearhead, you know, shaping what good looks like for their organization and their… So I'm… I've seen… You know, I do see the see the, you know, newer… Maybe newer estimators, newer, newer people to construction, trying out because they're used to it. Like Jeff mentioned, there's… There is that. But I think, you know, probably what what is, there's a good balance that I'm seeing across, what people are implementing, what people are doing, and and kind of trying to balance that for their organization too. Mackenzie Putici Perfect. Jeff, I'd be curious to know how do you get your senior estimator's judgment into every re… Review? You mentioned it was important, but is that, is there a sort of a knowledge transfer, or how do you go about that practically? Jeff Kirk That's that's a a really big advantage here is that we could take the checklist, the health… Document health review, we could take the constructability reviews and all of that and plug it into a skill, build a skill in the, in the AI program. And then, like I say, that was developed company wide through through senior leaders from the field, from safety, from from our QC department, from our precon group. And we take all of our experience and and dump it into a skill. And then a younger guy can run that skill and get the same results as if I were in the room asking questions. Then it leads, like I say, to better conversations about more important things earlier. Mackenzie Putici Perfect. And so I'd be curious to know how… This is something that obviously when when it's first brought into the the team or the company, it's a new tool, so people may not know how to use it. So how do you encourage experimentation without losing control of the number? Jeff Kirk Curiosity is a great thing for an estimator to have for anybody in precon is you wanna be curious. And we created an environment where they can be curious in a safe place. And that was one of the first things that, when AI came about, started scaring our IT group. It is how do we allow people to ask what if? Will it do this? Those sorts of questions. And thus, you know, document trunks gives them a safe sandbox that they can play in and get real answers, and be curious. Mackenzie Putici So, Jeff, we had a question come in. I'm just gonna throw it at you now. Jim asked, when you say dump the information in the skill, what specific information do you give it? Jeff Kirk We actually, we actually, worked with Megan and gave her a… I mean, it was a vast Excel checklist of everything we would look for at every stage of design. And, you know, is… Are are the are the rooftop units designed or the, you know, or is the plumbing fixture schedule there or door hardware specified, is fire rating shown? Everything we would look for at every stage of design, even down to a way to check the, do that quickly? And, you know, we've given all of this to Megan, bless her heart, And she has created skills so that you can run these health checks and these document reviews and apply all of the questions that I would apply if I were reviewing the set of drawings. Mackenzie Putici And, Megan, can you shed some light on sort of that process or, you know, like, the the handoff of information versus the skills and how you implement them? Maegan Spivey Yeah. The great thing is that, you know, once you… Your organization kind of has a specific task that you do defined or maybe some… Something specific, you know, you wanna do with the project documents, you know, that you want consistent. You define what you're trying to do, and you define what good looks like for it. And that's, so for… I would keep it specific to the task, but that's kind of what we mean when we, take some of the information. It's what is good luck. Like, whether it's a template, whether it's questions you want people to be asking, whatever the case is, you know, you've agreed, you know, either this is an organization fit. You know, this is all I want for, you know, this specific team to look for these things. Whatever it is, you can segment it out. But the idea is that, you can either set the standard for that specific task for your organization, or you can also do something like, you know, if it's for you, you know, you always do this one thing. You can do it for… Define it for you and yourself. But, again, one of the benefits of using something that, is collaborative and is available across your organization, is that the standards then, whatever good looks like, whatever knowledge or, you know, Jeff talks about, hey. We know what to… We're we're knowing what to look for. Help provide that, that level of information to, you know, whatever level or area. That's kinda what we mean by dumping the information. So the information relevant to the task, relevant to your organization. Mackenzie Putici Okay. Awesome. Thanks for clarifying that. And I'm sure many out there are like, hey. I've got all this information. So what what would this process really look like? So it's exciting. Maegan Spivey Yeah. Mackenzie Putici Okay. I'm gonna open our third poll of the day. So everyone out there, again, feel free to to click in. Our third question for you all is how many of your projects RFI's could have been caught in precon? Your potential answers are… Oh, wait. We might have a duplicate there. So apologies. Please don't click that first response. Some, many, or not sure are the three responses there ideally. So we're gonna move into sort of, questions worth asking. So questions we should all be asking ourselves. And I know, Jeff, RFIs are going out sooner than they used to, and some teams here, they're sending too many. How do you think about that? Jeff Kirk I… I'm not I'm not sure you can ask too many questions, but, we find that the earlier we ask them, the better the results are. We had a recent hard bid project a couple of weeks ago that we ran through DocumentCrunch. We ran it through our health checks. We came up with a lot of really good questions very early in the process. And when we… After we turned bids in, we learned that we were not low bidder. We were about 2% higher. But we ended up winning the project because the owner felt like our number was solid, that we had been more thorough and that there would be fewer of these RFIs that would come up later that would cost him money. So, you know, we're finding advantage to asking earlier. It… Kind of an unintended consequence, so to speak. Mackenzie Putici I like that. I like that. Alright. So we've got some good results here. It looks like most people are saying many, so I think there's, an obvious benefit here, to to catching things in precon. And we've already sort of opened the door on the topic here of AI. So, Megan, I wanna double click on that with you. I know everyone's using AI to go faster. So where's the line between streamlining the work and creating AI slop or things that just make it harder on the person reviewing it, too much information? Maegan Spivey Yeah. I think part of it is that some people take for grand… You know, they hear all these amazing things that it's… You know, does so much great work right away. And I think, though, like, there is that flexibility, but there's also consistency. There's a lot of different factors, in what contributes to an output you like. It could be just one time you get one answer you like, and then you keep doing that, taking for granted that down the road, it's going to stay consistent. Models change. Things… You know, your process changes. How do you stay up to date on that? And so when I think about… You know, when you look at the outputs, it's, you know, reading it and confirming it and, testing it out more than once, you know, being able to also have the flexibility to change the process, as you are trying to kind of narrow that. But, I think more often when I see… You know, we see it all the time. There's, like, AI generated comments. Like, people are prioritizing speed over quality. And so I think when you put your… It… The ideal form is that it's supplementing, not replacing. So if I just go ahead and, you know, spit out whatever it gives me because I liked it one time, you know, that is not a repeatable process likely, but it's also creating more work for the person on the other side because I've taken… I've stopped reviewing, and now I put the burden on somebody else to try to decipher what I'm trying to say. Maybe there were probably a few questions and then, you know, an e… You know, people… You write an email and you don't review all the questions that are in your bullet list. There's all these these factors of just, you know, do that first pass. And if you're turning something into a repeatable process, maybe for either you or maybe for your organization, taking that next step and trying it more than once, kind of holding everything with an open hand so that you keep, refining till it gets to the place that you want it, I think is just a good rule of thumb when you're using AI generated outputs is just, you know, taking that second step of not not… And, you know, it's it's it's exactly like what happens with emails. You know? The more time you spend, I think there's some kind of famous quote of, you know, I would have written you a shorter letter, but I didn't have time to because there's that editing process that you go back when you take that second look of, okay. Now I'm double checking my work or, you know, you submitted an essay in high school and you didn't actually proofread it before you submitted it. Oh, there's so much you can catch by that second review and, again, that repeatable process, doing it more than once, kind of taking the time to get it really to a consistent spot, so that you can do less editing, but still always double checking. Mackenzie Putici That's wise. That's wise. I know it's… There's… With AI, there's so much speed and so much skill, but there's always something. Exactly. Because I was like, that doesn't make sense. That's. out of line. So, but it does get better and better the more you use it. So… Jeff Kirk Yeah. Maegan Spivey Exactly. Mackenzie Putici Especially. on the same repeated task. Jeff Kirk Yeah. We we we we kinda have a motto around here is that don't bring me 14 pages of summary information that AI spit out for you. I want you to review it. I want you to understand it. I want you to boil it down, and let's have a conversation about what's important. We call it putting your name on it. Any AI generated information, if you're gonna distribute it, you must put your name on it by reviewing it, understanding it, and being able to walk through it. Mackenzie Putici It's a perfect policy, I think. So, Jeff, I know trades are are trying to get in front of our fives too. So I wanna ask you, what would make that smoother between a GC and its trades? Jeff Kirk It it it does make it smoother because it can happen quicker. We can have these conversations in week one, week two rather than late week three or the day before it bids. And we wanna be the general contractor that the subs come to for answers. I know it's frustrating for subs that they're asking estimators questions about things and that poor estimators are swamped with addenda and everything else. We wanna be a source of answers to their questions. We know that that makes it, makes them more comfortable. It creates an environment to where they will wanna work with us, and they will wanna give us a number that's not just stacked with contingency. And we find just chats with drawings can help. A sub can call and ask you a question and rather than somebody taking ten minutes to look it up, we can have a quick chat on on on the program and and get them an answer right there on the spot. Let's move on. Mackenzie Putici I think that's a good point about the, you know, often people are planning these contingency pricing into, say, the quotes, the bids. So, the more information they have, the more trust there is, the less surprised, the more they can feel like, oh, don't worry. That's not gonna happen. Better economics. Jeff Kirk What what do they say about the happy cows and and the, you know, happy cows get better milk? You know? It's it's it's it's kinda the same way. Create a good environment, good results happen. Mackenzie Putici Now I want some, like, Swiss cheese or something. Alright. Back to the topic. I know, Megan, you've been listening in, and you may be able to show us some things in DocumentCrunch here live today. So I wanna. queue you up for that. Maegan Spivey Awesome. Yeah. So what, what has really resonated with me throughout, getting to work, with Jeff is that, you know, the win isn't always finding the gotchas either. Sometimes it's finding them sooner so you can get them addressed sooner so that it it kind of, you know, starts improving things downstream. And he's, had that really good theme about… Through those answers as well. And so I kinda wanna show you what we're talking about, put that, here in front of, in front of what's… What we've been talking about. So for this example, you know, what he… He's mentioned before is those, you know, that checklist of questions. What are these things, that really… That we know to check? And, you know, for us here, this is one of our out of the box ones. This is kind of those industry wide gotchas that occur. So, you know, questions to check over your drawings, like contractor to verify that sheet completeness. And then also to, you know, those, items, for example, that may show up in specs and drawings or we know that they conflict. You know, if we have our own checklist of gotchas, we can go ahead and put that in now, and this will apply to all our uploaded documents. So one of the things that I heard… I've heard a lot is allowances. Allowances can be in the drawings. They can be in the specs, You know? And we miss the ones that are in the drawings because we're not looking always. We don't have as much time. Not that they're not… They can't spot it, but if there's a compressed timeline, how do we get it? And being able to go right where, the information is in the drawings and be able to go right back to the source, you know, that's kind of, the advantage of where we want people to be is checking, but how do we make it faster? And so for this situation, you know, what is great about this is it's also collaborative. So everybody, you know, has a chance to review. Maybe we take sections, maybe whatever the case is, but, we're reviewing these. We're able to check where they're coming from, And then we can say, you know, is this okay? Is it not? Does it need review? And depending on the scenario too, you know, you may wanna find something where you you found something. It's your normal hit list of gotchas that you're looking for. You know, this… We always find a problem with the specs, but not, you know, it… But it conflicts with the drawings. So now I can use that context, and I can go and take it. And then I'm gonna generate an RFI on it. And I'm ready to start, you know, pulling, you know, pull the, clarification here, for for architects review. And now I'm getting my RFI groups so that I can go ahead and send it out right away. So I'm reviewing quickly. I'm going through faster because the information's already found in surface for me. So once I get that in, I can start kind of accumulating all those questions that I want answered right away. And so in this scenario, I'm gonna let it keep working on the RFIs. But as I keep reviewing my summaries, one of the great things is now if I do the first pass, I flagged everything I need for that next person. Maybe it's my senior, reviewer, whatever the case is, and I'm gonna have them… I'm gonna put the ball in their court and move this over to them so they can do their second pass and make sure we don't need any additional RFIs. Maybe we need to call certain things out before we even get started on our, process. But, you know, when we talk about that kind of, collaborative, we wanna make sure that we're all kind of looking at the same information, and we have a clear line of who's next and who's up. So, Jeff also mentioned, which is great, you know, these, organization level skills. And for DocumentCrunch specifically, you know, now that I've gotten my RFIs out, I'm, you know, kind of got that first pass out so I can hopefully get responses quickly. And now I've… You know, for my organization, the next step of my process is something I've made a skill for, and this is how I want, you know, our organization to run. And so I'll start, you know, I wanna… Maybe I'm the general contractor. I'm gonna get my r… Now I wanna get my RFPs out. And so I wanna have a first pass on the trades based on this specific, you know, bid package. And then I also want to, get a high level scope that I can copy and paste maybe into our third party software, or I could do something like, you know, send out a huge email and give a high level scope for that trade so they kind of know what they're getting into in terms of bidding. And, remember that this is all your documents. So this is searching everything, and so we optimize for quality and not speed. So we wanna make sure that we're looking at your specs and your drawings and going through that, pretty cleanly. So for here, we've got one already set up. And for… In this situation, maybe it's my CSI division. That's how I plan things. Or, you know, if my usual scope is that I, split up, you know, one of the one of the divisions, I usually have two different trade partners that do that. Whatever it is, we can go in and start, refining that based on our process, and now we have some email ready, scopes. And I can massage this if I need to if maybe I see something a little bit different for this project, but it gives me a great baseline to start from. Another thing that we can do is… You know, now I've got my RFPs started. Now I'm gonna start my estimate. And I can do that whether or not, I'm a general contractor or, you know, if I'm a trade contractor. One thing I can do is customize… You know, I can do one trade at a time. I can go in and then I can, or if I'm a a trade contractor, what I can do is kinda define how I like to start my estimate and use what we have in the bid documents to begin that process and really get my estimate started and maybe, and for this, just as an example, I have it more conversational so we know where to start, and we can go through this process, that my company has defined. So one thing, I… So, again, this is… Because it's my company, I've kind of specified how I wanna call things out. You know, I want coordination details maybe called out. Maybe I want things double checked here that, you know, pulling again from what we had on the project level review, pulling it again once we start our scopes. So we're just allowing for that process that you might go through as you're learning with someone more senior, and trying to put it in so that it standardizes across the project. And so if you're the trade contractor you've decided to bid, one of the great things that you can also do is I'm gonna go ahead and go back in and, go into this. I'm going to… I'm… I've loaded my estimate, for example. So here, you can see that, you know, I put my estimate in. We'll use for this example just our our our straight estimate. And now we're going to kind of select and narrow down the documents I wanna use now for my check. And so I can start asking questions. Maybe I wanna clarify a few things. Maybe I don't wanna talk to the GC first. I wanna go ahead and do that first pass on my own bid documents, before I send out any questions. And then once I have kind of clarity there, I can… I've developed, you know, for my company what I want, which is a proposal generator. So I'm gonna take my estimate. I'm gonna have it… Have the referenceable materials of my drawings and specs, and I've got my template in there. I've got my, questions that my senior reviewer might ask, and they're gonna go through and walk me through that process that I've defined. So, again, we're we're trying to take a little bit of time off the senior people, but also not lose that training aspect. And that's one of the great things about the flexibility and customization that you can do when you use AI. And you could do things like walking through my standard exclusions, walking through some assumptions. I wanna double check. And, again, you have that access as you keep going through. And so for here, you can see here that, I've got a few started, but the idea is that, you know, as I walk through this, I can double check these base scopes. I've programmed all this. This is my knowledge for my company that I want everyone to be using. And that's what the benefit is here of kind of using, again, that org org level standard. So, you know, what we've walked through in this small process here is, you know, whether you're a GC or a trade, contractor, you can go through, review the bid documents yourself, and then issue your RFIs early so that you get in front of all those conflicts we see between the drawings and the specs or whatever those gotchas are for your company. You can go through and start getting that out and started earlier so that the responses are in time to do things like, you know, impact your scope and impact your proposals. And what kind of, if you get any, you know, qualifications or, any sort of contingencies like Jeff mentioned, kind of try to get as much as you can done before it's close to that bid day. Mackenzie Putici Perfect. Jeff, what did you think when you first saw this? Jeff Kirk Oh, it's, it's as an old estimator, it it really excites me, to see some of the things that we can that we can get AI to do for us. As Megan is talking, I mean, it just continues to bloom and develop, and at some point, we'll be tabulating bids. And and I can… I'm really excited by it. And off the cuff use, we've learned a lot of things just by saying I wonder if it will do this, because we have worked backwards on occasion. We've had the estimate ready to go. We did not use AI to prepare for it. And then we put it in document crunch and say, okay. Compare this estimate to these documents and tell me if if something's missing. And it is always educational to do that. Mackenzie Putici Fantastic. So we have maybe about ten minutes or fifteen minutes here for audience questions. But before we move into that, I have one final question for each of you. So, Jeff, my question for you is how do you measure success for your team today? Jeff Kirk This… The the the number one measure of success for us is did the owner, did the architect, and did our operations team have fun building this project. And, generally, what takes the fun out of the project is gotchas that didn't get caught in precond. And we… Our goal is to move all the issues we can, as many as possible, out of construction back into precon where they… They're just on paper at that point. Nobody gets hurt when they're solved there. And we found that if we can do that, we can make the process more fun. And it… We… Right now, we're using it from the RFP, and we hand everything off all the way through to the end of construction. And this knowledge goes… It passes along. It stays stays with the project. So operations don't have to figure out why was this decision made. You know? They can see the research that we did on. Mackenzie Putici Excellent. I like that that people Jeff Kirk having Mackenzie Putici be having Jeff Kirk having, fun? Mackenzie Putici Jeff. Jeff Kirk Are they having fun? Mackenzie Putici I think that's important. And and Megan, I know, you know, we've we've touched on a lot today, but if there's… If anyone in the audience is there and they leave, what would you say they should keep in mind or have a top of mind as they walk out of here? Maegan Spivey I think, you know, AI can help so much. I think we're we're, you know, it could be a pitfall or where it could be a really great supplement and help, to the accelerated timelines is doing the work to get your standards the way you want them, to define what good looks like, and, use a reliable way to kind of continually align those standards. So, you know, kind of keeping that north star. And, you know, one thing, I heard… I wish I could remember who said it, but, you know, they mentioned that, you know, as we we work to kind of, like, align these… I lost my train of thought. Well, anyway, I just think that it's really important to get your… To get what you can and not replace the process. That's what it is. You know, not just digitize your process, which, you know, a lot of companies have done is kind of rethink. How can we… If we take these pieces that we know we have to do, how can we get there faster and make that the process, that, you know, hopefully is easier on people and also gives them the knowledge and experience, and training that we need to continue to grow businesses and to be able to meet these tight deadlines. Mackenzie Putici Perfect. If the if the quote comes back to you, let us know, but I think you you communicated the point well. Okay. So let's dig into some questions here since we've got you both eyes and ears. Drew, this is a question for Jeff. He says he says, how do you handle this scenario? One of your competitors submits a poorly written RFI that generates a poorly generated answer that does not align with the project intent. There is no further time prior to bid date to clarify further. Jeff Kirk A lot of that depends on what the bid process is. Is it a government hard bid? Is it private hard bid? You know, is it a Centimeters at risk project? All of those kind of define how you handle late break. And can you put a qualification in your bid, or can you not? It it it just depends on the the way the RFP is set up. Who was the comedian that says, you know, you can't fix stupid? You know, if there's a GC out there asking bad questions and putting out bad information, you know, all we can do is control what we do. But we, again, we wanna be the source of good information. And if there's a GC out there putting out bad information to the sub community, we wanna be the people that subs come to for clarification. Mackenzie Putici Perfect. Jeff Kirk Hope that helps. Mackenzie Putici Yeah. Okay. This is probably for you, Megan. I think it came in when you were doing the walk through there. Sachin asked, how does the technology distinguish between an actual design discrepancy and an intentional design change across different drawing revisions? Maegan Spivey Yeah. Sure. And I think, again, one of the things I highlighted was the citations. You know, our, our, you know, specific to DocumentCrunch, we also have a foundational layer of understanding of the relationships between the documents. And so as something new comes out, making sure that the right document is prioritized when pulling that information, but then also giving you the opportunity to verify. I know an addendum came out. I know a revision came out. You know, one of the great things that you can do is, you know, you can try this yourself. There's gonna be a free trial link and, you know, use it on something you're familiar with and be able to go and check. Hey. I know this changed in the revision and see. And then, again, you can trace that back so that you know where it's coming from and that that relationship is being rightly preserved. Mackenzie Putici Perfect. I'm actually gonna throw this up. So if anyone does want to take a free trial and try this out for themselves, you can either scan that QR code there or go to documentcrunch.com/trial. So we'll leave that up for a bit. I know we have time for a few more questions, and we've got more in the queue. So Jim was asking us… Where did that go? Here we go. Sorry about that. Okay. So he asked, what would you have advised an A and E to include in his his or her design submittal? Sub… Yes. Submittal? Submission regarding to AI to make the general's job easier? Your top three things. Oh. Jeff Kirk Yeah. I can, I can name a couple here, but, one is how the documents are printed? A lot of times, we will see civil documents that are a photocopy of a plat that is then put onto a sheet. And those are kinda hard for AI to read. Sometimes a geotech report might be protected in some way. Just the way that it's printed can matter. And then at some point, there's gonna have to be a… If you remember when CAD and Revit came out and then subcontractors wanted to get the CAD drawings or the Revit model to continue for their shop drawings, a lot of thought a lot of the thought process got lost. And then architects. begin to specify that, you you need to draw your own model and then design into that. So at some point, AI is gonna have… There's gonna be a a clause that deals with that… Deals with AI in the same way. Is it, the the good thing about it is is that when when when it points to an issue, it tells you… It documents. Okay. The plan say this, the specs say this, and it tells you where it says it. So I'm sure the architects are gonna get tired of the slop at some point. So we try not to not to issue that. But there… There'll be a spec at some point. Don't send me no slot. Mackenzie Putici Yeah. I like that. No slot. No slot zone. Okay. Jim has asked also, I'm a security guy and a one man operation who is heavily into the AI. How do you approach the work review task? Maegan Spivey I'm guessing I'll take this one. Mackenzie Putici Okay. Maegan Spivey I I think if I understand the question correctly, it's kind of how do you how do you handle, you know, repeated reviews, maybe? Mackenzie Putici Oh, there may be a follow-up here. So I think… How do you approach to work review task and it… And isn't the danger in a lack of confidence review? Does that help at Clari? Maegan Spivey Oh, lack of confidence in the review. Well, I think if I'm I'm understanding the question correctly, you know, I would… You know, when you… It takes longer to verify something you aren't familiar with. So using something you are familiar with, you know, it does take a little bit more time, but, you know, the save… Time savings down the road are kind of exponential there, because you kind of start learning what you're asking and how that correlates. But, also, you know, if you put your standards in there, is this what I'd want it to find? And then you can start kind of evaluating. Is this, you know, what I'm saying? Am I saying it in a way, or am I doing something where, you know, it's not aligning with what I wanna see based on, you know, me trying? And so I think, you know, that idea of maybe trying on things that you're already familiar with, is is a helpful starting place, once you already… And I think too, one of the things that's hard about standardizing, maybe your own checklist or or, you know, what we would call in our product or a project level review is, you know, codifying those questions. You know, you do ask every time, and maybe you forget them because it's not relative to that project or whatever the case is. But that standardization and being… Having the flexibility to kind of add or, shape that as you kind of, get comfortable or familiar with, a system or kind of AI in general? Mackenzie Putici Perfect. Thank you for that, Megan. Okay. I think we have time for maybe, like, one or two more questions, so, I'll try to pick wisely. One question here is my worry is younger estimators just trust whatever the software spits out. How do you stop that? Jeff Kirk That that that is a legitimate worry. And this may also speak to the confidence question before. But when we first started using, AI, we looked at it as a first year intern. We still go through our normal processes, assuming AI is not even on the table. But the more we use it, the more confidence we have in it. And let's just say I check… I have a guy that's been in our group for twenty two years now. I check his work one way. I check a rookie a a totally different way. And I find that our use of AI is growing, and AI has somewhat graduated from that first year intern to now we treat it like a fourth year intern or a… An early stage rookie because we're gaining that confidence. But if I can put documents into, say, DocumentCrunch and get 80, 90% of the big questions out of the way in week one, why wouldn't I do that as opposed to tripping across it in week three? And that's kinda where we started out was is, hey. If it can handle 80% of the issues, let's get those out of the way early so that when the other ones do pop up, we're not inundated. But we're we're gaining confidence in it. And like I said earlier, we're also seeing that the younger people are coming to us with better, more intelligent questions. And we've got them risk minded now rather than did I miss one door. I wanna know did, you know, did we handle the casings correctly as opposed to there's a room without a door? But, it… I kinda liken AI to what a backhoe did to plumbing. And AI is gonna do that intellectual work. And if you were still a plumber today digging ditches by hand, your business is probably very small. And I kinda like an AI doing to intellectual work what the backhoe did to. Mackenzie Putici I like that. Thanks, Jeff. Megan, I'm gonna sneak in one final question, although I know we're, pushing it against time. Andrew said, we like to find and use tools that allow us quicker and more accurate reviews, but using an AI client like Copilot, we find only provides surface level results and avoids showing contradicting information. This causes longer sessions of trust but verify. How does DocumentCrunch differ from this model, and has it really cut down on the verification time? Maegan Spivey That's a really good question. And a lot of people, you know, they start experimenting with Copilot and may not have the best results, and so kind of shy away from using it and kind of label it as… You know, you know, it's kind of the… That terrible metaphor of throwing the baby out with the bathwater. Don't do that. Like, the idea is that, you know, there are different, the way, you know, kind of the the system is, there's, you know, generalization, and then there's kind of specificity. And, you know, kind of one of the things I mentioned in our demo is that, you know, you're not going to maybe get that rapid answer you're used to, but also are you getting the results you want, on, you know, specifications or drawings the… In these kind of general purpose tools, especially as they get bigger and bigger and bigger. And so I think the, first, I think it's good that you're checking everything. But, again, you know, try to go back to something you're already familiar with and kind of use that as your guide so you kind of understand the capabilities in the system. And, you know, especially as you start getting into larger and larger, you know, different sets of of inform… You know, these larger documents of specifications and drawings, when you know it, then it doesn't take as long to interrogate it afterwards and chase down all the information. But, also, you can kind of start checking is the… Is there a difference in the answer quality, that kind of thing, depending on what tool you use. So boring, but, you know, back to try it on on stuff you know, and it takes less time to verify. But if you don't… If you're, you know, don't… You're prioritizing differently because of time, and you have to go validate, that time isn't wasted because you're also, you know, building confidence in what you're seeing in the outputs and that sort of thing. Jeff Kirk Megan, that's that's a great point. We back tested it before we started using it on projects that we had built a year ago, two years ago. Mackenzie Putici So, yeah, it takes a little time up front, but like you said, if you back test it and you're pleased with the results or maybe find a few spots you wanna keep keep that eye out for, then it's perfect. Alright. So I think that's all the time we have for today. Any questions that you guys asked in the audience, don't worry. We're gonna hand those off, to the DocumentCrunch team so they can follow-up and make sure you get any information that you're looking for. But Megan, Jeff, any final thoughts here as we wrap? Jeff Kirk I would say try it. You know? It… Just just ask what if and give it a go. You'd be surprised at the results you get. Mackenzie Putici Love it. Megan? Maegan Spivey I can't beat Jeff's wisdom, so I'll I'll leave it on his. Mackenzie Putici Perfect. Well, you too, it's been great. Thanks for fielding so many questions and, it's it's just been a great conversation, so I appreciate your time. Maegan Spivey Thank. you so much. Jeff Kirk Thank you. Mackenzie Putici Awesome. Take care of you too. As mentioned, you guys, if you're on the audience, you asked a question, we will hopefully get you an answer quickly there following up. Hopefully, we got as much information out to you in one hour as possible. We're gonna wrap up here in maybe two minutes. So if you haven't already checked out the trial link and you wanna get that, please do that now. A reminder that in the docs tab, there's also that document crunch one pager. So if you just want a nice sort of concise, overview, that's there. So feel free to grab that and download it before we wrap. We're gonna be giving away our prize here in just a few seconds. Again, we've got that $250 Amazon gift card up for grabs. But as I'm giving or announcing that, we're also gonna open a quick survey. This is really a ten to thirty second pulse check. You're gonna see that in the chat box, q and a area. This is just from us here at Smart Brief to see how you enjoy the webinar, did it meet your needs and expectations, how's the platform, all the bells and whistles, that sort of thing. Though with that, let's give this prize away. Our lucky winner today is Stacia Snow from Minnesota. So congratulations. We're gonna reach you by email and make sure you get that prize sent over to you there. And with that, I just wanna give one final round of thanks. So, obviously, thanks to DocumentCrunch for making today possible. Thanks to our speakers for being here answering so many questions, and thanks to all of you for being here in the audience, filling out the polls, answering… Or not answering, asking a lot of questions, and, and just being so active in this chat. Hopefully, you learned a lot. Hopefully, this is something that will serve you. And if you want to check out any other webinars, of course, you can go to events.smartbrief.com. But until our next time here on a session together, I wish you all a fantastic rest of the day. Take care all.

Please provide citations & attributions for any information you generate from this content, thank you.