Tactical sheet
A one-page, at-a-glance summary organized around the information responding officers need first.
Managed pre-incident plan production for fire departments
Clear your preplan backlog.
PremiseAtlas captures building information and produces pre-incident plans for your department to review, approve, and use in its current system.
The managed workflow
- 01Managed field capture
- 02Human-reviewed drafting
- 03Department approval
- 04System-ready delivery
What you receiveOne complete package.
01 02 03 04 05 06
One complete package.
Six coordinated components.
Each building is prepared for department review, approval, and delivery in the format agreed for your current system.
View a sample preplan packageSchematic plans
Floor and site layouts showing department-approved access points, stairs, exits, fire protection features, utilities, hazards, and other operational locations.
System-ready data
Preplan fields prepared for the records or response system selected during project scoping.
Decision-point photography
Labeled images of entrances, control rooms, risers, roof access, and other verified locations selected with the department.
Capture evidence
Measurements, imagery, field notes, and source status retained for review, correction, and future updates.
Approval history
A traceable record of review status, requested corrections, final acceptance, and the date each building was verified.
The production workflow
Five steps from building list to accepted plan.
- 01
Choose the buildings
Your department identifies the district, occupancy types, priorities, existing records, and required preplan fields.
- 02
Arrange access
We coordinate entry with property owners and managers under your department’s authority, document restricted areas, and schedule each capture without consuming inspector time.
- 03
Capture accessible areas
A trained field team uses handheld LiDAR, wide-angle imagery, and a department-approved checklist to document accessible areas and operational features.
- 04
Draft and review
PremiseAtlas prepares the plan, checks it against the capture evidence, and routes it through the named review process. Inaccessible, obscured, owner-reported, and inferred information is identified.
- 05
Accept and deliver
Your department reviews the record, requests corrections, and approves the final version before it is delivered for operational use.
Production, approval, and delivery
We do the production work. Your department approves the result.
Roles, acceptance standards, and delivery format are agreed before fieldwork begins.
PremiseAtlas handles
Field capture, drafting, quality checks, documented limitations, approved corrections, and preparation of the final delivery package.
Delivery may be configured for First Due, ESO, Tablet Command, or another department-selected system.
Your department retains
Building priorities, tactical requirements, plan approval, final acceptance, inspections, code interpretation, enforcement, and crew familiarization.
The PremiseAtlas Preplan Backlog Sprint is a paid pilot for low- or medium-complexity occupancies. Before fieldwork begins, we agree on the buildings, required information, review process, delivery format, and measures of success.
Included
- Field capture and preplan production
- Quality checks and approved corrections
- Department review and final delivery
- A comparison with your current workflow
What you will learn
- Cost per accepted plan
- Time from capture to delivery
- Completeness, corrections, and rework
Hospitals, high-rises, major industrial sites, critical infrastructure, and restricted occupancies are scoped separately.
Questions
What departments usually ask first
Is this a fire inspection?
No. PremiseAtlas produces pre-incident planning records. We may document and flag an observed condition for department review, but inspection, code interpretation, enforcement, and approval remain with the authority having jurisdiction.
Does this replace company familiarization?
No. Crews should continue learning the buildings they may enter. PremiseAtlas reduces the production burden and creates a consistent record from the approved information.
Do we need to replace our current software?
No. We scope delivery around the system your department selects. Depending on the platform, this may mean structured files, PDFs, assisted entry, or a supported direct transfer.
How accurate are the plans?
Accuracy is defined and tested at the delivered plan. Pilot terms establish control measurements, critical-field checks, accepted tolerances, and rescan rules. Inaccessible and inferred areas are identified. Plans are not intended for construction or as-built use.
Who reviews and approves each plan?
The engagement identifies the PremiseAtlas reviewer and the department approver. No plan is marked accepted until the department completes its review.
How are plans kept current?
The department can select annual verification, event-triggered updates, or another approved cycle. Material changes, access limitations, and the last verification date remain visible in the record.
Where does the data live?
The project data plan defines processing location, access, retention, export, and deletion before capture begins. Restricted occupancies are handled under additional written requirements.
What does it cost?
The first engagement is priced as a fixed-scope pilot. Ongoing production is quoted by building complexity, field requirements, review requirements, and delivery method.
Start with the backlog
Clear a piece of the backlog and measure the result.
In 30 minutes, we can review your current workflow, identify a safe first building set, and determine whether a paid pilot is worth scoping. No occupancy files are required for the first conversation.
Book a 30-minute backlog review