Extra Work Orders

Purpose

Construction companies submit “extra work orders” to account for unplanned or extra work they do on a job site. These work orders were traditionally completed by hand and physically delivered to an approving authority. At Pepper, we determined that it was necessary to automate the extra work order process to expedite time to approval and tighten accountability of submitted work orders.

Method

I interviewed six members of Pepper Construction’s Self Perform Group to identify requirements for the technology solution. I then built initial mockups using Adobe XD to share with end users, gather their feedback, and iterate the design. Finally, I created the web application with the following technologies:

• Frontend: ASP.NET Core Blazor
• Backend: ASP.NET Core Web API, SQL Server Database

Blazor allowed me to create reusable web components, as I’d make with React or Angular, but written primarily in C# instead of JavaScript. I wanted to create a more seamless experience for the application’s users and write more manageable code but stay within the ASP.NET Core ecosystem.

Results

In its first year of use, the extra work order application has processed more than 37,000 hours of work on Pepper’s job sites, accounting for more than $1.1M dollars of labor cost. The web application significantly reduces the time to approve each work order and nullifies the chance of an individual losing a work order.