Every answer and its explanation appears here once you have finished the path. Each one then links to the matching glossary entry, where the concept is set out in full with its worked example.
1. On a project, the notice to proceed is dated March 4, the construction policy shows an April 1 attachment date conditional on payment of the first premium, and the premium is paid on April 22. A geotechnical borehole on February 12 damaged a neighbor's pipe, discovered in May. What has to be looked at first?
The date of the project's first physical operation, whatever it is, here the February 12 borehole
The useful question is when the risk starts, ahead of when cover starts, and the module puts them in that order for a reason: the attachment date sits in a document someone has in front of them, while the date of the first physical operation sits in another schedule kept by other people. A geotechnical borehole really does dig, it almost always precedes the opening of the site, and here it precedes any conceivable attachment date by seven weeks. The answers starting from April 1 or April 22 reason correctly about the contract and skip the gap, which is exactly what the module asks to be measured in days. The one invoking discovery transposes a claims-made mechanism onto a policy that works on occurrence.
Glossary entry →2. A transformer ordered fifteen months before the site opens is being wound at its manufacturer, paid by installments, with several million already committed. A fire destroys the workshop. Where does that leave the construction policy?
It does not respond: it has not attached and the equipment is not on site, two boundaries missing at once
Two boundaries are missing at once and both have to be seen, the one in time and the one in space: the policy has not attached, and even if it had, the equipment is off site. The module on off-site value describes that second boundary; this one describes the first, and a large project rarely crosses them on the same day. The answer leaving the risk with the manufacturer is the most instructive because it is legally right and financially wrong: the employer has paid installments, will pay them again at another manufacturer and wait another twelve to twenty-four months, and a recourse against a destroyed workshop is worth what that workshop is worth. The pro rata answer invents a proportionality neither boundary knows.
Glossary entry →3. A six-week gap in cover is discovered as a loss falls into it. The broker proposes backdating the attachment date. What is that proposal worth?
It cannot cover a loss already occurred and known: a gap once noticed is closed beforehand, or not at all
An insurance contract bears on an event whose occurrence is uncertain, and that requirement of chance is not a clause one negotiates but the contract's condition of existence. Backdating an attachment date is lawful, it is practiced, and it holds only for what nobody knew: it does not turn a known loss into a risk. The answer buying it with an additional premium is that of a good negotiator who has forgotten that price does not manufacture chance. The one declaring all backdating void makes the symmetrical error and denies a real tool to the projects that have not yet had a loss, that is, the ones that can still use it.
Glossary entry →4. The module notes that attention goes to the end dates and not the start ones. What follows from that?
That the imbalance in attention is the inverse of the imbalance in risk, the start additionally carrying demolition and site investigation
Both ends carry the same kind of risk, a badly dated switch in cover, and the start carries one more: preliminary demolition is often the most dangerous operation of the whole project and takes place before the construction site opens. At the end everyone is watching, minutes get signed and the stakes are visible; at the start, insurance sits on a list of thirty things to do. The answer proposing to take attention away from handover is the error to avoid absolutely: the module does not ask for vigilance to be moved, it asks for vigilance to be added where there is none. The one believing the start better covered inverts the reasoning: attention follows what is already known to be a problem, not what is one unnoticed.
Glossary entry →5. The module ends on a comparison that is almost never made. Why is it so rarely made?
Because it requires looking at two schedules at once, and they belong to two different people
The works schedule belongs to project management, the policy's real attachment date belongs to insurance or the broker, and the gap between them only shows if someone puts them side by side. It is an organizational obstacle and not a technical one, which is why it survives very competent teams on both sides. The answer waiting for the loss describes exactly what happens and presents it as a method: the dates are indeed established by then, and that is the moment the gap can no longer be closed. The one assuming the gap is nil on a well-structured project confuses the quality of the structuring with the coincidence of two schedules that nothing synchronizes.
Glossary entry →