Skip to main content
A buyer often runs a tender in several rounds. Each round has an updated set of documents and questionnaires, where only some requirements change. Realm uses the previous round in two ways: You can use both. Both work best when you link the previous round on the project first.

Linking the previous round

Open the new project and click Link previous round in the project header. Realm suggests the projects whose requirements match best. If the earlier round never went through Realm, link its files instead. In the same popover, choose Pick a knowledge folder to link a knowledge base folder with the old round’s files, or Upload a .zip to upload them as an archive. Realm extracts an uploaded zip into a shared knowledge folder named after the archive, and links that folder when the files finish processing.

Previous round comparison

If your company bid on an earlier round of the same tender through Realm, link that project as the previous round from the project header. Realm suggests likely candidates based on matching requirements. The comparison is available in both analysis views: as its own sidebar section in the dimensions workspace, and as a card with a View details dialog in the classic analysis. If the earlier round never went through Realm, compare against its files instead. From the same popover, choose Pick a knowledge folder to link a knowledge base folder holding the old round’s files, or Upload a .zip to upload them as an archive. An uploaded zip is extracted into a shared knowledge folder named after the archive, and Realm links that folder once the files finish processing. The comparison reads every document in the linked folder, parsing its spreadsheets so the file-by-file diff works the same as between two Realm projects. Reviewer comments only exist for rounds run in Realm, so a folder comparison has no feedback grading. Previous round comparison then appears in the Analysis tab’s sidebar, with four pages listed under it while it is open:
  • Overview: a headline and a short read on what the buyer rewrote, a few points on what the round means for your bid (the work ahead, the biggest risk, what got easier, and what became of your feedback), how much of your previous work carries over, the themes behind what changed, and a summary of your feedback. Beside it, About this comparison names the round it compares against and when it ran. Every count opens the list behind it, so selecting Reworded opens the reworded requirements.
  • Our feedback: each point your team raised last round and whether this round took it up.
  • Requirements: every requirement of this round matched against the last one.
  • Files: every compared file, each opening to its own changes.
Each list has a search box and filters with their counts, and shows one line per row. Select a row to read it in full in a panel beside the list. The sidebar flags how many of your points were not taken up. On the overview, Export Excel downloads the comparison as an Excel workbook: an Overview sheet with the written brief, its themes and each file’s counts, a Changes sheet with one line per change (a changed row gets a line per changed column, with the previous and current text side by side), and a Feedback sheet of your previous round’s points and what this round did with them. The comparison is context, not a verdict. It colors the written analysis but produces no score of its own.

How much carries over

The overview counts this round’s requirements as unchanged, reworded, or new, each with what it means for the bid: an unchanged requirement means your previous answer stands, a reworded one means starting from that answer and checking it, a new one means there is nothing to start from. The previous round’s questions that are no longer asked are counted apart, since they are not part of this round’s total. Two sets of counts appear on the page and they are not the same population. The requirement counts are matched across the whole round. The per-file counts are rows of each file. The page labels which is which, and they do not add up to each other.

What changed

Rather than list thousands of individual edits, Realm groups them into at most five themes and ranks them by how much they affect your bid (for example, every integration becoming its own requirement, or a scope statement naming a priority it did not name before). Each theme is a card with what is at stake and one change quoted from the files as it reads in both rounds; the first two start open. Theme sizes and quotes come from the files themselves, so they cannot drift from what the diff found.

Our feedback

If your team commented on the previous round’s rows, or answered a comment-form questionnaire, the comparison grades each of those points on whether this round takes it up: taken up, partly taken up, not taken up, or cannot tell from the documents. The list opens on the points not taken up; the filters switch to the other grades. Opening a point shows what you asked, what this round did with it, and why it got that grade.

Files

The files are listed busiest first, each with its changed, new, and gone row counts. Opening a file lists its individual changes, filtered by kind:
  • A changed row names the column that changed and shows the old and new value, for example a transfer method changing from real-time to SFTP, or a scoring class moving from V1 to V2.
  • Rows added or removed together, such as a whole service area dropped from a price form, collapse into one line with their row range instead of dozens of entries.
  • A row that reappears on another sheet shows as moved, and a row folded into a wider requirement shows as merged, with the surviving text.
  • The same new or removed row appearing several times is listed once with a count.
  • Sheets renamed between rounds are paired anyway. Supplier answer and score columns are left out of the comparison, and About this comparison says which.
Supporting documents (contracts, specifications, and other non-questionnaire files) are compared the same way, section by section, with a sentence on what each change means for a bidder. Changes that the totals count but that are not worth reading one by one sit behind each file’s Set aside filter rather than being dropped: edits that reword nothing (spacing, list numbering, punctuation), rows that only moved between sheets or merged into a wider requirement, and the rows of files only one round has, such as a market-dialogue form that this round does not use.

Requirements

Requirements pairs each of this round’s requirements with the question it came from, filtered by what happened to it: reworded, new, no longer asked, or unchanged. It opens on the reworded ones. Opening a requirement shows its wording in both rounds and any comments your team left on that question.

Keeping the comparison current

Linking or changing the previous round after an analysis exists refreshes only the comparison, not the written analysis. To fold the previous round into the analysis text, re-run a dimension analysis, or select Regenerate analysis on a standard one. If a file in either round changes later, the comparison is flagged as out of date under its title, and Re-run compares the rounds again.

Reuse previous answers

When you upload the new round’s questionnaire, Realm finds the questions you already answered in an earlier RFP, and offers to copy those answers.

Steps

  1. Upload the new questionnaire and let Realm process it.
  2. A tab on the section’s fill bar says how many answers Realm can reuse. Click Open on the tab.
  3. Check the suggested previous RFP. To use another one, pick it from the list at the top of the dialog.
  4. Review the rows. Each row shows the question and the previous answer. Clear the check box of any row you don’t want.
  5. Click Import. Unchecked rows stay open for filling.
If you closed the tab, or work on the RFP has already started, click Reuse previous answers next to the approval count in the RFP header.

Which previous RFP Realm suggests

  • If the project is linked to its previous round, Realm compares against that project’s RFPs.
  • Otherwise, or if none of them match, Realm compares against your 100 most recently updated RFPs.
  • Realm suggests an RFP that answers at least half of the open questions, or that belongs to the linked previous round. An RFP that shares only a few questions, such as the company name, is not suggested.
  • A filled-in RFP that you uploaded to the answer library also counts as a previous round.
The list in the dialog offers every RFP that answers at least one question, best match first, with how many questions each answers, its date and its tags. Without a linked previous round, it shows at most ten.

How rows are matched

Realm matches rows by their question text. It ignores requirement numbers, case and punctuation. Hover over Question changed to see what changed, with the edits to the earlier wording marked.

Answers that need a check

Realm checks each previous answer before import: Both labels import the answer without its review status, so a reviewer checks it. Realm skips the previous-buyer check when the previous RFP is in the same project or in the linked previous round, because the buyer is the same.

Answer quality of imported answers

When an imported approval ends, Realm grades the answer with the previous answer as its source. The answer quality details say why.

People, attachments and history

  • A row that keeps its approval also gets the previous row’s responders or team, and its reviewers, unless the row already has them. Nobody is notified about these rows.
  • Other imported rows come in unassigned. To assign them to the same people, turn on the switch in the dialog. Realm then sends the usual assignment notifications.
  • People who have left the organization are skipped.
  • Each imported row gets the previous row’s attachments, except files you can’t open. See Attachments.
  • Each imported row records in its activity which RFP it came from. The answer keeps its original sources, and an imported approval stays with the person who approved it.

Rules

  • An RFP can be based on one previous RFP only.
  • Realm imports only into rows that have no answer yet. Cells that already hold an answer are never overwritten.
  • A cell that still shows the buyer’s text, such as “Select from the list”, counts as unanswered.
  • Imported rows are left out of the fill plan, so filling the section writes only the rows that are still open.
  • While a fill is running, the import is unavailable.
  • If a row gets an answer after you open the dialog, or its previous answer changes, the import leaves that row out and says how many rows it left out.

Importing again

To import from another RFP, remove the link first. Click the previous RFP’s name in the RFP header and choose Remove link. Then click Reuse previous answers. Only RFP managers can remove the link. The answers already imported stay.