Late bid won (R030)

The winning bid was received after the submission deadline.

Methodology

A contracting process is flagged if:

• A valid bid’s received date is after the submission deadline.

• At least one tenderer of the valid bid is the supplier of an active award.

These tenderers are also flagged.

Example

The submission deadline is March 15. The Public Works Department leaks information from the received bids to CorruptX Solutions, to give it a competitive advantage. CorruptX Solutions submits a bid on April 1. The Public Works Department accepts the bid and awards the contract to CorruptX Solutions.

Why is this a red flag?

A corrupt buyer can award the pre-determined bidder by disregarding the submission deadline.

Based on “Bids after the deadline accepted” in Corruption in Public Procurement: Finding the Right Indicators and “Late submissions accepted” in Fraud in Public Procurement: A collection of Red Flags and Best Practices.

Output

The indicator’s value is always 1.0.

If the --map command-line flag is set, the Maps key contains:

ocid_tenderer_r030

The flagged tenderers for each flagged ocid.

Configuration

The indicator is not configurable.

Assumptions

This indicator assumes that the tenderer didn’t submit another valid bid before the submission deadline; in other words, its late bid is the winning bid.

Note

Is this assumption not true for your data? Does your data set the /awards[]/relatedBid field? Please create an issue on GitHub.

Demonstration

Input

{"ocid":"F","bids":{"details":[{"status":"valid","date":"2000-04-01T00:00:00Z","tenderers":[{"id":"W"}]}]},"tender":{"tenderPeriod":{"endDate":"2000-03-15T00:00:00Z"}},"awards":[{"status":"active","suppliers":[{"id":"W"}]}]}

Output

$ ocdscardinal indicators --settings docs/examples/R/030.ini --no-meta docs/examples/R/030.jsonl
{"OCID":{"F":{"R030":1.0}},"Tenderer":{"W":{"R030":1.0}}}