The index is the examiner's first impression
An examiner forms a view of the office before reading the first document. A clear index shows that the team knows what it has, where it lives, and who owns it. A disorganized production does the opposite, even when the underlying records are strong. The support desk should treat the index as part of the response, not as an afterthought.
The index is also a working tool for the team. It prevents duplicate requests, shows which items are outstanding, and gives reviewers a shared map. Without it, every request restarts a search through inboxes and shared drives. The time spent building the index is usually recovered during the first week of the examination.
Keep the index in a format that the team can update during the examination. A static spreadsheet that only one person can edit becomes a bottleneck. Use a shared table with a clear owner and a change log. The tool should support the response, not slow it down.
Agree the scope and the privileged boundary
Before collecting anything, confirm the scope of the request and the person who owns the legal boundary. Some documents may be privileged, some may contain personal data, and some may be outside the period. The desk should not decide those questions alone. A short scoping call with counsel and the examination lead prevents over-collection and under-production.
Record the scope in writing, including the date range, the custodians, and the systems covered. Note any category that was excluded and the reason. If the scope changes later, update the record rather than rebuilding the index from memory. A clear scope is the foundation for a defensible production.
Build the index from the request list
Start with the examiner's request list and give each item a stable identifier. Break broad requests into the specific documents that satisfy them. Map every request to at least one document or to a documented explanation of why none exists. This structure lets the team see gaps before the examiner does.
Do not organize the index by folder structure alone. Examiners think in requests, while the office stores files by project or person. The index should bridge the two views with a description, a date, and a location. A good index answers the question that was asked, not the question the filing system happened to answer.
Record location, owner, and status
For each document, record the title, the date, the author or owner, the system, and the production status. Add the version and a hash or immutable link if the document may change. The owner should be able to confirm authenticity and explain the context. A location without an owner is difficult to defend.
Use a small set of statuses such as identified, collected, reviewed, produced, and withheld. Avoid free-text status notes that mean different things to different people. A consistent status field lets the team report progress accurately. It also prevents a document from being produced twice or missed entirely.
Run a completeness pass
Before production, test the index against the original requests and against a sample of actual files. Look for documents that exist but were not indexed, and for index rows with no file behind them. Ask the owners to confirm that the set is complete for their area. A completeness pass catches the gaps that a folder crawl misses.
Check dates, names, and version numbers for consistency across the index. A document listed under the wrong date can fall outside the scope or create confusion. The desk should also confirm that redactions are applied consistently. A second reviewer should sample the production before it leaves the office.
Control versions during production
Freeze the production set once it has been reviewed. If a document must change, create a new version and record why. Do not overwrite the produced file, because the examiner may compare the index to what was delivered. Keep the approved set and the working set separate. Version control is part of the evidence.
Log every request for a new document and every follow-up question. The log should show the date, the requester, the response, and the owner. This record protects the team if the scope or the timeline is disputed later. It also makes the next request faster to answer.
Debrief after the examination
After the examination closes, review what worked and what caused delay. Identify the requests that took the longest and the documents that were hardest to locate. Ask the examiners for feedback if they are willing to give it. The debrief should produce a short list of fixes, not a long report.
For related guidance, see our article on building an executive decision log and our executive support services. The National Archives records management guidance provides a useful structure for inventory, retention, and access. Apply the parts that fit a private office rather than copying a federal schedule wholesale. The goal is a repeatable index that the next examination can reuse with only minor changes.
Key takeaways
- Build the index from the examiner's requests, with a stable identifier for each item.
- Confirm the scope and privileged boundary with counsel before collecting documents.
- Record title, date, owner, system, status, and version for every document.
- Run a completeness pass and a version freeze before anything is produced.
- Debrief after the examination and turn the lessons into one or two process fixes.