An estimator pasted a sub bid next to the plans and asked a chatbot whether everything was included. It came back with a missing hood for a pizza oven. The risk in a subcontractor proposal is an exclusion that never appears as a sentence.
The tool that followed from that afternoon marks every scope item Present, Missing, or Ambiguous. Ambiguous carries the same weight as the other two answers. Forcing the call into a yes or a no is how a reviewer misses the gap.
The checklist behind those marks has to be the firm's own: what dark shell includes here, what the base building covers, what the owner is supplying. A model left to invent those definitions will invent dumpster counts next.
The usual loss is the odd requirement buried in an unfinished document.
Fairley turns up here too. On a hard bid that allowed about ten business days where four weeks is usual, an estimating desk asked a model to verify that the issued drawings matched what the plans claimed existed. The sheets referenced a Project Manual that was never issued. The model cited the general note on G-010. The bid letter went out carrying allowances and exclusions for anything not fully drawn.
A bid requirements register is the next page of the same work, its rows pulled from the specs, the contract, and the addenda. A model can draft those rows, and each one still needs a human signature.