A poorly written CFO/CFA specification doesn't only hurt the contractors who respond to it — it hurts the institution that receives bids it can't compare, or awards a contract that turns out non-compliant once the work is done. Three errors appear almost every time: conflating CFO and CFA lots, missing regulatory references, and imprecise bills of quantities.

The three most common errors

Vague vs. usable specification language

What a solid specification must contain

Frequently asked questions

Who should write a CFO/CFA technical specification?
An engineering firm or experienced integrator, before the tender is published — not just the institution's procurement team working alone.

Should Decree 09-410 be explicitly cited?
Yes, as soon as a lot includes surveillance — it obliges every bidder to justify their licence at the point of submitting the bid.

Can a specification be modified after publication?
Generally no, or only through a formal amendment procedure — which is precisely why getting it right before publication matters.

Have a project in mind? Let's talk technical.

Tell us about your building and your needs. We'll respond with a clear approach.

Chat on WhatsApp