Request for Tender
- The Request for Tender is raised from the requesting organisation's ERP, with due process complete.
- If no such system exists yet, the current gazette-upload method can be used until it does.
- Implementation: Short.
What the public wants — and how it gets done.
Across the community's comments, one demand stands out: public money should be spent in the open. People want every tender visible before it is awarded — with a real window to flag inflated specs, single-bidder set-ups, or sites that don't suit the island. The recurring worry is that scrutiny slows delivery, and that big, well-connected firms still crowd out small local businesses. Weighing both sides, the approach the public converges on is procurement that is transparent by default: each tender opens for public comment, bidders are verified automatically against tax and registration records, and evaluation is handed to randomly-drawn, qualified citizens — so fairness and speed are built in, not merely promised. Here is exactly how that would work.
This summary is drafted automatically from public pros & cons — a first pass for the community to refine.
A walk-through of the gazette's procurement flow — swipe through each step.
Publishing every tender before it's awarded is the single biggest deterrent to backroom deals.
Auto-verifying tax and registration weeds out shell companies before they can even bid.
ޓެންޑަރުތައް ޢާންމުކޮށް ހާމަކުރުމަކީ ކޮރަޕްޝަން ހުއްޓުވުމަށް އެންމެ ވަރުގަދަ ފިޔަވަޅު.
Random citizen evaluators may not have the expertise to judge complex technical bids.