Missing input should be a named blocker, not a guessed value. Identify the absent artifact—test result, approval, release note, monitoring threshold, or rollback instruction—and state who can provide it by when. Keep dependent steps in a waiting state rather than marking them complete.
If a substitute is possible, define exactly what evidence it must provide and who may accept it. For example, a fresh smoke test might replace a stale report, but only if it covers the same release candidate. Record the decision and rerun affected checks once the input arrives. A launch should have an explicit go/no-go rule for unresolved missing data, especially when customer impact or security is involved.
Akousa