誰かが作業を始める前に SRO 会員資格を確認する

For each discipline, record what the firm or the individual doing it must hold: SRO membership in construction, in design or in survey, and any separate authorisation the work itself carries, such as work on a cultural heritage object or on a hazardous production facility. Mark the requirement blocking where a gap has to stop the work, and set the grace period you are willing to allow.

理由: The requirement belongs to the work rather than to the supplier, and writing it down first is what makes every later check mechanical instead of a judgement call. Blocking is the decision that matters, because a requirement that is only a note stops nobody. It also surfaces the work that needs no membership at all, since the Town Planning Code exempts contracts below a stated value and certain categories of work, and demanding it there costs you bidders for nothing.

For each firm, work through the prequalification questionnaire with the register extract in front of you: which SRO it belongs to, its membership number, when it joined, and which level of responsibility it holds against the value of the work you mean to give it. Attach the extract, and block the firm with the reason written down where the level does not cover that work. Read it from the extract, not from the scan on the firm's letterhead.

理由: Membership is a live status rather than a certificate: it can be suspended or terminated while the firm goes on sending the same scanned page. The level is the part most often wrong, because a firm that is genuinely a member is very often a member at a level below the contract it is about to sign.

Attach the requirement to the package in procurement so that an award cannot be made to a firm that does not meet it, and ask for the register extract as part of the offer rather than as something to be produced once the work is under way.

理由: Checked after award this only ever produces bad options: re-tender and lose the programme, or carry on with a contractor whose work you may not be able to hand over. Checked as a condition of award it costs one field on the offer form.

File the register extract for each firm together with the date it was taken, alongside the insurance and any separate authorisation, and keep it attached to the work package rather than in a general supplier folder.

理由: When the client's technical supervision or an inspection asks who was entitled to do this work, the answer has to be a document dated before the work started. An extract pulled after the question is asked proves only that the firm is a member today, which is a much weaker statement and usually the wrong one.

Put the requirement in the subcontract itself: membership held for the whole term and not only at signature, notice to you within a fixed number of days if it is suspended or terminated, and the right to suspend the work and withhold payment until it is restored.

理由: Membership lapses quietly and the SRO writes to its member, not to you. Checked once at award, it is a snapshot; written into the contract, it is a duty that runs for the whole term and gives you something to act on. A firm that was covered at award and is not covered in month eight goes on signing acts the client can later refuse, and that is normally found while the handover package is being checked.

Read the compliance answer across the project: holders a blocking requirement stops outright, holders still inside their grace period, credentials expiring soon, and requirements that bind nobody at all because no holder on the register matches them. Clear that list before those firms reach the site.

理由: This is the rare compliance question that is arithmetic rather than judgement, so it belongs in a report read on a date and not in somebody's habit. Expiry is worked out from the dates each time it is read rather than from a status somebody typed once, which is the only version of this check that survives a firm renewing late. A requirement binding nobody is the other half of the finding: the work is being done by somebody the requirement never reached.