Register bids made before or outside ComplyTrain with their outcome, score and lessons, attach the submitted documents for indexing, read your win rate by programme, and let new tenders learn from the history.
Submission History is your private record of bids, including ones submitted before you used ComplyTrain or outside it. Each record holds what you bid for, who you bid to, the outcome, the score and what you learned, and can carry the submitted document. The Tender Assistant and AI writing use the history as experience when you work on new tenders, and the page shows your win rate overall and by programme.
Open Submission History in the Tenders menu.
Tenders you run in Tenders do not need to be registered here. Once a tender is recorded as Won or Lost, it is already part of the experience new tenders draw on, even after it is archived; see record the outcome.
Product location: /tender/past-submissions. Open Submission History in Tenders.
Task | Permission |
|---|---|
Browse, search and read the statistics | View Tenders ( |
Register, edit, attach documents to, re-index, archive, restore and delete records | Manage Answer Library & Past Submissions ( |
Product location: /tender/past-submissions. Open Submission History in Tenders.
Choose Register submission. The form Register a past submission opens.
Fill in the fields.
Choose Save.
Field | What to enter | Limits and defaults |
|---|---|---|
What was bid for | The tender or contract name as you know it, such as "Hospital cleaning framework, lot 2". | Required. Up to 500 characters. Without it the form shows A name is required. |
Buyer / awarding authority | The organisation that ran the competition. | Optional. |
Programme | The funding programme or framework the bid was made under, such as "Horizon Europe" or a national framework. Use the same spelling each time, because the statistics and the Programme filter group records by it. | Optional, free text. |
Outcome | Won, Lost, Shortlisted, Withdrawn or Unknown. | Won by default. |
Year | The year the bid was submitted. | A whole year from 1900 to 2200. |
Score and Max score | The score the buyer awarded and the maximum it was marked against. | Enter both or neither: A score needs its maximum to be meaningful — provide both or neither. The score must be between 0 and the maximum, and the maximum must be above 0. |
Tags (comma separated) | Topics for filtering, such as | Up to 50 tags of up to 100 characters each. |
What we learned | Feedback and lessons: why it won or lost and what to do differently. | Up to 20,000 characters. |
Notes | Anything else worth keeping, such as contract length or partners. | Up to 20,000 characters. |
To change a record, choose Edit on its row. The form Edit past submission opens with the saved values. If someone else changed the record while you were editing, reload the page and make your change again.
Product location: /tender/past-submissions. Open Submission History in Tenders.
Attach the document you submitted, so its content can be searched and used as evidence for new bids.
Upload the file to a vault in Documents, if it is not there yet. See find and upload documents.
Open the record in Submission History and attach the document from the vault.
The Indexing column shows where the document stands:
Indexing status | Meaning |
|---|---|
No document | No document is attached. The record still counts in the statistics and in what new tenders learn from. |
Queued | The document is attached and waiting to be indexed. |
Indexed | The document's content is searchable. |
Failed | The document could not be indexed. Point to the status to see the reason. |
Re-index appears while an attached document is not yet indexed. Choose it to queue the document again, for example after replacing a scanned file with a text-searchable one. You can replace the attached document with another one or remove it from the record; the file itself stays in its vault.
Product location: /tender/past-submissions. Open Submission History in Tenders.
The figures at the top cover every record that is not archived.
Figure | What it shows |
|---|---|
Win rate | Won divided by the records that were decided (won, lost or shortlisted), with a line showing how many of all records were decided. Shows "—" until a record is decided. |
Won, Lost, Shortlisted | The number of records with each outcome. |
Win rate by programme | For each programme: won, lost and the win rate. Records without a programme are grouped under No programme. |
Withdrawn and Unknown records count in the totals but not in the win rate. Shortlisted counts as decided but not as won, so the win rate here can be lower than the dashboard's win rate for tenders run in Tenders.
Product location: /tender/past-submissions. Open Submission History in Tenders.
Filter | How it works |
|---|---|
Search | Finds words in what was bid for, the buyer, programme, lessons and notes, and any part of the name. Press Enter or choose Apply. |
Outcome | One outcome, or All outcomes. |
Programme | One programme, or All programmes. The list offers every programme in use. |
Year | Records submitted in one year. |
Show archived | Includes archived records, marked Archived. |
The list shows the most recent submissions first, a page at a time, with the columns What was bid for (and the buyer underneath), Programme, Outcome, Year and Indexing.
Product location: /tender/past-submissions. Open Submission History in Tenders.
Archive keeps the record but stops new tenders learning from it and leaves it out of the statistics. Use it for bids that no longer reflect how you work. Restore brings it back.
Delete removes the record after you confirm Delete this record?. The outcome and lessons are lost; an attached document stays in its vault. Archive instead if you only want the assistant to stop learning from it.
Product location: /tender/past-submissions. Open Submission History in Tenders.
Records that are not archived and whose outcome is Won, Lost or Shortlisted are used together with the tenders you have won or lost in Tenders:
Cross-reference knowledge on a tender's AI assessments tab includes them in its results, counted under Past submissions.
When AI drafts a response section, it is given your past submissions, with their outcomes and buyers, as experience to learn from.
The Tender Assistant can look them up, including What we learned, when you ask what you have bid for before, for example "Have we bid to this health authority before, and what did we learn?".
Attached documents can also turn up when your team searches for existing evidence. The history is private to your organisation.
Product location: /tender/past-submissions. Open Submission History in Tenders.
A facilities company moves its bid archive into ComplyTrain.
For each of last year's twelve bids, the bid coordinator chooses Register submission, enters the name, buyer, Programme (for example "Crown Commercial Service FM framework"), Outcome, Year, and the score out of the maximum where the buyer published one.
Under What we learned, the coordinator pastes the key points from each debrief letter.
The submitted PDFs are uploaded to the company's bid archive vault and attached to their records. The Indexing column moves from Queued to Indexed.
Win rate by programme now shows that the company wins 4 of 6 bids under the framework but only 1 of 5 open competitions, and the team uses that when making the next bid decision.
