A project can pass its building final and still miss its opening date because a fire approval remains open. An inconsistent suite number or unpaid required fee can cause the same delay.
A local building or zoning department issues a certificate of occupancy (CO) to state that a building complies with applicable codes and safety standards and may legally be occupied for its approved use. New construction, additions, major alterations, and changes of use commonly require one before occupancy, following the building permit application that started the project.
The exact trigger, application, inspection sequence, and issuing office vary by jurisdiction. Building officials and permit staff review the required approvals, so project teams should track every open permit, failed inspection, agency hold, missing project file, and unpaid fee until the issuing authority clears the project. Occupancy before issuance can lead to enforcement action, delays in opening a business, or an order to vacate.
This guide explains what the certificate establishes, when it is required, who issues it, and how project teams can manage the closeout workflow.
What Is a Certificate of Occupancy?
A certificate of occupancy confirms the legal use and occupancy of a building or defined portion of a building. It records that the issuing authority has completed the required review of building code compliance and determined that the space may be occupied for the approved use.
Certificate Contents and Limits
Under Section 111 of the 2021 International Building Code (IBC), still the edition most U.S. jurisdictions have adopted since local governments typically lag the newer 2024 edition by several years, a building or structure generally cannot be used or occupied, and a change of occupancy cannot occur, until the building official issues a CO. Issuance does not approve violations of the code or other local ordinances. The certificate typically identifies the permit, property address, owner or authorized agent, approved use and occupancy, and construction type. It also records the occupant load, sprinkler status, applicable code edition, and any special conditions.
A CO is not a blanket guarantee that no code violation exists. A building official may also suspend or revoke a certificate issued in error or based on incorrect information. The same authority applies to a building later found to violate applicable requirements.
Alternative Certificate Names
Some jurisdictions use a different name. Baltimore City, for example, calls the document an occupancy permit. Other jurisdictions issue a certificate of completion or letter of completion for work that does not change the building's occupancy or use.
When Do You Need One?
A CO is commonly required when work creates a new occupied space or changes how an existing space will be used. The exact trigger depends on the adopted code and local administrative rules, and it typically follows the same permit and documentation requirements that governed the underlying construction project.
Common CO Triggers
Typical triggers include:
Construction of a new building
An addition that creates occupiable space
A major alteration affecting egress, fire protection, or construction type
A change in use or occupancy classification
Conversion of a building, such as commercial space to residential use
Occupancy of a new tenant space where local rules require a separate certificate
Local rules determine which triggers apply to a specific project.
Jurisdiction-Specific Rules and Exceptions
NYC requires new buildings to have a CO and existing buildings to obtain a current or amended CO when use, egress, or occupancy changes. San Antonio ties the requirement to each tenant space in a multi-tenant building rather than the property as a whole, and allows a simpler name-change update instead of a new CO when the approved use doesn't change (see the Texas FAQ below for the fuller process).
A new CO is not always required for minor alterations or permit-exempt work. The same may apply to a change in ownership or tenancy when the approved use remains unchanged. Others exempt specific residential properties or older buildings. Project teams should verify the adopted code and local administrative rules for each market. One city's requirements do not apply to another market.
Risks of Early Occupancy
Without a required CO or temporary certificate, the owner may be unable to legally open the space. Open violations can also interfere with a sale or refinancing, and local authorities may issue stop-work or vacate orders.
Who Issues It?
The local building official or another authority having jurisdiction issues the certificate of occupancy and makes the final issuance decision.
Issuing Authority
Depending on the municipality, that authority may sit within a building department, inspectional services department, development services department, or combined licensing and inspections agency.
Required Sign-Offs
Several departments may contribute required sign-offs. Fire prevention, zoning, health, public works, environmental, accessibility, elevator, and utility authorities may each place holds or provide required sign-offs based on the project type.
Issuance Workflow
A typical issuance workflow follows these steps:
Confirm the permit scope. Verify that the building permit and associated trade permits cover the work completed in the field.
Submit the application. Provide the legal address, owner or tenant information, approved use, permit numbers, plans, and any jurisdiction-specific forms.
Complete required final inspections. These may include building, electrical, mechanical, plumbing, fire, elevator, zoning, health, and site inspections.
Correct deficiencies. Resolve failed finals, complete corrective work, submit missing records, and schedule re-inspections.
Close permits and agency holds. Confirm that related permits are finaled and released and that required departmental approvals have been recorded.
Pay outstanding fees. A certificate may remain pending while required fees remain unpaid.
Receive the certificate. The building official issues the CO after determining that the applicable conditions have been met.
The closeout package may include approved drawings, inspection reports, special-inspection reports, fire-alarm and sprinkler acceptance records, energy compliance records, permit logs, agency sign-offs, and evidence that correction notices have been resolved. The required package depends on the adopted code and local workflow.
Temporary Certificates of Occupancy
A temporary certificate of occupancy (TCO) authorizes occupancy for a defined period when the building official determines that a building or specified portion can be occupied safely, even though not all permitted work is complete.
When a TCO Is Appropriate
A TCO may be appropriate when life-safety systems, required egress, utilities, and the occupied area are complete, but limited work remains elsewhere. The building official sets the scope and expiration date. A TCO does not let the project team defer conditions that affect safe occupancy.
Conditions and Expiration
Teams should track every TCO condition as a closeout commitment. Common TCO controls include the expiration date, permitted floors or tenant areas, unresolved permit items, inspection status, the responsible contractor, the target correction date, and the renewal deadline. An expired TCO can expose the owner and occupants to enforcement action.
TCO Versus Final CO
A final CO differs from a TCO because the building official issues the final certificate after the required work and approvals, fees, and records are complete. A certificate of completion is different again. Some jurisdictions use it for remodels, shell work, or other completed work that does not establish a new occupancy or change of use.
Certificate of Occupancy Requirements in Practice
CO requirements vary, but most issuing workflows test the same core question. Do the permit record, approved design, field inspections, and agency approvals establish that the space can legally be occupied for its intended use?
Approved Scope and Project Files
The completed work should match the approved drawings, specs, permit scope, and recorded revisions, the same as the as-built verification discipline that construction closeout generally depends on. Unapproved field changes, inconsistent suite numbers, missing engineering letters, or outdated drawings can stop issuance even when most construction is complete.
Project teams should reconcile the permit log against the current drawing set and identify every permit that must be closed. This includes building and trade permits as well as associated fire-protection, elevator, utility, civil, or site permits when applicable. Project teams may need to finalize every related permit, secure the release of each agency hold, or obtain TCO approval.
Final Inspections and Life-Safety Acceptance
Project teams must ensure that inspectors pass and record required final inspections. Life-safety sequencing deserves particular attention because fire-alarm, sprinkler, emergency-lighting, exit-sign, and egress approvals may depend on one another.
Do not request the building final merely because the scheduled completion date has arrived. Confirm completed trade finals and passed acceptance tests. Verify closed correction notices and installed required labels and signage. Make sure inspectors can access the full scope. A premature inspection request can require rescheduling and delay final approval.
Departmental Approvals and Administrative Closeout
A building final alone may not clear every hold because zoning, planning, fire, health, accessibility, engineering, or other agencies may still need to approve the project. Unpaid fees, unresolved violations, open applications, and mismatched property records can also block the certificate.
A useful closeout dashboard tracks open permits, agency holds, failed finals, unresolved corrections, and incomplete acceptance tests. It also tracks missing project files, correction cycles, and days from final inspection to issuance. Those fields show where the workflow is stuck.
Automating Certificate of Occupancy Verification
Use AI agents only after you document the jurisdiction's requirements and decision rights. Properly configured AI agents may analyze project files, cross-check closeout records, execute routing steps, and assemble review packages. AI agents can run record comparisons and routing so permit coordinators and project managers can focus their time on resolving exceptions and making judgment calls.
Validate Project Files and Route Reviews
When approved drawings, inspection reports, special-inspection reports, permit logs, and agency sign-offs disagree, Datagrid's AI agents can analyze those project files, compare identifiers and statuses, and flag missing or conflicting records for review.
An Audit Agent or custom agent can apply a documented checklist to the package. The checklist must reflect the current jurisdiction and project type. If the rules are incomplete or outdated, the agent may produce false positives or miss a local requirement, so permit staff and project teams must review exceptions.
Route identified exceptions, prompt follow-ups, and record receipt of required sign-offs when approvals move through separate teams or systems. Teams should define workflow rules for that routing.
AI agents may connect through supported integrations with built-world and collaboration systems including Procore, Autodesk Construction Cloud, SharePoint, and Microsoft Teams. Supported connector access may exclude some agency systems. Teams must confirm permissions, data quality, and the system of record before deployment.
Coordinate Inspection Readiness
Before requesting a final inspection or re-inspection, teams can compare inspection logs, correction lists, contractor commitments, and project schedules to identify incomplete prerequisites. A voice-powered lookup of inspection status or agency sign-offs can support that check when closeout records sit across several connected systems. Teams should use connected calendar workflows, where available, to coordinate review meetings or inspection-readiness checkpoints.
An AI agent can detect a missing fire-alarm acceptance record. Field conditions still require an official inspection, and the inspector confirms that the installed system operates correctly.
Assemble Packages and Monitor Deadlines
When every approval appears complete, but staff still need to compile the record, a standardized template can assemble permit details, final inspection results, agency sign-offs, conditions, and supporting project files into a draft package. The building official must still validate the record, apply required legal language, and make the issuance decision.
Records management can keep the certificate and supporting closeout records organized for audits or appeals.
Deadline monitoring matters most when multiple projects or temporary certificates are active. Teams should add responsible parties and TCO expiration dates to the closeout dashboard. Alerts should direct operators to the underlying record so building officials can determine compliance. Treat source data as potentially late, duplicated, or incorrectly coded, and treat the official permit system as the source of truth.
Conflicting permit statuses, unresolved agency holds, or an approaching TCO expiration may put occupancy approval at risk. An Audit Agent can compare the permit number, suite identifier, inspection status, agency hold owner, and TCO expiration date. It can then route each exception to the responsible operator.
Automate Certificate of Occupancy Verification With Datagrid's Agentic AI
Datagrid's AI agents compare project files, permit logs, and agency sign-offs against the closeout checklist, so permit coordinators and project managers spend their time resolving exceptions instead of assembling the record:
Project file and closeout validation: Cross-check identifiers and statuses across the full closeout record set, surfacing missing or conflicting items before they delay issuance.
Inspection-readiness checks: Compare inspection logs, correction lists, contractor commitments, and project schedules to surface incomplete prerequisites before requesting a final inspection.
Closeout package assembly: Compile the scattered permit, inspection, sign-off, and condition records into one draft closeout package, ready for the building official to check and finalize.
TCO and deadline monitoring: Track TCO expiration dates, unresolved agency holds, and conflicting permit statuses, and route each exception to the responsible operator.
Building officials keep every issuance decision and required legal determination; the agents keep the underlying record reconciled and current.
Get started with Datagrid to compare one project's closeout package against its permit log and see which holds need attention first.
Frequently Asked Questions About Certificate of Occupancy Requirements
Enforcement, local procedures, and TCO expiration commonly raise questions during CO closeout.
What Happens if I Don't Have a CO?
Enforcement may include delays in opening or an order to vacate, while open violations may interfere with a sale or refinancing.
How Do You Get a Certificate of Occupancy in Texas?
Texas does not have one uniform municipal CO workflow; requirements depend on the local jurisdiction. San Antonio, for example, requires a CO for businesses and for each tenant space in a multi-tenant building based on its approved use, while a name-change update may apply if the owner or lessee changes without a change in approved use.
How Do You Get a Certificate of Occupancy in Boston?
In Boston, use the Inspectional Services Department's legal occupancy record as the baseline. Confirm that the property address and approved occupancy match the permitted scope, then follow the local issuing authority's closeout workflow.
What Happens When a Temporary Certificate of Occupancy Expires?
An expired TCO can expose the owner and occupants to enforcement action. Project teams should track its conditions and renewal deadline before the authorized occupancy period ends.
