Before you invite a new bidder into an ongoing review, agree what they can see and when they need to respond. Give them today's approved files, a short catch-up note and a clear route for questions. Check earlier answers separately before sharing them.
Suppose a new buyer joins on Thursday. The first buyers started on Monday, the accounts were corrected on Tuesday, and someone answered a question about a customer contract on Wednesday. Sending Monday's folder leaves the new team behind. Forwarding the whole email chain may expose another buyer's questions or negotiations.
The free new-bidder worksheet helps you prepare a clear starting point without reconstructing every conversation.
Agree the starting point before sending an invitation
Ask the person running the deal to confirm four things:
- Who is joining, including the named people on the buyer's team and any advisors.
- Which documents are approved for this team at this stage.
- Who handles questions and decides whether an answer can be shared.
- Which dates apply to this bidder, including any agreed changes to the existing timetable.
Keep the invite list specific. A colleague from the same company may have a different job and need different access. Check any agreed confidentiality requirements before releasing the files.
Plan the buyer's access separately from the seller's working area and other bidders' spaces. HighQ's setup guidance distinguishes bidder roles, file access and Q&A permissions. Whatever service you use, check each of those areas on its own. Thomson Reuters' bidder-site guidance.
Give the new team a short catch-up note
Prepare a note that answers: What is available now? What changed before we arrived? What is still coming? Where do questions go?
For the Thursday arrival, that might look like this:
| Item | What the new bidder receives | What the seller checks |
|---|---|---|
| Business overview | Current approved overview | The linked file is the approved revision |
| Quarterly accounts | Corrected accounts and a short explanation of the correction | The period and revision match the explanation |
| Customer-contract question | A separate answer approved for this bidder, if useful | Other buyers' names, questions and negotiating details stay outside it |
| Forecast still being prepared | A note naming the missing item and the next update date | Someone is responsible for that update |
| Review timetable | Confirmed question and response dates | The deal lead has agreed them for this bidder |
Put a preparation date and time on the note. It describes the starting point the team received. Later changes can follow the normal update process.
A simple message could read:
"Your starting documents are available in the room. The accounts include Tuesday's correction; the explanation is beside the file. The forecast is still being prepared, and Alex will update you on Friday. Please send questions to Alex using the document name. Your review dates are listed below."
Replace the example dates, names and commitments with your actual arrangements. If a date is unconfirmed, say so and name who will confirm it.
Review past answers before reusing them
Useful facts can be buried inside private exchanges. Pull out the information you want to share and check it in its new context.
| Earlier material | What to do before sharing |
|---|---|
| A general explanation of a figure | Check it still matches the current file, then approve a clean answer for the new team |
| A buyer's question containing assumptions about its plans | Prepare a standalone explanation if the underlying fact should be shared |
| A proposed price, special term or private negotiation | Keep it within the agreed audience and ask the deal lead before any wider use |
| An answer that is now out of date | Correct it and check who else needs the correction |
| An unresolved question | Record the next step and person handling it; avoid presenting it as settled |
Be careful when adding someone to an existing discussion group. For example, Finsight documents that users added later to a permission group can see question threads already shared with that group. Check the behavior of the service you use before adding a new participant. Finsight's Q&A documentation.
Keep a private record of which answers were approved for which teams. For the ongoing process, use the guide to managing requests from several buyers.
Check what the new person can actually open
Work through the new team's access before sending the welcome message. Check the current overview, an important financial file and any document mentioned in the catch-up note. Confirm that seller notes and another bidder's material are outside the new team's view.
Also check links in shared documents. A link to a file does not by itself give someone permission to open it, and a link to an old attachment may send them to the wrong version.
Decide whether this review needs downloads. Keep the decision consistent with the agreed process. Once someone has downloaded a copy, later changes to the room cannot update that copy. The download-permissions guide covers that choice in more detail.
Keep the timetable clear
A new invitation can create different assumptions. The seller may expect the original deadline to hold; the buyer may assume its review starts from the day it receives access.
Write down the agreed dates for questions, responses and the next decision. Confirm any extension with the person running the deal. An invitation sent by the software leaves those business decisions open until people agree them.
After the first exchange, check for practical problems: a named reviewer missing from the invite list, a file they cannot open or an unexplained correction. A successful file open tells you the link worked. It does not tell you that the buyer has understood or completed its review.
Add the new bidder's room from the current library
In Aurora, you can create a room for the new bidder and select files from the same library used for the existing review. That lets you reuse current source documents while choosing this team's access. Groups and individual permissions refine access within the room; they cannot reveal files excluded from it.
If a shared source document receives a new version, people see the current version when they reopen or refresh it in their rooms. Use the catch-up note to explain changes that matter to the review. Prepare that note and any reusable answers as ordinary documents with your own sharing decisions.
To try the setup, use three small sample PDFs: a business overview, a financial summary and an internal planning note. Create one library and two bidder rooms. Include the first two files in both rooms and keep the internal note outside them. This fits Aurora's 30-day trial and two-room allowance. For an existing deal, check the remaining room allowance before adding another. Try Aurora with a sample project.
Before sending the real invitation, finish the worksheet's starting note and unresolved-items list. The new team should be able to find today's approved files, understand the important changes and know who to ask next.
New bidder catch-up worksheet
Free to use and adapt. Keep your completed worksheet in your own project files.
Download Worksheet (.md)Use this free worksheet when a buyer joins a review already underway. Keep the internal preparation sections private. Share only the checked starting note and files approved for that bidder.
Guide: https://auroradatarooms.com/guides/adding-bidder-ongoing-review
1. Confirm the incoming team
- Deal or project:
- Bidder/team name:
- Named reviewers and email addresses:
- Advisors who also need access:
- Person coordinating the review:
- Person approving disclosure:
- Agreed confidentiality requirements checked by:
- Remaining room/user allowance checked by, if applicable:
Confirm each person's role. Avoid adding a new bidder to another bidder's existing group simply to save setup work.
2. Prepare the starting note
Prepared on (date, time and timezone):
Starting documents available from:
| File or subject | Current file link, period and revision | Important change or explanation | Approved for this team by |
|---|---|---|---|
| Business overview | |||
| Financial information | |||
| Another selected document |
For example: the quarterly accounts include Tuesday's correction; include the explanation with the corrected file.
| Item still coming | Person handling it | Next update date | Confirmed or awaiting confirmation? |
|---|---|---|---|
Where questions should go:
How reviewers should identify the file or question:
| Process date | Date and timezone | Confirmed with | Still open? |
|---|---|---|---|
| Questions due | |||
| Expected response or next update | |||
| Next decision or review step |
3. Check earlier answers for reuse
Internal preparation: keep other bidders' identities, questions and negotiations out of the shared starting note unless their disclosure is specifically approved.
| Earlier item | Still accurate? | Clean explanation to prepare | Details to keep separate | Person approving reuse |
|---|---|---|---|---|
| Explanation of a corrected figure | Confirm against the current file | Describe the correction and affected period | Original buyer's question and assumptions | |
If the earlier answer is wrong or outdated, list who needs a correction and who will send it. Check whether an existing Q&A or discussion group exposes earlier conversations to newly added members.
4. Check access before the invitation
- [ ] The invite list matches the agreed people and roles.
- [ ] The overview and other important files are the current approved versions.
- [ ] Links in the starting note lead to files this team can open.
- [ ] Seller notes and other bidders' private material are outside this team's view.
- [ ] Previous answers have been checked for accuracy and permitted reuse.
- [ ] Download settings fit the agreed process.
- [ ] Missing items have a named person and a next update.
- [ ] Timetable changes have been confirmed; unresolved dates are labeled.
Checked by:
Date and time:
5. Confirm the first exchange
Record missing reviewers, inaccessible files and questions about the starting note. Opening a file alone does not confirm that someone has understood it or finished reviewing it.
| Issue raised | Person handling it | Next action | Date |
|---|---|---|---|
This worksheet helps organize sharing. The people running the deal must decide the permitted disclosures, confidentiality arrangements and timetable. Anyone may use the blank resource without an Aurora account.
