Study guide
8.2 Electronic Document Review and Workflow Integration
ICC Certified Building Official CBO
Track your progress as you read
Finished sections get a check mark.
1 Introduction
About the ICC CBO Exam How to Use This Guide
2 Chapter 1: Legislative and Alternative Methods
1.1 Code Adoption and Local Amendments 1.2 Board of Appeals and Alternative Materials/Methods
3 Chapter 2: Code Enforcement and Due Process
2.1 Permits and Construction Documents 2.2 Inspection Process and Certificate of Occupancy 2.3 Notices, Violations, and Stop Work Orders 2.4 Right of Entry and Administrative Warrants 2.5 Due Process and Equal Protection 2.6 Hazard Abatement and Emergency Measures 2.7 Tort Liability and Sovereign Immunity 2.8 Code Enforcement Prosecution and Civil Remedies
4 Chapter 3: Human Resources in Code Administration
3.1 Anti-Discrimination Laws in Public Employment (ADA, Title VII) 3.2 Wage, Hour, and Safety Laws (FLSA, OSHA) 3.3 Personnel Discipline, Performance, and Dismissal 3.4 Labor Relations, Grievances, and Due Process
5 Chapter 4: Reports and Public Records
4.1 Records Management and Document Retention 4.2 Public Records Disclosure and Freedom of Information Laws
6 Chapter 5: Customer Service and Public Relations
5.1 Customer Service Principles in Public Administration 5.2 Public Relations, Media, and Stakeholder Communication 5.3 Interagency Cooperation and Coordination 5.4 Conflict De-escalation and Dispute Resolution 5.5 Feedback Strategy and Continuous Service Improvement
7 Chapter 6: Personnel Administration
6.1 Job Descriptions and Personnel Needs Assessment 6.2 Recruitment, Selection, and Onboarding Processes 6.3 Staff Training, Professional Goals, and Certification 6.4 Performance Appraisals and Supervision Standards
8 Chapter 7: Financial Management
7.1 Operating and Capital Budget Development 7.2 Fee Structures, Valuation, and Revenue Generation 7.3 Financial Controls, Audits, and Cost Recovery
9 Chapter 8: Department Records and Information Systems
8.1 Permitting and Code Enforcement Reporting Systems 8.2 Electronic Document Review and Workflow Integration 8.3 Information Security, Data Privacy, and Disaster Recovery
10 Chapter 9: Architectural Plan Review
9.1 Use and Occupancy Classifications (IBC Chapter 3) 9.2 Construction Types and Height/Area Limitations (IBC Chapters 5 & 6) 9.3 Fire and Smoke Protection Features (IBC Chapters 7 & 8) 9.4 Fire Protection Systems (IBC Chapter 9) 9.5 Means of Egress and Occupant Load (IBC Chapter 10)
11 Chapter 10: Structural Plan Review
10.1 Design Loads and Structural Criteria (IBC Chapter 16) 10.2 Materials Standards and Foundations (IBC Chapters 18-23)
12 Chapter 11: Building Systems and Energy Code Plan Review
11.1 Mechanical (IMC) and Fuel Gas (IFGC) Plan Review 11.2 Plumbing Systems (IPC) and Backflow Protection 11.3 Electrical (NEC/NFPA 70) and Energy (IECC) Code Plan Review
13 Chapter 12: Field Inspection and Construction Compliance
12.1 Accessibility Standards and ANSI A117.1 Compliance 12.2 Soil Conditions, Excavation, and Site Inspections 12.3 Footing and Foundation Inspections 12.4 Concrete, Masonry, Steel, and Wood Structural Inspections 12.5 Rough-in MEP Inspections 12.6 Special Inspections and Quality Assurance (IBC Chapter 17) 12.7 Existing Buildings, Alterations (IEBC), and Final Inspections
8.2 Electronic Document Review and Workflow Integration
Key Takeaways Explain This Topic AI
Electronic Plan Review (EPR) processes digital drawing sets, improving efficiency under the framework of IBC Section 107.
Vector-based PDFs (ISO 32000) are standard for review due to text searchability and zoom scale preservation, while PDF/A is required for long-term archiving.
Parallel (concurrent) review workflows route plans to multiple departments simultaneously, reducing bottlenecks relative to sequential routing.
Digital signatures using Public Key Infrastructure (PKI) validate design professionals' seals and make documents tamper-evident.
Mobile integration allows field inspectors to access approved plan sets, attach photo corrections in real-time, and log inspection results dynamically.
Last updated: July 2026
- Electronic Document Review and Workflow Integration
- The Transition to Electronic Plan Review (EPR)
The traditional plan review process relied on large-format paper blueprints that were physically routed from one reviewer to another. This manual system was slow, prone to lost documents, and restricted plan review to a sequential workflow. The transition to Electronic Plan Review (EPR) or ePlan review has revolutionized code administration.
Under Section 107 of the International Building Code (IBC), submittal documents (plans, specifications, and calculations) must be submitted in two or more sets with each permit application. EPR systems digitize this requirement, allowing applicants to upload vector-based documents directly to the department's portal. This shift reduces physical storage requirements, eliminates print costs for applicants, and allows building departments to process permits faster through automated routing and concurrent reviews.
Document Standards: Formats, Vector Graphics, and Archiving
To maintain data integrity and compatibility across platforms, building departments must establish strict document submission standards.
PDF (ISO 32000) as the Standard Format: The Portable Document Format (PDF) is the industry standard. Specifically, departments require vector-based PDFs rather than rasterized (scanned) PDFs. Vector PDFs retain mathematical lines and coordinate data, allowing plan reviewers to zoom in infinitely without pixelation, search for text strings (such as "fire barrier" or "accessibility"), and use digital measurement tools with high accuracy.
PDF/A for Long-Term Archiving: Under ISO 19005, PDF/A is a standardized format designed for the long-term preservation of electronic documents. PDF/A restricts features that hinder archiving, such as external font links, encryption, and JavaScript. This format ensures that approved architectural plans remain readable for decades, satisfying public records retention laws.
PDF/E for Engineering: Under ISO 24517, PDF/E is designed for engineering and construction workflows, supporting 3D model drawings and high-resolution CAD files.
Workflow Integration: Sequential vs. Parallel Review
The core efficiency gain of EPR is the transition from sequential to parallel (concurrent) review workflows:
Sequential Review Workflow: Plans are routed to one department at a time. For instance, the planning department reviews for zoning compliance, and only after their approval are the plans routed to the structural engineer. If structural fails, the plans go back to the architect, resetting the sequence. This linear path is slow and creates significant bottlenecks.
Parallel (Concurrent) Review Workflow: The workflow engine automatically distributes copies of the digital plan set to all reviewing departments (building, planning, fire, public works, health) simultaneously. Reviewers enter their comments and markups in real-time on a single master document or separate layers of the same set. This collaborative environment allows reviewers to identify conflicting requirements early. For example, if the planning department requests a setback change that impacts a fire exit discharge path, the fire and planning reviewers can coordinate immediately rather than after independent, isolated reviews.
Collaborative Markup Protocols and Revision Tracking
To maintain a clear and legally defensible audit trail, permitting systems utilize specialized collaborative markup software (such as Bluebeam Revu, ePlanSoft, or integrated EPR modules) that follow strict protocols:
Separation of Markup Layers: Reviewer comments and corrections are placed on separate metadata layers. The base vector drawings are locked, preventing any modification of the applicant's original work.
Standardized Color-Coding and Correction Libraries: Departments standardize markup colors (e.g., Red for building/structural, Blue for planning/zoning, Green for fire, Orange for public works) and use pre-configured "correction libraries" to insert standardized code citations (e.g., "Provide handrail return per IBC 1014.6").
Version Control and "Slip-Sheeting": When plans are rejected, the applicant must resubmit revised sheets. Rather than uploading an entirely new set, modern systems support "slip-sheeting" — replacing only the revised pages in the master set. The software retains previous versions of the sheets in a hidden history layer, ensuring that the department can track changes over time and verify that all requested corrections were made without introducing new violations.
Automated Comparison Tools: Reviewers utilize software-based comparison tools to detect unauthorized changes. The "Overlay Comparison" tool stacks the old and new drawings on top of each other, displaying changes in contrasting colors (e.g., additions in green, deletions in red). The "Side-by-Side Vector Comparison" analyzes the underlying geometry to highlight even minor adjustments.
Professional Seals and Cryptographic Digital Signatures
The transition to electronic submittals introduces legal questions regarding professional licensure stamps and seals. Building officials must ensure that electronic submittals comply with state engineering and architecture board regulations, as well as the Federal Electronic Signatures in Global and National Commerce (ESIGN) Act and the Uniform Electronic Transactions Act (UETA).
Electronic Signatures vs. Digital Signatures: An electronic signature can be as simple as an image of a signature pasted onto a document. This offers no security or verification. A digital signature uses a cryptographic system (Public Key Infrastructure, or PKI) to bind a digital certificate issued by a trusted Certificate Authority (CA) to the document.
Legal Validation and Tamper Evidency: Under state licensing laws, professional engineers (PE) and registered architects (RA) must stamp and sign construction documents. EPR systems validate these stamps by verifying the cryptographic certificate of the digital signature. Once signed, the document becomes "tamper-evident." Any subsequent modification to the PDF (such as editing a dimension or adding a markup) breaks the cryptographic seal, alerting the plans examiner that the document has been altered since the designer signed it.
Field Integration and Mobile Access
EPR workflows extend beyond the office. Cloud-hosted permitting databases sync with mobile devices used by inspectors in the field:
Mobile Access to Approved Plans: Field inspectors can pull up the stamped, approved plan set on tablets or ruggedized laptops directly at the job site. This ensures they are inspecting the building based on the exact version authorized by the plans examiner.
Real-Time Corrections and Photo Capture: Inspectors log results in real-time. If a framing inspection fails, the inspector can take a digital photograph of the deficient connection (e.g., missing hurricane ties per IRC R802.11), attach the photo directly to the inspection record, cite the code section, and instantly email the correction notice to the contractor.
Automatic Scheduling and Route Optimization: Mobile integrations use GIS to calculate the most efficient driving route for inspectors based on scheduled inspections, minimizing travel times and maximizing field efficiency.