Pre-Inspection / Existing-Condition Documentation
Document observable conditions before investigation, inspection, engineering review, maintenance, repair, construction, or other work changes them.
EAS | PROJECT & ASSET DOCUMENTATION
Documentation, Not Media.
A documentation pathway of EYE AM STUDIOS, LLC
EAS captures visual and spatial documentation and preserves it through a controlled documentation lifecycle so the resulting record can be understood, traced, and trusted years later.
We create structured documentation records for construction projects, engineering investigations, industrial assets, infrastructure, project conditions, and real-world environments where accuracy, context, continuity, and long-term reference matter.
EYE AM STUDIOS, LLC
Florida-based project & asset documentation
FAA Part 107 Certified
Authorized commercial aerial documentation operations
Insured Operations
Professional liability and operational coverage
Service Region
Tampa Bay & Central Florida — nationwide where scoped
Business Contact
projects@eyeamstudios.com- Structured Capture
- Project Context Preserved
- QCM Reviewed
- Organized Delivery
- Long-Term Reference
Why documentation matters
Conditions Change. Records Must Remain Trustworthy.
Construction becomes concealed. Equipment gets repaired. Assets are modified. Sites change. Project conditions disappear. Personnel change. Physical environments evolve. Later decisions may depend on earlier conditions. EAS creates the structured record while the documentation opportunity still exists.
Progress & Milestone Records
Document defined project milestones and changing conditions throughout an active project.
Insurance & Warranty Support
Preserve organized documentation that may support authorized insurance, warranty, repair, or dispute review.
Long-Term Asset Reference
Create structured records that remain useful after personnel, conditions, projects, or systems change.
Before an Asset Changes
Document an asset before repair, modification, replacement, disassembly, shutdown, removal, or other material change.
What we do
Project & Asset Documentation for Real-World Conditions
EAS creates structured visual and spatial documentation records for construction, engineering, industrial, infrastructure, facilities, and asset-intensive environments. Spatial Evidence Documentation remains a capability and record classification within this pathway — not the name of the entire business.
Capture methods do not determine the documentation level. The required record outcome determines the level; the appropriate technologies are then selected to create it.
Visual Documentation
High-resolution visual records organized by project, asset, location, condition, sequence, milestone, and approved documentation purpose.
Spatial Documentation
Ground, aerial, mapped, 360°, photogrammetric, and 3D-capable documentation used when location, orientation, scale, spatial relationships, context, and repeatability matter.
Controlled Record Continuity
A governed documentation lifecycle preserving project context, asset identity, metadata, handling history, QCM status, organization, release status, and long-term reference.
Applications
Project & Asset Documentation Applications
CON
Construction
Support documentation for pre-cover conditions, hidden conditions, milestones, progress, turnover, closeout, repair, and warranty reference.
Explore Construction DocumentationENG
Engineering Support
Support documentation for existing-condition investigations, structural review, engineering site review, repair documentation, observation support, condition records, and engineering reference.
Licensed engineers retain all responsibility for interpretation, analysis, conclusions, and professional judgment.
Explore Engineering DocumentationIND
Industrial
Support documentation for equipment, piping, facilities, industrial assets, maintenance, shutdowns, outages, repairs, condition history, and asset lifecycle.
Explore Industrial DocumentationINF
Infrastructure
Support documentation for sites, utilities, civil works, transportation, public assets, infrastructure construction, maintenance conditions, and long-term reference.
Explore Infrastructure DocumentationALC
Asset Lifecycle
Support records across Baseline → Modification → Maintenance → Comparison → Repair → Turnover → Future Reference.
Explore Asset Lifecycle DocumentationWhat you receive
A Documented Outcome — Not a Folder of Files
Clients receive structured documentation packages designed for review, comparison, authorized sharing, and future reference — with project or asset context, declared level, and control profile preserved in the delivery record.
Structured Documentation Package
Organized visual, spatial, contextual, and supporting documentation — not a folder of disconnected files.
Project / Asset Record Summary
High-level record identification, classification, status, and governance information in one traceable project or asset record.
Review-Ready Organization
Records structured for inspection support, engineering review, insurance reference, maintenance planning, comparison, and authorized sharing.
Controlled Release
Deliverables registered and prepared according to the approved Documentation Level, Control Profile, and scope of work.
Documentation in practice
Evidence Packages — Not a Photography Portfolio
Representative anonymized examples showing how declared documentation purpose, level, control profile, and deliverables appear in a controlled project record.
Construction Condition Record
Milestone condition documentation before concealment, turnover, or warranty closeout review.
- Documentation Level
- Level II — Organize the Record
- Control Profile
- Enhanced Record
- Capture Context
- Interior and exterior progress capture with milestone sequencing, area classification, and comparison structure.
Example deliverables
- Phase-based visual record set
- Milestone and area index
- Annotated points of interest
- Structured PDF summary report
Anonymized milestone summary preview
- Milestone
- Pre-drywall — Level 2
- Zone A
- Mechanical rough-in visible
- Zone B
- Electrical rough-in indexed
- Report
- Milestone comparison structure attached
QCM Status: QCM Verified — Scope and Delivery Readiness
Release Status: Registered for Controlled Release
Engineering Existing-Condition Record
Structured documentation supporting engineering investigation or review of observable site and asset conditions.
- Documentation Level
- Level II — Organize the Record
- Control Profile
- Enhanced Record
- Capture Context
- Ground documentation with orientation references, points of interest, and investigation-support organization.
Example deliverables
- Organized visual record set
- Point-of-interest index
- Capture summary with scope context
- Structured PDF summary report
Anonymized investigation index preview
- Subject
- Existing-condition investigation support
- Area 01
- Primary structure — accessible elevations
- Area 02
- Adjacent condition context indexed
- Report
- Review-ready organization attached
QCM Status: QCM Verified — Scope and Delivery Readiness
Release Status: Registered for Controlled Release
Industrial Asset Record
Equipment or asset documentation organized by asset identity, location, condition, and lifecycle event.
- Documentation Level
- Level II — Organize the Record
- Control Profile
- Standard Record
- Capture Context
- Asset-centered visual documentation with location context, condition sequencing, and lifecycle event labeling.
Example deliverables
- Asset-indexed visual record set
- Location and condition index
- Lifecycle event summary
- Structured PDF summary report
Anonymized asset index preview
- Asset
- Process unit — accessible envelope
- Location
- Unit area / elevation referenced
- Event
- Pre-outage condition baseline
- Index
- Condition views organized by asset ID
QCM Status: Verified for Scope and Delivery Readiness
Release Status: Ready for Controlled Delivery
Spatial Site Record
Mapped site documentation for layout reference, progress tracking, and spatial condition relationships.
- Documentation Level
- Level III — Spatially Understand the Record
- Control Profile
- Standard Record
- Capture Context
- Georeferenced aerial and ground documentation with mapped orientation, scale reference, and site layout context.
Example deliverables
- Mapped site reference documentation
- Spatial record index
- Branded PDF map sheet
- Documentation summary report
Anonymized spatial record preview
- Coverage
- 12.4 ac site envelope
- Reference
- Mapped grid + orientation north
- Layers
- Progress areas + access routes
- Deliverable
- PDF map sheet + record index
QCM Status: Verified for Scope and Delivery Readiness
Release Status: Ready for Controlled Delivery
When to request documentation
Request Before the Record Opportunity Is Lost
Before Conditions Change
Concealment, demolition, installation, or weather can close the documentation window before the condition is recorded.
Before a Review or Investigation
Engineering review, inspection support, insurance reference, or failure review requires a trustworthy baseline.
At a Project Milestone
Progress phases, turnover, closeout, warranty baseline, or maintenance intervals need a structured record.
When Spatial Context Matters
Location, scale, orientation, or site relationships must be preserved — not just individual photographs.
Before an Asset Changes
Repair, shutdown, modification, replacement, or removal will alter what can later be observed or compared.
Documentation technology
Technology Selected by Documentation Need
Clients purchase the documented outcome—not the camera used to create it. The required documentation outcome determines the capture method.
- Ground Photography
- Aerial Documentation
- 360° Capture
- Floor Plans
- Mapping
- Photogrammetry
- 3D / Point Cloud
- Interactive Asset Records
- Spatial Documentation
The documentation standard
How UECS Protects the Record
EYE AM STUDIOS uses the Unified Evidence Continuity System (UECS) to govern documentation controls where applicable to the project's scope, Documentation Level, Control Profile, risk, and intended use.
UECS is the structured framework used to establish the project record, preserve documentation context, maintain continuity across the evidence lifecycle, perform Quality Control Management review, register deliverables, control release, and support long-term archival reference — at the depth declared in the approved scope.
The depth of UECS control applied to a project is determined by the approved scope of work, documentation level, control classification, project risk, intended use, and contractual requirements.
Quality Control Management review is performed for clarity, completeness, scope alignment, continuity, usability, and delivery readiness — limited to the requirements of the declared Documentation Level and Control Profile.
UECS does not make every record identical. It ensures that every record is governed according to a declared and traceable documentation profile.
01
Intake
Establish the documentation purpose, authorization, scope, intended use, documentation level, control classification, site access, and delivery requirements.
02
Capture
Create visual and spatial source records according to the approved scope, capture plan, site conditions, access limitations, and documentation requirements.
03
Organize
Preserve relevant metadata and structure source files, working derivatives, references, indexes, and deliverables within the controlled project record.
04
Verify
Perform Quality Control Management review for clarity, completeness, scope alignment, continuity, usability, and delivery readiness.
05
Deliver
Register and prepare the approved documentation package for controlled client release, review, sharing, and authorized use.
06
Preserve
Maintain the organized project record according to the approved archival, retention, access, and continuity requirements.
01
Intake
Establish the documentation purpose, authorization, scope, intended use, documentation level, control classification, site access, and delivery requirements.
02
Capture
Create visual and spatial source records according to the approved scope, capture plan, site conditions, access limitations, and documentation requirements.
03
Organize
Preserve relevant metadata and structure source files, working derivatives, references, indexes, and deliverables within the controlled project record.
04
Verify
Perform Quality Control Management review for clarity, completeness, scope alignment, continuity, usability, and delivery readiness.
05
Deliver
Register and prepare the approved documentation package for controlled client release, review, sharing, and authorized use.
06
Preserve
Maintain the organized project record according to the approved archival, retention, access, and continuity requirements.
- Structured capture intake
- Metadata preservation
- Chain-of-custody tracking
- QCM verification
- Evidence registry and logging
- Controlled evidence-package delivery
- Archival continuity
Documentation levels
Documentation Levels & Record Control Profiles
Documentation Levels define the depth and maturity of the record being created. Control Profiles define how that record is governed, reviewed, handled, and released.
Capture methods are selected according to the approved record requirements, site conditions, access limitations, risk, and intended use. Clients purchase a documented outcome — not a specific camera, drone, or capture tool.
Level I
Establish the Record
Create a structured baseline visual record of existing conditions, assets, work, locations, or project environments.
Level II
Organize the Record
Expand the baseline record through indexing, classification, points of interest, annotations, comparison structure, reporting, or inspection-support organization.
Level III
Spatially Understand the Record
Establish mapped, measured, georeferenced, or otherwise spatially organized documentation that communicates location, scale, orientation, and relationships.
Level IV
Planned / Select AvailabilityDigitally Preserve the Record
Create advanced digital representations through technologies such as photogrammetry, LiDAR, point clouds, 3D models, digital environments, or comparable preservation methods.
Capture methods do not determine the documentation level. The required record outcome determines the level; the appropriate technologies are then selected to create it.
Level V
Evidence Elevation
An elevated governance overlay that may apply additional continuity, custody, verification, registry, release, or archival controls to an otherwise approved documentation level.
Record Control Profiles
Documentation Levels define the depth and maturity of the record. Control Profiles define how the record is governed, reviewed, handled, and released.
Standard Record
Structured project organization, QCM review, and controlled delivery suitable for routine documentation requirements.
Enhanced Record
Expanded organization, review, reporting, continuity, or delivery controls for projects requiring greater documentation depth.
Controlled Record
Custody-aware handling, documented continuity, stronger access and release controls, and elevated project-record governance.
Verified Record
A verification-focused profile with enhanced continuity, review, registry, package-control, and release requirements.
Differentiators
What Makes EAS Documentation Different
Cameras, drones, 360 systems, mapping platforms, photogrammetry, and LiDAR are capture tools. The service being purchased is the documented outcome.
01
Documentation-First
Every project begins with the record that must be created—not the camera used to create it.
02
Outcome-Based Capture
Capture technologies are selected according to the approved documentation need, site conditions, access, risk, and intended use.
03
Controlled Handling
Source records, project context, working derivatives, review status, and deliverables are managed according to the declared UECS control profile.
04
Quality Control Management
Delivery packages receive QCM review for clarity, completeness, continuity, scope alignment, usability, and delivery readiness — within the declared Documentation Level and Control Profile.
05
Structured Documentation Delivery
Clients receive organized documentation packages designed for review, comparison, authorized sharing, decision support, and future reference.
06
Long-Term Continuity
Records are created with future interpretation, comparison, dispute reduction, archival value, and decision support in mind.
Process
From Capture to Controlled Delivery
Step 1
Define the Record
Determine the documentation purpose, scope, requirements, locations, assets, milestones, and intended use.
Step 2
Capture the Condition
Perform the authorized documentation using the selected capture methods.
Step 3
Organize the Record
Structure documentation around project, asset, location, condition, system, zone, milestone, or other approved hierarchy.
Step 4
Verify the Package
Quality Control Management review confirms clarity, completeness, continuity, and delivery readiness for the declared level.
Step 5
Deliver the Record
Release the approved documentation package through the authorized delivery pathway.
Project and asset records
From Temporary Project Conditions to Long-Term Asset Records
Project Documentation
Project → Activity → Condition → Record
Documents what occurs during construction, repair, investigation, outage, maintenance, installation, modification, milestone, or other project activity.
Asset Documentation
Asset → Location → Condition → History
Preserves information around the physical asset so identity, location, condition, and history remain usable after personnel or systems change.
Lifecycle Documentation
Baseline → Work → Change → Verification → Turnover → Maintenance → Future Reference
Connects temporary project conditions to long-term asset records so later decisions can reference earlier documented states.
Who this is built for
Built for the People Who Must Make Decisions Later
EAS documents conditions so authorized decision-makers can review a trustworthy record. EAS does not perform the licensed functions of these users.
- General Contractors
- Owners
- Developers
- Structural Engineers
- Civil Engineers
- Engineering Firms
- Facility Managers
- Industrial Operators
- Maintenance Teams
- Asset Managers
- Inspectors
- Insurance Professionals
- Consultants
- Public Agencies
Scope guardrails
Clear Scope. No Confusion.
EYE AM STUDIOS provides documentation services. Unless expressly included within an authorized scope of work and performed through an appropriately qualified professional, deliverables do not constitute engineering analysis, a certified land survey, legal opinion, regulatory approval, claims adjustment, diagnostic testing, destructive or nondestructive examination, code-compliance determination, defect diagnosis, repair recommendation, or licensed inspection conclusion.
EYE AM STUDIOS records and organizes observable and spatially represented conditions so owners, contractors, engineers, inspectors, insurers, attorneys, facility managers, and other authorized decision-makers can review a trustworthy project record.
EYE AM STUDIOS applies documented controls intended to strengthen record continuity, traceability, authenticity assessment, and future usability. Final admissibility, legal sufficiency, engineering interpretation, regulatory acceptance, and evidentiary weight remain subject to the applicable authority, proceeding, contract, jurisdiction, and qualified reviewer.
Document It Before the Condition Changes.
Whether the record needs to support construction, engineering review, maintenance, asset management, turnover, future comparison, or long-term reference, EAS begins by identifying what must be documented and why.
For construction, engineering, industrial, infrastructure, and other project or asset environments.