IT operations research

Software Inventory Reconciliation Coverage Study

A source-bounded protocol for software inventory reconciliation, with declared units, adverse controls, reproducible review, and explicit limitations.

16 min read · 10 sources · Verified 2026-10-13

Research question and boundary. Software Inventory Reconciliation Coverage Study asks how consistently endpoint, identity, procurement, and application-owner records identify the same software population. Stage 1 uses one software product and its installation, entitlement, owner, version, support, exception, and retirement evidence across declared systems as the declared observation unit and freezes the cohort, system boundaries, local and UTC times, source versions, inclusion rules, and expected decision before outcomes are reviewed. Record ITV-R-1013-01 distinguishes system events, business facts, owner decisions, reviewer classifications, implementation evidence, and unresolved hypotheses. It includes routine, missing-source, conflicting-version, wrong-identity, inaccessible-system, unavailable-owner, reversed, corrected, and reopened cases. Two reviewers classify a stratified subset independently using written behavioral anchors, preserve first-pass disagreement, and adjudicate against retained evidence. Report numerator, denominator, exclusions, null values, age bands, correction rate, disagreement, and residual cases. Alternative explanations include configuration, logging gaps, clock drift, synchronization, case mix, ownership changes, policy versions, and selection effects. An IT virtual assistant may preserve, normalize, compare, route, and schedule; authorized technical, security, privacy, legal, employment, financial, and business owners retain consequential decisions. The ten public sources inform the protocol but do not inspect this environment, prove causation, certify a provider, or establish a universal benchmark. Preserve the query, codebook, sample receipt, chronology, reviewer notes, decision log, approved action, verification, limitations, and refresh trigger so another authorized analyst can reproduce the bounded result without unnecessary sensitive data.

Population and observation window. Software Inventory Reconciliation Coverage Study asks how consistently endpoint, identity, procurement, and application-owner records identify the same software population. Stage 2 uses one software product and its installation, entitlement, owner, version, support, exception, and retirement evidence across declared systems as the declared observation unit and freezes the cohort, system boundaries, local and UTC times, source versions, inclusion rules, and expected decision before outcomes are reviewed. Record ITV-R-1013-02 distinguishes system events, business facts, owner decisions, reviewer classifications, implementation evidence, and unresolved hypotheses. It includes routine, missing-source, conflicting-version, wrong-identity, inaccessible-system, unavailable-owner, reversed, corrected, and reopened cases. Two reviewers classify a stratified subset independently using written behavioral anchors, preserve first-pass disagreement, and adjudicate against retained evidence. Report numerator, denominator, exclusions, null values, age bands, correction rate, disagreement, and residual cases. Alternative explanations include configuration, logging gaps, clock drift, synchronization, case mix, ownership changes, policy versions, and selection effects. An IT virtual assistant may preserve, normalize, compare, route, and schedule; authorized technical, security, privacy, legal, employment, financial, and business owners retain consequential decisions. The ten public sources inform the protocol but do not inspect this environment, prove causation, certify a provider, or establish a universal benchmark. Preserve the query, codebook, sample receipt, chronology, reviewer notes, decision log, approved action, verification, limitations, and refresh trigger so another authorized analyst can reproduce the bounded result without unnecessary sensitive data.

Source hierarchy. Software Inventory Reconciliation Coverage Study asks how consistently endpoint, identity, procurement, and application-owner records identify the same software population. Stage 3 uses one software product and its installation, entitlement, owner, version, support, exception, and retirement evidence across declared systems as the declared observation unit and freezes the cohort, system boundaries, local and UTC times, source versions, inclusion rules, and expected decision before outcomes are reviewed. Record ITV-R-1013-03 distinguishes system events, business facts, owner decisions, reviewer classifications, implementation evidence, and unresolved hypotheses. It includes routine, missing-source, conflicting-version, wrong-identity, inaccessible-system, unavailable-owner, reversed, corrected, and reopened cases. Two reviewers classify a stratified subset independently using written behavioral anchors, preserve first-pass disagreement, and adjudicate against retained evidence. Report numerator, denominator, exclusions, null values, age bands, correction rate, disagreement, and residual cases. Alternative explanations include configuration, logging gaps, clock drift, synchronization, case mix, ownership changes, policy versions, and selection effects. An IT virtual assistant may preserve, normalize, compare, route, and schedule; authorized technical, security, privacy, legal, employment, financial, and business owners retain consequential decisions. The ten public sources inform the protocol but do not inspect this environment, prove causation, certify a provider, or establish a universal benchmark. Preserve the query, codebook, sample receipt, chronology, reviewer notes, decision log, approved action, verification, limitations, and refresh trigger so another authorized analyst can reproduce the bounded result without unnecessary sensitive data.

Sampling and exclusions. Software Inventory Reconciliation Coverage Study asks how consistently endpoint, identity, procurement, and application-owner records identify the same software population. Stage 4 uses one software product and its installation, entitlement, owner, version, support, exception, and retirement evidence across declared systems as the declared observation unit and freezes the cohort, system boundaries, local and UTC times, source versions, inclusion rules, and expected decision before outcomes are reviewed. Record ITV-R-1013-04 distinguishes system events, business facts, owner decisions, reviewer classifications, implementation evidence, and unresolved hypotheses. It includes routine, missing-source, conflicting-version, wrong-identity, inaccessible-system, unavailable-owner, reversed, corrected, and reopened cases. Two reviewers classify a stratified subset independently using written behavioral anchors, preserve first-pass disagreement, and adjudicate against retained evidence. Report numerator, denominator, exclusions, null values, age bands, correction rate, disagreement, and residual cases. Alternative explanations include configuration, logging gaps, clock drift, synchronization, case mix, ownership changes, policy versions, and selection effects. An IT virtual assistant may preserve, normalize, compare, route, and schedule; authorized technical, security, privacy, legal, employment, financial, and business owners retain consequential decisions. The ten public sources inform the protocol but do not inspect this environment, prove causation, certify a provider, or establish a universal benchmark. Preserve the query, codebook, sample receipt, chronology, reviewer notes, decision log, approved action, verification, limitations, and refresh trigger so another authorized analyst can reproduce the bounded result without unnecessary sensitive data.

Field dictionary. Software Inventory Reconciliation Coverage Study asks how consistently endpoint, identity, procurement, and application-owner records identify the same software population. Stage 5 uses one software product and its installation, entitlement, owner, version, support, exception, and retirement evidence across declared systems as the declared observation unit and freezes the cohort, system boundaries, local and UTC times, source versions, inclusion rules, and expected decision before outcomes are reviewed. Record ITV-R-1013-05 distinguishes system events, business facts, owner decisions, reviewer classifications, implementation evidence, and unresolved hypotheses. It includes routine, missing-source, conflicting-version, wrong-identity, inaccessible-system, unavailable-owner, reversed, corrected, and reopened cases. Two reviewers classify a stratified subset independently using written behavioral anchors, preserve first-pass disagreement, and adjudicate against retained evidence. Report numerator, denominator, exclusions, null values, age bands, correction rate, disagreement, and residual cases. Alternative explanations include configuration, logging gaps, clock drift, synchronization, case mix, ownership changes, policy versions, and selection effects. An IT virtual assistant may preserve, normalize, compare, route, and schedule; authorized technical, security, privacy, legal, employment, financial, and business owners retain consequential decisions. The ten public sources inform the protocol but do not inspect this environment, prove causation, certify a provider, or establish a universal benchmark. Preserve the query, codebook, sample receipt, chronology, reviewer notes, decision log, approved action, verification, limitations, and refresh trigger so another authorized analyst can reproduce the bounded result without unnecessary sensitive data.

Independent classification. Software Inventory Reconciliation Coverage Study asks how consistently endpoint, identity, procurement, and application-owner records identify the same software population. Stage 6 uses one software product and its installation, entitlement, owner, version, support, exception, and retirement evidence across declared systems as the declared observation unit and freezes the cohort, system boundaries, local and UTC times, source versions, inclusion rules, and expected decision before outcomes are reviewed. Record ITV-R-1013-06 distinguishes system events, business facts, owner decisions, reviewer classifications, implementation evidence, and unresolved hypotheses. It includes routine, missing-source, conflicting-version, wrong-identity, inaccessible-system, unavailable-owner, reversed, corrected, and reopened cases. Two reviewers classify a stratified subset independently using written behavioral anchors, preserve first-pass disagreement, and adjudicate against retained evidence. Report numerator, denominator, exclusions, null values, age bands, correction rate, disagreement, and residual cases. Alternative explanations include configuration, logging gaps, clock drift, synchronization, case mix, ownership changes, policy versions, and selection effects. An IT virtual assistant may preserve, normalize, compare, route, and schedule; authorized technical, security, privacy, legal, employment, financial, and business owners retain consequential decisions. The ten public sources inform the protocol but do not inspect this environment, prove causation, certify a provider, or establish a universal benchmark. Preserve the query, codebook, sample receipt, chronology, reviewer notes, decision log, approved action, verification, limitations, and refresh trigger so another authorized analyst can reproduce the bounded result without unnecessary sensitive data.

Adverse controls. Software Inventory Reconciliation Coverage Study asks how consistently endpoint, identity, procurement, and application-owner records identify the same software population. Stage 7 uses one software product and its installation, entitlement, owner, version, support, exception, and retirement evidence across declared systems as the declared observation unit and freezes the cohort, system boundaries, local and UTC times, source versions, inclusion rules, and expected decision before outcomes are reviewed. Record ITV-R-1013-07 distinguishes system events, business facts, owner decisions, reviewer classifications, implementation evidence, and unresolved hypotheses. It includes routine, missing-source, conflicting-version, wrong-identity, inaccessible-system, unavailable-owner, reversed, corrected, and reopened cases. Two reviewers classify a stratified subset independently using written behavioral anchors, preserve first-pass disagreement, and adjudicate against retained evidence. Report numerator, denominator, exclusions, null values, age bands, correction rate, disagreement, and residual cases. Alternative explanations include configuration, logging gaps, clock drift, synchronization, case mix, ownership changes, policy versions, and selection effects. An IT virtual assistant may preserve, normalize, compare, route, and schedule; authorized technical, security, privacy, legal, employment, financial, and business owners retain consequential decisions. The ten public sources inform the protocol but do not inspect this environment, prove causation, certify a provider, or establish a universal benchmark. Preserve the query, codebook, sample receipt, chronology, reviewer notes, decision log, approved action, verification, limitations, and refresh trigger so another authorized analyst can reproduce the bounded result without unnecessary sensitive data.

Missingness analysis. Software Inventory Reconciliation Coverage Study asks how consistently endpoint, identity, procurement, and application-owner records identify the same software population. Stage 8 uses one software product and its installation, entitlement, owner, version, support, exception, and retirement evidence across declared systems as the declared observation unit and freezes the cohort, system boundaries, local and UTC times, source versions, inclusion rules, and expected decision before outcomes are reviewed. Record ITV-R-1013-08 distinguishes system events, business facts, owner decisions, reviewer classifications, implementation evidence, and unresolved hypotheses. It includes routine, missing-source, conflicting-version, wrong-identity, inaccessible-system, unavailable-owner, reversed, corrected, and reopened cases. Two reviewers classify a stratified subset independently using written behavioral anchors, preserve first-pass disagreement, and adjudicate against retained evidence. Report numerator, denominator, exclusions, null values, age bands, correction rate, disagreement, and residual cases. Alternative explanations include configuration, logging gaps, clock drift, synchronization, case mix, ownership changes, policy versions, and selection effects. An IT virtual assistant may preserve, normalize, compare, route, and schedule; authorized technical, security, privacy, legal, employment, financial, and business owners retain consequential decisions. The ten public sources inform the protocol but do not inspect this environment, prove causation, certify a provider, or establish a universal benchmark. Preserve the query, codebook, sample receipt, chronology, reviewer notes, decision log, approved action, verification, limitations, and refresh trigger so another authorized analyst can reproduce the bounded result without unnecessary sensitive data.

Timeline reconstruction. Software Inventory Reconciliation Coverage Study asks how consistently endpoint, identity, procurement, and application-owner records identify the same software population. Stage 9 uses one software product and its installation, entitlement, owner, version, support, exception, and retirement evidence across declared systems as the declared observation unit and freezes the cohort, system boundaries, local and UTC times, source versions, inclusion rules, and expected decision before outcomes are reviewed. Record ITV-R-1013-09 distinguishes system events, business facts, owner decisions, reviewer classifications, implementation evidence, and unresolved hypotheses. It includes routine, missing-source, conflicting-version, wrong-identity, inaccessible-system, unavailable-owner, reversed, corrected, and reopened cases. Two reviewers classify a stratified subset independently using written behavioral anchors, preserve first-pass disagreement, and adjudicate against retained evidence. Report numerator, denominator, exclusions, null values, age bands, correction rate, disagreement, and residual cases. Alternative explanations include configuration, logging gaps, clock drift, synchronization, case mix, ownership changes, policy versions, and selection effects. An IT virtual assistant may preserve, normalize, compare, route, and schedule; authorized technical, security, privacy, legal, employment, financial, and business owners retain consequential decisions. The ten public sources inform the protocol but do not inspect this environment, prove causation, certify a provider, or establish a universal benchmark. Preserve the query, codebook, sample receipt, chronology, reviewer notes, decision log, approved action, verification, limitations, and refresh trigger so another authorized analyst can reproduce the bounded result without unnecessary sensitive data.

Alternative explanations. Software Inventory Reconciliation Coverage Study asks how consistently endpoint, identity, procurement, and application-owner records identify the same software population. Stage 10 uses one software product and its installation, entitlement, owner, version, support, exception, and retirement evidence across declared systems as the declared observation unit and freezes the cohort, system boundaries, local and UTC times, source versions, inclusion rules, and expected decision before outcomes are reviewed. Record ITV-R-1013-10 distinguishes system events, business facts, owner decisions, reviewer classifications, implementation evidence, and unresolved hypotheses. It includes routine, missing-source, conflicting-version, wrong-identity, inaccessible-system, unavailable-owner, reversed, corrected, and reopened cases. Two reviewers classify a stratified subset independently using written behavioral anchors, preserve first-pass disagreement, and adjudicate against retained evidence. Report numerator, denominator, exclusions, null values, age bands, correction rate, disagreement, and residual cases. Alternative explanations include configuration, logging gaps, clock drift, synchronization, case mix, ownership changes, policy versions, and selection effects. An IT virtual assistant may preserve, normalize, compare, route, and schedule; authorized technical, security, privacy, legal, employment, financial, and business owners retain consequential decisions. The ten public sources inform the protocol but do not inspect this environment, prove causation, certify a provider, or establish a universal benchmark. Preserve the query, codebook, sample receipt, chronology, reviewer notes, decision log, approved action, verification, limitations, and refresh trigger so another authorized analyst can reproduce the bounded result without unnecessary sensitive data.

Authority boundary. Software Inventory Reconciliation Coverage Study asks how consistently endpoint, identity, procurement, and application-owner records identify the same software population. Stage 11 uses one software product and its installation, entitlement, owner, version, support, exception, and retirement evidence across declared systems as the declared observation unit and freezes the cohort, system boundaries, local and UTC times, source versions, inclusion rules, and expected decision before outcomes are reviewed. Record ITV-R-1013-11 distinguishes system events, business facts, owner decisions, reviewer classifications, implementation evidence, and unresolved hypotheses. It includes routine, missing-source, conflicting-version, wrong-identity, inaccessible-system, unavailable-owner, reversed, corrected, and reopened cases. Two reviewers classify a stratified subset independently using written behavioral anchors, preserve first-pass disagreement, and adjudicate against retained evidence. Report numerator, denominator, exclusions, null values, age bands, correction rate, disagreement, and residual cases. Alternative explanations include configuration, logging gaps, clock drift, synchronization, case mix, ownership changes, policy versions, and selection effects. An IT virtual assistant may preserve, normalize, compare, route, and schedule; authorized technical, security, privacy, legal, employment, financial, and business owners retain consequential decisions. The ten public sources inform the protocol but do not inspect this environment, prove causation, certify a provider, or establish a universal benchmark. Preserve the query, codebook, sample receipt, chronology, reviewer notes, decision log, approved action, verification, limitations, and refresh trigger so another authorized analyst can reproduce the bounded result without unnecessary sensitive data.

Reperformance test. Software Inventory Reconciliation Coverage Study asks how consistently endpoint, identity, procurement, and application-owner records identify the same software population. Stage 12 uses one software product and its installation, entitlement, owner, version, support, exception, and retirement evidence across declared systems as the declared observation unit and freezes the cohort, system boundaries, local and UTC times, source versions, inclusion rules, and expected decision before outcomes are reviewed. Record ITV-R-1013-12 distinguishes system events, business facts, owner decisions, reviewer classifications, implementation evidence, and unresolved hypotheses. It includes routine, missing-source, conflicting-version, wrong-identity, inaccessible-system, unavailable-owner, reversed, corrected, and reopened cases. Two reviewers classify a stratified subset independently using written behavioral anchors, preserve first-pass disagreement, and adjudicate against retained evidence. Report numerator, denominator, exclusions, null values, age bands, correction rate, disagreement, and residual cases. Alternative explanations include configuration, logging gaps, clock drift, synchronization, case mix, ownership changes, policy versions, and selection effects. An IT virtual assistant may preserve, normalize, compare, route, and schedule; authorized technical, security, privacy, legal, employment, financial, and business owners retain consequential decisions. The ten public sources inform the protocol but do not inspect this environment, prove causation, certify a provider, or establish a universal benchmark. Preserve the query, codebook, sample receipt, chronology, reviewer notes, decision log, approved action, verification, limitations, and refresh trigger so another authorized analyst can reproduce the bounded result without unnecessary sensitive data.

Sensitivity analysis. Software Inventory Reconciliation Coverage Study asks how consistently endpoint, identity, procurement, and application-owner records identify the same software population. Stage 13 uses one software product and its installation, entitlement, owner, version, support, exception, and retirement evidence across declared systems as the declared observation unit and freezes the cohort, system boundaries, local and UTC times, source versions, inclusion rules, and expected decision before outcomes are reviewed. Record ITV-R-1013-13 distinguishes system events, business facts, owner decisions, reviewer classifications, implementation evidence, and unresolved hypotheses. It includes routine, missing-source, conflicting-version, wrong-identity, inaccessible-system, unavailable-owner, reversed, corrected, and reopened cases. Two reviewers classify a stratified subset independently using written behavioral anchors, preserve first-pass disagreement, and adjudicate against retained evidence. Report numerator, denominator, exclusions, null values, age bands, correction rate, disagreement, and residual cases. Alternative explanations include configuration, logging gaps, clock drift, synchronization, case mix, ownership changes, policy versions, and selection effects. An IT virtual assistant may preserve, normalize, compare, route, and schedule; authorized technical, security, privacy, legal, employment, financial, and business owners retain consequential decisions. The ten public sources inform the protocol but do not inspect this environment, prove causation, certify a provider, or establish a universal benchmark. Preserve the query, codebook, sample receipt, chronology, reviewer notes, decision log, approved action, verification, limitations, and refresh trigger so another authorized analyst can reproduce the bounded result without unnecessary sensitive data.

Corrective-action mapping. Software Inventory Reconciliation Coverage Study asks how consistently endpoint, identity, procurement, and application-owner records identify the same software population. Stage 14 uses one software product and its installation, entitlement, owner, version, support, exception, and retirement evidence across declared systems as the declared observation unit and freezes the cohort, system boundaries, local and UTC times, source versions, inclusion rules, and expected decision before outcomes are reviewed. Record ITV-R-1013-14 distinguishes system events, business facts, owner decisions, reviewer classifications, implementation evidence, and unresolved hypotheses. It includes routine, missing-source, conflicting-version, wrong-identity, inaccessible-system, unavailable-owner, reversed, corrected, and reopened cases. Two reviewers classify a stratified subset independently using written behavioral anchors, preserve first-pass disagreement, and adjudicate against retained evidence. Report numerator, denominator, exclusions, null values, age bands, correction rate, disagreement, and residual cases. Alternative explanations include configuration, logging gaps, clock drift, synchronization, case mix, ownership changes, policy versions, and selection effects. An IT virtual assistant may preserve, normalize, compare, route, and schedule; authorized technical, security, privacy, legal, employment, financial, and business owners retain consequential decisions. The ten public sources inform the protocol but do not inspect this environment, prove causation, certify a provider, or establish a universal benchmark. Preserve the query, codebook, sample receipt, chronology, reviewer notes, decision log, approved action, verification, limitations, and refresh trigger so another authorized analyst can reproduce the bounded result without unnecessary sensitive data.

Pilot design. Software Inventory Reconciliation Coverage Study asks how consistently endpoint, identity, procurement, and application-owner records identify the same software population. Stage 15 uses one software product and its installation, entitlement, owner, version, support, exception, and retirement evidence across declared systems as the declared observation unit and freezes the cohort, system boundaries, local and UTC times, source versions, inclusion rules, and expected decision before outcomes are reviewed. Record ITV-R-1013-15 distinguishes system events, business facts, owner decisions, reviewer classifications, implementation evidence, and unresolved hypotheses. It includes routine, missing-source, conflicting-version, wrong-identity, inaccessible-system, unavailable-owner, reversed, corrected, and reopened cases. Two reviewers classify a stratified subset independently using written behavioral anchors, preserve first-pass disagreement, and adjudicate against retained evidence. Report numerator, denominator, exclusions, null values, age bands, correction rate, disagreement, and residual cases. Alternative explanations include configuration, logging gaps, clock drift, synchronization, case mix, ownership changes, policy versions, and selection effects. An IT virtual assistant may preserve, normalize, compare, route, and schedule; authorized technical, security, privacy, legal, employment, financial, and business owners retain consequential decisions. The ten public sources inform the protocol but do not inspect this environment, prove causation, certify a provider, or establish a universal benchmark. Preserve the query, codebook, sample receipt, chronology, reviewer notes, decision log, approved action, verification, limitations, and refresh trigger so another authorized analyst can reproduce the bounded result without unnecessary sensitive data.

Limitations. Software Inventory Reconciliation Coverage Study asks how consistently endpoint, identity, procurement, and application-owner records identify the same software population. Stage 16 uses one software product and its installation, entitlement, owner, version, support, exception, and retirement evidence across declared systems as the declared observation unit and freezes the cohort, system boundaries, local and UTC times, source versions, inclusion rules, and expected decision before outcomes are reviewed. Record ITV-R-1013-16 distinguishes system events, business facts, owner decisions, reviewer classifications, implementation evidence, and unresolved hypotheses. It includes routine, missing-source, conflicting-version, wrong-identity, inaccessible-system, unavailable-owner, reversed, corrected, and reopened cases. Two reviewers classify a stratified subset independently using written behavioral anchors, preserve first-pass disagreement, and adjudicate against retained evidence. Report numerator, denominator, exclusions, null values, age bands, correction rate, disagreement, and residual cases. Alternative explanations include configuration, logging gaps, clock drift, synchronization, case mix, ownership changes, policy versions, and selection effects. An IT virtual assistant may preserve, normalize, compare, route, and schedule; authorized technical, security, privacy, legal, employment, financial, and business owners retain consequential decisions. The ten public sources inform the protocol but do not inspect this environment, prove causation, certify a provider, or establish a universal benchmark. Preserve the query, codebook, sample receipt, chronology, reviewer notes, decision log, approved action, verification, limitations, and refresh trigger so another authorized analyst can reproduce the bounded result without unnecessary sensitive data.

Evidence packet. Software Inventory Reconciliation Coverage Study asks how consistently endpoint, identity, procurement, and application-owner records identify the same software population. Stage 17 uses one software product and its installation, entitlement, owner, version, support, exception, and retirement evidence across declared systems as the declared observation unit and freezes the cohort, system boundaries, local and UTC times, source versions, inclusion rules, and expected decision before outcomes are reviewed. Record ITV-R-1013-17 distinguishes system events, business facts, owner decisions, reviewer classifications, implementation evidence, and unresolved hypotheses. It includes routine, missing-source, conflicting-version, wrong-identity, inaccessible-system, unavailable-owner, reversed, corrected, and reopened cases. Two reviewers classify a stratified subset independently using written behavioral anchors, preserve first-pass disagreement, and adjudicate against retained evidence. Report numerator, denominator, exclusions, null values, age bands, correction rate, disagreement, and residual cases. Alternative explanations include configuration, logging gaps, clock drift, synchronization, case mix, ownership changes, policy versions, and selection effects. An IT virtual assistant may preserve, normalize, compare, route, and schedule; authorized technical, security, privacy, legal, employment, financial, and business owners retain consequential decisions. The ten public sources inform the protocol but do not inspect this environment, prove causation, certify a provider, or establish a universal benchmark. Preserve the query, codebook, sample receipt, chronology, reviewer notes, decision log, approved action, verification, limitations, and refresh trigger so another authorized analyst can reproduce the bounded result without unnecessary sensitive data.

Decision and refresh rule. Software Inventory Reconciliation Coverage Study asks how consistently endpoint, identity, procurement, and application-owner records identify the same software population. Stage 18 uses one software product and its installation, entitlement, owner, version, support, exception, and retirement evidence across declared systems as the declared observation unit and freezes the cohort, system boundaries, local and UTC times, source versions, inclusion rules, and expected decision before outcomes are reviewed. Record ITV-R-1013-18 distinguishes system events, business facts, owner decisions, reviewer classifications, implementation evidence, and unresolved hypotheses. It includes routine, missing-source, conflicting-version, wrong-identity, inaccessible-system, unavailable-owner, reversed, corrected, and reopened cases. Two reviewers classify a stratified subset independently using written behavioral anchors, preserve first-pass disagreement, and adjudicate against retained evidence. Report numerator, denominator, exclusions, null values, age bands, correction rate, disagreement, and residual cases. Alternative explanations include configuration, logging gaps, clock drift, synchronization, case mix, ownership changes, policy versions, and selection effects. An IT virtual assistant may preserve, normalize, compare, route, and schedule; authorized technical, security, privacy, legal, employment, financial, and business owners retain consequential decisions. The ten public sources inform the protocol but do not inspect this environment, prove causation, certify a provider, or establish a universal benchmark. Preserve the query, codebook, sample receipt, chronology, reviewer notes, decision log, approved action, verification, limitations, and refresh trigger so another authorized analyst can reproduce the bounded result without unnecessary sensitive data.

What the software inventory reconciliation coverage study data shows

Treat this as a planning benchmark, not a universal number. Compare the benchmark against your ticket volume, SaaS stack, documentation backlog, and support risk before assigning recurring work.

The useful output is a decision about capacity, not a static statistic. If the workflow is high volume and low judgment, an IT virtual assistant can absorb coordination and upkeep. If the workflow is low volume but high risk, keep it with the technical owner and use the assistant only for preparation, reminders, and documentation.

Decision rules

Consolidated statistics

Sources

1. NIST Cybersecurity Framework 2.0Governance and cybersecurity risk outcomes.
2. NIST SP 800-53 Revision 5Security and privacy control catalog.
3. NIST SP 800-61 Revision 3Incident response recommendations.
4. NIST Digital Identity GuidelinesIdentity proofing, authentication, and federation guidance.
5. CISA Cybersecurity Performance GoalsPrioritized baseline cybersecurity practices.
6. CISA Secure by DesignSecurity ownership and design principles.
7. CISA Known Exploited Vulnerabilities CatalogAuthoritative vulnerability-prioritization input.
8. FTC Data Security GuidanceBusiness data-security guidance.
9. NIST Privacy FrameworkPrivacy risk-management framework.
10. Records Management Policy and GuidanceRecords lifecycle and policy references.

Measurement checklist

How to read the result

A good research page should leave the manager with a working number and a clear boundary: what the assistant can do every week, what the assistant can prepare for review, and what must never move without the accountable technical owner.

Source and refresh note

This planning page is dated for 2026 and should be refreshed quarterly as tool stacks, ticket patterns, and security expectations change.

How should teams use this benchmark?

Use it to define task volume, access limits, review cadence, and escalation rules before assigning work.