Report completeness is how thoroughly a vulnerability submission explains the issue, the steps needed to reproduce it, and its security impact. A useful report typically identifies the affected product or component, provides clear reproduction instructions and evidence, and describes what an attacker could achieve. Exact requirements vary by program.
Completeness matters because security teams need enough information to verify, prioritize, and fix a finding. In bug bounty programs and vulnerability disclosure workflows, a clear, reproducible report can reduce triage delays and uncertainty. Defenders can encourage this by publishing submission guidelines and requesting missing details when needed. A report that lacks information may be harder to act on, but that does not necessarily mean the underlying issue is invalid.