1. E-procurement Portal
  2. Features
  3. Tender desk
Feature · Tender desk

Tender desk

Tender desk for the procurement team and its reviewers.

OverviewApproved Tenders for Award
E-procurement Portal · Tender desk

Approved Tenders for Award

Ordered waits for the buyer

New
Tender numberParentOffer USDEvaluation scoreDecision atRevision
TS-80001PR-746805107027 Oct320
TS-83434PR-509224306012 Oct950
TS-82608PR-415363801517 Oct110
TS-56674PR-378575502511 Oct690
TS-73899PR-978443902510 Oct50
6 of 6 records
PR-74680Tender submissions · TS-80001
Offer USD510
Evaluation score70
Decision at27 Oct
Revision320
Example screen with sample data

What you can do

Tender desk

A tender submission sits beneath the purchase request it answers. Its tender number, offer amount, submission date, evaluation score, decision date and revision let the team compare an offer with the underlying need. Submitted tenders form the evaluation queue. Approved and rejected states record the outcome of that assessment before any award action.

How the work is organized

  • Offer. Buyer links each tender to the request and records its tender number, amount and submission date.
  • Evaluation. The score, decision date and revision explain the assessment of a submitted offer.
  • Outcome. The tender status separates draft, submitted, approved, rejected and completed work.

A request can have several tender submissions, so the parent link matters more than a tender number alone. Compare offers under the same request before changing a tender to Approved. An approval is the input to the award action; Completed means the award operation has persisted its receipt. Keep the offer revision in view while comparing the decision with the amount and score.

What to agree during setup

Agree how tender numbers are issued, what the evaluation score means and who records the offer. Decide how revised offers are distinguished from the submitted revision.

Choose one buying organization for the first cycle. Identify the person who can correct the record when the case fails a check. Write down the expected decision and evidence for the pilot before people begin using the queue. This makes it possible to distinguish a record awaiting action from a record that is ready to close.

Check the handoff on an actual case

Create a pilot tender under an approved request. Enter the offer amount, submission date and score; then check the parent request. Move the tender to Submitted, inspect the evaluation queue and record the decision. Check the resulting status and revision.

Ask the next person to open the same parent request and explain the next action from the record itself. They should point to the responsible owner, current status and supporting decision or receipt. If those disagree, return the case to the person who owns the correction and record the reason. Rehearse the failure route as well as the successful one.

What your team sees

  • Tender Evaluation Queue — Compare submitted offers and scores under their parent requests.
  • Tender Status Board — Follow each tender from draft through decision and completion.

What it keeps track of

Data model
Tender submissions
Sealed tender submissions evaluated and awarded against a purchase request.
Purchase requests
Demand records raised by buyers, carrying lifecycle, budget and supplier context.
Suppliers
Registered suppliers eligible to receive tender invitations and orders.
Organizations
Buying organizations that own procurement records.

Who uses it

Permissions
Buyer
Leads this part of the process.
Buyer
Carries operational records; Purchasing Approver reviews eligible decisions; Auditor reads the resulting evidence.

Set up E-procurement Portal your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started