BCF issue quality and coordination workflows

A useful BCF issue should be actionable without a meeting. Include a focused viewpoint, affected elements, a concise problem statement, the expected resolution, ownership, priority, due date, and enough project context to understand the impact. Avoid screenshots that show the entire federated model when a tighter view would communicate more.

Teams should also agree how status transitions work, who may close an issue, whether element references survive model versions, and how duplicate findings are consolidated. BCF moves information; it does not replace a coordination protocol.