---
title: "Manage a tender's team, details and status"
description: "Decide who can reach a tender, keep its details and team lead current, move it through its statuses, and archive or permanently delete it."
url: https://helpcenter.complytrain.net/en/articles/232-manage-a-tender-s-team-details-and-status
collection: "Getting set up"
updated: 2026-09-22
language: en
---

# Manage a tender's team, details and status

Decide who can reach a tender, keep its details and team lead current, move it through its statuses, and archive or permanently delete it.

Decide who can reach a tender, keep its details and team lead current, move it through its statuses, and archive or permanently delete it.

Each tender has a team, a set of details and a status. The team decides who can reach the tender at all. The details describe the opportunity and name the team lead. The status tells everyone where the bid stands, from **Draft** to **Won**, **Lost** or **Archived**.

## Who can change what

Product location: `/tender/workspaces/{workspaceId}` (fallback: `/tender/workspaces`). Open Tenders, then choose the tender's name in the list. The Overview tab opens.

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Action</p></th><th colspan="1" rowspan="1"><p>Permission needed</p></th></tr><tr><td colspan="1" rowspan="1"><p>Read the tender, its team and its details</p></td><td colspan="1" rowspan="1"><p><strong>View Tenders</strong> (<code>tender:view</code>), and being on the team</p></td></tr><tr><td colspan="1" rowspan="1"><p>Edit the details</p></td><td colspan="1" rowspan="1"><p><strong>Create &amp; Work on Tenders</strong> (<code>tender:manage-workspaces</code>)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Add and remove team members, change their roles and choose the team lead</p></td><td colspan="1" rowspan="1"><p><strong>Manage Tender Team</strong> (<code>tender:manage-team</code>)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Move the tender between <strong>Draft</strong>, <strong>Active</strong>, <strong>Withdrawn</strong> and <strong>Archived</strong></p></td><td colspan="1" rowspan="1"><p><strong>Create &amp; Work on Tenders</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p>Submit the tender, and record a submitted tender as <strong>Won</strong>, <strong>Lost</strong> or <strong>Withdrawn</strong></p></td><td colspan="1" rowspan="1"><p><strong>Submit Tenders</strong> (<code>tender:submit</code>)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Permanently delete an archived tender</p></td><td colspan="1" rowspan="1"><p><strong>Submit Tenders</strong></p></td></tr></tbody></table>

You must also be on the tender's team; Admins can reach every tender and pass every permission check. Controls you cannot use are not shown. See [Who can do what](https://help.complytrain.net/en/tender/overview/#who-can-do-what).

## Read the Overview

Product location: `/tender/workspaces/{workspaceId}` (fallback: `/tender/workspaces`). Open Tenders, then choose the tender's name in the list. The Overview tab opens.

Open the tender; it opens on **Overview**. The tiles summarise progress:

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Tile</p></th><th colspan="1" rowspan="1"><p>What it counts</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Requirements</strong></p></td><td colspan="1" rowspan="1"><p>Requirements marked <strong>Addressed</strong>, out of all requirements except those marked <strong>Not applicable</strong>.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Upcoming deadlines</strong></p></td><td colspan="1" rowspan="1"><p>Deadlines whose status is <strong>Upcoming</strong>.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Formality</strong></p></td><td colspan="1" rowspan="1"><p>Formalities marked <strong>Satisfied</strong>, out of all formalities except those marked <strong>Not applicable</strong>.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Output documents</strong></p></td><td colspan="1" rowspan="1"><p>Output documents that are <strong>Final</strong> or <strong>Submitted</strong>, out of all output documents.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Team</strong></p></td><td colspan="1" rowspan="1"><p>Members of the tender's team.</p></td></tr></tbody></table>

Items marked **Not applicable** are left out of both numbers, so a tile reads complete once everything that applies is done.

Below the tiles, the details show **Reference number**, **Tender type**, **Submission deadline**, **Estimated value** with its currency, **Team lead** and **Description**. A dash means a value is not recorded; **Team lead** and **Description** appear only when set.

The **Bid decision** and **Approval workflow** cards are also on **Overview**. They are commitments that need **Submit Tenders**; see [Prepare the submission](https://help.complytrain.net/en/tender/prepare-submission/).

## Edit tender details

Product location: `/tender/workspaces/{workspaceId}` (fallback: `/tender/workspaces`). Open Tenders, then choose the tender's name in the list. The Overview tab opens.

1.  On **Overview**, choose to edit the details.
    
2.  Change the fields you need. To clear an optional field, empty it.
    
3.  Save. The details card, the header and the tender list show the new values.
    

<table style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>Limits</p></th><th colspan="1" rowspan="1"><p>Where the value is used</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Tender name</strong></p></td><td colspan="1" rowspan="1"><p>Required, up to 500 characters.</p></td><td colspan="1" rowspan="1"><p>Page header, tender list, dashboard, submission package cover and file names.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Description</strong></p></td><td colspan="1" rowspan="1"><p>Up to 20,000 characters.</p></td><td colspan="1" rowspan="1"><p>The details card. The Tender Assistant reads it for context.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Issuing organisation</strong></p></td><td colspan="1" rowspan="1"><p>Up to 500 characters.</p></td><td colspan="1" rowspan="1"><p>Header, tender list and search, <strong>Win rate by organisation</strong>, submission package cover.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Reference number</strong></p></td><td colspan="1" rowspan="1"><p>Up to 255 characters.</p></td><td colspan="1" rowspan="1"><p>Tender list search, submission package cover.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Tender type</strong></p></td><td colspan="1" rowspan="1"><p>One of the listed types, or none.</p></td><td colspan="1" rowspan="1"><p><strong>Win rate by type</strong> on the dashboard and in reports.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Submission deadline</strong></p></td><td colspan="1" rowspan="1"><p>Date and time.</p></td><td colspan="1" rowspan="1"><p>Tender list order, the dashboard's <strong>Upcoming Deadlines</strong>, the submission package cover.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Currency</strong></p></td><td colspan="1" rowspan="1"><p>Exactly three letters, such as EUR.</p></td><td colspan="1" rowspan="1"><p>Shown with the estimated value.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Estimated value</strong></p></td><td colspan="1" rowspan="1"><p>A number.</p></td><td colspan="1" rowspan="1"><p><strong>Win rate by deal size</strong>, and pipeline value in reports.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Team lead</strong></p></td><td colspan="1" rowspan="1"><p>One member of the team; search by name. Needs <strong>Manage Tender Team</strong>.</p></td><td colspan="1" rowspan="1"><p>Shown on <strong>Overview</strong>. Choosing a team lead gives that member the <strong>Lead</strong> role, and the previous Lead becomes a <strong>Contributor</strong>. The team lead receives review requests for response sections, together with each section's owner.</p></td></tr></tbody></table>

The tender's vault keeps the name it was given when the tender was created.

The **Submission deadline** here is separate from the entries on the **Deadlines** tab. When the issuer moves the deadline, change both; see [Track deadlines, formalities and clarifications](https://help.complytrain.net/en/tender/deadlines-formalities/).

The details can be edited until the tender is submitted; after that they are read-only. If someone else saved a change to the tender while you were editing, your save is refused so their change is not lost. Reload the page and make your change again.

## Manage the team

Product location: `/tender/workspaces/{workspaceId}` (fallback: `/tender/workspaces`). Open Tenders, then choose the tender's name in the list. The Overview tab opens.

Open the **Team** tab. It lists each member with their role.

To add a colleague:

1.  In **Select a user…**, search for and choose the person. Everyone in your organisation who can use Tenders is listed.
    
2.  Choose their role: **Lead**, **Contributor**, **Reviewer** or **Observer**. The default is **Contributor**.
    
3.  Choose **Add**. The button is available once a person is chosen.
    

The person can reach the tender straight away: it appears in their tender list and on their dashboard. To change a member's role, add them again with the new role.

To remove a member, choose **Remove** on their row. **Remove team member?** explains that this removes the user from this tender and that they keep access to other tenders. Choose **Remove** to confirm. The tender disappears from their list, and they can no longer open it. Reassign any response sections they own; see [Write, review and approve sections](https://help.complytrain.net/en/tender/write-review-sections/).

A tender always keeps at least one member, so the last member cannot be removed. The person who created the tender joins its team automatically as **Lead**. An Admin can add themselves to any tender, for example to take over a bid when its team has left.

## Team roles and the team lead

Product location: `/tender/workspaces/{workspaceId}` (fallback: `/tender/workspaces`). Open Tenders, then choose the tender's name in the list. The Overview tab opens.

The role records each person's part in the bid, so colleagues can see who does what:

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Role</p></th><th colspan="1" rowspan="1"><p>Typical use</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Lead</strong></p></td><td colspan="1" rowspan="1"><p>The team lead: runs the bid and receives review requests for every response section.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Contributor</strong></p></td><td colspan="1" rowspan="1"><p>Writes response sections and gathers evidence.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Reviewer</strong></p></td><td colspan="1" rowspan="1"><p>Checks and approves sections before submission.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Observer</strong></p></td><td colspan="1" rowspan="1"><p>Follows the bid without working on it, such as a sponsor.</p></td></tr></tbody></table>

What each member can do comes from their permissions, not their role. To keep an observer read-only, make sure their roles in **Settings** hold **View Tenders** but not **Create & Work on Tenders**.

The team lead is the member with the **Lead** role, shown as **Team lead** on **Overview**. A tender has one Lead at a time, and the person who creates it starts as **Lead**. To hand the lead to someone else, choose them as **Team lead** in the details, which gives them the **Lead** role; giving a member the **Lead** role on **Team** has the same effect. Either way the previous Lead becomes a **Contributor**, and both need **Manage Tender Team**. The team lead receives review requests for every response section, together with each section's owner.

## Change the status

Product location: `/tender/workspaces/{workspaceId}` (fallback: `/tender/workspaces`). Open Tenders, then choose the tender's name in the list. The Overview tab opens.

1.  Open the tender.
    
2.  In the header, open **Change status…**. It lists only the statuses the tender can move to next.
    
3.  Choose the new status. The badge beside the list changes at once.
    

<table style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Current status</p></th><th colspan="1" rowspan="1"><p><strong>Change status…</strong> offers</p></th><th colspan="1" rowspan="1"><p>Other moves</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Draft</strong></p></td><td colspan="1" rowspan="1"><p><strong>Active</strong>, <strong>Archived</strong></p></td><td colspan="1" rowspan="1"><p>—</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Active</strong></p></td><td colspan="1" rowspan="1"><p><strong>Withdrawn</strong>, <strong>Archived</strong></p></td><td colspan="1" rowspan="1"><p><strong>Submitted</strong>, only through <strong>Submit tender</strong> on <strong>Submission</strong>.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Submitted</strong></p></td><td colspan="1" rowspan="1"><p><strong>Archived</strong></p></td><td colspan="1" rowspan="1"><p><strong>Won</strong>, <strong>Lost</strong> or <strong>Withdrawn</strong>, recorded with the tender's outcome action by someone with <strong>Submit Tenders</strong>.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Won</strong>, <strong>Lost</strong></p></td><td colspan="1" rowspan="1"><p><strong>Archived</strong></p></td><td colspan="1" rowspan="1"><p>—</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Withdrawn</strong></p></td><td colspan="1" rowspan="1"><p><strong>Active</strong>, <strong>Archived</strong></p></td><td colspan="1" rowspan="1"><p>—</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Archived</strong></p></td><td colspan="1" rowspan="1"><p>Nothing</p></td><td colspan="1" rowspan="1"><p><strong>Delete permanently</strong>.</p></td></tr></tbody></table>

Submitting needs **Submit Tenders**, passes the readiness check or records your reason for overriding it, and never happens through **Change status…**. See [Prepare the submission](https://help.complytrain.net/en/tender/prepare-submission/). Once a tender is **Submitted**, someone with **Submit Tenders** records whether it was won, lost or withdrawn with the outcome action on the tender; see [Record the outcome](https://help.complytrain.net/en/tender/record-outcome/).

The status affects what you see elsewhere:

-   The dashboard's **Active**, **Draft** and **Submitted** tiles count tenders by status.
    
-   **Submit tender** is available only while the tender is **Active**.
    
-   **Won** and **Lost** feed the win rates on the dashboard and in reports.
    
-   Moving a tender to **Archived** frees a place under your plan's tender limit.
    

The status also decides what can still be changed:

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Status</p></th><th colspan="1" rowspan="1"><p>What can be changed</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Draft</strong> or <strong>Active</strong>, or <strong>Withdrawn</strong> before it was submitted</p></td><td colspan="1" rowspan="1"><p>Everything, within your permissions.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Submitted</strong>, or <strong>Won</strong>, <strong>Lost</strong> or <strong>Withdrawn</strong> after submission</p></td><td colspan="1" rowspan="1"><p>The tender details, requirements, deadlines, formalities, response and documents are read-only, except that a deadline's status can still be changed. The outcome, the debrief and the clarifications can still be recorded, and the team can still be managed.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Archived</strong></p></td><td colspan="1" rowspan="1"><p>Nothing. You can open and read the tender, and permanently delete it.</p></td></tr></tbody></table>

If **Could not change the tender status. Reload and try again.** appears, someone else changed the tender in the meantime. Reload the page and choose again.

## Archive a tender

Product location: `/tender/workspaces/{workspaceId}` (fallback: `/tender/workspaces`). Open Tenders, then choose the tender's name in the list. The Overview tab opens.

Archive a tender when the bid is over and you want to keep it for reference: choose **Archived** in **Change status…**.

-   The tender stays in the tender list; filter by **Status** to find it.
    
-   It no longer counts towards the **Active**, **Draft** and **Submitted** tiles or your plan's limit.
    
-   A won or lost tender keeps counting in the win rates.
    
-   Archiving is final: an archived tender cannot return to any other status, and nothing in it can be changed.
    

Record the outcome and the debrief before archiving: once the tender is archived they cannot be added, and the result must be recorded to count in your win rates. See [Record the outcome](https://help.complytrain.net/en/tender/record-outcome/).

## Delete a tender permanently

Product location: `/tender/workspaces/{workspaceId}` (fallback: `/tender/workspaces`). Open Tenders, then choose the tender's name in the list. The Overview tab opens.

Only an archived tender can be deleted, and only by someone with **Submit Tenders**.

1.  Open the archived tender and choose **Delete permanently**.
    
2.  **Permanently delete this tender?** names the tender and lists what goes with it: requirements, deadlines, formalities, output documents, team, assessments and all uploaded documents.
    
3.  Choose **Delete permanently** to confirm. The tender list opens.
    

The tender, its vault with every document in it, and its knowledge base are deleted, and none of it can be recovered. Answer Library entries promoted from the tender stay in the library, and Submission History is not affected. If **Could not delete the tender. Reload and try again.** appears, reload the page and check whether the tender is still archived.

## Example: a framework bid team

Product location: `/tender/workspaces/{workspaceId}` (fallback: `/tender/workspaces`). Open Tenders, then choose the tender's name in the list. The Overview tab opens.

A bid manager has created "Regional Health Framework 2026 – Lot 2" from the issuer's documents. The bid involves pricing, so only the people working on it should see it.

1.  On **Team**, add the solution architect and the pricing lead as **Contributor**, the quality manager as **Reviewer**, and the commercial director as **Observer**. The commercial director's roles hold **View Tenders** only.
    
2.  Check **Team lead** on **Overview**: the bid manager created the tender, so they joined the team as **Lead** and are its team lead. Review requests for every section reach them as well as the section owner.
    
3.  Move the tender to **Active**.
    
4.  After the clarification round, the issuer moves the submission deadline back by a week. Edit **Submission deadline** in the details, and change the submission entry on **Deadlines** to match.
    

Colleagues outside the team do not see the tender in their list, on their dashboard or in tender reports. When the result arrives, someone with **Submit Tenders** records it, the team completes the debrief, and the bid manager archives the tender.
