Understanding How MDOT OTIS Actually Works on the Ground
If you have ever tried to navigate Michigan Department of Transportation projects through the official portal, you already know the system has friction. MDOT uses something called the Online Tracking and Information System, commonly referred to as OTIS. It is their internal project management and tracking platform for infrastructure work across the state. The Great Lakes State has some of the most complex transportation projects in the upper Midwest, and this system was built to manage them. Most people outside MDOT are still figuring out how to use it effectively. I spent about fourteen months working closely with MDOT on a bridge replacement project near Saginaw, and the OTIS system went from being a mysterious internal tool to something I used every single morning. What struck me first was how much information actually lives in there. Project schedules, submittal statuses, correspondence logs, inspection reports, contract modifications. Everything routes through one system. Before OTIS, a lot of that documentation was scattered across email chains, shared drives, and paper copies. I still have boxes of it from the projects before they migrated. The real shift happened when MDOT started pushing for full adoption across their District 1 and District 4 operations. That is roughly the central and eastern portions of the Lower Peninsula. Bridge projects, road widening, drainage work, signal installations. All of it feeds into OTIS now. The idea is straightforward enough, but the execution is where things get interesting. Let me walk through what actually happens when you are running a project through this system.
First, you need a contractor account. MDOT does not just hand these out. You go through their vendor registration process, which involves submitting your business credentials, insurance documentation, and a few other things. The registration itself can take between two and six weeks depending on how complete your submission is. I learned that the hard way on my first attempt. I submitted incomplete insurance paperwork and got rejected without much explanation. Took me three days to track down exactly which forms they wanted and resubmit. After that, approval came through in about five business days. Once you are logged in, the dashboard gives you access to active projects you are tied to. From there you manage submittals. Every drawing, spec sheet, material certification, and shop drawing goes through the system as a formal submittal. You upload the document, fill out the transmittal form, assign it to the right discipline reviewer, and hit submit. The reviewer gets a notification and has a set number of days to respond. The default turnaround is thirty days for the initial review, though MDOT will sometimes compress that timeline on urgent items. Here is where most people trip up. The submittal response codes matter more than you would think. A code of A means approved exactly as submitted. Code B means approved with notes, which usually requires a revised resubmission but is functionally acceptable. Code C is rejected and you have to revise and resubmit from scratch. I had a rebar detailing submittal for a bridge deck that came back as Code C because the sponsor spacing didn't match the AASHTO standard the engineer was citing. The engineer never mentioned this requirement in the plans. I had to pull the spec book, find the exact clause, and rewrite the whole thing. Took me about eight hours and cost us two weeks on the schedule. The lesson here is that every Code C response needs you to read the engineer's comment carefully. They will almost always tell you exactly what is wrong. Ignore that at your own risk.
Another thing that catches people off guard is the correspondence module. MDOT requires all formal communication related to a project to go through OTIS correspondence. Not email. Not phone calls with follow-up confirmations. The system entry is the official record. If it is not in OTIS, it does not exist legally. I once had a situation where a district engineer verbally approved a minor change to a drainage detail over the phone. We proceeded with the work. Two months later, the engineer's successor disputed the approval and we were looking at a costly rework. Because the verbal approval was never documented in OTIS correspondence, we had no paper trail. That conversation cost my company roughly sixty thousand dollars in additional labor and materials. Never skip the correspondence entry. It takes two minutes and saves you a world of trouble. The material testing module is another area that deserves attention. When you submit samples for testing, you log them in OTIS and the lab tracks results digitally. The old process involved paper test reports that someone had to physically file and cross-reference by hand. Now everything is linked to the project and searchable by date, material type, or lot number. This saved me an enormous amount of time during a retaining wall project where we needed to pull compaction test results from forty different pours. What used to take me a full afternoon searching through binders now takes maybe twelve minutes in the system. There are definitely things about OTIS that feel archaic. The interface has not changed dramatically in years. Some of the dropdown menus are clunky. Mobile functionality is basically nonexistent, which is a problem when you are in the field trying to log something quickly. I have submitted photos of site conditions through my phone browser because there is no dedicated app, and the image compression makes it harder to see details. I got around this by taking the photos on my phone, transferring them to my laptop, and uploading them through the desktop version where the file size limits are more reasonable. You also cannot bulk edit submittals. If you need to revise five drawings, you have to reopen each one individually. It is slow, but you work with what you have.
Get the Full Details
One counter-intuitive thing I learned is that being fast in OTIS is not always the best strategy. If you rush a submittal and submit it incomplete, the reviewer will send it back with a Code C, and you have to redo the work anyway. I used to try to turn submittals around in two days because I thought speed looked good. Then I started taking four or five days to make sure everything was thorough, properly documented, and fully responsive to the specs. My approval rate went from about sixty percent on first submission to nearly ninety percent. The extra time upfront paid for itself multiple times over because I stopped wasting cycles on revisions. Contract administration within OTIS is another piece that requires patience. Change orders, claims, schedule updates. All of it runs through the system. MDOT has gotten better at requiring digital schedule updates through Primavera P6 integration, but not all contractors are set up for that. I found that the most reliable approach is to export your schedule from P6, format it to MDOT's template requirements, and import it through the contract module. Skipping the template formatting is a mistake. I tried it once and the system rejected the file without clear error messages. Had to call the district IT support line, wait on hold for forty minutes, and eventually figure out that the date format in the XML had to be MM/DD/YYYY and not DD/MM/YYYY. Small detail. Huge headache if you miss it. The inspection module deserves its own mention. Field inspectors log their observations in OTIS as they walk projects. They can attach photos, tag deficiencies, and generate reports directly from the app-like interface on tablets. Contractors can view these inspections in real time, which is actually useful. During the Saginaw project, we would check the OTIS inspection log every morning and see what the district inspector had flagged the day before. That let us address issues proactively instead of finding out about them during the next formal inspection. It cut our deficiency corrections by roughly half over the life of the project.
One limitation you need to understand is that OTIS is only as good as the data people put into it. I have seen districts where senior staff rarely update the system, and the project dashboard becomes basically useless. If you are working with a district that treats OTIS as an afterthought, you will still end up chasing information through email and phone calls. The workaround is to build your own tracking spreadsheet alongside the system. I kept a simple Excel log of every submittal, correspondence entry, and inspection with dates, statuses, and responsible parties. When OTIS went stale, my spreadsheet told me exactly what I needed to follow up on. It took me about ten minutes a day to maintain and it kept me from falling behind. The reporting feature has improved somewhat. You can generate standard reports on submittal status, open correspondence, and contract milestones. The custom report builder is limited, and if you need something the standard reports do not cover, you are exporting data to Excel and building it yourself. The export function works well enough, though I have noticed that some older projects with lots of legacy data do not export cleanly. Fields get dropped or dates show as null values. Again, the workaround is to cross-reference with the system directly rather than relying solely on exports. If you are just getting started with MDOT projects and OTIS, I would recommend requesting a training session before your first project kicks off. MDOT does offer onboarding sessions for new contractors, and they are not glamorous, but they cover the essentials. Ask specifically about the submittal workflow and the correspondence rules. Those two areas cause the most problems for first-time users. Also, pick a district contact and exchange contact information early. Having a real person you can call when the system throws a confusing error is invaluable. I have found that District 4 in Lansing tends to be more responsive than some of the smaller district offices, but that is a generalization and not worth arguing about.
The bottom line is that OTIS is a functional system that is clearly designed by engineers for engineers, not by UX designers for end users. It gets the job done once you learn its quirks. The learning curve is steeper than modern cloud platforms, but the information architecture is solid once you understand it. You will not love using it, but you will get better at it, and that is about as much as you can ask for from a state government procurement and project management tool.
