Data Room Preparation Agent

A dispositions coordinator assembling a sale data room spends most of the calendar on collation, not judgment. The work is gathering files from property management, pulling executed leases and amendments, locating maintenance and capex histories, naming folders to a buyer-facing index, and stripping personal data that should never leave the seller's systems. An agent can take that collation loop and run it continuously as records change, so the room is a classified, redacted packet rather than a shared drive of leftovers.

The agent does not open the room. It compiles source records, assigns each file to an index category, flags gaps, and applies redaction rules that counsel has already approved. Counsel still decides what buyers see, when the virtual data room (VDR) goes live, and which exceptions stay sealed. That split keeps speed on the coordinator's side of the table without moving privilege or disclosure decisions onto a model.

related often needs the same rent rolls and capex files. Treat the data room packet as the canonical extract so valuation and buyer diligence are not working from two different versions of the building.

The packet is only as complete as the systems the coordinator can point at. Typical feeds are the property-management system (rent roll, tenant contacts, arrears, insurance certificates), the lease archive (executed leases, side letters, consents, guarantees, deeds of variation), and the maintenance stack (work orders, warranties, inspection reports, planned preventative maintenance, major works). Accounting exports for service-charge reconcilations and capex ledgers usually sit alongside those three.

The agent should ingest structured extracts first and documents second. A current rent roll in a table is more reliable than a PDF of last year's tenancy schedule. Where both exist, the structured extract is the source of truth for occupancy and rent, and the PDF is filed as supporting evidence with a timestamp. Duplicate files are collapsed by checksum and by a simple identity key (asset, unit, document type, effective date) so the index does not fill with five copies of the same insurance certificate.

Empty output is required when a source the packet depends on is missing. If there is no lease archive for the asset, the agent does not invent a tenancy schedule from the rent roll. If maintenance history is not connected, the agent does not pad the technical folder with marketing photos. A missing feed produces an empty folder for that index section, a gap log with the expected source and last successful pull, and no placeholder files. Coordinators can then chase the property manager or the lawyer's matter file instead of discovering the hole when a bidder asks for the HVAC warranties.

Classification maps each record to a buyer-facing index, not to the seller's internal folder names. A useful index is stable across assets: title and planning, leases and occupational documents, rent and arrears, service charge, insurance, technical and surveys, capex and major works, environmental, litigation and disputes, and operational contracts. The agent scores each file against that taxonomy using filename, MIME type, extracted entities (unit numbers, tenant legal names, document dates), and a short set of document-type rules counsel has signed off.

Ambiguous files stay in a review queue. A scanned PDF labelled "misc" that mentions both a side letter and an insurance claim should not be auto-filed into leases. The coordinator sees the candidate labels, the extracted snippets, and a confidence flag. Only files above the agreed threshold land in the packet. Everything else waits. That rule is slower on day one and much faster by week two, because the review queue teaches the rules without letting a misfiled personal injury claim sit in the technical folder.

Redaction is a separate pass after classification. The agent masks personal data that diligence does not need: home addresses of individual tenants where the lease already identifies the unit, staff names on work orders, bank details on invoices, ID numbers on KYC packs that drifted into the property file. It does not redact commercial terms. Rent, break dates, dilapidations positions, and outstanding claims stay visible because those are why the buyer opened the folder. Counsel supplies the redaction policy; the agent applies it and produces a redaction log (field, rule, file, page or cell) so a reviewer can reverse a mask without re-running the whole room.

When a source record is absent, redaction does not run on that section. There is nothing to mask. The gap log is the output. Running redaction over empty folders would create a false sense that the section was reviewed.

The coordinator's job is a complete packet and a clean exception list. Counsel's job is disclosure. Before the VDR opens, counsel reviews three artifacts the agent must produce every time: the classified index with file-level provenance (source system, original path, ingest time), the redaction log, and the gap log. Those three documents are the human-in-the-loop surface. If any of them is missing, the room does not go live.

Counsel also decides privilege and withheld items. Litigation files, pricing strategy memos, and incomplete environmental reports often sit in the same matter folder as the lease. The agent can label them as withheld candidates. It cannot release them. The coordinator marks the withhold, counsel confirms, and the packet that buyers receive simply omits those files. The index still shows that a withheld category exists, so a later disclosure round does not look like the seller hid the folder structure.

Opening the room remains a counsel action: invite list, watermarking, Q&A permissions, and staged folders (first-round teasers versus full diligence). The agent can package zip-ready trees and VDR upload manifests. It does not send invites and it does not toggle folder visibility. That keeps the speed gain in assembly while the legal act of opening stays with the people who will answer the bid questions.

Disposals slip when the room is a one-off dump from six weeks ago. Between teaser and best-and-final, leases are assigned, arrears move, and a roof leak appears in the work-order system. The agent should re-pull on a schedule the coordinator sets, reclassify only new or changed files, and re-apply redaction to those files alone. Unchanged files keep their prior labels so counsel is not asked to re-approve the entire index every night.

Change reports matter as much as the files. Each refresh should list additions, replacements, and removals, tied to the same identity key used for de-duplication. The coordinator forwards that delta to counsel. Counsel decides whether the live VDR is patched immediately or held for the next Q&A round. Bidders should never see a silent overwrite of a lease they already reviewed.

The same current packet feeds adjacent work. related needs a stable view of tenancy risk and outstanding capex so bid scores are not arguing with an outdated rent roll. related needs an honest picture of lease profile and technical condition before mandates are matched. When those models read the same classified extract the data room uses, the coordinator stops reconciling three spreadsheets the week bids land.

If a refresh cannot reach a required source, the agent does not ship a partial room as if it were complete. It ships the last good packet (if counsel already opened on that version) plus a gap log for the failed pull. For a room that has not opened yet, a failed required feed means empty output for that section and no go-live recommendation. Speed comes from removing collation, not from pretending the archive is full.

The practical test for the coordinator is simple. Can counsel open the room from the agent's packet, redaction log, and gap log without a weekend of renaming files? If yes, the agent is doing its job. If counsel still has to hunt for the executed lease, the classification rules or the source connections are wrong, and the next cycle should fix those inputs rather than adding more folders.