Create a tender with the New Tender wizard by filling it in, uploading the tender documents and reviewing what was found, or describing the opportunity to the assistant.
The New Tender wizard creates a tender and everything it needs: its own document vault, a knowledge base the assistant reads from, and a place on the team for you. You can fill the details in yourself, upload the issuer's documents and review what the assistant finds in them, or describe the opportunity to the assistant in conversation.
Product location: /tender/workspaces/new. Open Tenders, then choose New Tender.
You need Create & Work on Tenders (tender:manage-workspaces). See Who can do what.
Your plan must allow another tender that is not archived; see The plan limit on tenders.
Document storage must be set up for your organisation, because each tender gets its own vault in Documents.
For the upload route, have the tender documents to hand as PDF, Word (.doc or .docx), plain text, Markdown or RTF files.
Product location: /tender/workspaces/new. Open Tenders, then choose New Tender.
Open Tenders and choose New Tender, either on the dashboard or on the tender list. The wizard asks How would you like to start this tender?
Choice | Use it when | What happens after Create tender |
|---|---|---|
Upload a tender document | You have the RFP, tender notice or other documents from the issuer. | The files are uploaded and read, and the Tender Assistant opens. Each document is analysed, and you review the requirements, deadlines, formalities and expected outputs found in it and choose which to add. |
Fill in manually | You prefer to type the details and build the lists yourself. | The tender opens on its Overview. |
Describe to AI | You know the opportunity but have no documents yet, or want to talk it through. | The Tender Assistant opens and asks you about the opportunity, then sets the tender up from your answers. |
The next step shows the chosen route's name at the top. Back returns to the three choices; Cancel returns to the tender list without creating anything.
Product location: /tender/workspaces/new. Open Tenders, then choose New Tender.
Every route asks for Tender name. Fill in manually also shows the other fields:
Field | What it holds | Limits and default |
|---|---|---|
Tender name | The name your team will recognise, such as the programme and lot. It also names the tender's vault. | Required. Up to 500 characters. |
Issuing organisation | The buyer or awarding body. It appears under the tender name and in the tender list, and drives Win rate by organisation. | Optional. Up to 500 characters. |
Reference number | The issuer's reference for the opportunity. It is searchable in the tender list and printed on the submission package cover. | Optional. Up to 255 characters. |
Tender type | The kind of opportunity: Request for Proposal (RFP), Request for Quote (RFQ), Invitation to Tender (ITT), Request for Information (RFI), Grant, Framework agreement or Other. It drives Win rate by type. | Defaults to Unspecified. |
Submission deadline | The date and time the bid is due, in your local time. It orders the tender list and feeds Upcoming Deadlines on the dashboard. | Optional. |
Currency | The currency of the estimated value, as a three-letter code. | Optional. Exactly three letters, for example EUR, GBP or DKK. |
Estimated value | The expected contract or grant value, as a number, for example 2500000. It sets the tender's Win rate by deal size band. | Optional. Must be a number; the wizard tells you when it is not. |
Approval workflow | How documents in the tender's vault are approved. No approval: documents go straight from draft to published. Review & approval: documents are submitted for review, then approved before publishing. | Defaults to No approval. |
With Upload a tender document and Describe to AI, only the name is asked for. The other details are filled in from the documents or the conversation, and the approval workflow starts as No approval. You can change any of them afterwards; see Edit tender details.
Product location: /tender/workspaces/new. Open Tenders, then choose New Tender.
Choose Upload a tender document and enter the Tender name.
Under Tender documents, drag the files onto Drag & drop your tender documents here, or select the area to browse. You can also reach it with the Tab key and press Enter or Space to browse.
Check the file list. Each file shows its size; choose Remove beside a file you added by mistake. Adding the same file twice has no effect.
Choose Create tender. The button reads Creating… while the tender is created and the files are uploaded.
Files of any other type are left out, with the message Some files were skipped — only PDF, Word, text, Markdown and RTF files are allowed. If you choose Create tender without a file, the wizard asks you to Add at least one tender document to upload.
Ingesting provided information then shows each file with its progress, for example Reading text… or Indexing…, and a count such as 2 of 3 document(s) ready. A file that cannot be searched, such as a recording when transcription is not enabled for your organisation, shows Not searchable; a file that could not be processed shows Failed. When every file has finished, the Tender Assistant opens by itself and asks about anything it could not find in the files. Continue to chat anyway opens it straight away while the files finish in the background.
In both cases, each document is also analysed for the review described next. The assistant never adds what the analysis finds on its own: nothing reaches the tender until you have reviewed it.
Product location: /tender/workspaces/{workspaceId}/rfp-analysis/{documentId} (fallback: /tender/workspaces). Open the tender; a finished analysis offers its review of what was found in that document.
Each uploaded document is analysed separately, and the whole of each document is read. While an analysis runs, its progress shows, for example Extracting requirements… and Extracting deadlines…. When a document's analysis finishes, the tender shows what was found in it for you to review. An analysis you have not reviewed stays waiting on the tender, including while you work in the Tender Assistant.
The review lists what was found under Requirements, Deadlines, Formalities and Expected outputs. Each item shows its type and the page it came from, for example p. 12; expected outputs the issuer demands carry Required.
Read each item against the tender documents. Untick anything you do not want, such as background information that is not a requirement or a date that was misread.
Choose the add button, which shows how many items are ticked, for example Add 40 to the tender. The button reads Adding… while they are saved.
The tender opens with a message such as Added 40 item(s) to the tender.
Choose Skip for now to open the tender without adding anything; the analysis stays waiting for your review. If nothing was found, the page says so; you can still build the tender yourself. Review each document's analysis in the same way.
Added items are ordinary entries on the Requirements, Deadlines, Formality and Output documents tabs. Edit, re-prioritise or delete them there like items you typed yourself. See Capture and track requirements and Track deadlines, formalities and clarifications.
The analysis reads only this tender's documents. The uploaded files stay in the tender's vault, where the assistant and later analyses can use them. To analyse a document you add later, see Analyse the RFP and run assessments.
Product location: /tender/workspaces/{workspaceId}/chat (fallback: /tender/workspaces). Opens by itself after Create tender; later, open the tender and choose Chat with AI.
Choose Describe to AI, enter the Tender name and choose Create tender.
The Tender Assistant opens and asks what it needs: the opportunity, the issuing organisation, key dates, the estimated value and any formal requirements.
Answer in your own words. The assistant fills in the tender's details and adds requirements, deadlines and a response structure from your answers.
Review what it added on each tab before relying on it. See Work with the Tender Assistant.
Product location: /tender/workspaces/new. Open Tenders, then choose New Tender.
A new tender in Draft, with the details you entered. It appears in the tender list and on the dashboard for everyone on its team.
You, as the first member of the tender's team, with the Lead role. That makes you the tender's team lead.
A document vault named after the tender, for example Tender — Regional Health Framework 2026 [3f9a1c2e], holding any files you uploaded, and a knowledge base that indexes them for the assistant. See What a new tender creates.
The chosen approval workflow on that vault.
A new tender counts towards your plan's limit on tenders that are not archived. When the bid work starts, move the tender to Active; see Change the status.
Product location: /tender/workspaces/new. Open Tenders, then choose New Tender.
What you see | What to do |
|---|---|
A tender name is required. | Enter a name. |
A message that your plan's tender limit has been reached | Archive a tender you have finished with, or ask your Admin to move to a larger plan. |
A message that document storage or the knowledge-base set-up is not ready for your organisation | Ask your Admin to contact ComplyTrain support. No tender is created. |
A message that the estimated value is not a number | Enter the amount as digits, for example 2500000. |
Could not upload the tender document. Please try again. | The tender has already been created. Create the tender again from the same page: the wizard continues with the tender it already made and retries the upload, without creating a second tender. |
Could not create the tender. Please try again. | Nothing was created. Check the details and choose Create tender again. |
Product location: /tender/workspaces/new. Open Tenders, then choose New Tender.
Your bid manager is preparing a response to a regional health authority's framework for clinical-software services. The issuer has published a 90-page invitation to tender, a pricing schedule and a declarations form. Questions are allowed until 24 October, and bids are due at noon on 14 November.
Choose New Tender, then Upload a tender document. Name the tender "Regional Health Framework 2026 – Lot 2".
Drop in the three files and choose Create tender. When Ingesting provided information finishes, the Tender Assistant opens; answer its questions about anything the files did not say.
When the invitation to tender's analysis finishes, open its review. Untick the paragraphs describing the authority's background, keep the 34 requirements, the question deadline and the submission deadline, keep the signed-declaration and 40-page-limit formalities, and keep the technical response and pricing schedule as expected outputs. Choose Add 40 to the tender: 34 requirements, two deadlines, two formalities and two expected outputs. Review the pricing schedule's and the declarations form's analyses the same way, unticking anything already added.
On Overview, edit the details: set Issuing organisation, Reference number, Tender type to Framework agreement, Submission deadline to 14 November at 12:00, Currency GBP and Estimated value 4800000.
On Team, add the solution architect, the pricing lead and the quality manager.
Move the tender to Active.
The tender now appears under Upcoming Deadlines on the dashboard of everyone on its team. Record the questions you raise before 24 October on Q&A, linked to the requirements they concern; see Track deadlines, formalities and clarifications.
