CRE Document Ingestion

Classify and extract structured data from CRE rent rolls, T-12 financials, and offering memoranda.

1|Updated May 17, 2026
One-click install
npx skills add https://github.com/Envision-Construction/Envision-Skill-Repo --skill cre-document-ingestion-envision-construction
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: CRE Document Ingestion
Source: https://github.com/Envision-Construction/Envision-Skill-Repo/tree/main/plugins/real-estate/cre/skills/document-ingestion
Command: npx skills add https://github.com/Envision-Construction/Envision-Skill-Repo --skill cre-document-ingestion-envision-construction

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Commercial real estate deal packages arrive as unstructured PDFs, Excel files, and images, forcing analysts to manually identify document types and re-key data before underwriting can begin. This Skill automates classification and structured extraction from rent rolls, T-12 operating statements, and offering memoranda. ## Core Features & Use Cases - Document Classification: Identifies rent rolls, T-12/T-3 statements, offering memos, leases, surveys, Phase I ESAs, appraisals, and other deal documents with confidence scoring. - Specialist Parsers: Extracts unit-level rent roll data, T-12 revenue/expense/NOI line items, and OM property characteristics, pricing, and seller information into structured JSON schemas. - Cross-Validation & Gap Analysis: Flags conflicting figures across documents, detects missing required fields, and lists standard CRE documents not yet provided. - Use Case: An acquisitions analyst receives a broker's deal package containing a rent roll, T-12, and OM. The Skill classifies each file, extracts unit mix, NOI, and asking price into structured output, and flags that the Phase I ESA and title commitment are still missing. ## Quick Start Classify the attached deal documents and extract structured data from the rent roll, T-12, and offering memorandum.

Frequently Asked Questions about CRE Document Ingestion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract data from a rent roll into structured format?▼

Provide the rent roll as Excel, CSV, or PDF and the parser maps varied column headers, normalizes unit types like 2x2 to 2BR/2BA, and outputs unit mix, occupancy, rents, and lease expirations as JSON. It validates unit counts and flags rent or square footage outliers.

How to parse a T-12 operating statement for underwriting?▼

The financials parser handles monthly-column, annual summary, and budget-comparison T-12 formats, extracting revenue lines, expense categories, and NOI with per-unit metrics. It excludes below-the-line items like CapEx and debt service and validates that revenue minus expenses equals NOI.

What document types can CRE document classification identify?▼

The classifier identifies rent rolls, T-12/T-3 operating statements, offering memoranda, pro formas, PSAs, surveys, inspection/PCA reports, Phase I ESAs, title commitments, and lease abstracts. Each classification includes a confidence level, and ambiguous files are flagged for user confirmation.

Does the offering memo parser work with scanned PDFs or images?▼

Yes, it accepts PDFs, PowerPoint, Word documents, and image-based property flyers, but OCR quality directly affects extraction confidence for scanned files. Key fields like asking price, unit count, and cap rate are located via phrase recognition and section headers.

What happens when rent roll and offering memo data conflict?▼

Conflicts are never silently resolved; each is flagged with both values and a recommended resolution based on source authority. For example, the rent roll is treated as more authoritative for occupancy while the OM is authoritative for asking price.

What are the limitations of automated CRE document extraction?▼

Confidence drops below 0.70 for partial-year financials, heavily combined expense categories, pro forma mixed with actuals, or PDFs with ambiguous table structure. Missing critical fields like address, unit count, or price block underwriting and require manual input.