> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tendor.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Projects

> How projects work in Tendor, from qualification checks to documents, AI assistance, routines, and submission review.

A project is the working space for a tender, grant, or standalone bid effort. It keeps project files, opportunity resources, AI analysis, drafts, comments, versions, AI-created files, and final exports together.

<CardGroup cols={2}>
  <Card title="Watch projects and AI" icon="circle-play" href="/guides/videos/projects-and-ai">
    See how project workspaces and Ask AI work together.
  </Card>
</CardGroup>

## Create a project

You can create a project from an opportunity or start a standalone project from **Projects**.

Use a standalone project when:

* The buyer sent documents directly to your team
* The opportunity is not in the feed
* You need a workspace for a renewal, panel response, or standalone bid task
* You want to organise documents before linking them to a sourced opportunity

## What belongs in a project

Use the project as the working record for one bid, grant, renewal, or response.

| Keep in the project                     | Keep in the Library            |
| --------------------------------------- | ------------------------------ |
| Buyer tender packs and addenda          | Current insurance certificates |
| Draft responses and pricing files       | Licences and accreditations    |
| Returnable schedules and declarations   | Policies and procedures        |
| Clarification notes and review comments | Case studies and references    |
| Final exports and submitted versions    | Capability statements and CVs  |

## Before you write

Run **Pre-qualification / Gap Analysis** before drafting the full response. It helps your team decide whether to proceed and what must be fixed first.

The analysis should surface:

* Tender asks and mandatory requirements
* Fit and non-fit findings against your organisation evidence
* Hidden disqualifiers and red flags
* Compliance, capability, evidence, commercial, and timeline gaps
* Human review items
* A go, no-go, or proceed-with-caution recommendation
* Source references from the tender pack and your Library

<Warning>
  Do not treat generated analysis as a final bid decision. Use it to focus human review on requirements and gaps that can change the outcome.
</Warning>

## Project files

Use project files for submission-specific material:

* Buyer tender packs and addenda
* Draft responses
* Pricing files
* Returnable schedules
* Declarations and forms
* Meeting notes and review comments
* Final exports

You can organise files into folders, search attachments, preview supported files, download files, and download groups of files where available.

## Ask AI in a project

Project chat keeps the project context attached. Ask AI can use available project files and opportunity resources to answer questions, draft content, find gaps, or prepare checklists.

If Ask AI needs another document, it may request the file in chat. Upload the requested file and continue the same conversation.

## Work with your team

Use projects to keep bid work visible:

* Put buyer documents and draft files in one place
* Use clear file names so teammates can find the right version
* Keep reusable evidence in the Library rather than copying it into every project
* Review AI-generated drafts before they become submission content
* Record final decisions, risks, and next actions where the team can find them

Some AI-created files and reports also appear in **Results** or **Ready for review**. Use the project when the work belongs to one submission, and use Results when you want to review generated work across your workspace.

## Document workspace

Use the document workspace to edit supported Office files, leave comments, save reviewed drafts, and export final documents. AI-generated document changes should be reviewed before they become the final submission version.

## Routines

Use routines for repeated project work, such as keeping project context current, preparing recurring summaries, or checking for follow-up actions.

## Submission review

Before submitting, confirm:

* Mandatory requirements are answered
* All required attachments are included
* Evidence is current and correctly referenced
* Pricing, declarations, and approvals have been reviewed
* Final exports open correctly
* The team has recorded the outcome or next action