Skip to content

Bids stay sealed. Everything else stays on the record.

Bid prices are encrypted with a key unique to each tender and open only at the time you set. Every view, download, score and decision is time-stamped, so you can show who did what, and when, on any tender.

Per-tender encryption Time-stamped audit trail Access by role, per tender

How a sealed bid stays sealed.

Four steps, the same on every tender. None can be skipped.

  1. Submitted

    The bidder prices your BoQ and submits before the deadline. Bids close at the deadline you set.

  2. Encrypted with the tender's own key

    Bid prices are encrypted with a key unique to this tender, never shared with another.

  3. Locked until the opening

    No one on the tender, including your own team, can see a price before the opening you scheduled. Technical evaluators score without them.

  4. Opened and logged

    At the scheduled time the envelopes are decrypted, and the opening goes on the record with every view after it.

The controls behind it.

What's live today is marked live. What's coming is marked coming.

Who sees what

Prices and documents reach only the people meant to see them.

  • Per-tender encryption Bid prices are encrypted with a key unique to each tender.
    Live
  • Access by role, per tender Each person sees what their role on that tender allows, and nothing else.
    Live
  • Company rules, enforced Envelopes, minimum bidders and anonymous evaluation, set company-wide. Enforced on Enterprise; defaults on Essential and Pro.
    Live

Accounts and the record

Who signs in, and everything they do once they have.

  • Full audit trail Views, downloads, scores and decisions, time-stamped.
    Live
  • Enforced password policy Your password rules, applied to every user in your company. On Enterprise.
    Live
  • Single sign-on Sign in with your company identity provider.
    Coming
Preventing fraud is a challenge for any company connected with the construction industry. The ProTenders system has given us improved visibility and control over documents and indeed the whole process.
Charles Saleh Manager, Tendering Department, Dhafir Development & Contracting

Your tender data, in the systems you already run.

Read tenders, bids, awards and evaluations through the API (Pro); webhooks tell your systems when they change (Enterprise).

  • API and webhooks Read tenders, bids, awards and evaluations through the API (Pro). Webhooks tell your systems when they change (Enterprise).
    Live
  • Excel in and out Import BoQs and evaluation matrices; export comparisons and registers.
    Live
  • AI assistants Ask about your tenders from Claude or ChatGPT, within your permissions. On Enterprise.
    Coming

Open the API reference

Example webhook Webhooks are on Enterprise
POST https://erp.example.com/hooks/protenders
{
  "id": "evt_8c1f2e64-3b7a-4d2e-9f61-5a0c7d2b9e13",
  "type": "tender.state_changed",
  "api_version": "v3",
  "occurred_at": "2026-10-14T16:05:00Z",
  "data": {
    "object": {
      "type": "tender",
      "id": 48213,
      "url": "https://api.protenders.com/v3/tenders/48213"
    },
    "from": "opened",
    "to": "awarded"
  }
}

A thin event: your system fetches the full tender from the URL with its own token. Example. The API reference has every field.

All integrations ProTenders works with Procore

See the opening log on your own package.

A walkthrough on your own tender, then guided setup.

For your IT team

How bids are encrypted, who can access what, and what the audit trail records.