Hands-on training with permit management system, data entry, reporting functions, and troubleshooting. Covers system navigation and basic tasks.
2
hours
0.2
CEUs
Administrative, Legal & Management
1.7.4
Hands-on training with permit management system, data entry, reporting functions, and troubleshooting. Covers system navigation and basic tasks.
Format
On-Demand Online
Delivery
Self-Paced
Access
24/7 After Enrollment
Certification
Certificate of Completion
Have questions about this course or our platform?
Contact our support teamNavigate permit software system effectively
Permit-management software is the electronic replacement for the paper files and file-card systems that building departments relied on for decades. ICC's building department administration literature describes these systems as a set of digital tools that automate and streamline the permit process end to end: application intake, plan review, permit issuance and tracking, fee calculation and collection, inspection scheduling, posting of inspection results, project tracking, and overall workflow management. Whatever the vendor or the department's size, the organizing idea is the same — one shared record per project, visible to everyone who touches it. The permit technician who takes in the application, the plans examiner who reviews it, the inspector who visits the site, and the supervisor who signs the certificate of occupancy are all reading and writing the same record. When a new staff member opens a permit in the system, they are looking at the department's institutional memory of that project.
The record is organized around the permit lifecycle. A project enters as an application, moves through completeness screening and plan review, becomes an issued permit, accumulates inspection results, and closes with a final inspection and, where applicable, a certificate of occupancy. The software enforces this sequence through statuses and workflow steps: a permit cannot normally be issued while a plan-review task is open, an inspection cannot be scheduled on an application that has not been issued, and a certificate of occupancy checklist will not clear while required inspections or conditions remain outstanding. Learning to navigate the system largely means learning where each lifecycle stage lives on the screen — the application data, the fee ledger, the plan-review tasks and correction letters, the inspection history, any holds or conditions, and the attached documents.
Day to day, most staff interact with a handful of core functions: searching for records (by permit number, address, parcel, or applicant name), reading a record's current status, entering new information in their area of responsibility, and answering questions from the public. Systems differ in packaging — the administration literature distinguishes stand-alone single-function tools, integrated community-development suites that share data with planning, zoning, and code enforcement, and large enterprise platforms serving many departments — but the daily user experience of searching, reading, and updating records is common to all of them.
New users are not expected to learn the system alone. Departments that implement these systems typically designate team leaders or "superusers" — often the staff who worked with the vendor during implementation — to train and support their coworkers, and vendors provide training and ongoing support under service agreements. Many departments also maintain a training or test environment where new staff can practice entering applications and results without touching live records. The professional habit to build early: when unsure, ask or use the sandbox — never experiment on a real permit record.
A newly hired permit technician takes a counter visit from a homeowner who wants to know why her kitchen remodel permit "is taking so long." Rather than guessing or handing the question to a supervisor, the technician searches by address, opens the permit record, and reads the workflow: the application was accepted three weeks ago, plan review was completed last week, and a correction letter was sent to the applicant's designer requesting revised plans — the ball is in the applicant's court, not the department's. The technician shows the homeowner the correction letter in the record, prints a copy, and explains what the designer must resubmit. A conversation that could have ended in frustration ends with the homeowner knowing exactly what is holding up her project and what happens next. That is what the shared record is for: any trained staff member can give an accurate, current answer because the whole history is in one place.
The most common navigation mistakes are search mistakes: browsing lists instead of searching, searching only by permit number when the caller has only an address, or giving up when one search key fails instead of trying the parcel or applicant name. Others involve reading only part of the record — quoting a status without checking for holds, open conditions, or unpaid fees elsewhere on the record, so the answer given at the counter turns out to be wrong. New users also sometimes assume the public portal shows the same detail staff see, and either over-promise what an applicant can find online or fail to direct them to self-service options that exist. The corrections: learn every search key the system offers, read the whole record — status, holds, fees, conditions — before answering, learn what the portal actually displays, and route genuinely unclear situations to a superuser rather than improvising.
Enter and retrieve permit and inspection data
Everything the system produces — fee calculations, plan-review routing, inspection scheduling, reports, and ultimately the certificate of occupancy — is built from data that a person entered. The administration literature lists consistent data capture, reliable archiving, and a verifiable electronic audit trail among the core benefits of electronic permitting, but those benefits only materialize when entry is disciplined. The permit record is, in practical effect, the department's legal record of the project: it is what the department produces when a dispute, a claim, or a records request arrives years later. That gives routine data entry a significance new staff sometimes underestimate. The address and parcel linkage must be right, because every later lookup — by staff, by a title company, by a future owner — starts there. The permit type and project description must be right, because they drive which fees are calculated, which reviews are required, and which inspections are generated. Statuses must be kept current, because other people's work queues are built from them.
Errors cascade. A wrong occupancy classification or permit type entered at intake can send the file down the wrong review path, calculate the wrong fees, and generate the wrong inspection list — and each downstream user tends to trust what the record says. This is why departments emphasize accuracy at the point of entry over speed: correcting a record after work has been routed on bad data costs far more than the seconds saved by rushing intake. Structured fields exist precisely so the system can act on the data; information buried in a free-text note is invisible to fee calculation, scheduling, and reporting.
Inspection results are the field half of data discipline. Modern systems support mobile entry on phones or tablets, so the inspector records the result on site rather than from memory at the end of the day; the administration literature notes that mobile inspection tools capture results in real time when a connection is available and store and forward them when it is not, and that photos taken in the field can be attached directly to the inspection record — documenting the condition observed and guiding both the contractor's corrections and the next inspector's follow-up. Checklists configured for the inspection type help ensure nothing is missed, and the inspector can pull up the permit's full history on site: previous results, correction notices, approved plan documents, holds, and contact information. Prompt posting matters beyond the department's own workflow — contractors and owners watch results through the portal, and "expedited posting of inspection results" is one of the customer-service gains that justify these systems in the first place.
Holds and conditions deserve special care. A hold placed on a record — for unpaid fees, a zoning issue, an unresolved code enforcement case — is how one part of the organization stops another part from advancing a project that should not advance. Entering a hold clearly, and releasing it promptly when resolved, is data entry with direct legal and customer-service consequences.
An inspector arrives for a rough framing inspection and, before leaving the vehicle, opens the permit on a tablet. The history shows the previous inspection failed with three correction items, each with a photo. Walking the site, the inspector verifies each correction against its photo, finds one item still incomplete, photographs it, and enters a partial-approval result with a specific correction note — all before leaving the driveway. By the time the contractor calls the office that afternoon, the result, the note, and the new photo are already on the record and visible through the portal, and the office staff answering the phone can read exactly what the inspector saw. No callbacks, no reconstruction from memory, no dispute about what was said on site.
The classic entry mistakes are: typing information into free-text comment fields when a structured field exists for it, so fees, routing, and reports never see it; selecting the wrong permit type or work class at intake, which miscalculates fees and generates the wrong inspection list; batching inspection results for end-of-day or next-morning entry, which leaves contractors and office staff working from a stale record; and inventing personal workarounds — private spreadsheets, sticky notes, duplicate "shadow" records — that fragment the official record and break reporting. A related error is creating a new record when one already exists for the project, leaving two half-complete histories. The corrections are procedural: use the structured field the system provides, slow down at intake because that is where errors are cheapest to prevent, enter results on site or the same day, correct errors through the system's amendment or void process rather than deletion so the audit trail survives, and raise process gaps with a supervisor instead of engineering around them.
Generate required reports from the system
Reporting is where the discipline of Modules 1 and 2 pays off. Because every application, fee, plan review, and inspection result lives in one database, the system can answer management questions that would take days to compile from paper files. The administration literature identifies flexible reporting — documenting the volume of work completed and the revenue generated — as a principal benefit of permitting systems, and notes that most systems ship with standard reports for tracking activity daily, weekly, or monthly, while departments needing more can extract data through standard database connections and build custom reports tailored to the jurisdiction.
A new staff member should learn the handful of reports the department actually runs on a rhythm. Activity reports count applications received, permits issued, and inspections performed over a period — the basic workload picture. Open-permit and aging reports list permits that have been idle, inspections that have been requested but not performed, and permits approaching expiration — these are the supervisor's early-warning tools for backlogs and stalled projects. Revenue reports summarize fees assessed and collected and support reconciliation with the finance department; where the department collects payments through the system, the payment records must tie out. Turnaround reports measure how long plan reviews and permit issuance actually take, which is how a department knows whether it is meeting its service commitments and where the bottlenecks are. Workload reports by inspector or reviewer support fair assignment and staffing decisions. Many of these figures also flow outward — to the jurisdiction's governing body, to budget requests, and to the public — so their accuracy is a matter of departmental credibility, not just internal convenience.
Every report is only as good as the data behind it. An aging report fills with false alarms if staff leave statuses stale; a revenue report misstates collections if fees were adjusted outside the system; an activity count is wrong if duplicate records were created. This is the practical answer to a question new users often ask — "why does it matter which box I pick?" — the box you pick at intake is a row in the report the building official hands to the city council. Report generation itself has its own discipline: understand the date range and filters before running the report, understand what each column counts (applications received is not permits issued), and never manually edit exported numbers to "fix" them — if the report is wrong, the underlying records are wrong, and the records are what must be corrected.
The same database serves the department's records-management obligations. Permit records are public records subject to retention requirements and records requests, and the system's archive is the department's defensible, searchable answer — including the electronic audit trail showing who entered what and when.
A title company calls during a pending property sale: their records show no certificate of occupancy for a tenant build-out completed several years ago, and closing is stalled. Under a paper system this would mean an archive search measured in days. Instead, staff search the address, open the historical permit, and find the complete story in minutes: every inspection with dates, results, and the inspectors' notes; the conditions attached at issuance and their sign-offs; the final inspection approval; and the certificate of occupancy document attached to the record. Staff print the CO and the inspection history, and the closing proceeds the same week. The dispute was resolvable only because every result and condition had been entered when it happened — the value of data discipline usually appears years after the entry was made.
Common reporting mistakes include running a report without checking its date range, filters, or status definitions and then circulating misleading numbers; treating different metrics as interchangeable (counting applications as issuances, or requested inspections as completed ones); exporting a report and hand-editing the figures instead of correcting the underlying records; and ignoring what the report reveals — an aging report no one acts on is just a list. A subtler failure is not closing the loop: staff who see their own stale statuses appear on an exception report and fix the symptom in the report rather than the record. The corrections: learn precisely what each standard report counts, verify parameters before distributing anything, fix data at the record level so every future report is right, and treat exception and aging reports as work queues that drive follow-up, not as paperwork.
Permit-management software gives a building department one shared, lifelong record for every project — from application intake through plan review, permitting, inspections, and the certificate of occupancy. This course covered the three competencies every new user needs: navigating the system to find and read records accurately, entering permit and inspection data with the discipline the legal record demands, and generating the standard reports supervisors and governing bodies rely on. The connecting theme is that the record is only as trustworthy as the people maintaining it: accurate intake drives correct fees and routing, on-site result entry with photos keeps contractors and colleagues working from current information, and clean data makes reports — and years-later disputes — resolvable in minutes. Use training environments and superusers while learning, correct errors through the system rather than around it, and treat every entry as a permanent public record, because it is.