Available RFP settings
- Default RFP assistant: Choose the default AI assistant that will be used to answer RFPs across your organization. This is set to Realm by default, but you can select a custom-built agent tailored for your use cases.
- Answer profiles: Named styles for how RFP answers are written, whichever assistant fills the RFP: a Concise or Detailed answer length, and writing instructions such as tone of voice or terminology. One profile is the organization default. See Answer profiles.
- Require explicit approval for export: When enabled, RFPs must receive explicit approval before they can be exported. When disabled, RFPs can be exported at any time without requiring approval. This setting applies to all newly created RFPs.
- Enable reviewers: When enabled, questionnaires show a Reviewer column where you can assign a dedicated reviewer for each answer. Reviewers can approve the rows they are assigned to. Individual RFPs can override this with the Reviewer column setting in their own RFP settings.
- Only reviewers can approve rows: When enabled, only a row’s assigned reviewer, RFP owners, and admins can approve rows, and members and assignees can’t. It applies to every RFP that has reviewers turned on, whether through Enable reviewers or the RFP’s own settings.
- Enable attachments: Adds an Attachments column to questionnaires so documents can be attached to answers and included in the export. See Attachments.
Project statuses
Project statuses are the steps a project moves through, such as To discuss, Requires research, or Follow-up with customer. Every status belongs to one of six categories: Not started, Evaluating, Drafting, Completed, No-go, and Archive. The category decides what moving a project into the status does, so a custom Completed status asks for confirmation like Completed does, and a custom No-go status records a No-go decision. Every organization starts with one status per category. You can rename and recolor these, but not delete them.- Add a status: Click + on a category. Archive takes no custom statuses.
- Edit a status: Open the status menu and choose Edit to change its name, description, or color. A status keeps its category.
- Reorder: Drag a status by its handle, or use Move up and Move down in its menu. In Drafting, the order also sets how full each status’s icon is, so the icon shows how far along a project is.
- Delete a status: Projects in the status move to their category’s built-in status.
Go/No-Go analysis dimensions
Analysis dimensions are the angles your company weighs a bid along, such as whether you may formally take part, whether the contract terms work, and whether the deal is worth the money. Realm scores each dimension separately in Go/No-Go analysis. With no dimensions configured, Go/No-Go uses its standard single-score evaluation. Adding the first dimension switches new analyses over to scoring by dimension. Deleting the last one switches them back. Analyses that already ran keep the results they have.Adding a dimension
Select Add dimension. Start from Blank dimension, or from one of the built-in templates, which you can then edit:
Each dimension has:
- Name: what the dimension is called on the analysis. Keep it short, as it is the title of a card.
- Instructions: what this dimension judges, and how strictly. Realm uses the instructions twice, first to pick the requirements this dimension should judge, then to judge them, so say what belongs to the dimension as well as what does not. Being specific matters on a large tender, because the dimensions share a fixed number of requirement judgments per analysis and a dimension that claims everything keeps only the requirements it most turns on. The instructions also decide how the run works the dimension: judging requirements one at a time, judging a related set together, or reading the tender documents themselves, as described under Three kinds of dimension.
- Knowledge: Default uses the same knowledge base as when filling out the project’s RFPs. Limited knowledge restricts this dimension to the sources you select, which is useful for a dimension that should only read your contract templates or your certificates. Uploaded files makes the files you upload the dimension’s sole knowledge base; the files land in a shared Go/No-Go Files knowledge folder, visible to the whole organization. A dimension with an empty selection or no uploaded files finds no evidence in your knowledge base, though it can still search the web if you turn that on. The Customer relationship template opens with limited knowledge pre-selecting your connected Salesforce and HubSpot integrations, so the dimension searches your CRM for the history with this buyer instead of the whole knowledge base; with no CRM connected it opens on the default knowledge base.
- Web search: lets this dimension search the web as well as your knowledge base. Off by default.
Three kinds of dimension
A dimension judges the requirements Realm extracted from the tender (one at a time, or a related set together) or reads the tender documents themselves. You do not choose between them: each analysis run reads the dimension’s instructions and the tender’s extracted requirements and decides which kind fits. The result card shows what the run did, and a document assessment lists the files it read.
A requirement dimension of either kind never sees the tender’s own text: it searches your knowledge base for evidence about the requirements, and the tender is left out because it restates the requirements and so appears to answer them. That is why a question like “is this written around a competitor’s product” becomes a document assessment. Between the requirement kinds, Realm leans toward judging a set together, and evaluates one at a time only when a dimension genuinely spans many unrelated requirements. If a run decided differently than you expected, the instructions are the lever: say plainly whether the dimension should judge your fit or read the buyer’s text, and how narrow its subject is, then re-run the analysis.
Use the arrows on each row to set the order. It is the order the dimensions appear in on the analysis. An organization can have up to 20 dimensions.
Editing or deleting a dimension does not change analyses that already ran. Re-run an analysis to apply the change.
The summary agent
The summary agent reads every dimension’s result and decides the overall recommendation. Its instructions say how to weigh the dimensions against each other. The built-in instructions weigh dimensions by severity rather than by average, treat a failed eligibility-style dimension as ruling out a Go on its own, and separate demonstrated problems from questions your knowledge base could not answer. Edit them to match how your company decides, for example to make a legal red line as decisive as eligibility. Reset to default restores the built-in instructions.Dimensions and the summary agent are organization-wide, and changing them
needs permission to manage organization settings. Every project’s Go/No-Go
analysis uses the same set.