The Permit Was Approved. The Crew Still Couldn’t Start.

A practical approach to finding approved permits and coordinating work when contractors arrive.

A signed permit can establish that work is approved, but that does not help much if the people receiving a crew cannot find it.

For one commercial building, CoreData developed a browser-based Permit to Work application that brought the work schedule, permit status, contacts and signed paperwork together in one searchable view. The interface was deliberately simple, supported by enterprise infrastructure and access controls behind the scenes.

The Operational Problem

The building had an established permit form and approval process. The difficulty was managing and locating permits when contractors arrived, often early in the morning. Security and loading dock staff needed to identify the scheduled work, check its status and locate the signed form. A crew could arrive on the wrong date, a calendar entry could be incorrect, or several related work orders could make it difficult to identify the right permit. Resolving those questions could delay the crew and disrupt the tenant’s plans. The existing building-management tools and a subsequent SharePoint approach added complexity to a task that needed to be straightforward for the people at the point of arrival.

A Register Organized Around Scheduled Work

The application presented permits in a searchable grid sorted by date and time. Each record brought together the work description and type of service; the scheduled date and time; recorded status, such as approved, rejected, cancelled or deferred; building, tenant and contractor contacts and phone numbers; and a scanned copy of the signed permit. Phone numbers were prominent because when a crew was waiting, staff needed to reach the right person. The register organized information for daily use; the signed form remained the approval document.

Clear Roles and Responsibilities

Building administration maintained the records and manually updated their status. Security and loading dock staff had read-only access. The application had digital-signature capability, but the customer chose not to add another signature step. The existing signed permit remained in use, and the administrator’s status entry helped staff track it operationally. An approved status did not replace the signed permit or authorize work outside its approved scope. If a date or work order did not match, staff could search for related records and contact the administrator or tenant to resolve the discrepancy through the existing process.

Simple to Use, Supported by Enterprise Infrastructure

The application was designed around a focused task: find scheduled work, review the record and retrieve the permit. Browser-based access supported use across devices. Access used single sign-on; administrative changes and frontline lookup were separated by role; and redundant server and domain arrangements supported continued access. The result was a straightforward interface for daily users, backed by infrastructure and controls suited to the organization’s operating environment.

The Outcome

The recurring permit-management problems stopped after implementation. The customer identified the system’s simplicity as a key reason it worked, and the application remains in use today. The lesson was not that the permit form needed replacing. The opportunity was to make the right information accessible to the people who needed it, at the moment they needed it.

Is Your Permit Information Easy to Find?

If your approval process is established but staff still struggle to locate permits when crews arrive, CoreData can help examine the handoff between building administration, security, the loading dock and contractors. We can review the workflow and identify where a focused application might make it easier to coordinate the work.

Discuss your permit workflow