Give reviewers a short index built around the questions they need to answer. For each question, name the file, point to the section that helps, give the document's issue and say who can fill a gap. Then check the index from the recipient's side before you send it.
It usually starts with a polite email a day after you shared the pack: "Thanks for this. Where would I find the service history?" A folder full of documents can still leave someone unsure where to begin. A good index gives them a route through the material and shows plainly which requests are still open.
Start with the questions on the reviewer's desk
Ask what the reviewer needs to find out at this stage. A business considering equipment for a new production line might ask:
- Which operating conditions were used in the trial run?
- What service history is available?
- When could the equipment be delivered?
Those questions point to a first reading route through test summaries, maintenance records and delivery information. Folders named after your departments, or after whoever uploaded the files, help a newcomer much less.
Write down a few priority questions before you index the whole collection. You can add more as the review goes on. Keep the wording close to what people actually ask.
Build an index that links questions to evidence
Give each question a reference you can use in emails, and keep it fixed when you add rows. The reference names the question. The document's own issue or revision names the material that answers it.
Here's a possible first page for the equipment review. The filenames and references are examples to adapt.
| Question | File and location | Issue and section | What it covers | Follow-up |
|---|---|---|---|---|
| Q01: Which conditions were tested? | Testing / Production run summary.pdf | Issue 2, section 3 | The recorded run and its stated conditions | Technical coordinator answers scope questions |
| Q02: What service history is available? | Maintenance / Service record.pdf | Issue 1, records to 30 September | The service entries supplied | Operations contact checks any missing period |
| Q03: When could delivery take place? | Delivery / Delivery schedule.pdf | Issue 3, milestones table | The current proposed dates | Project coordinator confirms changes |
| Q04: Is there an energy-use report? | Requested, no file yet | No issue yet | Still outstanding | Technical coordinator confirms availability and next update |
A missing item needs a visible status and a named person. An empty cell leaves the reviewer guessing whether the file was overlooked, held back or never produced.
Use links where they work for the recipient, and keep the filename and folder next to them. If a link or access fails, the reviewer can still say what they were looking for. Listing a file in the index never gives anyone permission to open a restricted file.
This borrows a habit from research data: explain what a collection contains, how the parts fit together and who to contact. Cornell's README guidance for research data recommends exactly those elements, and they adapt well to an outside business review. Cornell's README guidance.
Make names and folders match the index
Use short, descriptive filenames a reviewer will recognize. If a document already has a known title or reference, keep it and add the explanation in the index. Renaming files mid-review can break the link to earlier questions and emails.
Pick a folder structure that suits this collection, such as Testing, Maintenance and Delivery. Don't create several similar homes for the same kind of record. Stanford's file-management guidance recommends consistent, descriptive names and a clear structure that suits the work. Stanford's naming guidance.
Explain unfamiliar abbreviations once. Add the date or issue wherever things could otherwise be read two ways. And don't treat a file's upload date as proof of when its contents became current.
The index can give context a filename can't. For Q01, a short note that the summary covers one specific run tells the reviewer what to look for. It doesn't show the equipment will perform the same way everywhere. That conclusion still needs the document and the specialist responsible for it.
Check what this audience could learn
An index is a shared document too. A filename, question or description can give away a private negotiation, a customer's identity or an internal investigation, even when the linked file stays locked.
Write each index for the audience receiving it. For the technical equipment review, price-negotiation notes may fall outside the agreed scope. Keep those notes, and any index entries that hint at them, out of that audience's pack. A separate commercial reviewer may need a different reading route.
You can keep the full picture in an internal request register. The external version should hold only what this audience is cleared to see. Word outstanding requests in a way the recipient is allowed to read.
The same goes for short introductions and folder descriptions. Check the whole route through the pack, including the notes around the documents.
Run a find-it check before sending
Ask a colleague who didn't prepare the pack to work from the recipient's access. Use sample documents for a first setup test. Give them three questions and ask them to:
- Find the file using the index.
- Find the section that answers the question.
- Name the document's issue and any limit on what it covers.
- Say who they'd contact if the answer is missing or unclear.
Note where they got stuck. A broken link needs a fix to the link or to access. A vague title needs a clearer name or more context. A file that never answers the question needs a follow-up request. Adding folders won't solve every one of those.
The UK Data Service describes good documentation as information that helps someone with no prior knowledge of a project understand the material. The find-it check applies that idea to your pack. It's a simple editing exercise, and it makes no promise about saving time. UK Data Service documentation guidance.
Keep the reading route current
When a source document changes, check its index entry at the same time. Sections and page numbers move, gaps close and someone else may take over. Record the real date you reviewed the index so recipients know when the pointers were last checked.
If two documents disagree, flag the question to its owner. A tidy index shouldn't quietly turn an unresolved difference into an approved answer. For conflicting copies already in circulation, see the guide to aligning advisors on financial versions.
Put the method to work in Aurora
In Aurora, keep your source documents in a library and give each audience a room with only the files you pick for it. Write an index for that audience as an ordinary document and add it to the room. You maintain the index yourself as the collection changes.
The room's Find Documents search helps participants find the items they can see by name and folder. It doesn't search inside PDF or Word contents. Clear names help people find the file, and the index points them to the right section inside it. Access groups and individual permissions can narrow access inside a room, so check the index and its files as the people who'll use them.
Try three test PDFs and a short index in one library. Put them in a room, invite a test recipient you control and run the find-it check. If there's a second audience, use a second room with its own selection and index. That fits the 30-day trial: one organization, unlimited libraries, two rooms, three internal users and 25 external users, with no card required. Try the setup in Aurora.
Start with the free worksheet below. Pick three real review questions and map each to its evidence, the section that helps and an owner. For the wider sharing setup, see when a shared folder is enough for external review.
Reviewer evidence index and find-it check
Free to use and adapt. Keep your completed worksheet in your own project files.
Download Worksheet (.md)Use this sheet to link review questions to the material that answers them. Start with three questions and add more as you go. It works with any document-sharing service and is free to use, no account needed.
Pack details
Purpose and audience: [What this review covers and who receives this index]
Pack owner and contact: [Who maintains the index and answers "where is it?" questions]
Index issue: [Your identifier]
Pointers last checked: [Actual date]
Current source location: [A place recipients can open]
Questions and evidence
Use one row per question. Add more references if several files help answer it. Keep question references the same across updates.
| Question reference and wording | Filename and location the recipient can open | Document issue and section | What it covers or what's missing | Owner and next step |
|---|---|---|---|---|
| Q01: | ||||
| Q02: | ||||
| Q03: |
Useful statuses for a gap include "Requested", "Awaiting clarification" and "Available for review". Pick wording your recipient will understand. A file being available doesn't mean its contents are accepted or the question is settled.
Audience check
- Are the question, filename and description themselves fine for this audience to see?
- Can the recipient open every item listed?
- Does the section given match the issue you've supplied?
- Are abbreviations and important dates explained?
- Does every open item have a named person and a next step?
- Have private internal notes been taken out of the shared index?
Find-it check
Ask someone who didn't prepare the pack to work from the recipient's access. Use sample files for a first setup test. Give the tester three questions and no verbal tour of the folders.
| Question | Found the right file? | Found the section? | Named the issue and scope? | Knew who to ask? | Fix and retest |
|---|---|---|---|---|---|
| Q01 | |||||
| Q02 | |||||
| Q03 |
Write down what actually happened. Don't mark a row as passed just because the file exists. The check is done when the tester can find the evidence, or find the recorded gap and the person responsible for it.
Keep the index current
When a listed document changes, recheck its issue, location, section and scope. Record the real check date and tell recipients about important changes through the agreed channel. Keep the full internal request register separate if it holds anything this audience shouldn't see.
