Go/No-Go analysis

Go/No-Go analysis reads the tender files in a project, pulls out what the buyer asks for, and checks each requirement against your knowledge base. It answers two questions:

• Can we bid? Whether you meet the formal conditions for taking part.
• Should we bid? How well your capabilities match what the buyer wants.

You find it on the Go/No-Go Analysis tab of a project. The analysis ends with a recommendation, and the tab is also where your team records the decision it actually makes.

​

Running an analysis

By default Realm leaves the least critical requirements out of the evaluation to keep it fast. To evaluate everything, open the menu on the Start Extraction button and choose Evaluate all. If the evaluation fails, the header offers Retry Evaluation.

​

Types of requirement

Realm sorts every extracted requirement into one of four types, and each type is used differently.

​

Can we bid?

The Can we bid? panel collects every qualification requirement that needs attention, worst first, with the file it came from. A failed qualification only counts as a blocker when the tender makes it a condition of taking part. Other failures are gaps. Hard blockers come first in the list, because they decide the question on their own. Select a finding to open it. The dialog shows the requirement, the evidence Realm found, and the sources behind the verdict. Previous and next controls step through the whole list without closing the dialog, and resolving a finding moves you to the next one, so you can work through the panel in one pass.

​

Solution fit score

Capability requirements produce the solution fit score, rated from Very Low to Very High. Each requirement counts according to how critical the tender makes it, from Must-have down to Minor. The score counts only the requirements where your knowledge base held evidence one way or the other. Requirements with no evidence are shown as No evidence and do not count against you, and commercial terms and procedural items stay out of the score entirely. If nothing could be scored, the header says so instead of showing a number. The caption under the score says how many capability requirements were scored, and how many were left out for lack of evidence. Below the panels, requirements are grouped by the file they came from, so you can open a file and read every verdict in it.

​

Overriding a verdict

When you know better than the analysis, open the requirement and use the Reviewer override section of the dialog. Choose the verdict yourself: Yes, Partially, No, or No evidence. For a failing qualification you also set whether it is a resolvable or a hard blocker. Every override needs a written reason, an evidence document, or both, and then Save override. An uploaded document also joins the project’s files, so the rest of the team can see it. Use Edit override to revise yours later, or Clear override to hand the requirement back to Realm’s verdict. The score updates as soon as you save, and Realm’s original verdict stays visible next to yours. Once verdicts have changed, the header offers Regenerate analysis, which rewrites the written analysis from where the verdicts now stand.

​

Recording the bid decision

Realm states a recommended action, Go, No-bid, or Improve position, with the reasons behind it. The recommendation is advice. The Bid decision panel records what your team decides. Select Record decision and fill in:

• the outcome: Go, No-bid, or Improve position,
• the rationale for it,
• any conditions attached to it,
• follow-up actions, which team members can check off as they are done.

You cannot record a decision while an evaluation is still running or while the analysis is being written, so the decision always rests on a complete assessment. A decision keeps a frozen snapshot of the assessment it was based on, and every past decision stays visible, so you can see what was known at the time. If a decision differs from Realm’s recommendation, the panel says so. If the assessment changes afterwards, the decision is flagged as based on an older assessment. To change course, record a new decision. The decision also sets the project’s status: A No-go project stays in the RFP list under its own status instead of being archived, and all three statuses can be used as filters there.

​

Keeping the analysis current

A banner flags the analysis as possibly outdated when the project’s documents change, when the linked tender notice is superseded by a newer version, or when the submission deadline changes. Select Re-run analysis to extract and evaluate everything again. Re-running discards reviewer overrides, so Realm warns you first and says how many would be lost. Other ways to refresh the analysis:

• Re-evaluate in the header’s actions menu keeps the extracted requirements and evaluates them again. You can pick a different agent for the new run.
• Changing the project language reevaluates every requirement and regenerates the analysis in the new language.

​

Comparing with a previous round

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 Previous round comparison card then sorts this round’s requirements into changed, unchanged, new, and no longer present, summarizes what changed in each reworded requirement, and surfaces the comments your team left on the previous round’s questionnaire rows. Select View details to read them. The comparison is context, not a verdict. It colors the written analysis but produces no score of its own. Linking or changing the previous round after an analysis re-runs only the comparison, so press Regenerate analysis to fold it into the analysis text. If the linked round changes later, the card flags the comparison as outdated and offers a re-run.

​

Customer context from your CRM

When a project is linked to a CRM opportunity, the opportunity and its account become background for the analysis. CRM content is never cited as a source. If an analysis already exists when the link changes, Realm marks it as outdated so you can regenerate it.

​

Exporting the analysis

Choose Export from the actions menu in the header to download the analysis as an Excel workbook. It holds an overview sheet with the headline, score, verdict counts, and written analysis, a sheet of eligibility findings, and a sheet of every requirement with its verdict, explanation, override, and sources.

​

Asking questions about the analysis

Embedded Chat can read the project’s files, summary, Go/No-Go analysis, extracted requirements, and progress. Use it to ask why a requirement got the verdict it did, or what a blocker would take to resolve. See Realm inside RFPs.