---Presenter: Kevin KramerSubject: Change RequestsDetails: What is a change request and how do we document?Duration: 00:20:27---00:00:00.020 --> 00:00:01.420 - Interquest 00:00:03.370 --> 00:00:07.716 - So. I think we all know what a change request is, but I'm just 00:00:07.716 --> 00:00:11.834 - going to kind of. High level cover it it's a change request 00:00:11.834 --> 00:00:15.057 - is any change the scope of the project. Anything that impacts 00:00:15.057 --> 00:00:18.280 - the delivery of the project from a budget, timeline or other 00:00:18.280 --> 00:00:19.745 - impact area of the project. 00:00:20.370 --> 00:00:23.604 - Um, so there's a challenge with the specific deliverable due to 00:00:23.604 --> 00:00:26.250 - unforeseen complexity. That's going to increase the budget. In 00:00:26.250 --> 00:00:29.484 - effect, the timeline that should be a change request, removal of 00:00:29.484 --> 00:00:33.012 - an item from scope should be a change request. If it's outside 00:00:33.012 --> 00:00:36.834 - of the discovery phase. Addition of an item to the scope is a 00:00:36.834 --> 00:00:40.860 - change request. And in the case of project like a DI, that's 00:00:40.860 --> 00:00:43.750 - even a change request in discovery. If it's a fixed 00:00:43.750 --> 00:00:48.100 - budget. Um, if there's a timeline change due to a client 00:00:48.100 --> 00:00:50.868 - machine required deliverables. That is technically a change 00:00:50.868 --> 00:00:53.636 - request our existing change request form doesn't really 00:00:53.636 --> 00:00:56.750 - support some of these other scenarios 'cause it's really 00:00:56.750 --> 00:01:00.556 - just an hours in a time and materials based change request. 00:01:01.260 --> 00:01:06.210 - So. Would that will cover in a minute the updated change 00:01:06.210 --> 00:01:09.906 - template that we've put together and kind of go over some detail 00:01:09.906 --> 00:01:13.910 - there? So how do we document it so the change request should be 00:01:13.910 --> 00:01:17.298 - loaded in base camp? Are possible you guys have made it 00:01:17.298 --> 00:01:20.070 - painfully clear that there are instances where client doesn't? 00:01:20.860 --> 00:01:25.161 - Use Basecamp so we should email those and management should be 00:01:25.161 --> 00:01:26.725 - copied on that documentation. 00:01:26.725 --> 00:01:31.390 - Uhm. This goes back to our back to the basics on how do we? Why 00:01:31.390 --> 00:01:34.270 - do we document? Because people like to leave things out when it 00:01:34.270 --> 00:01:35.470 - could get them in trouble. 00:01:36.050 --> 00:01:40.060 - Um, specifically our client PMS that are working on projects. 00:01:40.800 --> 00:01:45.147 - So uhm, and then the last component here is. 00:01:45.960 --> 00:01:48.494 - Less of a healbot more of A. 00:01:49.470 --> 00:01:52.580 - We should get a documented approval back before we start 00:01:52.580 --> 00:01:56.001 - any work and that should be an email approving. It assigned 00:01:56.001 --> 00:01:59.111 - change requests coming back to us. A base camp message 00:01:59.111 --> 00:02:02.221 - approving it, or recorded phone call with associated notes that 00:02:02.221 --> 00:02:03.465 - document the verbal approval. 00:02:04.290 --> 00:02:07.362 - Now I do know that some of you have stronger feelings about 00:02:07.362 --> 00:02:08.898 - making sure we have a signed 00:02:08.898 --> 00:02:12.380 - document. Um, and as long as that's not slowing down your 00:02:12.380 --> 00:02:15.040 - project, I encourage you to push that with your clients. 00:02:15.610 --> 00:02:19.198 - But if we can't get that done and it starts to slow things 00:02:19.198 --> 00:02:22.510 - down where we can't get work when you know it's an approved 00:02:22.510 --> 00:02:26.098 - thing, we need to look at the other methods. Just as long as 00:02:26.098 --> 00:02:27.754 - it's documented in one of these 00:02:27.754 --> 00:02:31.370 - forms. I do not want to encourage the last one, but 00:02:31.370 --> 00:02:34.620 - worst case scenario we can do it. We need to send the change 00:02:34.620 --> 00:02:38.330 - request document it. And kind of put that it was approved on the 00:02:38.330 --> 00:02:41.074 - phone call when that call was, and so on. What kind of show you 00:02:41.074 --> 00:02:45.828 - some of that? So I will actually pull up the form. Uh, as we kind 00:02:45.828 --> 00:02:49.056 - of go through the discussion, but I just wanted to give you 00:02:49.056 --> 00:02:50.939 - guys a quick overview of what it 00:02:50.939 --> 00:02:53.898 - looks like. So these are just screenshots taken from Excel. 00:02:53.898 --> 00:02:57.811 - That's why you have that page one there. So this is the first 00:02:57.811 --> 00:03:01.122 - page we got our change request header or brief description. The 00:03:01.122 --> 00:03:04.433 - change request detail. There are instances where you may not have 00:03:04.433 --> 00:03:08.045 - any hours or anything to adjust here, so you would just delete 00:03:08.045 --> 00:03:12.116 - this section. Um, going forward. We've got the. 00:03:12.760 --> 00:03:16.169 - Uh, additional totals for quality assurance testing 00:03:16.169 --> 00:03:19.578 - meetings, project management. Those are are already 00:03:19.578 --> 00:03:21.526 - calculating using our standard 00:03:21.526 --> 00:03:23.350 - percentages. Excuse me 00:03:24.010 --> 00:03:25.935 - And then total up at the bottom. 00:03:26.660 --> 00:03:30.599 - Uh, the new section of edit is the project impacts. So when I 00:03:30.599 --> 00:03:33.629 - built our original change request form, I was only about 00:03:33.629 --> 00:03:37.568 - four months in it clarity and we just don't have a good process 00:03:37.568 --> 00:03:41.204 - and I kind of slapped one together when I built this one. 00:03:41.204 --> 00:03:45.143 - I went and looked at about 20 to 30 different examples online on 00:03:45.143 --> 00:03:47.567 - how different companies document change request in different 00:03:47.567 --> 00:03:51.506 - ways. And since I saw Garrett online, he got the honor of kind 00:03:51.506 --> 00:03:52.718 - of giving me feedback. 00:03:53.300 --> 00:03:58.604 - Which was little brutal in places, um so. 00:03:58.610 --> 00:04:00.765 - I 00:04:00.765 --> 00:04:06.760 - what? He picks it up the next time, OK? 00:04:07.760 --> 00:04:11.434 - Uh, so just kind of scope, budget, timeline risk? What kind 00:04:11.434 --> 00:04:15.442 - of go through? How to fill those out in just a second? 00:04:15.970 --> 00:04:20.806 - Uhm, and then I've added a new disclaimer and a couple other 00:04:20.806 --> 00:04:24.064 - things there. And there's a couple of fields will want to 00:04:24.064 --> 00:04:27.088 - talk through and figure out how we want to best use them as a 00:04:27.088 --> 00:04:30.112 - team or even want to keep them so will go through that from a 00:04:30.112 --> 00:04:31.408 - high level on what is changed. 00:04:31.970 --> 00:04:34.913 - Um, if someone does not believable it wanted, the 00:04:34.913 --> 00:04:38.183 - formatting has been improved to make it look more professional, 00:04:38.183 --> 00:04:39.491 - please tell me now. 00:04:40.230 --> 00:04:44.468 - And I'll just stop and go try again. Um, the payment terms are 00:04:44.468 --> 00:04:48.380 - now defined in the header, so it's clear that is a toggleable 00:04:48.380 --> 00:04:51.640 - option. The codes for different things have been simplified and 00:04:51.640 --> 00:04:55.226 - modified. The rates are modified by the payment terms selected at 00:04:55.226 --> 00:04:59.421 - the top. PM meetings, QA have all been updated into auto 00:04:59.421 --> 00:05:03.114 - calculate. Uh, we've added the general description to header, 00:05:03.114 --> 00:05:06.336 - added the project impacts summary in approval section, and 00:05:06.336 --> 00:05:08.842 - then some additional rewarding on the disclaimer. 00:05:09.720 --> 00:05:14.241 - So what I've called out here is kind of what we're. 00:05:15.060 --> 00:05:17.825 - Expecting in those different sections, and they're 00:05:17.825 --> 00:05:19.405 - essentially just note sections. 00:05:19.930 --> 00:05:24.415 - Um, so they're designed for you guys to call out any risk and 00:05:24.415 --> 00:05:28.210 - help you with the expectation management side of the house. So 00:05:28.210 --> 00:05:31.315 - if something clearly calls out if it's In addition, 00:05:31.315 --> 00:05:34.420 - modification, removal scope, or you're expecting this to cause 00:05:34.420 --> 00:05:37.870 - additional scope creep based on the discussions for the change 00:05:37.870 --> 00:05:41.610 - request. Things like that can easily be called out in the 00:05:41.610 --> 00:05:45.063 - scope section. Budget if it's a really risky estimate. Uhm, and 00:05:45.063 --> 00:05:49.054 - we may be already padded it band. I can think of tons of 00:05:49.054 --> 00:05:52.124 - places where you could have called this out with better. 00:05:52.124 --> 00:05:56.115 - That would have helped and giving you a point to be like we 00:05:56.115 --> 00:05:58.264 - said so over here that this is 00:05:58.264 --> 00:06:02.148 - potential. Timeline Gary This is something you have been asking 00:06:02.148 --> 00:06:07.244 - for for a long, long time. When we submit a change request to 00:06:07.244 --> 00:06:10.380 - preemptively call out the potential effects to the 00:06:10.380 --> 00:06:14.590 - timeline. And then risk if there are potential risks to other 00:06:14.590 --> 00:06:18.011 - sections of the project to kind of make sure we're documenting 00:06:18.011 --> 00:06:19.255 - those in reviewing them. 00:06:20.230 --> 00:06:25.066 - So those are the big changes and I will go ahead and. 00:06:25.720 --> 00:06:28.250 - Pause the slide show for a moment because our next section 00:06:28.250 --> 00:06:29.630 - would be to discuss the feedback 00:06:29.630 --> 00:06:33.720 - for the new template. So I'm gonna go ahead and pull that up 00:06:33.720 --> 00:06:35.460 - and we can talk through it. 00:06:36.110 --> 00:06:39.482 - And we can kind of show you guys how it functions and. 00:06:40.220 --> 00:06:45.628 - Give me any feedback or things that you think we need to add, 00:06:45.628 --> 00:06:47.292 - subtract and whatnot so. 00:06:47.920 --> 00:06:52.036 - I will take a deep breath and let you guys kind of jump in 00:06:52.036 --> 00:06:53.506 - with any questions or concerns. 00:06:59.340 --> 00:07:04.306 - I've already been through it once. I guess what I have is a 00:07:04.306 --> 00:07:08.508 - question slash idea sort of thing. How do you feel and 00:07:08.508 --> 00:07:13.474 - this is something that I had had to do with center just due 00:07:13.474 --> 00:07:17.294 - to the fact that the change requests is essentially their 00:07:17.294 --> 00:07:18.440 - form of invoicing. 00:07:20.310 --> 00:07:25.540 - Where I've been creating just multiple sheets on one workbook. 00:07:26.050 --> 00:07:29.515 - And having a different change request on each one of those 00:07:29.515 --> 00:07:32.980 - sheets also doable with this. Yeah, of course, but I'm just 00:07:32.980 --> 00:07:36.760 - wondering since I just never have never brought it up due to 00:07:36.760 --> 00:07:40.540 - the fact that it hasn't come up anywhere. What are your thoughts 00:07:40.540 --> 00:07:44.635 - about that? Do you think that's a good idea? Just have like 1 00:07:44.635 --> 00:07:47.785 - centralized workbook that has a change request for every change 00:07:47.785 --> 00:07:51.565 - request that's come up for that project, so you can almost just 00:07:51.565 --> 00:07:55.345 - make one. That's like, you know this is Project X is change 00:07:55.345 --> 00:07:59.440 - request workbook. I think that is a fantastic idea. I like that 00:07:59.440 --> 00:08:03.496 - idea for you guys to have one workbook that stored in teams 00:08:03.496 --> 00:08:07.214 - that has all the change request advertised to the project or 00:08:07.214 --> 00:08:09.580 - it's all in one file. I think 00:08:09.580 --> 00:08:13.340 - that's. A magical thing that we should do, Daniel that is an 00:08:13.340 --> 00:08:14.380 - excellent idea. Yeah, great. 00:08:14.880 --> 00:08:22.210 - OK, cool. Are you saying that that is for internal use or 00:08:22.210 --> 00:08:24.178 - for external user both? 00:08:24.180 --> 00:08:28.296 - I think that could be depending on the client. I have always 00:08:28.296 --> 00:08:31.040 - preferred printing them to PDF and sending them. 00:08:31.620 --> 00:08:35.899 - Yeah, that's fine and they can't change anything or see our 00:08:35.899 --> 00:08:39.870 - formulas. Specifically, is the reason I prefer them to go, uh, 00:08:39.870 --> 00:08:43.225 - as a PDF, but I think from an internal standpoint where 00:08:43.225 --> 00:08:47.495 - someone was like hey go get me all my change request. If it was 00:08:47.495 --> 00:08:51.460 - all in one file that would make it super easy for you. Yeah, 00:08:51.460 --> 00:08:54.510 - that's super beneficial from an internal standpoint and then you 00:08:54.510 --> 00:08:57.865 - can literally just print any one of those worksheets inside that 00:08:57.865 --> 00:09:01.830 - workbook as a PDF and that's how you share it with the client. 00:09:01.830 --> 00:09:05.490 - But for internal purposes, I love that that's great date or a 00:09:05.490 --> 00:09:08.540 - feature. You can name it whatever it needs to be. 00:09:08.590 --> 00:09:11.518 - Yeah, you know no. 00:09:11.520 --> 00:09:17.300 - Map or. I don't know why I didn't think of that sooner. 00:09:17.300 --> 00:09:18.890 - That's an awesome idea actually. 00:09:18.900 --> 00:09:26.320 - Get rid of that address your question correctly or OK. 00:09:27.340 --> 00:09:30.470 - Uhm, I have another question that you can't really see 00:09:30.470 --> 00:09:33.287 - because we we you can't really see the formulas. 00:09:34.460 --> 00:09:38.932 - I don't like the formulas 'cause I think that more PM time is 00:09:38.932 --> 00:09:42.028 - needed, especially on high change request projects I or 00:09:42.028 --> 00:09:45.812 - meeting time is needed as well. Currently the meeting time is 00:09:45.812 --> 00:09:49.940 - rounded up from 5% on project, management is rounded up from 15 00:09:49.940 --> 00:09:55.100 - and then QA is rounded up from 15 as well. I think those are a 00:09:55.100 --> 00:09:59.572 - bit light, but I know that that is also what Ron estimates on 00:09:59.572 --> 00:10:04.388 - his template as well. Typically when I sent them out I do QA for 00:10:04.388 --> 00:10:06.796 - 20 meeting for 10:00 AM PM for 00:10:06.796 --> 00:10:10.374 - 15. We need to be consistent with sales on this. Or would it 00:10:10.374 --> 00:10:13.311 - matter, Kevin? So here's the thing. And this has happened to 00:10:13.311 --> 00:10:14.379 - us in the past. 00:10:15.640 --> 00:10:21.828 - 15 percent, 5% in 15% at the 35% Uplift on the development hours. 00:10:22.590 --> 00:10:26.880 - So at 10 hour task is getting an additional 4 hours for the. 00:10:27.950 --> 00:10:31.369 - For you guys to manage it and it shouldn't take more than four 00:10:31.369 --> 00:10:32.947 - hours to test and manage that 00:10:32.947 --> 00:10:38.538 - piece. Uhm, I do think, uh, there is grounds to 00:10:38.538 --> 00:10:41.198 - say that you know, uhm? 00:10:42.560 --> 00:10:45.644 - If you have a client where you're like, Hey, you guys are 00:10:45.644 --> 00:10:48.471 - requesting lots of stuff, I'm going to add a supplemental line 00:10:48.471 --> 00:10:51.041 - item for supporting for your custom reporting. Each time we 00:10:51.041 --> 00:10:54.382 - have to do a change request and adding hours in there, I think 00:10:54.382 --> 00:10:57.723 - that would be acceptable. I also have no problem as long as it's 00:10:57.723 --> 00:11:00.293 - clearly communicated to your client. If you guys coming in 00:11:00.293 --> 00:11:03.891 - and changing this formula value if you want, I can put this in a 00:11:03.891 --> 00:11:04.919 - config table that's hidden. 00:11:05.450 --> 00:11:08.070 - Uhm, but increasing these values over what their original project 00:11:08.070 --> 00:11:11.476 - was called out for does need to be approved. And Garrett, I do 00:11:11.476 --> 00:11:14.358 - know there are situations in your case where that would be 00:11:14.358 --> 00:11:18.288 - the case, so if we would like I can move this out to your config 00:11:18.288 --> 00:11:21.694 - table that you guys can hide and unhide and make changes to those 00:11:21.694 --> 00:11:26.554 - values. Well, I think if we're going to print a PDF that won't 00:11:26.554 --> 00:11:30.598 - be necessary, so that's for you to control Garrett so you don't 00:11:30.598 --> 00:11:32.283 - have to have control that. 00:11:32.590 --> 00:11:35.230 - Change that in Excel. 00:11:35.230 --> 00:11:41.920 - OK, yeah. It's like also on and then I'm going to use you HD 00:11:41.920 --> 00:11:46.600 - is an example. They would use a lot of meeting time for bringing 00:11:46.600 --> 00:11:50.920 - developers on for meetings, or if they were doing a lot of 00:11:50.920 --> 00:11:54.520 - training or documentation, would you recommend that that is added 00:11:54.520 --> 00:11:59.200 - along with like QA and meeting stuff? Or would you add that as 00:11:59.200 --> 00:12:02.800 - an additional item that would then also invited QA meeting 00:12:02.800 --> 00:12:06.400 - some project management? I would buffer that into the requested 00:12:06.400 --> 00:12:10.210 - change. So I think, uhm. And since we have the unique 00:12:10.210 --> 00:12:13.301 - experience of having Jim here, I think for things like the 00:12:13.301 --> 00:12:15.549 - integration where he had requested that he probably 00:12:15.549 --> 00:12:18.359 - wouldn't argue if we added another 15 hours to that, 00:12:18.359 --> 00:12:21.731 - because we knew we were going to have the developers on phone 00:12:21.731 --> 00:12:26.030 - calls. I would not have at all, so I think it 00:12:26.030 --> 00:12:27.398 - just really becomes a. 00:12:28.500 --> 00:12:32.112 - I mean, each of your clients is different. I don't want to 00:12:32.112 --> 00:12:35.724 - dictate it to the point where you guys can't adjust for your 00:12:35.724 --> 00:12:38.009 - different clients. So I think. 00:12:38.800 --> 00:12:41.506 - This is a good starting place and should be our standard 00:12:41.506 --> 00:12:44.458 - staple template. But if you guys need to adjust formulas or add 00:12:44.458 --> 00:12:45.688 - things in a certain way. 00:12:46.310 --> 00:12:49.742 - I'm completely open to letting you do that. We have to manage 00:12:49.742 --> 00:12:50.886 - to our clients expectations. 00:12:52.090 --> 00:12:54.140 - So I have no problem. 00:12:55.240 --> 00:12:57.627 - Saying you guys can make slight adjustments based on the project 00:12:57.627 --> 00:13:00.014 - you're dealing with. Also, if anyone thinks they can make it 00:13:00.014 --> 00:13:02.618 - look better, you're welcome to take this and try and stash it 00:13:02.618 --> 00:13:07.247 - up to. OK, hard pass on design but uhm so we would just then if 00:13:07.247 --> 00:13:10.595 - we're going to try and make adjustments or we would need to 00:13:10.595 --> 00:13:13.385 - approve those with the client, approve those of Management and 00:13:13.385 --> 00:13:15.059 - then change them on the sheet 00:13:15.059 --> 00:13:20.130 - before we. Bring the PDF and send them off. You got it, 00:13:20.130 --> 00:13:24.496 - thanks. Quick question on this and this is I guess for that 00:13:24.496 --> 00:13:25.720 - meetings in Project Management. 00:13:26.860 --> 00:13:30.838 - Would it be wise for those to be kind of a standard description 00:13:30.838 --> 00:13:34.816 - thing that maybe has some call outs like kind of to what you 00:13:34.816 --> 00:13:37.876 - were just bringing up their Garrett like the meeting? These 00:13:37.876 --> 00:13:40.630 - are internal meetings or whatever you know, whatever kind 00:13:40.630 --> 00:13:44.914 - of call it we want to have for that, just so when they get 00:13:44.914 --> 00:13:48.892 - them. This has a asterisk aura got no. Don't say gotcha, but it 00:13:48.892 --> 00:13:51.952 - is essentially gotcha. So what am I going to do? 00:13:52.030 --> 00:13:54.648 - These meetings, these are internal meetings, project 00:13:54.648 --> 00:13:55.770 - management this includes. 00:13:56.320 --> 00:13:59.609 - Time, you know project meetings with client. You know those kind 00:13:59.609 --> 00:14:02.898 - of things. So we have basic standard ones there. Daniel, but 00:14:02.898 --> 00:14:05.290 - I think if you guys want to put 00:14:05.290 --> 00:14:09.547 - something together. For that, an kind of make that the standard 00:14:09.547 --> 00:14:13.320 - in the template I would endorse and support that 100% cool. 00:14:13.990 --> 00:14:17.206 - Rest of team. What do you guys think about something like that? 00:14:17.206 --> 00:14:20.958 - Just so we have it on there? 'cause I know that one of the 00:14:20.958 --> 00:14:24.442 - things that I've gotten, I don't want to say feedback I think is 00:14:24.442 --> 00:14:27.926 - really the most blunt way to say it of wanting more details on 00:14:27.926 --> 00:14:28.998 - that style of thing. 00:14:29.640 --> 00:14:34.294 - Would that be something you guys could see being good? Or do you 00:14:34.294 --> 00:14:38.590 - think that pigeon holds us too much? I mean, if you're talking 00:14:38.590 --> 00:14:42.170 - about adding more detail to each line item, maybe I 00:14:42.170 --> 00:14:45.034 - misunderstood, but is that what you're saying specifically? 00:14:45.034 --> 00:14:48.972 - Having standard ones here? Been looking at this meeting so it's 00:14:48.972 --> 00:14:52.194 - not like these meetings. These are internal meetings or 00:14:52.194 --> 00:14:56.132 - whatever. Whatever it is we want to specifically outline that to 00:14:56.132 --> 00:14:58.996 - be project manager access specifically done for managing 00:14:58.996 --> 00:15:00.070 - your project and. 00:15:00.100 --> 00:15:02.290 - You know pending emails you etc. 00:15:03.430 --> 00:15:06.979 - OK, I mean, Yeah 'cause I each each uh change request is always 00:15:06.979 --> 00:15:09.982 - you know different obviously so we put our description in there, 00:15:09.982 --> 00:15:14.077 - but as far as standard ones go? I mean, if you want to have it 00:15:14.077 --> 00:15:17.080 - already filled out like it? Does here with the project management 00:15:17.080 --> 00:15:18.718 - one, I guess that would be. 00:15:19.290 --> 00:15:22.122 - For some samples or something, and I'll let you guys have seen 00:15:22.122 --> 00:15:25.426 - all the time, I'll let you guys as a team take those off line 00:15:25.426 --> 00:15:28.258 - and come up with the best wording for those and I'll just 00:15:28.258 --> 00:15:31.090 - give my nod once it's done or give you guys any feedback. 00:15:33.650 --> 00:15:37.190 - That's fine, I already gave that feedback, so I agree. But yeah, 00:15:37.190 --> 00:15:40.435 - we can come up with ideas and then let you know. 00:15:42.020 --> 00:15:45.529 - I've been told I'm bad at Delegating. I'm trying to work 00:15:45.529 --> 00:15:47.443 - on that, so Congrats, more work 00:15:47.443 --> 00:15:50.550 - for you guys. I got 00:15:50.550 --> 00:15:54.546 - it. The biggest thing is that used to we guys had a whole 00:15:54.546 --> 00:15:57.282 - bunch of codes for you guys to tide to the different rates. 00:15:57.800 --> 00:16:02.384 - Uhm, I have simplified this. So you get your back and your 00:16:02.384 --> 00:16:03.912 - consulting your front end 00:16:03.912 --> 00:16:08.044 - licensing another. Uh, so if I chose back in, for instance, 00:16:08.044 --> 00:16:11.080 - it's automatically update the rates if I change this to pay 00:16:11.080 --> 00:16:13.012 - upon completion, it's automatically going to adjust 00:16:13.012 --> 00:16:16.600 - all of that as well, so you're only having to change it once 00:16:16.600 --> 00:16:19.912 - instead of in 15 places. If you guys have something like a 00:16:19.912 --> 00:16:22.672 - license, you'll notice that this throws an error, and that's 00:16:22.672 --> 00:16:25.432 - because it's going to overwrite this formula with the cost. 00:16:26.170 --> 00:16:30.566 - It says enter cost but it cuts it off. Um, so for this, if 00:16:30.566 --> 00:16:33.706 - someone says they want to add the multi store functionality, 00:16:33.706 --> 00:16:37.788 - you would just type, you know 5000 in here. If it's a $5000 00:16:37.788 --> 00:16:39.358 - license and in that would. 00:16:41.070 --> 00:16:43.366 - Need to carry over here, which it doesn't. 00:16:44.750 --> 00:16:48.852 - I will need to fix a tiny bug there. Um, because if it's a 00:16:48.852 --> 00:16:51.782 - license or other, it wouldn't actually multiply and then I 00:16:51.782 --> 00:16:54.126 - need to take it out of the hours 00:16:54.126 --> 00:16:57.308 - calculation too. Because I think we've all seen the 00:16:57.308 --> 00:17:00.870 - errors to go out on invoices or the hours are wrong, or it 00:17:00.870 --> 00:17:03.062 - doesn't match because the hours, some included something 00:17:03.062 --> 00:17:04.706 - that was not an hour so. 00:17:05.780 --> 00:17:08.600 - I will make those tweaks over the weekend an update 00:17:08.600 --> 00:17:10.010 - that part of the template. 00:17:11.310 --> 00:17:13.926 - So, but does that make sense? 00:17:14.880 --> 00:17:19.404 - Goodman no yeah I was gonna ask does it? That's great. Does this 00:17:19.404 --> 00:17:23.928 - whole thing print to one page still or like it does go off 00:17:23.928 --> 00:17:26.016 - into 2 pages of the project 00:17:26.016 --> 00:17:29.144 - impacts? That's mainly because they have these a little bit 00:17:29.144 --> 00:17:32.816 - spaced and a disclaimer is much larger than it used to be. 00:17:33.460 --> 00:17:39.478 - OK um. Wonder if there's a way to clean that up, some at the 00:17:39.478 --> 00:17:43.006 - page break, but I guess it's going to change depending on the 00:17:43.006 --> 00:17:46.240 - number of lines you add. So yeah, that's why I typically 00:17:46.240 --> 00:17:49.768 - printed to PDF, 'cause then they can see that it doesn't. It 00:17:49.768 --> 00:17:51.188 - keeps going. Kind of shows it 00:17:51.188 --> 00:17:55.390 - running. Uhm, yeah, that's cool. No big deal, but if you 00:17:55.390 --> 00:17:58.486 - have very simple descriptions then you can collapse these 00:17:58.486 --> 00:17:59.862 - down to one line. 00:18:00.980 --> 00:18:04.660 - That helps, and if you're not using sections of the 00:18:04.660 --> 00:18:07.604 - project impacts, you guys can delete those out. 00:18:08.780 --> 00:18:10.499 - So and then. 00:18:11.130 --> 00:18:14.265 - Uh, this summary down here. So this actually pulls the total 00:18:14.265 --> 00:18:15.975 - change in hours in the total 00:18:15.975 --> 00:18:19.582 - change in cost. The status dropdown geared I know is one of 00:18:19.582 --> 00:18:20.950 - the things you had a question 00:18:20.950 --> 00:18:25.085 - about. Especially if we're going to do the multiple sheets in a 00:18:25.085 --> 00:18:28.790 - row, I think that's probably why a lot of the templates had this 00:18:28.790 --> 00:18:32.210 - in it. So once you have it approved, you can market as 00:18:32.210 --> 00:18:35.630 - approved so you can. You can document when it was approved on 00:18:35.630 --> 00:18:38.886 - or whatever. Who was it? A provide. You had a signature 00:18:38.886 --> 00:18:39.738 - you could like. 00:18:40.880 --> 00:18:43.604 - Put a link to where the sign version was loaded or something 00:18:43.604 --> 00:18:44.966 - like that so you have reference 00:18:44.966 --> 00:18:50.660 - points. Um? And in the disclaimer, if you guys 00:18:50.660 --> 00:18:54.840 - don't like the way this is written, I would encourage you 00:18:54.840 --> 00:18:56.360 - guys to run past. 00:18:56.960 --> 00:19:00.446 - Rewrite it and kind of run it. Past CRI just kind of put my 00:19:00.446 --> 00:19:01.442 - thoughts. It takes immigrants 00:19:01.442 --> 00:19:02.438 - feedback and incorporated it. 00:19:03.120 --> 00:19:09.026 - Um? But these are things like that. Kristen is asked for for 00:19:09.026 --> 00:19:12.830 - the taxes. Which it says that these are still a best estimate. 00:19:12.830 --> 00:19:15.341 - We haven't gone into the technical details. I haven't 00:19:15.341 --> 00:19:18.689 - gone in pre built the code and that's what I'm charging you 00:19:18.689 --> 00:19:22.559 - for. Yeah, we also added this call out to regression. 00:19:23.070 --> 00:19:23.980 - Um? 00:19:25.450 --> 00:19:28.629 - And this is something Garrett suggested adding, so I just want 00:19:28.629 --> 00:19:32.097 - you guys to be able to read through this and look through 00:19:32.097 --> 00:19:35.854 - it. I posted this in the PM channel earlier today and so any 00:19:35.854 --> 00:19:38.744 - feedback is welcome and you guys don't necessarily need my 00:19:38.744 --> 00:19:42.790 - blessing. But if you guys want to read this and run it past CR, 00:19:42.790 --> 00:19:45.380 - that's fine. So at one. 00:19:46.360 --> 00:19:48.810 - The second to last word is applica pull instead of 00:19:48.810 --> 00:19:51.505 - Bowl. You can just go to be there that be great. 00:19:54.380 --> 00:20:00.000 - Yeah. What doesn't do a spell check? 00:20:00.580 --> 00:20:08.322 - March. All right, uhm? Lisa doesn't underline 00:20:08.322 --> 00:20:11.283 - in bright red. 00:20:12.000 --> 00:20:16.512 - Uh, so any other thoughts guys? Did we agree that this is 00:20:16.512 --> 00:20:21.776 - better? It may not be perfect, but it is at least better. It is 00:20:21.776 --> 00:20:25.160 - better. Yeah, for real thank you. Yeah, I agree.