A floodwall project register lists “possible contractor strike” as something that might delay work if it occurs. What is the correct classification?

A risk is an uncertain event or condition that, if it occurs, can affect one or more project objectives. Listing a possible contractor strike that might delay floodwall work is correct risk classification on the project register. Calling it an issue because strikes are always happening somewhere fails by concept: an issue is a current problem already affecting the project; a possible future strike has not yet occurred on this job. Calling it a constraint that already locks the labor calendar fails because a constraint is an imposed limit already in force, not a speculative labor event waiting to happen. Calling it an assumption that a strike will definitely start next month fails because assumptions are factors taken as true for planning; asserting a definite strike without evidence invents certainty and uses the wrong artifact type. Exam caveat: probability language such as “possible” or “might” usually signals risk until the event materializes and becomes an issue requiring active response. Operational check: enter the strike scenario in the risk register with probability, impact, owners, and responses (for example alternate crews or schedule buffer), review it at risk meetings, and convert it to an issue only if a strike actually begins.