Use the dashboard, the tender list, the Answer Library and Submission History, see who can do what and who can reach each tender, and what a new tender sets up for you.
Tenders is where your organisation prepares bids and grant applications. For each opportunity you record what the issuer asks for, track its deadlines and formal conditions, write and review the response documents, submit, and record the outcome. Finished bids feed a library of reusable answers and a history of past submissions.
When Tenders is enabled for your organisation, Tenders appears in the main menu for people with a licensed seat. Training learners do not see it; see Manage seats and account classes. Inside the module, the dashboard and the navigation are titled Grants & Tenders.
Product location: /tender. Open Tenders in the main menu; the Grants & Tenders dashboard opens.
Open Tenders in the main menu. The module's navigation has four entries:
Navigation entry | Page | What it is for |
|---|---|---|
Dashboard | Grants & Tenders | Your tenders at a glance: counts by status, win rates, recent tenders and upcoming deadlines. |
Tenders | Tenders | The list of tenders you can reach. While you are in the list, All Tenders and New Tender appear beneath it. |
Answer Library | Answer Library | Approved, reusable answers to questions that come up in bid after bid. |
Submission History | Submission History | Past bids, including ones submitted before you used ComplyTrain, with their outcome and lessons. |
New Tender on the dashboard or the list opens the wizard that starts a tender. See Start a tender.
Product location: /tender. Open Tenders in the main menu; the Grants & Tenders dashboard opens.
The dashboard shows only tenders you can reach. Admins see every tender.
Area | What it shows |
|---|---|
Active, Draft, Submitted | How many tenders are in each status. Archived tenders are not counted. |
Win rate | Tenders won as a share of tenders won or lost, from the outcome recorded with each tender's outcome action, which also sets the debrief's Outcome. The caption shows the counts, for example 3 won · 2 lost. Archived tenders keep counting. A dash means no tender has been decided yet. |
Win rate by organisation | The win rate for each issuing organisation. Tenders without one are grouped together. |
Win rate by type | The win rate for each tender type, such as Framework agreement or Grant. |
Win rate by deal size | The win rate in the bands Under 100k, 100k – 1M, Over 1M and Unspecified value. The bands compare the estimated amount only, whatever its currency. |
Recent Tenders | The tenders most recently worked on, each with its status. Choose a name to open the tender. |
Upcoming Deadlines | The next submission deadlines still to come on open tenders, that is tenders in Draft, Active or Submitted, soonest first. |
The three breakdown tables appear once at least one tender has been won or lost. They list only organisations, types and bands with a decided tender, best win rate first, and the organisation table shows up to 20 organisations. When you have no tenders yet, Recent Tenders shows No tenders yet.
Product location: /tender/workspaces. Open All Tenders in the Tenders navigation.
Open Tenders, or All Tenders beneath it. Each row shows Name, Issuing organisation, Status and Deadline; a dash means the value is not recorded. Choose the name to open the tender.
Filter | What it does |
|---|---|
Status | All statuses, or one status. The list updates as soon as you choose. |
Search | Finds tenders whose name, issuing organisation or reference number contains what you type, in any combination of capitals. Press Enter or choose Apply. |
Deadline range | Limits the list to tenders whose submission deadline falls between two dates. |
The list is sorted by submission deadline, soonest first, with tenders that have no deadline at the end. Archived tenders stay in the list; choose a status to hide them. No tenders match means nothing fits the filters.
Every tender has one of seven statuses:
Status | Meaning |
|---|---|
Draft | The tender is being set up. New tenders start here. |
Active | You are working on the bid. Only an active tender can be submitted. |
Submitted | The bid has been submitted through Submit tender. Its details, requirements, deadlines, formalities, response and documents are read-only, except that a deadline's status can still be changed; the outcome, debrief and clarifications can still be recorded, and the team can still be managed. |
Won / Lost | The issuer's decision has been recorded. |
Withdrawn | You stopped pursuing the tender. It can be made active again. |
Archived | The tender is closed and kept for reference, and nothing in it can be changed. Only an archived tender can be permanently deleted. |
Tenders in Draft, Active or Submitted are open: the bid is still in play. How a tender moves between statuses, and who may move it, is described in Manage a tender's team, details and status.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open Tenders, then choose the tender's name in the list.
A tender's page shows its name and issuing organisation, its status with Change status…, and Chat with AI, which opens the Tender Assistant. The tabs hold the work:
Tab | What it holds | Described in |
|---|---|---|
Overview | Progress tiles, the tender's details, the bid decision and the approval workflow. | |
Requirements | What the issuer requires, with priority, progress and whether you can meet each one. | |
Deadlines | Dates such as the question deadline and the submission deadline, with reminders. | |
Formality | Formal conditions such as signatures, certificates, language and page limits. | |
Output documents | The documents you must produce, and their response drafts. | |
Team | Who can reach the tender, and their role on it. | |
Compliance matrix | Every requirement and what addresses it, with exports. | |
Win/loss | The debrief once the result is known. | |
Q&A | Clarification questions to the issuer and the answers received. | |
Submission | The readiness check, the submission package and Submit tender. | |
Chat | Opens the Tender Assistant. | |
Products | The product configurations this bid offers, and answers drawn from them. | |
AI assessments | Readiness, improvement and gap assessments. | |
Documents | The files in the tender's own document vault. |
The page remembers the open tab in its address, so a link you share opens on the same tab.
Product location: /tender/answer-library. Open Answer Library in the Tenders navigation. Submission History is the next entry.
The Answer Library holds answers your organisation has approved for reuse, such as a standard description of your quality system or your data-protection arrangements. Writers insert approved answers into response sections. See Build and use the Answer Library.
Submission History records bids you have made, inside or outside ComplyTrain, with the buyer, programme, outcome, score and lessons learned. The Tender Assistant learns from what won and what did not. See Keep a history of past submissions.
Both are shared across your organisation rather than belonging to one tender.
Product location: /settings/roles. Open Roles & Permissions in Settings, then Roles.
Tenders permissions come from roles. An Admin adds them to roles in Settings, under Roles & Permissions, where they are listed under Grants & Tenders. See Create roles and choose their permissions. Buttons and actions appear only for people who can use them.
Permission | Code | What it allows |
|---|---|---|
View Tenders |
| Open the tenders you can reach and read everything in them: requirements, deadlines, clarifications, formalities, response documents, the compliance matrix, assessments, readiness and win-rate figures. Open response documents and your own assistant conversations read-only. |
Create & Work on Tenders |
| Create tenders and do the work of the bid: edit details, requirements, deadlines, clarifications and formalities; write and revise response documents; map requirements; bid products; run RFP analysis and assessments; move a tender between Draft, Active, Withdrawn and Archived. |
Submit Tenders |
| Make the commitments: record the bid decision, set the approval workflow, publish a response, build the submission package, submit the tender, and record a submitted tender as won, lost or withdrawn. Also needed to permanently delete an archived tender. |
Manage Answer Library & Past Submissions |
| Add, edit, approve and retire Answer Library entries, promote approved response sections into the library, and maintain Submission History. |
Manage Tender Team |
| Add and remove people on a tender's team, choose its team lead and assign response sections to them. |
Admins pass every permission check and can reach every tender.
When the Tenders permissions were introduced, every role that existed in your organisation received all five, so nobody lost access. A role you create afterwards starts without them: add the ones it needs. To keep submission with your bid managers, for example, remove Submit Tenders from the roles your writers hold.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open Tenders, then choose the tender's name in the list. Choose the Team tab.
A tender is visible only to the people on its team, and to Admins. Tenders you are not on do not appear in your list, on your dashboard, in reports or in search.
The person who creates a tender joins its team automatically with the Lead role, which makes them its team lead.
Anyone with Manage Tender Team who can reach the tender can add colleagues to it. An Admin can add themselves to any tender.
A tender always keeps at least one team member; the last member cannot be removed.
Permissions and team membership work together. Team membership decides which tenders you can reach; your permissions decide what you can do in them. A colleague on the team who holds only View Tenders can read the tender but not change it. See Manage the team.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open Tenders, then choose the tender's name in the list. Choose the Documents tab.
Creating a tender also sets up what it needs to hold documents and let the assistant read them:
Created | What it is for |
|---|---|
A document vault | Holds the tender documents you upload, drafts, evidence, published response documents and submission packages. It is named after the tender, for example Tender — Regional Health Framework 2026 [3f9a1c2e]; the bracketed code keeps names unique. It does not count towards your plan's limit on vaults. |
A knowledge base | Indexes the vault's documents so the Tender Assistant, RFP analysis and AI writing can work from them. It is used only for this tender's work and is not added to other assistant conversations. |
An approval workflow | The tender's vault uses the approval workflow chosen for the tender: No approval or Review & approval. |
The Documents tab lists the files in the vault with their document type and state. Open Document Vault opens the tender's vault in Documents, where you can upload further files. Documents are indexed while they are in draft, in review, approved or published, and leave the index when archived or made obsolete.
Permanently deleting a tender also deletes its vault and knowledge base; see Delete a tender permanently.
Product location: /settings/billing/plans. Open the Plans tab in Billing & Payments.
Your plan sets how many tenders your organisation can have that are not archived. Archived tenders do not count, whatever their outcome; won, lost and withdrawn tenders count until you archive them.
When you reach the limit, the New Tender wizard tells you so and does not create the tender. Archive a tender you have finished with, or move to a larger plan; see Choose a new plan.
Product location: /tender. Open Tenders in the main menu; the Grants & Tenders dashboard opens.
Documents: each tender's vault appears in Documents, and tender documents appear in All Documents. See Find documents.
Products: the Products tab binds product configurations from Products to the bid. Choosing a product needs the Products module and View Products. See Bid products.
Quality: when your organisation uses Quality Management, an existing quality or vault document can be attached to a requirement as what addresses it. See Check compliance and coverage.
Reports: built-in tender reports cover the pipeline and deadlines, requirement progress, deliverables, clarifications, the Answer Library and win/loss. See Record the outcome.
Notifications and tasks: assigning a response section notifies its new owner and adds a task to their inbox; review requests, approvals and assessment results arrive as notifications. Deadline reminders go to every member of the tender's team, in the app and by email according to each person's notification preferences. See Your notifications.
