> tpl_prc_016
Software/SaaS License Requirements Worksheet
Detailed software asset management and entitlement planning model calculating active consumption, named vs concurrent licensing, burst buffers, true-up exposure, and multi-tier discount optimization.
License planning model calculating active user consumption, named vs concurrent tiers, true-up exposure, and discounts.
Important Tech Document Template & Operational Notice
TinyCTO.tv Tech Document Template Notice: This template is a general educational and operational starting point. It is not legal, tax, accounting, investment, procurement, regulatory, security or certification advice. Requirements vary by jurisdiction, organization, contract and risk. Review and adapt it with qualified professionals before relying on it.
Problem Solved
Enterprises overspend by 25-40% on SaaS subscriptions by procuring software based on unvalidated department requests without measuring actual monthly login telemetry, suffering catastrophic audit true-up penalties when vendor compliance audits strike.
When to Use
- •Sizing software and SaaS seat requirements prior to signing multi-year enterprise license agreements (ELAs)
- •Auditing true usage and reclaiming unassigned or dormant licenses across enterprise tools
- •Calculating exposure and defending against external publisher compliance audits
When NOT to Use
- •For overarching procurement master contracts (use TPL-PRC-017)
- •For cloud computing consumption and infrastructure sizing (use TPL-CLD-008)
5 Template Sections & Structural Outline
Classifying publisher licensing mechanics: Named User, Concurrent Floating, Processor Core, Tiered API Consumption, or Feature-Gated Modules.
Analyzing 30/60/90-day SSO authentication logs to identify abandoned accounts. Enforcing automated deprovisioning policies for users with 45+ days of inactivity.
Mapping user personas into tiered bundles: Enterprise Power Users (15%), Standard Operational Users (55%), and Restricted Read-Only or Casual Reviewers (30%).
Simulating annual true-up scenarios: calculating financial penalties if headcount surges exceed contract buffers. Factoring in pre-purchased burst buffers.
Structuring commitment tiers against projected hiring growth. Comparing upfront annual prepayment discounts against flexible quarterly true-down rights.
Completion Instructions
Independent Review Checklist
- All mandatory sections completed
- No secrets or passwords included
- Executive sponsor sign-off obtained
Software/SaaS License Requirements Worksheet - Worked Case Study
Fictional Entity: Global Enterprise Collaboration & Productivity Suite SaaS Portfolio (12,500 Enterprise Seats)
Real-world production case study demonstrating complete operational adoption for Global Enterprise Collaboration & Productivity Suite SaaS Portfolio (12,500 Enterprise Seats).
- •Ingested Okta SSO telemetry across 12,500 licensed users, discovering 2,840 completely inactive accounts over a 90-day period
- •Down-tiered 4,100 users from $45/mo Enterprise suites to $12/mo Standard viewer accounts, generating $1.62M in annual recurring savings
- •Secured contractual 15% True-Down flexibility rights on renewal, protecting against future corporate headcount fluctuations
Frequently Asked Questions
What is the operational difference between "True-Up" and "True-Down" rights in SaaS contracts?
A True-Up requires the customer to pay retroactive fees if actual usage exceeds contracted seat commitments. A True-Down allows the customer to reduce their contracted seat count (and recurring billing) at annual contract milestones if headcount shrinks or software usage declines. True-Down must be aggressively negotiated upfront.
How should IT procurement audit indirect software consumption (e.g. API integrations)?
Indirect usage occurs when third-party apps query the licensed software via APIs (e.g. Salesforce or SAP), which vendors often claim requires additional licenses. Audit contracts to ensure automated machine-to-machine integrations are explicitly covered under standard enterprise platform licenses.
What is automated dormant seat harvesting and how frequently should it execute?
Automated harvesting queries SSO logs every 30 days. If a user has not authenticated for 45 consecutive days, the system revokes their license, returning it to the available enterprise pool. This prevents purchasing new licenses when onboarding new employees.
Download Tech Document Pack
Auth RequiredDownload all blank templates, worked scenarios, and verification manifests in a single verified archive.
Authoritative Sources
- ISO/IEC 19770-1:2017 Information Technology — IT Asset ManagementISO • OFFICIAL REQUIREMENT
- FinOps Foundation: SaaS Spend Management FrameworkFinOps Foundation • OFFICIAL REQUIREMENT
- Gartner: Tool Sizing and Optimization Strategies for SaaS ContractsGartner • OFFICIAL REQUIREMENT