Consulting & AdvisoryFree
Client Data Room Index in Reading Order
Every file indexed against the question it can answer, then ranked into what you read on Monday, what you skim, and what nobody opens.
River reads the folder you were handed and returns two things: an index with a row per file, and a reading order. Each row carries the type, the date the document states about itself, the owner it names, and which of your engagement questions it could answer. The order is the deliverable. It says which ten files earn the first morning, which twenty get skimmed for one figure, and which two hundred nobody opens, with the reason sitting beside each one.
What ranks for this search is written for the other side of the table. Numbered folder trees, a naming convention, permission tiers, watermarks, a question module, build the structure before you upload anything. Sound advice for whoever owns the documents. You do not own them, you cannot rename them, and half the time there is no room at all, just a drive share with four folders called Archive and a spreadsheet somebody exported in 2019.
Built for the consultant, the fractional operator and the diligence analyst who gets the folder on Monday and presents in week six. Reach for it before you open the first file. The gap list for what never arrived lives in the consultant client intake checklist, and the scoring comes later in the consulting assessment pack. Every finding you eventually write has to cite one of these files, which is the whole premise of the findings and recommendations pack.
A folder you did not build gets read in a different order
Start by counting, not reading. Every guide on structuring a room recommends deep numbered folders with a dated filename at the bottom, and the Windows API caps a whole path at 260 characters unless a program asks for the extended form explicitly. Four levels of that convention plus a name like 02-Financial-Audited-Statements-2025.pdf spends the budget quickly. So the count that came out of the zip and the count in the room's own index are two different numbers, and finding the gap takes ten minutes.
Then rank on three things, in this order. Authority first: one executed agreement outranks six drafts of it, and a signed variation outranks the clause it changed. Grain second, because a file has to hold the level of detail your question needs, and a board pack showing group cost per unit cannot answer a question asked per site however many times you reread it. Recency third and last, since the most recent version of a document nobody signed is still not evidence. Where two packs disagree, reconciling the client's accounts decides which to rank.
The skip list is the half nobody writes down, and it is where the week comes back. A tender folder from the firm you replaced is superseded by the award that followed it. Six monthly decks are slices of a workbook you already hold. And a spreadsheet is not a dataset. Excel's published limits stop a worksheet at 1,048,576 rows and one cell at 32,767 characters, so an export that hit either arrived trimmed and no amount of reading finds the rest.
How it works
Send the folder
A drive export, a data room download, or forty attachments from the kickoff thread.
Name the questions
Three to eight things the engagement has to answer, taken from the signed scope.
Read the order
The ranked list, the minutes each file is worth, and the reason it sits where it does.
Work down it
Start at rank one and stop where the questions are answered, not where the folder ends.
What you get
- One row per file, with the date the document states about itself and where it said it
- A reading order ranked on authority and grain rather than on folder name or upload date
- The skip list, with the file that supersedes each entry named beside it
- Six versions of one document collapsed into a single authoritative row and five you never open
- Every file mapped to the engagement question it can answer, or to none of them
- The minutes each first-pass file is worth, so a day of reading fits inside a day
Common questions
What does it need from me?
A file listing at minimum: names, paths, sizes, dates. That alone produces the version groups, the duplicate sets and a first ranking. Hand over the files themselves and the index gains the date each document states about itself, the owner it names, and the grain it actually holds, which is what turns a ranking into a reading order.
Three files are called Final and they disagree. Which one wins?
None of them on the strength of the word. The stack ranks on what the documents carry: a signature, an approval line, a board minute quoting a figure, a footer naming the author. Where nothing separates them the row says so and names who can settle it, and why two exports disagree takes the difference apart line by line.
Will it tell me a file is not worth reading?
That is the output most people came for. A file lands on the skip list with a reason: superseded by a named later document, duplicated by a named workbook, outside the period the engagement covers, or holding a grain too coarse for any question you asked. Overrule any row you like. The reason is there to be argued with.
Does this replace the client intake checklist?
No, they answer different halves. The consultant intake checklist covers what the client owes you and has not sent, tracked as requests with owners and dates. This covers the material that did arrive and the order to take it in. Most engagements need both in the same week, and the index feeds the request list.
Half the folder is the previous firm's reports. Does the index cover those?
A predecessor's report is indexed like anything else, and the reading order puts it high, because it is the fastest route to what the client already believes. Their recommendations are a separate job: reviewing the previous consultant's work turns the deck into a register with a status against every recommendation. The index tells you which of their files was the one actually presented.
What happens to scans and photographs?
They get indexed and read. A scanned board minute, a photographed whiteboard and a signature page shot on a phone all carry content, and often carry the date the rest of the folder is missing. Where a page genuinely will not resolve, the row names it and says what it was going to support instead of quietly dropping it.
Is this the same as a legal document index?
Close in mechanism, different in purpose. A document chronology and key document index is built for a dispute, so it runs in date order and keys to the issues in a pleading. This runs in the order that answers your engagement questions soonest, which puts an unsigned model above a dated memo when the question is about cost.
Client Data Room Index in Reading Order
Fill in the form and your workspace opens with the work already underway.