Skip to content

Tenders

Tenders is for bidding work: the pipeline of opportunities, the documents each one needs, the scoring behind the decision to bid, and the named approval that let the submission go out.

Try it in the demotender · 5 tasks

Before you start

  • Approval steps, with real people named — a tender approval that routes to a role nobody holds will sit until the deadline passes.
  • A document library, so the same certificates are not re-attached from somebody’s desktop each time.

What Tenders does

Bidding work: the pipeline, the documents and who approved the submission.

01

Move a tender through its stages to submission

A tender is created, moved through stages and submitted. The stage history is the audit: it answers when the decision to bid was taken and on what.

02

Get the submission approved

Approval steps put a named person in front of the submission to approve or reject it. Both outcomes are recorded — a rejection with a reason is worth more than a bid that quietly never went.

03

Manage attachments

Attachments can be seen, added, renamed, replaced or removed, each under its own permission. Replace rather than re-add when a document supersedes another, so the bid cannot go out carrying both versions.

04

Use scoring rules, import sources and the document library

Scoring rules make the decision to bid consistent rather than a matter of who read it. Import sources bring opportunities in; the library keeps the documents you attach to all of them.

05

Read the pipeline and reports

The pipeline is the forward view, the reports the backward one — what was bid, what was won, and what it cost to find out.

Worth knowing

  • Deadlines are held in UTC. A tender that closes at midnight closes at midnight in the deadline’s own terms, not in the reader’s.

What it claims to do

The capability list this guide is written against, unabridged. Nothing above adds to it.

Tenders on the Sales page
  • Tenders created, moved through stages and submitted
  • Approval steps where a named person approves or rejects
  • Attachments seen, added, renamed, replaced or removed
  • Scoring rules, import sources and a document library
  • Pipeline and reports

Where it connects

The modules Tenders hands work to, or takes it from. Most problems that look like one module are a handover between two.