In the Microsoft Azure datacenter network, a technician repairs a link and an on-call engineer, on a different shift and a different continent, decides whether the repair holds. The only channel between them is the technician’s free-text note. When the note omits the measurements the engineer needs, the ticket stalls: the median blocked ticket took 7.0 days to resolve, of which roughly one hour was engineering work. The rest was waiting for an account of the work that the note did not carry.

We treat the note as the object to be repaired. A pipeline in production for ten months parses each note at write time into two lightweight schemas, STAR and ECO, using deterministic rules for measurements and a language model for prose. It reaches 0.913 F1 against a 2,141-note gold standard, above a stronger frontier model working alone, and across a staggered rollout of 450+ datacenters the deployed package cuts time-to-repair by 3.4 days. Resolution time falls steeply in a completeness score, at a rate that holds across five physically unrelated failure types, which is what we would expect if the constraint were in the handoff rather than in the physical work.