Skip to content

Project Reference Documents

Attach source documents to a project and use them in SOW analysis and an editable AI overview

Open a project and select Documents to add briefs, specifications, contracts, or other supporting material. Documents belong to the project and provide context for its SOWs.

Add and manage documents

Project editors and owners can upload files or drag them into the Documents panel. Supported files are PDF, Word (.doc and .docx), UTF-8 text, and Markdown, up to 4 MB per file. You can select several files; each uploads separately.

Each entry shows its filename, size, upload date, and whether its text is available to agents. Anyone with project read access can download the original. Editors can remove a document after confirming which file to remove. Removal prevents future use as project reference material; it does not rewrite an existing SOW or saved overview.

Originals are stored privately in the organization’s file storage. A SOW-only sharing grant does not grant access to project documents.

Draft a project overview

On Overview, select Draft with AI after adding at least one document with readable text. Tanda’s agent uses the project’s current description and document excerpts to prepare a proposal.

Review the draft, its source documents, and any limitations. You can edit the draft before selecting Save overview, which updates the project description. Discard draft leaves the current description as it is. If someone changes the project while you are reviewing, saving asks you to reload and review a fresh draft instead of overwriting their changes.

This action does not change the project’s SOWs or agreed scope.

Use references through MCP

Ask an assistant to read the project’s supporting documents before analyzing or drafting work:

“Read the reference documents for Social Platform, then identify gaps in its SOW.”

The assistant calls list_project_documents with the project ID, then get_project_document for extracted text. Both tools require project read access and support pagination. draft_project_overview prepares an editable proposal; save_project_overview saves a reviewed version. Overview tools require write scope and editor access.

SOW generation uses reference excerpts while drafting the SOW, task items, acceptance criteria, and tests. Coverage-gap proposals also include references when the caller has project access. Assistants should cite filenames and document IDs and flag contradictions with existing scope.

Text extraction limits

Image-only or protected PDFs, encrypted Word files, and damaged documents may not have extractable text. They remain available for download, with a message explaining that agents cannot read their text. Upload a searchable PDF or an unprotected document to make the content available.

PDF text extraction supports up to 200 pages. Stored extracted text is limited to 200,000 characters per document. Automatic agent context includes up to 20 documents, 12,000 characters per document, and 60,000 characters overall. The overview draft reports when it used excerpts. The MCP read tool can retrieve further stored text; download the original when extraction itself was shortened.

Document contents are treated as source material, not instructions to the assistant. References inform proposals; they do not approve changes to scope.

Type to search…

↑↓ navigate↵ selectEsc close