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.
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.
Bidding work: the pipeline, the documents and who approved the 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.
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.
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.
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.
The pipeline is the forward view, the reports the backward one — what was bid, what was won, and what it cost to find out.
The capability list this guide is written against, unabridged. Nothing above adds to it.
Tenders on the Sales pageThe modules Tenders hands work to, or takes it from. Most problems that look like one module are a handover between two.