Main idea

In a security questionnaire prepared from facts filed by topic, a missing piece of information can no longer hide behind an old wording. The topic is there, the question too, but no verified fact makes it possible to answer: the gap becomes visible.

A visible gap can become an action. Rather than filling the box with a reassuring sentence, you prepare a precise question for the team concerned, noting which lines of the questionnaire the answer will let you complete. You know whom to ask, and why.

A plausible sentence hides a risk. An explicit gap turns it into identifiable work.

Why it matters

It reverses the usual value of a gap in an answer: it is no longer a failure to hide but the entry point for a targeted request. The work still to do becomes visible, assignable and bounded, instead of being scattered across a random search for who knows what.

It also sets a condition for a flagged gap not to remain just one more remark: that it be tied to a recipient and to the use the answer will make of it.

Nuances and limits

You need a filing system that brings gaps to the surface; in a pile of old documents, the absence of a piece of information doesn't show. Visibility is an effect of structure, not of goodwill.

And a question sent is not an answer obtained: if the team asked doesn't reply, the gap stays open, simply better named.

Open questions

• How many directed gaps can a team absorb before the questions become one more interruption?