How do tender exclusions hide skills gaps in Bosaso?

Tender exclusions in Bosaso can hide a skills gap because a bidder may remove the work it cannot carry out, then win the package around it. The price looks clean and the scope reads narrowly. The gap only shows when that task is due, and nobody on site has the crew, plant or record system to do it. Read exclusions as a statement about capability, not just about price.

What does an exclusion in a Bosaso tender actually remove?

An exclusion removes a defined item of work from the bidder's price and responsibility.

That is legitimate when the client keeps the item with another contractor or a direct supplier. It becomes a risk when the excluded item sits inside the critical path of the package being awarded. Ask what happens on the day the excluded work is due. Who walks onto the site, with which tools, under whose instruction, and where does their work appear in the programme?

The second check is arithmetic. Compare the priced scope with the drawings and the bill of quantities. A bid that is quiet about an item is not the same as a bid that has excluded it in writing. Ask the bidder to list every exclusion in one table, then map each line against the scope. Local practice on how far a bidder may narrow a scope is something to confirm with the procuring office handling your tender, not to assume.

If the excluded item is groundworks, edge protection, waterproofing or testing, ask the client's engineer to confirm the interface before award.

How do tender exclusions and skills gaps combine in Bosaso?

A skills gap becomes dangerous when a bidder excludes what it cannot do and still takes the package that depends on it.

The pattern runs like this. A firm has blocklayers and a mixer but no one who has set out a drainage line or fired a waterproofing membrane. It excludes those lines, prices the rest low, and wins. On site, the excluded work is handed to whoever is available. The workmanship defects then appear at the junction: a membrane that stops short of an upstand, a pipe that falls the wrong way, a wall built before the setting out is checked.

Detection is a paper exercise first. Ask for the method statement for the excluded item and the name of the person who will supervise it. Ask how that person's past work was checked, and request sample inspection records from a completed job. Walk a recent site by the same firm and look at the junctions that match the excluded scope. If the bidder cannot show records or a named supervisor, treat the exclusion as a capability signal and ask the procuring office how the interface will be managed.

Who checks the interface once the work starts?

A named person on the client side, with a written inspection plan, checks the interface.

General practice is to hold a pre-start meeting where each exclusion is read aloud, the responsible party is named, and the interface points are listed with dates. The client's engineer or clerk of works then inspects those points against the specification and keeps the record. Where the client has no site staff, the procuring office or the design engineer can advise what minimum supervision the contract allows.

Keep three documents current: the exclusion list, the interface schedule, and the inspection record for each interface. When a defect appears at an interface, the records show whether the work was inspected, who signed it off, and what the contract says about the sequence of trades and reinstatement. Check what your contract allows before you act on a defect.

What to do next

Before you award, send every bidder a short written request: list all exclusions in one table, name the supervisor for each excluded item, and attach one inspection record from a completed job of the same type. Compare the answers side by side. Ask the procuring office how the interface will be managed. Award only when every excluded line has a named owner, a date and a check.