Keep one private request log for your team and send each buyer a reply containing only their own questions and approved answers. Give every request an ID, a person handling it and a next step. When two buyers ask for the same document, reuse the preparation while checking each buyer's access separately.
One buyer emails a list on Monday. Another sends a spreadsheet on Tuesday. Both want the latest quarterly accounts, but their question numbers differ. By Friday, someone has prepared the accounts twice and nobody is sure which version reached the second buyer.
A request log avoids this when it keeps two records apart: the work on a document, and who received it.
Keep the buyer's question and add your own ID
Copy the exact request into your internal log, including the buyer's original question number. Add a short ID your team can use in email and calls, such as A-04. Keep that ID when the answer changes.
Record the period and format requested. "Latest accounts" could mean the last completed quarter, year-to-date figures or signed annual statements. Ask before someone spends an afternoon preparing the wrong pack. BDC's guide to selling a business identifies year-end and interim financial statements and projections among the documents buyers commonly request.
Assign one person to prepare the answer and another to approve sharing where needed. They may be the same person in a small team. Agree a response date. If the answer needs more time, record when you will give the buyer an update.
Prepare a shared answer once
Suppose two buyers ask for the same quarterly accounts. Give the source document an internal reference, such as F-01, and link both requests to it. Keep the source version and period alongside that reference.
Four requests in your private log could look like this:
| Request | Buyer asks for | Source or work needed | Next step |
|---|---|---|---|
| A-04 | January to March accounts | F-01, version 3 | Shared with Buyer A; confirm the link opens |
| B-07 | January to March accounts | F-01, version 3 | Approval to share with Buyer B still pending |
| A-05 | Revenue by customer | A summary approved for sharing | Finance prepares a draft by Thursday |
| B-08 | Latest forecast | Period and format unclear | Ask Buyer B which forecast they need |
A-04 and B-07 use the same preparation. They still need separate delivery records. Approval to send a document to Buyer A does not mean you may send it to Buyer B.
If a buyer needs a different summary, create a separately identified file and record what it covers. Avoid silently editing the shared source to answer just one buyer.
Use a few statuses that tell people what to do
Choose labels that describe the next action:
- Preparing: someone is collecting or writing the answer.
- Waiting for approval: the answer is ready for the person who decides what can be shared.
- Shared: the approved answer has been sent to this buyer.
- Follow-up: the buyer has asked a further question, or something remains missing.
- Resolved: the request is complete under the process you agreed with the buyer.
"Shared" records delivery. Confirm separately whether the buyer has read the answer and has further questions. Agree how requests will be closed, for example during the regular review call. Mark them resolved once the agreed follow-ups have been handled.
A spreadsheet is enough for a small request list. If people keep using different labels, Excel's drop-down lists can help keep the status column consistent.
Use the free buyer request worksheet to set up the private log and a separate reply for each buyer.
Send each buyer a clean reply
Keep the master log restricted to the people coordinating the sale. It may reveal other buyers' identities, questions, negotiating positions or internal comments.
Prepare a separate buyer-facing reply with only that buyer's question number, the answer, the approved document link and any outstanding next step. Copy the required fields into a fresh reply or file. Hiding spreadsheet rows or filtering a shared master is not a reliable way to keep its other contents private.
For B-07, a reply might read:
Your question 7: The January to March accounts are now available in Financials. The link below opens version 3. The April figures are still being prepared; we will update you on Thursday.
Send that reply only after approval and access are confirmed. Review the recipient list, the exact file and the permission to view or download. Ask your advisors what you may share, and when.
Record what actually reached each buyer
For each delivery, save the source version, date and time, recipient or room, and the reply you sent. If you shared several documents, list them individually so a later correction can be traced to the affected requests.
When a file changes, use those records to find the buyers who received the earlier version. Check the revised content is approved for each audience, then tell them what changed and where the current file is.
Keep a short follow-up note under the original request ID, so a colleague can see the question's history without searching several inboxes. Downloaded copies remain on the recipient's device, so a new shared version does not update those copies.
Keep the files organized in Aurora
You can keep approved deal documents in one Aurora library and create a room for each buyer, choosing the documents each room shares. If people within a buyer's team need different access, groups can refine their access to documents already included in that room.
Keep the request log as a separate internal working document. Aurora's library and rooms organize the shared files; the worksheet tracks questions, approvals and replies.
An approved replacement version stays attached to the same library document. Rooms already sharing that document show its current version when participants reopen or refresh, within their access. Check the room selection before adding a file or changing who can see it.
Start with the next two requests
Take two open questions from your inbox. Write down what each buyer needs, who will prepare the answer and the next update date. If both questions use the same source, link them to that source while keeping their approval and delivery records separate.
Before you close a request, check that the answer covers the requested period, the recipient can open the approved files, and every remaining question has a named next step.
To try the file-sharing setup, start a 30-day free trial with harmless sample documents. Create one library and two buyer rooms, give each room a different selection, and check both recipient views. The trial includes one organization, unlimited libraries, two rooms, three internal users, 25 external users and 10 GB of storage, with no card required.
For the checks before sharing, use the buyer disclosure checklist. For later changes, read how to keep shared documents current.
Buyer request log and reply worksheet
Free to use and adapt. Keep your completed worksheet in your own project files.
Download Worksheet (.md)Use this worksheet in your existing spreadsheet or project notes. Keep the completed master private to the people coordinating the sale. Create a separate reply for each buyer.
Set up the work
- Sale or project:
- Person maintaining this log:
- People allowed to read the master:
- Person approving each type of document:
- Regular review time:
- How you and the buyer agree a request is resolved:
Record one request
Copy this block for each question. Keep the same internal ID through follow-ups.
- Internal request ID:
- Buyer and original question number:
- Exact question:
- Required period and format:
- Date received:
- Person preparing the answer:
- Person approving sharing:
- Answer or work needed:
- Source document reference and location:
- Source version and period:
- Status: Preparing / Waiting for approval / Shared / Follow-up / Resolved
- Next action and person handling it:
- Due date or next update:
- Approval by, date and scope:
- Approved recipient or room:
- View or download access:
- Actual version delivered:
- Delivery date, time and timezone:
- Copy or location of the reply sent:
- Follow-up question and date:
- Resolution and how it was confirmed:
Example: two requests, one prepared document
| Request | Source | Approval | Delivery |
|---|---|---|---|
| A-04: January to March accounts | F-01 version 3 | Approved for Buyer A | Shared in Buyer A's room; date and time recorded |
| B-07: January to March accounts | F-01 version 3 | Pending for Buyer B | Nothing sent yet |
Update B-07 after its own approval and delivery. Do not mark it shared because A-04 is shared.
Prepare a buyer-facing reply
Copy only the following fields into a fresh message or document. Check the finished reply contains no other buyer's information or internal comments.
- Your question number:
- Question or short description:
- Answer:
- Approved file link, period and version:
- Anything still outstanding:
- Person handling the next step:
- Next update date:
Example reply after approval: Your question 7: The January to March accounts are available at [approved link], version 3. April figures are being prepared. We will update you on Thursday.
Check before sending
- The answer addresses the exact question, period and format.
- Approval covers this buyer and this version.
- Links open the correct files with the right view or download access.
- The reply contains only this buyer's questions and approved answers.
- Each missing item has a person handling it and a next update date.
- The log records what was actually sent and when.
A filtered view or hidden spreadsheet rows can leave other contents in the file. Send a separately prepared reply instead of the private master.
When a document changes
- Changed source reference and new version:
- Requests that received the previous version:
- Buyers affected:
- Sharing approval checked for each buyer:
- Short explanation of the change:
- Current link and delivery record:
- Follow-up required:
Tell affected buyers where the current file is. A download already on their device will not change when you replace the shared source.
Close the loop
Record whether the buyer has further questions and how the request was resolved under your agreed process. Delivery, reading and acceptance are different events. Keep the original question and follow-ups together.
This worksheet organizes work; your transaction advisors can help decide what may be disclosed and when.
