Key performance indicators, dashboard creation, trend analysis, and data-driven decision making. Covers metrics for permitting, inspection, and enforcement.
2
hours
0.2
CEUs
Administrative, Legal & Management
1.7.4
Key performance indicators, dashboard creation, trend analysis, and data-driven decision making. Covers metrics for permitting, inspection, and enforcement.
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 teamIdentify key performance metrics for building departments
Start with why a building department measures anything at all. Most of a department's best work is invisible: the fire that never started, the deck that did not collapse, the plan-review comment that caught a structural error on paper instead of in the field. When budget season arrives, invisible work is the easiest work to cut. A department that can show only anecdotes — "we're swamped," "the counter line is out the door" — is negotiating from weakness. A department that can show its workload, its turnaround against published goals, and its cost of service is negotiating with evidence. ICC's Building Department Administration text puts the management version plainly: you can't manage what you can't measure, and it treats creating performance measures and indicators for every department operation as one of the manager's perpetual tasks. Its staffing chapter shows where this leads — it builds the case for inspector positions from counted units of inspection work, converting the month's actual inspection demand into hours and hours into positions. That arithmetic is only possible because someone recorded every inspection. Data converts "we need help" into "here is the workload, here is what it takes to serve it."
The second discipline is honesty about what a number actually measures. Building Department Administration draws the distinction that anchors this course. Inputs are the resources consumed — staffing, contractor labor, administrative costs and overhead. Output indicators are just numbers: inspections performed, notices sent, violations found, permits issued. The book is blunt that most jurisdictions treat these as performance measures, but they are not — a count of activity says nothing about whether a program is effective or efficient. True performance measures compare results against a goal or baseline: plan-review turnaround against a published service goal, the time between finding a violation and achieving compliance, whether conditions are measurably better than last year. Knowing which kind of number you are looking at is the difference between analytics and bookkeeping.
Two frameworks from the book give structure to a metric set. First, when service goals for permitting, plan review, and inspections are established with stakeholder input, performance can be measured in three distinct areas: quality (error rate), timeliness, and customer satisfaction. Second, the book identifies four possible performance-measurement categories — workload, efficiency, effectiveness, and service delivery. A balanced metric set touches all of them; a metric set that is all workload counts is the output-indicator trap wearing a dashboard.
From those frameworks, a practical core metric set for a building department looks like this:
Volume and workload trends. Permit applications, plan submittals, and inspection requests over time — the demand side of the staffing equation, and the earliest warning of a construction upswing or slowdown.
Turnaround times by review type. Days from complete submittal to first plan-review response, and from application to issuance, measured separately for each permit type against a published goal. A single blended average hides everything interesting.
Inspection response and aging. Time from inspection request to inspection performed — with same-day or next-day service the goal many departments set — plus the count of requests waiting and how long they have waited.
Results mix and reinspection rate. The proportion of inspections passed, failed, and partially approved, and how often the same work requires repeat visits. A rising reinspection rate is a quality signal about the incoming work, the clarity of correction notices, or both — and every reinspection is capacity that cannot serve a new request.
Revenue versus cost of service. Permit fees are intended to defray the cost of operating the department, and the book warns that a consistent large profit is evidence either that fees are excessive or — more likely — that the department is understaffed for the service it is charging for. Tracking revenue against actual cost of service keeps the fee structure honest in both directions.
Customer-satisfaction signals. Survey results, quality-control callbacks, complaint and compliment counts — the third leg of the quality/timeliness/satisfaction triad, and the one most often skipped because it is hardest to count.
A new building official inherits a department that reports one number to the city manager each month: permits issued. Construction is booming, the count keeps rising, and budget requests keep getting denied — after all, the numbers are "up." The official rebuilds the monthly report around the measurement hierarchy: permits issued stays, now alongside inspection requests per field day, plan-review turnaround against the published goal, inspection response time, and the aging list of reviews in queue. The new picture shows turnaround slipping further from the goal each month even as output climbs — rising output, falling performance, the signature of a unit running past capacity. Paired with a workload-based staffing calculation of the kind Building Department Administration demonstrates, the same data that once argued against the department now makes its staffing case.
The most common error is reporting outputs as if they were performance — counting inspections performed with no goal, baseline, or trend to compare against. The correction is to pair every count with a standard: not a raw inspection total, but requests served within the published same-day goal. A second error is measuring only what the permit system counts automatically, which skews the set toward workload and away from quality and satisfaction; the correction is deliberately covering all four categories. A third is setting targets without involving the staff who must meet them. The book is specific: staff should be included in the discussion when targets are established so they understand the expectations, progress should be checked in time to adjust, unreasonable targets should be revised, and met targets should be recognized.
Create dashboards for operational performance monitoring
A dashboard is not a data dump — it is an argument about what matters, updated on a schedule. The design discipline starts before any chart is drawn, with the questions the department's leaders actually ask: Are we meeting our published turnaround goals? Where is work piling up? Is demand rising faster than capacity? Is the quality of incoming submittals getting better or worse? Are customers being served? Each dashboard element should exist because it answers one of those questions; anything that answers no question is decoration that dilutes the page.
Three design rules carry most of the weight:
One page. An operational dashboard the building official reviews monthly should fit on a single page or screen. If a metric matters enough to track, it matters enough to fight for space; if it cannot win space on the page, it belongs in the drill-down detail behind the page, not on it. Different audiences get different pages — the supervisor's version can carry per-reviewer queues that would be noise (and potentially unfair) in front of a council.
Trends, not snapshots. A single month's number is almost meaningless on its own — plan review took eleven days; is that good? The same number plotted against the published goal and the prior twelve months tells a story: holding steady, drifting, or recovering. Building department workloads are cyclical, so a snapshot will always be partly weather; the trend line is the signal. This is the same logic the book applies to budgeting, where multi-year trends in department activity are the guide precisely because any single season misleads.
Written definitions. Every metric needs a written definition — where the clock starts and stops, what is excluded, which system field feeds it — so the number means the same thing every month. "Plan-review turnaround" measured from first submittal is a different metric than one measured from complete submittal; both are defensible, but the department must pick one, write it down, and disclose it. Undefined metrics drift, and drifting metrics destroy the trend lines that make a dashboard useful. Definitions are also the defense when a number is challenged in public: the answer to "how do you calculate that?" should be a document, not a shrug.
None of it works without data quality underneath. Building Department Administration observes that efficiency benchmarks are established using data generated by the department's computer data-management systems — permit processing times, plan-review status, inspection scheduling — which means the dashboard can only be as good as the discipline of the people feeding those systems. Three habits do most of the work: results entered the same day the work happens (an inspection resulted three days late poisons every response-time number in between); structured fields instead of free text (a result code can be counted; a narrative comment cannot); and no off-system side records, because work tracked in a personal spreadsheet is invisible to every metric. Garbage in, garbage out is the failure mode here, not a cliché. A department that rolls out a dashboard without first tightening data entry will spend its first quarter explaining wrong numbers — and a dashboard that burns its credibility early rarely gets it back.
A department builds its first operations dashboard and the opening review meeting goes sideways: the inspection supervisor insists the response-time figure is wrong because "we never miss same-day." Investigation shows the number is technically correct but the inputs are not — two inspectors batch-enter their results at week's end, so mid-week requests appear to age for days before being served. The fix is not a better chart; it is a data-discipline standard: results entered before end of shift, result codes chosen from the structured list, and the definition of "response time" (request timestamp to result timestamp) written into the dashboard's definitions page so everyone argues about the same number. Two months later the trend line is trusted — which is the only condition under which a dashboard changes decisions.
The most common failure is building the dashboard around what the software exports easily instead of what leaders need to decide, yielding a page of activity counts and no performance; the correction is to start from the decision-makers' questions and work backward to the data. The second is the everything dashboard — dozens of measures, no hierarchy — corrected by the one-page rule and drill-down detail. The third is presenting snapshots without goals or history, corrected by putting the goal and the trailing trend on every chart. The fourth is skipping written definitions, which surfaces the first time two staff members compute different values for the same metric in front of an audience. And the quietest: publishing on undisciplined data, then losing the room when the first number proves wrong. Fix the data entry first; publish second.
Use data analytics to inform policy and resource decisions
The point of measuring is to decide differently. Building Department Administration notes that local governments increasingly depend on data — compiled within a department and across departments — to understand patterns, target effort where risk concentrates, and plan responses, citing survey work showing performance analytics in use across policing, public works, code compliance, and parks operations. For a building department, the policy applications are concrete: workload trends drive the staffing request; turnaround data against service goals drives process redesign; fee-versus-cost analysis drives the fee schedule; compliance-time data drives enforcement procedure. The budgeting literature adds a caution: performance data informs allocation arguments but does not settle them — whether a high-performing unit gets more money or an underperformer gets less remains a judgment about values and priorities, not a lookup. Data narrows the argument; it does not replace it.
Using data well also means refusing to weaponize it. The book's warning about output goals is the sharpest lesson in this course: establishing goals that require a specific number of notices sent per day or week creates a culture that focuses on output indicators rather than performance. Any count that becomes a quota will be gamed — inspections split to inflate totals, easy violations written while hard ones wait, reviews rushed at the cost of the error rate. Two rules keep analytics constructive. First, aim metrics at processes, not individuals: dashboards exist to find systemic bottlenecks, while individual evaluation remains a supervisory function fed by direct observation, spot reviews, and quality-control checks — the tools the book assigns to supervisors — with data as context, never as the verdict. Second, always pair volume with quality: inspections per day means nothing without the reinspection rate beside it. Paired metrics make the honest path the only path to a good-looking number.
Then there is cadence — data informs policy only if it arrives on a rhythm that matches the decisions:
Monthly operations review. The one-page dashboard, reviewed with supervisors: goals versus actuals, aging queues, emerging bottlenecks. This is the working meeting where small corrections happen before they become budget problems, and it satisfies the book's requirement for timely progress checks against established targets.
Quarterly governing-body story. A handful of high-level measures tied to what the council actually cares about — service speed, fiscal position, customer satisfaction, safety outcomes — with trend context and a short narrative. This is also where the department banks credibility it will spend at budget time.
Annual report. The full-year picture: workload trends, performance against every published service goal, fee revenue versus cost of service, and the coming year's targets. The book notes that performance measures should be reviewed regularly against goals — the annual cycle is where targets themselves get re-examined, and where the staffing math from the workload data becomes next year's request.
A department's dashboard shows plan-review turnaround badly missing its published goal, and the obvious policy response — hire another plans examiner — is drafted into the budget request. But the building official segments the data first: turnaround measured from first submittal is terrible, while turnaround measured from complete submittal is inside the goal. The bottleneck is not review speed; it is intake — a large share of submittals arrive incomplete and cycle through resubmittal before review can begin. The policy answer changes entirely: a published completeness checklist, an intake screening step before a submittal enters the review queue, and a new metric — percentage of submittals accepted as complete on first try. Six months later, first-submittal turnaround has closed most of the gap without a new position. That is analytics informing policy: the data did not just show the department was slow, it showed where — and the where changed the answer.
The classic misuse is turning counts into quotas, which the book warns builds an output-focused culture; the correction is aiming metrics at processes, pairing every volume measure with a quality measure, and keeping individual evaluation grounded in supervisory review rather than dashboard rankings. A second mistake is treating the first plausible explanation as the root cause — buying staff when the bottleneck was intake — corrected by segmenting before deciding: by permit type, by process stage, by time period. A third is reporting to the governing body only when asking for something, which reads as advocacy; a steady quarterly rhythm in good months and bad is what makes the budget-season numbers believable. A fourth is letting the metric set fossilize: measures should be reviewed against goals regularly, retired when they stop informing decisions, and revised when they prove unreasonable — a dashboard is a management tool, not a monument.
This course provides comprehensive professional development in data analytics and performance dashboards. Key performance indicators, dashboard creation, trend analysis, and data-driven decision making. Covers metrics for permitting, inspection, and enforcement. The through-line is honesty about numbers: inputs, outputs, and true performance measures are different things, and a department that counts activity without comparing it to goals is doing bookkeeping, not analytics. Built on disciplined data entry, defined metrics, and a one-page, trend-oriented design, a dashboard makes invisible work visible — to supervisors monthly, to the governing body quarterly, and to the budget process annually — while the guardrails against quota culture keep measurement serving improvement rather than punishment.