research

Measuring how often software trials reach production unapproved

A method for tracing free trials into production use and measuring the share that never passed approval, security review, or the software inventory.

Short answer

Use this benchmark to size repeatable IT work, set the review cadence, and decide what stays with the technical owner before assigning the workflow to an IT virtual assistant.

Research playbook

MeasureVolume and handling time
OwnerTechnical manager validates
Risk ruleName sensitive access
RefreshQuarterly benchmark review
On this pageJump to section

Key stats

Sample floor20 productsStudy protocol
Evidence sources4 minimumStudy protocol
Population unitTeam trialStudy protocol

Key takeaways

A trial can become a production tool without a purchase order, a security review, or a line in the inventory. The team starts with a free account, connects a data source, and keeps using it after the trial ends. This study traces trials into production use and measures the share that never passed the documented approval route. It gives software owners a number for the shadow IT they suspect but cannot see.

Question and scope

The study asks what share of software trials in use at the end of the period reached production without an approval record. The unit is one trial account for one product in one team. The population is every trial the team can identify through sign-up records, single sign-on, expense data, and browser or device management. The result is a lower bound because trials that leave no trace cannot be counted.

Exclude personal trials that never touched company data or a company device. Include trials that started on a personal account but later connected to company email or files. Record the inclusion rule and the evidence used for each case. A vague scope makes the unapproved share impossible to compare across cycles.

Define a trial and a production use

Treat an account as a trial when the vendor offers it free for a limited period or when the team describes it as an evaluation. Treat the use as production when the team relies on it for live work, stores company data in it, or connects it to a system others depend on. The label on the billing record is less important than the actual use. Record the evidence for the classification in the study row.

A trial that is still being evaluated at the end of the period is not automatically production. Mark it as active evaluation and record the decision date. A trial that has passed its end date and still holds live data is production for the purpose of this study. Write the definitions before looking at the cases so the result is not shaped by the exceptions.

Build the trial frame

Combine the single sign-on application list, the expense system, the procurement queue, and the browser extension inventory. Match products by domain and vendor name, because the same tool can appear under different labels. Add the team that requested each trial and the date the account first appeared. No single source will contain every trial.

Search the support queue for messages about free accounts, evaluation limits, and upgrade prompts. Ask team leads for tools they use but do not own. Record the source for each entry so a reviewer can verify it. A trial found only through a conversation is still a case, but it needs a note.

Trace trials through billing and identity

For each trial, check whether the vendor appears in the card statement, the invoice ledger, or the procurement system. A charge is strong evidence that the trial converted. Check the single sign-on logs for regular use by more than one person. A tool used daily by a team is production even when the invoice says free.

Look for connected integrations, such as email, calendar, or the support desk. An integration is evidence that the tool holds live data and needs review. Record the date the connection was made and who approved it. A trial that connects to core systems without review is the highest-risk case in the study.

Sample teams and products

Take a random sample across departments, with at least twenty trial products in the first cycle. Oversample teams that handle customer data or make purchases, because those tools carry more risk. Keep the population count and the sampling rule with the result. A sample drawn only from the procurement queue will contain no unapproved trials by construction.

For each sampled product, interview the person who uses it most and the manager who would approve a purchase. Ask how the trial started, what data it holds, and what would happen if it were removed. Compare the answers with the records. The gap between the interview and the record is often the finding.

Measure the unapproved share

Count the trials in production with no approval record and divide by the total trials in production. Report the count and the share, then split by data sensitivity and by whether the tool has an integration. A tool that holds customer records deserves its own line. The share should be reported with the evidence quality for each case.

Measure how long each unapproved tool has been in production using the first sign-in or the first charge. If the date is unknown, mark the age as unmeasured. Count the tools that were approved after the study began as a separate remediation result. The starting share and the repair count tell different stories.

Compare with the approval policy

Find the written rule for trials, including the security review threshold and the requirement to register a tool in the inventory. Compare the findings with that rule rather than with a general expectation. If the policy is silent on trials, that gap is part of the result. A rule that only covers purchases cannot govern a free account.

Check whether the policy names who can approve a trial and how long an approval lasts. Note the tools that had a verbal approval but no record. Record the approver and the date where it can be confirmed. Verbal approval is a process finding, not a reason to mark the tool approved.

Interview the requester

Ask the person who started the trial what problem it was meant to solve and how they found the tool. A recommendation from a peer, a vendor email, and a search result lead to different risks. Record whether anyone reviewed the tool before the account was created. The answer explains why the formal route was skipped.

Ask what would happen if the tool were removed today. A team that can name the workaround is experimenting, while a team that cannot has a production dependency. Record the answer in the study row. The distinction changes the remediation priority.

Account for trials bought on cards

Reconcile the card statement with the trial frame and look for vendor names that do not appear in single sign-on. A small charge after a free period is a strong signal that a trial converted. Match the charge to the team and the person who holds the card. The expense record often finds tools that identity data misses.

Check whether the charge was approved or reimbursed without a software review. Record the amount and the date, but keep the report focused on the process rather than the individual. A card purchase can be legitimate for a small tool, but it still needs an owner and an inventory entry. Note whether the person knew about the trial process before making the purchase.

Use the result in the software inventory

Add the unapproved tools to the inventory with the evidence and the owner, even before the department decides. An entry marked as pending review is better than a tool that exists only in a card statement. Set a date for the decision and a date to verify the inventory entry. The inventory becomes the single list the next study starts from.

Remove tools that the department confirms it no longer uses and keep the closed record for the year. Compare the inventory with the card statement each quarter to catch new trials early. Ask the budget owner to review the pending list. A clean inventory makes the next unapproved share smaller and easier to explain.

Report and next use

Give each department a list of its unapproved tools with the data and integrations involved. Ask for a decision to approve, replace, or remove each one. Set a date for the decision and a date to verify removal. Keep the report factual and avoid turning a tool review into a blame exercise, because people will stop reporting trials if the first response is punishment.

Repeat the study after the trial form and inventory process change, and compare the same departments. If the unapproved share falls but the number of trials rises, the process is working and the organisation is experimenting more visibly. Keep the method with the software inventory owner. The goal is a complete list, not a zero count.

Sources and next step

Use the NIST Cybersecurity Framework 2.0 and the CISA Cross-Sector Cybersecurity Performance Goals as primary references for the DNS change, recovery key, software trial, privileged account, and forwarding rule measures discussed here. The NIST SP 800-53 Rev. 5 supports the access and audit record checks, and the GAO data reliability guidance supports the sampling and verification approach used in these methods. Apply your own policies, contracts, and system documentation when adapting the method.

Compare this study with the privileged account age audit and the mailbox forwarding survival study before combining them into one review cycle. If the measurement work is recurring and your technical owner can define the scope, review the service areas and contact ITVirtualAssistant to discuss a limited pilot.

Benchmark brief

What this research page must produce

Working number

A practical estimate for volume, review time, escalation rate, and assistant capacity.

Operating boundary

A clear split between routine support, preparation work, and technical ownership.

What the measuring how often software trials reach production unapproved 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.

Workflow

Recommended operating workflow

1

Collect a baseline

Pull the last 30 to 90 days of examples related to measuring how often software trials reach production unapproved, including completed work and unresolved exceptions.

2

Classify the work

Tag each item by routine admin, manager approval, technical decision, security risk, or vendor dependency.

3

Set the operating number

Use the median weekly volume and review time to decide how many assistant hours the workflow deserves.

4

Refresh the benchmark

Recheck the numbers quarterly so tool growth, new systems, and security requirements do not silently change the scope.

Decision rules

MetricUse it to decideManager action
Weekly volumeWhether the workflow is worth assigning as recurring assistant work.Approve a weekly capacity target and backlog threshold.
Access sensitivityWhether the assistant can work directly or only prepare review notes.Set least-privilege permissions and removal dates.
Escalation rateWhether the workflow is stable enough to delegate.Rewrite the SOP when exceptions exceed the agreed threshold.

Consolidated statistics

StatisticFigureSource
Sample floor20 productsStudy protocol
Evidence sources4 minimumStudy protocol
Population unitTeam trialStudy protocol

Sources

  1. CISA Cross-Sector Cybersecurity Performance GoalsSupply chain and asset goals for software used in the business.
  2. NIST Cybersecurity Framework 2.0Governance and supply chain risk outcomes for third-party tools.
  3. NIST SP 800-53 Rev. 5, Security and Privacy ControlsConfiguration and inventory controls behind the approved software list.
  4. NIST SP 800-128, Guide for Security-Focused Configuration ManagementConfiguration records that make trial-to-production matching possible.

Measurement checklist

FieldWhat to captureOwner
VolumeWeekly request count, backlog age, and repeat issue patternsAssistant prepares, manager reviews
RiskAccess level, customer impact, security sensitivity, and approval needsTechnical owner
CadenceDaily, weekly, monthly, or quarterly review rhythmManager
EvidenceSample tickets, logs, screenshots, and before-after examplesAssistant collects, owner validates
EscalationTriggers, approval path, response time, and stop-work rulesTechnical owner

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.

Get free benchmark review