ITAD for Singapore stat boards & GLCs, tender-ready documentation.

What we hold today, and what we don't.

Public-sector ITAD often expects specific certifications. We don't oversell. Today, what we deliver is documentation discipline aligned with established information-security frameworks, plus per-job Certificate of Destruction to NIST 800-88 + IEEE 2883-2022. We are working towards formal information-security and recycler-licensing credentials and will list them on this page with issuer, number and expiry once they're in place.

If your tender requires a credential we don't yet hold, we will partner with a credentialed provider for the slice that needs it — and tell you exactly which slice, in writing, before you commit.

Where stat boards, GovTech-adjacent agencies and GLCs typically procure.

Singapore public-sector IT retirement runs through a small set of recognised channels. GeBIZ is the dominant procurement portal — vendor enrolment is a one-off process that takes weeks but unlocks tender visibility. Stat boards (HDB, IRAS, MOH, MND, MOE, etc.) use GeBIZ for ITAD tenders above their financial-authority threshold and direct procurement below. GLCs (SingPost, ST Engineering, Sembcorp, PSA, etc.) run more flexible commercial procurement but increasingly mirror stat-board documentation expectations. GovTech itself runs internal-IT retirement through standard procurement channels.

Three documentation expectations recur across public-sector ITAD tenders. First, a structured response format — most tenders specify response sections, page limits, and annex requirements. We prepare to that format rather than reusing a generic capability deck. Second, a sample Certificate of Destruction with realistic-looking but fake serials. Third, references — typically two or three from comparable scopes; for public-sector tenders we share SG-MNC and DC-operator references where the customer has consented. Fourth, indicative pricing per asset-class tier rather than a single lump-sum.

• Sample Certificate of Destruction · Sanitised; realistic format with fake serials; in PDF + PDF/A.
• Sample chain-of-custody log · From a comparable engagement; redacted for commercial sensitivity.
• Destruction methodology · Written description with NIST SP 800-88 Rev. 1 + IEEE 2883-2022 citations.
• Insurance evidence · Transit cover, professional indemnity, public liability — current certificates.
• Operator + witness identity · Named individuals; security-clearance status if your tender requires it.
• References · Two or three SG-based MNC / DC / private-sector references with permission letters.
• Pricing per asset-class tier · Not a lump-sum; transparent per-line residual or per-asset destruction fee.
• Sub-contractor structure · If a credentialed party covers a slice of scope, named with boundary description.

Where we partner instead of overclaim.

Public-sector tenders sometimes specify credentials we don't currently hold (the Singapore-specific end-of-life ICT-equipment-management standard; certain industry destruction-program credentials; specific ISMS certifications). We don't oversell. Where a tender requires a credential we don't yet hold, our default response is structured partnership: a credentialed sub-contractor owns that slice of scope, we own the rest, and the tender response describes the boundary in writing. This avoids the downstream-discovery problem where the awarded vendor's claimed credential turns out to be missing or expired.

Working towards formal certification is on the roadmap; the pages here will be updated when issuer, certificate number and expiry date are in hand. Until then, what we deliver is data-erasure to NIST 800-88 + IEEE 2883-2022 with a per-job Certificate, plus structured partnership for the credentialed slices.

Visual reference.