What exactly counts as proof when an issue is closed and can i show that record
1
Proof is what closes an issue in BidLight. Three things: a screenshot of the fix, a tagged user who owns it, and the model commit that made the change. No commit, no close. That is the whole rule.
add comment
Answers
0
<p>Proof is what closes an issue in BidLight. Three things: a screenshot of the fix, a tagged user who owns it, and the model commit that made the change. No commit, no close. That is the whole rule.</p>
<p>What that gives you on the job: no more chasing Teams threads and email to find out whether a clash was actually handled. The issue is pinned to the element it concerns, so the record sits where the problem was. The 6am digest tells each owner what they own, and the project view shows who is behind while there is still schedule to recover.</p>
<p>At handover you have a trail, not a folder of screenshots. Every export is versioned and compared element by element, so each closed issue ties back to a specific model state and a named person. That is the record you walk the owner through.</p>
<p>Why it matters in dollars: a clash caught in the model costs about $50 to fix. The same one found in the field runs $5,000 to $50,000. An unresolved one can burn $15K to $50K a week in idle field labour.</p>
<p>Start with Basics at $260 per licence per year, up to Max at $590. Enterprise is custom.</p>