https://www.servicenow.com/community/itom-forum/suggestion-improving-progress-tracking-amp-collaboration-in/m-p/3541500#M127149 <DIV><P>In our organization, we actively use <STRONG>Discovery Admin Workspace</STRONG> for the following recurring activities:</P><OL><LI><STRONG>Insights for Missing Compute Resources</STRONG> – to identify and correct stale or missing discovery records</LI><LI><STRONG>Diagnostics Error Type Corrections</STRONG> – to analyze and remediate recurring discovery errors</LI></OL><P>These activities are continuous and often handled by <STRONG>multiple administrators in parallel</STRONG>.<BR /><BR /></P><DIV><H3><STRONG>Challenge Observed</STRONG></H3><P>When two or more people are working on the same set of recurring Discovery insights or diagnostic records, it becomes difficult to:</P><UL><LI>Understand <STRONG>who is working on what</STRONG></LI><LI>Track <STRONG>progress</STRONG> on validation or correction</LI><LI>Identify <STRONG>what has already been validated</STRONG> versus what is <STRONG>still pending</STRONG></LI></UL><P>Since these records reappear over time, there is currently <STRONG>no clear traceability or ownership visibility</STRONG> within Discovery Admin Workspace.</P></DIV><P>&nbsp;</P><DIV><H2><STRONG>Question 1: Progress Visibility</STRONG></H2><P>What is the recommended way to indicate <STRONG>work‑in‑progress</STRONG> on Discovery insights or diagnostics so that:</P><UL><LI>Other admins know a record is already being reviewed or handled</LI><LI>Duplicate effort is avoided when multiple people work simultaneously</LI></UL><P>Are there any <STRONG>OOTB features</STRONG>, best practices, or integrations (e.g., with tasks, notes, or states) to convey progress clearly?<BR /><BR /></P><DIV><H2><STRONG>Question 2: Validation &amp; Reporting</STRONG></H2><P>What is the best approach to <STRONG>track and report</STRONG> on:</P><UL><LI>How many insights/records have been <STRONG>validated or corrected</STRONG></LI><LI>How many are <STRONG>still open or unresolved</STRONG></LI><LI>Historical tracking for recurring records (trends over time)</LI></UL><P>Would this be best handled through:</P><UL><LI>Custom fields or states</LI><LI>Linking Discovery insights to <STRONG>tasks/incidents</STRONG></LI><LI>Performance Analytics / reports</LI><LI>Any recommended data model or workflow approach?</LI></UL><HR /><H2><STRONG>Goal</STRONG></H2><P>The goal is to improve:</P><UL><LI>Collaboration between Discovery admins</LI><LI>Visibility into ongoing work</LI><LI>Accurate reporting on Discovery health and remediation progress</LI></UL><P>Any guidance, platform capabilities, or real‑world implementation suggestions from the community would be greatly appreciated.</P></DIV><P><BR /><BR /></P></DIV></DIV> Tue, 12 May 2026 17:47:40 GMT VIvek V 2026-05-12T17:47:40Z https://www.servicenow.com/community/itom-forum/suggestion-improving-progress-tracking-amp-collaboration-in/m-p/3541500#M127149 <DIV><P>In our organization, we actively use <STRONG>Discovery Admin Workspace</STRONG> for the following recurring activities:</P><OL><LI><STRONG>Insights for Missing Compute Resources</STRONG> – to identify and correct stale or missing discovery records</LI><LI><STRONG>Diagnostics Error Type Corrections</STRONG> – to analyze and remediate recurring discovery errors</LI></OL><P>These activities are continuous and often handled by <STRONG>multiple administrators in parallel</STRONG>.<BR /><BR /></P><DIV><H3><STRONG>Challenge Observed</STRONG></H3><P>When two or more people are working on the same set of recurring Discovery insights or diagnostic records, it becomes difficult to:</P><UL><LI>Understand <STRONG>who is working on what</STRONG></LI><LI>Track <STRONG>progress</STRONG> on validation or correction</LI><LI>Identify <STRONG>what has already been validated</STRONG> versus what is <STRONG>still pending</STRONG></LI></UL><P>Since these records reappear over time, there is currently <STRONG>no clear traceability or ownership visibility</STRONG> within Discovery Admin Workspace.</P></DIV><P>&nbsp;</P><DIV><H2><STRONG>Question 1: Progress Visibility</STRONG></H2><P>What is the recommended way to indicate <STRONG>work‑in‑progress</STRONG> on Discovery insights or diagnostics so that:</P><UL><LI>Other admins know a record is already being reviewed or handled</LI><LI>Duplicate effort is avoided when multiple people work simultaneously</LI></UL><P>Are there any <STRONG>OOTB features</STRONG>, best practices, or integrations (e.g., with tasks, notes, or states) to convey progress clearly?<BR /><BR /></P><DIV><H2><STRONG>Question 2: Validation &amp; Reporting</STRONG></H2><P>What is the best approach to <STRONG>track and report</STRONG> on:</P><UL><LI>How many insights/records have been <STRONG>validated or corrected</STRONG></LI><LI>How many are <STRONG>still open or unresolved</STRONG></LI><LI>Historical tracking for recurring records (trends over time)</LI></UL><P>Would this be best handled through:</P><UL><LI>Custom fields or states</LI><LI>Linking Discovery insights to <STRONG>tasks/incidents</STRONG></LI><LI>Performance Analytics / reports</LI><LI>Any recommended data model or workflow approach?</LI></UL><HR /><H2><STRONG>Goal</STRONG></H2><P>The goal is to improve:</P><UL><LI>Collaboration between Discovery admins</LI><LI>Visibility into ongoing work</LI><LI>Accurate reporting on Discovery health and remediation progress</LI></UL><P>Any guidance, platform capabilities, or real‑world implementation suggestions from the community would be greatly appreciated.</P></DIV><P><BR /><BR /></P></DIV></DIV> Tue, 12 May 2026 17:47:40 GMT https://www.servicenow.com/community/itom-forum/suggestion-improving-progress-tracking-amp-collaboration-in/m-p/3541500#M127149 VIvek V 2026-05-12T17:47:40Z