Capability template for project and delivery

Property diligence index

The transaction lead gets a diligence room in order: every document indexed by workstream, every checklist item and request tracked, and every open finding tied to the report or request that raised it. Specialists judge the findings; nothing is valued or sent.

Put this on your planBuild this in a sprint

Add it to a workflow in the Fully Powered Planner, beside the teams and roles that will run it. Book a fit call

The outcome

During a property transaction, reports arrive from inspectors, the title company, environmental consultants and the seller, each on its own day and in its own format. Questions come out of them faster than anyone can keep track of. This capability turns the pile into one index you can work from.

You get a document index and an open-item tracker, grouped by workstream. Each document shows its author, its dates, whether every page arrived and which checklist item and request it answers. Each checklist item shows whether it is received, received but worth a second look, requested and outstanding, or not yet requested. Each open item names the report and page, or the request, that raised it, who has it and when it is due. A count at the top proves the checklist adds up.

The index uses only what you supply. It does not read the reports, value anything or say what a finding means. Missing pages, two versions of one report and statements that conflict are listed as questions for a person.

Who starts the work, and when

A transaction coordinator or acquisitions lead starts it when the diligence period opens, and runs it again whenever reports, answers or new items arrive. The transaction lead reviews each run, assigns the follow-up and decides what goes to which specialist.

What they supply

  • The diligence checklist, by workstream, with the date each item is due.
  • The request log: what was asked of whom and when, and whether it has been answered.
  • The list of documents received, with dates and page counts.
  • The items raised from those documents and requests, in your words, with the page they came from.
  • The agreed deal timetable, as the date the diligence period ends, plus the roles involved.

What comes out

One index in a fixed order. At the top, a count that ties the checklist together and shows how many requests and items are open. Then each workstream in turn: its documents with flags, its checklist, its requests and its open items. After the workstreams come the conflicting statements, the items that trace to no source, and a short list of decisions for the transaction lead. Anything that cannot be matched is printed as a question, never guessed.

An invented example

Illustrative example with invented data. The company, the property, the people and every document, date and note below are invented. Quillfeather Property Group is an invented company buying Linden Court Apartments, an invented 24-unit building. The acquisitions lead runs the capability and is also the transaction lead who reviews it. First come the inputs the acquisitions lead supplied, in full, then the index the capability returned. Today is Tuesday 10 November 2026.

The inputs

1. Settings

Deal name: Linden Court purchase
Property label: Linden Court Apartments, 24 units
Today: 2026-11-10
Diligence period ends: 2026-11-20
Transaction lead: Acquisitions lead
Chase after: 5 days
Due-soon window: 5 days

2. Diligence checklist

checklist_id,workstream,item_text,due_date
C01,Physical condition,Building inspection report,2026-11-06
C02,Physical condition,Roof inspection report,2026-11-06
C03,Physical condition,Pest inspection report,2026-11-13
C04,Title and survey,Title commitment,2026-11-06
C05,Title and survey,Documents listed as exceptions in the title commitment,2026-11-09
C06,Title and survey,Boundary survey,2026-11-13
C07,Environmental,Phase I environmental report,2026-11-13
C08,Seller records,Trailing twelve-month operating statements,2026-11-06
C09,Seller records,Service contract copies,2026-11-13

3. Request log

request_id,workstream,request_text,requested_on,requested_from,checklist_id,status
Q01,Physical condition,Building inspection report,2026-10-26,Inspector A,C01,Received
Q02,Physical condition,Roof inspection report,2026-10-26,Roofing contractor A,C02,Received
Q03,Title and survey,Title commitment,2026-10-26,Title agent A,C04,Received
Q04,Title and survey,Copies of the documents listed as exceptions,2026-11-02,Title agent A,C05,Open
Q05,Seller records,Trailing twelve-month operating statements,2026-10-26,Seller's broker,C08,Received
Q06,Seller records,Service contract copies,2026-11-02,Seller's broker,C09,Open
Q07,Seller records,Written explanation of the difference between the two operating statements,2026-11-06,Seller's broker,,Open
Q08,Environmental,Phase I environmental report,2026-10-28,Environmental consultant A,C07,Open

4. Document list

doc_id,workstream,title,author,report_date,received_date,pages_stated,pages_received,request_id,checklist_id
D01,Physical condition,Building inspection report,Inspector A,2026-11-03,2026-11-04,62,62,Q01,C01
D02,Physical condition,Roof inspection report,Roofing contractor A,2026-11-02,2026-11-04,14,12,Q02,C02
D03,Title and survey,Title commitment,Title agent A,2026-11-04,2026-11-05,9,9,Q03,C04
D04,Seller records,Operating statements trailing twelve months,Seller's broker,2026-10-30,2026-10-30,11,11,Q05,C08
D05,Seller records,Operating statements trailing twelve months,Seller's broker,2026-11-05,2026-11-05,11,11,Q05,C08
D06,Seller records,Tenant ledger summary,Seller's broker,2026-11-06,2026-11-06,3,3,,

5. Items raised

item_id,source_doc_id,source_request_id,page_ref,item_text,assigned_to,due_date,status,conflicts_with
I01,D01,,p. 14,Further evaluation recommended for water staining in unit 7,Property manager,2026-11-13,Open,
I02,D01,,p. 31,Parking lot drainage noted; contractor estimate requested,Property manager,2026-11-09,In progress,
I03,D02,,p. 6,Photo schedule mentioned in the report is not in the pages received,,2026-11-11,Open,
I04,D03,,Schedule B item 4,Commitment lists an easement exception; copy of the easement document requested,Acquisitions lead,2026-11-12,Open,
I05,D03,,Cover page,Commitment effective date confirmed with Title agent A,Transaction coordinator,2026-11-09,Closed,
I06,,Q04,,Exception documents not yet received; title review cannot finish,Transaction coordinator,2026-11-12,Open,
I07,D05,,p. 2,Total operating expenses differ from the earlier statement,Acquisitions lead,2026-11-12,Open,I08
I08,D04,,p. 2,Total operating expenses as shown in the earlier statement,Acquisitions lead,2026-11-12,Open,
I09,,,,Ask seller about roof age,,,Open,

The index

PROPERTY DILIGENCE INDEX: Linden Court purchase, Linden Court Apartments, 24 units

Prepared for: Acquisitions lead. Index as of 10 November 2026. Diligence period ends 20 November 2026, 10 days away.

Count: Checklist 9 items: Received 2, Received, check first 2, Requested, outstanding 3, Not requested 2. Tie-out: 2 + 2 + 3 + 2 = 9. Documents 6. Requests 8: open 4, received 4, withdrawn 0. Items raised 9: open 7, in progress 1, closed 1; tied to a source 8, not tied 1.

WORKSTREAM: Physical condition

Documents
  D01: Building inspection report, Inspector A, dated 3 November 2026, received 4 November 2026. Pages 62 of 62. Answers C01. Request Q01. Items raised: I01, I02.
    Flags: None.
  D02: Roof inspection report, Roofing contractor A, dated 2 November 2026, received 4 November 2026. Pages 12 of 14. Answers C02. Request Q02. Items raised: I03.
    Flags: Pages incomplete: 2 missing.

Checklist
  C01: Building inspection report, due 6 November 2026. Received.
  C02: Roof inspection report, due 6 November 2026. Received, check first.
  C03: Pest inspection report, due 13 November 2026. Not requested. Due in 3 days.

Requests
  Q01: Building inspection report, to Inspector A, sent 26 October 2026. Received. Checklist C01. Items raised: none.
  Q02: Roof inspection report, to Roofing contractor A, sent 26 October 2026. Received. Checklist C02. Items raised: none.

Open items
  I03: Photo schedule mentioned in the report is not in the pages received. Source D02, p. 6. Assigned: owner not assigned. Due 11 November 2026. Open. Due in 1 day.
  I02: Parking lot drainage noted; contractor estimate requested. Source D01, p. 31. Assigned: Property manager. Due 9 November 2026. In progress. Overdue by 1 day.
  I01: Further evaluation recommended for water staining in unit 7. Source D01, p. 14. Assigned: Property manager. Due 13 November 2026. Open. Due in 3 days.
  Closed items not listed: 0.

WORKSTREAM: Title and survey

Documents
  D03: Title commitment, Title agent A, dated 4 November 2026, received 5 November 2026. Pages 9 of 9. Answers C04. Request Q03. Items raised: I04, I05.
    Flags: None.

Checklist
  C04: Title commitment, due 6 November 2026. Received.
  C05: Documents listed as exceptions in the title commitment, due 9 November 2026. Requested, outstanding. Overdue by 1 day.
  C06: Boundary survey, due 13 November 2026. Not requested. Due in 3 days.

Requests
  Q03: Title commitment, to Title agent A, sent 26 October 2026. Received. Checklist C04. Items raised: none.
  Q04: Copies of the documents listed as exceptions, to Title agent A, sent 2 November 2026. Open 8 days, chase due. Checklist C05. Items raised: I06.

Open items
  I04: Commitment lists an easement exception; copy of the easement document requested. Source D03, Schedule B item 4. Assigned: Acquisitions lead. Due 12 November 2026. Open. Due in 2 days.
  I06: Exception documents not yet received; title review cannot finish. Source Q04. Assigned: Transaction coordinator. Due 12 November 2026. Open. Due in 2 days.
  Closed items not listed: 1.

WORKSTREAM: Environmental

Documents
  None.

Checklist
  C07: Phase I environmental report, due 13 November 2026. Requested, outstanding. Due in 3 days.

Requests
  Q08: Phase I environmental report, to Environmental consultant A, sent 28 October 2026. Open 13 days, chase due. Checklist C07. Items raised: none.

Open items
  None.
  Closed items not listed: 0.

WORKSTREAM: Seller records

Documents
  D04: Operating statements trailing twelve months, Seller's broker, dated 30 October 2026, received 30 October 2026. Pages 11 of 11. Answers C08. Request Q05. Items raised: I08.
    Flags: Two versions of C08: D05 is dated 5 November 2026.
  D05: Operating statements trailing twelve months, Seller's broker, dated 5 November 2026, received 5 November 2026. Pages 11 of 11. Answers C08. Request Q05. Items raised: I07.
    Flags: Two versions of C08: D04 is dated 30 October 2026.
  D06: Tenant ledger summary, Seller's broker, dated 6 November 2026, received 6 November 2026. Pages 3 of 3. Answers no checklist item. Request none. Items raised: none.
    Flags: Not on the checklist: no checklist item named.

Checklist
  C08: Trailing twelve-month operating statements, due 6 November 2026. Received, check first.
  C09: Service contract copies, due 13 November 2026. Requested, outstanding. Due in 3 days.

Requests
  Q05: Trailing twelve-month operating statements, to Seller's broker, sent 26 October 2026. Received. Checklist C08. Items raised: none.
  Q06: Service contract copies, to Seller's broker, sent 2 November 2026. Open 8 days, chase due. Checklist C09. Items raised: none.
  Q07: Written explanation of the difference between the two operating statements, to Seller's broker, sent 6 November 2026. Open 4 days, within chase window. Not on checklist. Items raised: none.

Open items
  I07: Total operating expenses differ from the earlier statement. Source D05, p. 2. Assigned: Acquisitions lead. Due 12 November 2026. Open. Due in 2 days.
  I08: Total operating expenses as shown in the earlier statement. Source D04, p. 2. Assigned: Acquisitions lead. Due 12 November 2026. Open. Due in 2 days.
  Closed items not listed: 0.

Conflicting statements: I07 (D05, p. 2) and I08 (D04, p. 2), named by I07. A qualified specialist judges which is right; the index does not compare them.

Items not tied to a source: I09: Ask seller about roof age. Assigned: owner not assigned. No due date. Open. Reason: no source named.

Decisions for the transaction lead
1. Owners to assign: I03, I09.
2. Requests to chase, if a person chooses to: Q04 (Title agent A), Q06 (Seller's broker), Q08 (Environmental consultant A).
3. Checklist items not yet requested: C03, C06.
4. Documents with flags to check: D02, D04, D05, D06.
5. Conflicting statements to put to a qualified specialist: I07, I08.
6. Items not tied to a source, to link or drop: I09.
7. Which qualified specialist judges each open finding, and what follow-up is assigned.

This index, built from the lists supplied for Linden Court purchase, shows what has been received, requested and raised, and where each open item came from. It does not show that a report is complete in content, that any finding is resolved, or what a property is worth. Qualified specialists judge the findings and the transaction lead decides the follow-up. The index changes no records and sends nothing.

How the figures were reached

  • Checklist: C01 and C04 have an unflagged document, so Received (2). C02 has a document with missing pages and C08 has two versions, so Received, check first (2). C05, C07 and C09 have no document and an Open request, so Requested, outstanding (3). C03 and C06 have neither, so Not requested (2). 2 + 2 + 3 + 2 = 9 rows.
  • Pages: D02 stated 14, received 12, so 2 missing.
  • Days: today is 10 November. Q04 and Q06 were sent 2 November, 8 days; Q08 was sent 28 October, 13 days; Q07 was sent 6 November, 4 days. With a chase-after of 5 days, Q04, Q06 and Q08 are chase due and Q07 is within the window. C05 was due 9 November, 1 day overdue. C03, C06, C07 and C09 are due 13 November, in 3 days. I02 was due 9 November, 1 day overdue; I03 is due in 1 day; I04, I06, I07 and I08 are due in 2 days; I01 is due in 3 days. The end date, 20 November, is 10 days away.
  • Items: nine rows. Open I01, I03, I04, I06, I07, I08, I09 (7); In progress I02 (1); Closed I05 (1). Eight name one existing source and one, I09, names none. I07 names I08, so the pair is listed once.

Where it fits

It is not an evidence index for an audit; that is audit evidence index. It does not compare bids; that is vendor quote comparison. It is not a document index for a construction lender's draw package; that is lender draw package index. It does not track the documents a client owes an engagement; that is client document request tracker. Decisions that come out of the findings can be recorded with the decision log.

What has to change for your company

Name your workstreams and keep the spelling identical in every list. Set how many days a request may sit before it is due for a chase, and how far ahead an item counts as due soon. Decide who is the transaction lead and who may assign follow-up. Agree which specialist judges which kind of finding, so the assignment is quick. Fix the column names in your exports once, so each deal starts from the same four lists.

What has been checked

Fully Powered AI wrote this capability template. It was editorially reviewed on 10 November 2026. It was tried on its invented example on 10 November 2026 in Claude, in one run; the record is published with it. It has not yet been tested in a client environment or as a packaged version in ChatGPT, Claude, Copilot or Gemini.

Testing in your environment means running it on a closed deal your team already knows, with cases written in advance: a report with missing pages, two versions of one statement, a request marked received with no document, an item with no owner. The transaction lead checks every line against the lists before anyone relies on the index. Pilot acceptance-test preparation builds that test set, and What we test before we call an AI workflow ready shows the record.

The full capability template

Everything above is the outline. The complete capability template is the working version: the roles, the inputs, the procedure, the exceptions and stop conditions, the output format, the reviewer checklist, the acceptance tests, the instructions for an AI assistant and what to customize for your company. It comes with a download and the link to its folder in Fully Powered’s public repository.

View the full template

Free with an account. Sign in by email: no password and no card.

Next step

Put this capability to work for your team: on your plan, or built with you in a sprint.

Put this on your plan

Add it to a workflow in the Fully Powered Planner, beside the teams and roles that will run it.

Build this in a sprint

In a sprint, Fully Powered adapts this capability template to your rules, proves it on your own work and puts it in the hands of the roles that own it.

Two ways to begin:

Rather talk it through first? Book a fit callDiscuss adapting this