CONSTRUX
Bid-On

A submission with no closing date

A dynamic market accepts applications at any point in its life. A UVDB registration is maintained, not returned. Putting a target date in the deadline field would judge every certificate in the pack against an invention.

Everything in a bid tool is built around a return date. It is the right assumption for an invitation to tender and wrong for two things a contractor actually chases.

A dynamic market under the Procurement Act accepts applications at any point in its life, obliges the authority to consider them within a reasonable period, and cannot cap its membership. There is no closing date to miss. And a registration — UVDB, Constructionline — is maintained rather than returned: it is live until it lapses.

The available workaround was to put a target date in the deadline field, and that is precisely what this exists to avoid. Every expiry verdict in the pack would then be judged against a date somebody made up, and “this certificate lapses before the deadline” would be a statement about an invention.

So a rolling submission carries no deadline at all, and is judged against the day it is read — every time it is read. One function decides which day that is, because a screen judging against today while the export gate judged against a deadline would disagree about whether a certificate is valid, and that is the only question either of them is being asked.

The consequence is the feature. A rolling pack goes backwards on its own: exportable when read in December, red when read in February because the cited certificate lapsed in January, with no event in between and nobody having touched it. That is the honest behaviour for a membership nobody returns, and it is the thing a dated bid cannot express.

Nothing invents a countdown. Days remaining is absent rather than zero, because a countdown of nought reads as “due today” on something with no due date at all. The register sorts rolling submissions last — they are never the thing with the least time left — and never counts one as late, because a permanent false alarm against every membership a provider maintains is how a register stops being read. The exported pack prints the day it was judged on instead of a return date, so a buyer never reads an invented date off the front page.

The watching agent swaps its finding over, too. A dated bid near its deadline that cannot be exported is urgent. A membership pack that cannot be exported has nothing forcing it — no deadline makes anybody finish it — so it sits unfinished indefinitely while certificates age underneath it, and that is what gets reported instead.

See the record being made rather than described.

Launch the demo environment

← All posts