Software asset management

A software licence true-up worksheet before the vendor call

A worksheet that reconciles entitlement, active users, and contract terms before a renewal call so the company negotiates from evidence.

Short answer

Start with repeatable IT work that has a clear owner, clear access limits, and a review cadence. Keep risky technical decisions with the manager or provider who owns the system.

Delegation playbook

Best fitRepeatable IT admin
OwnerManager or IT lead
Risk ruleEscalate technical judgment
PilotTwo-week sample workflow
On this pageJump to section

A licence true-up call often starts with a vendor number and a deadline. Without a worksheet, the team agrees to a count it cannot defend and pays for seats nobody uses. The worksheet brings entitlement, usage, and contract terms into one view before the call. It turns a tense negotiation into a set of questions with evidence behind them. The goal is to leave the call with an agreed number and a written record of how it was reached.

Pull entitlement and usage data

Collect the contract, the order form, and the latest invoice for the product. Note the licensed quantity, the metric, the term, and any minimum commitment. Export the active user list from the administration console on the same day. Keep both files with the date and the source in the worksheet. Store the files in one folder so the negotiator can open them during the call.

Ask the vendor for a current entitlement statement if the contract is unclear. Compare the statement with the invoice and the order form. Record any difference rather than choosing the most convenient number. The worksheet should show what the company bought and what the vendor believes it sold. A vendor statement that disagrees with the invoice is a question for the account manager.

Define what counts as an active user

Write a clear definition of an active account for this product. Decide whether it means a sign-in in the last thirty days, an assigned licence, or an enabled account. Apply the same definition to every user in the export. A count without a definition cannot be defended in a negotiation. Write the definition in the worksheet so the next reviewer applies the same rule.

Check how the vendor measures usage in the contract. Some products count named users, others count devices or monthly active users. Note any automated suspension or true-up clause. The definition should match the contract metric, not the easiest report to produce. A contract that counts devices may need a separate export from the management console, and the worksheet should record which export was used.

Reconcile differences by account

Match the entitlement list to the active users and mark each account as in use, dormant, shared, or unknown. Investigate the dormant accounts before the call. Check whether they belong to leavers, test users, or people who need access next month. Each category needs a different decision. The worksheet should show the evidence for each category, not only the total.

Count the shared accounts separately because they often hide multiple users. Note any account used by a contractor or an integration. Ask the owner to confirm the ones marked unknown. The reconciled list is the evidence the team brings to the vendor. A shared account used by ten people can look like one seat in the export, so the count is not treated as people.

List the questions for the vendor

Write the questions before the call, starting with how the vendor calculated its number. Ask which metric applies, what period it covers, and how it treats dormant accounts. Ask for the data in writing. A verbal figure cannot be checked after the meeting. Send the questions to the vendor before the call when the account manager agrees, and give them a deadline before the meeting.

Add questions about downgrade options, co-termination, and payment terms. Ask what happens if the company reduces seats during the term. Record the answers beside the questions. The call should fill gaps in the worksheet, not reopen the basics. Ask for the answers in writing so the worksheet can be checked later, and attach the reply to the file with the date it arrived.

Agree the negotiation limits

Decide the maximum seat count and the maximum annual cost before the call. Base the limits on the reconciled usage and the budget owner's instruction. Write down what the company will accept and what it will walk away from. A limit agreed in the meeting is a limit under pressure. Include the budget owner's name and the date the limit was approved.

Identify the concessions that matter, such as a shorter term, a review date, or training. Rank them so the negotiator knows what to trade. Confirm who can approve a change above the limit. The worksheet should carry the approval name and the date. A concession that costs nothing today can create a renewal trap next year, so ask the vendor to confirm it in writing.

Record the outcome and the next date

After the call, write the agreed quantity, price, term, and any conditions in the worksheet. Send a summary to the vendor and ask for confirmation. Update the contract record and the renewal calendar. The next owner should not have to reconstruct the conversation. Ask the vendor to confirm the quantity and price in writing within two working days, and store the confirmation with the worksheet.

Note the assumptions that could change the count, such as a hiring plan or a project end. Set a review date before the next renewal window. Assign the person who will update the usage export. A true-up that ends with an invoice but no record will be repeated next year. A hiring plan that adds ten seats should be visible before the next invoice.

Keep the worksheet for the next cycle

Store the worksheet with the contract and the usage export in the software register. Name it by product and renewal year rather than by the person who prepared it. Keep the vendor's written confirmation with it. The next cycle starts from a known baseline instead of an empty sheet. Name the file with the product and the renewal year so it is easy to find.

Review the definitions and the metric each year because vendors change packaging. Check whether the product now bundles features the company buys separately. Add the finding to the renewal calendar. The worksheet becomes more useful each time it is reused. Check whether a bundled product now covers a tool the company buys separately before the next renewal window opens, and record the answer in the worksheet.

Sources and next step

Use the CISA Cross-Sector Cybersecurity Performance Goals and the NIST Cybersecurity Framework 2.0 as primary references for the printer, domain, support rota, licence, and desk move practices discussed in these guides. The NIST SP 800-53 Rev. 5 supports the access and asset records, and the SBA cybersecurity guidance frames the vendor and account ownership checks. Apply your own policies, contracts, and system documentation to the workflow.

Compare this guide with the domain renewal register and the licence true-up worksheet before changing a live process. If the coordination is recurring and your technical owner can define the boundaries, review the IT virtual assistant service areas and contact ITVirtualAssistant to discuss a limited pilot.

Operating brief

What this guide should help you decide

Delegate

Routine intake, status updates, records, screenshots, and documentation upkeep.

Keep ownership

Approvals, risky system changes, security decisions, and final technical judgment.

How to use this guide

Use this page to decide what an IT virtual assistant should handle first. If the task is recurring, documented, and easy to review, it is usually a better first delegation candidate than work that requires live technical judgment.

Treat the article as an operating brief, not just a topic overview. The goal is to turn loose IT work into a named workflow with inputs, outputs, permissions, review cadence, and a handoff rule that protects the business while reducing manager load.

Workflow

Recommended operating workflow

1

Define the request

Write what a software licence true-up worksheet before the vendor call means in your company, where requests enter, and what finished work looks like.

2

Limit the access

Give the assistant only the tool permissions needed for intake, records, status updates, or documentation.

3

Run a pilot

Use a two-week sample period so the manager can review accuracy before expanding the workflow.

4

Review patterns

Summarize repeat issues, blocked requests, and escalation volume so the technical owner can improve the process.

Decision rules

QuestionVA fit signalEscalate when
Is the work repeatable?The same request appears weekly and can be described in steps.The request changes business policy or system design.
Can quality be reviewed?The manager can inspect the output without redoing the work.Only a senior technical person can judge correctness.
Is access contained?The assistant can work with read-only or role-limited access.Admin rights, customer data, or security settings are involved.

Delegation checklist

  • Write the intake source, expected output, and manager review cadence.
  • Confirm the assistant has only the permissions needed for the workflow.
  • List the events that require escalation before work continues.
  • Track examples for two weeks before changing the workflow.
  • Save examples of good and bad outputs so the assistant has concrete references.
  • Review the workflow monthly and remove permissions that are no longer needed.

Example first-week agenda

Day one should cover the workflow owner, tools, allowed actions, forbidden actions, and escalation language. By the end of week one, the assistant should have produced a small sample of completed work, a list of unclear requests, and a manager-reviewed improvement note.

What to review before delegating

Confirm the owner, access level, review cadence, and escalation path before assigning any recurring IT workflow to a remote assistant.

What should an IT virtual assistant handle first?

Start with repeatable, reviewable work such as ticket summaries, account records, documentation updates, and checklist follow up.

Get free IT support review