This form is designed to help teams and individuals review recurring subscriptions and software renewals over a defined audit period. It gathers information about what is currently paid for, how it is used, what it costs, when it renews, and whether it should be kept, changed or discontinued. Complete each section as accurately as possible using invoices, vendor portals, procurement records and usage reports where available. Responses are for internal planning purposes and do not constitute legal, financial or regulatory advice.
Tip: work through the sections in order. Sections that do not apply to your situation can be marked as not applicable in the notes fields rather than left blank.
Audit reference or internal tracking code
Date this audit was started
Date this audit was completed
Audit period covered
Name of the person completing this audit
Job title or role
Department, team or cost centre
Organization or household name
Email address for audit follow-up
Phone or messaging contact (optional)
Which best describes the scope of this audit?
Individual or single user
Small team (2 to 10 people)
Department or business unit (11 to 100 people)
Whole organization (more than 100 people)
Managed service provider auditing on behalf of a client
Name of the client or account being audited
Who is the primary budget holder for these subscriptions?
Myself
A department manager
A finance or procurement function
An IT or operations function
Shared across several budget holders
Other
Please describe who holds the budget
This section captures a high-level picture of the subscription portfolio before individual items are examined in detail.
Approximate number of active subscriptions or software licences in scope
Estimated total annual spend on subscriptions and software
How is the portfolio currently recorded?
A maintained spreadsheet or document
A dedicated asset or licence management tool
An accounting or expense platform
Records held by individual team members
No formal record exists
How do you currently discover or track subscriptions without a formal record?
Has a subscription audit been carried out in the past 12 months?
Please summarize the key findings and actions from the previous audit
What has prevented an audit from taking place until now?
Which categories of subscription are included in this audit?
Productivity and office suites
Communication and conferencing
Design, creative and media
Development, code hosting and developer tooling
Customer relationship and sales platforms
Marketing, email and analytics
Finance, accounting and invoicing
Storage, hosting and cloud infrastructure
Security, backup and identity management
Learning, training and professional development
Industry-specific or specialist software
Personal or household subscriptions
Other:
How confident are you that the subscription list is complete?
Very confident — all spend is accounted for
Mostly confident — a few items may be missing
Somewhat confident — significant gaps are likely
Not confident — this audit is the first attempt at a full inventory
List each subscription or licence below. The annual cost column calculates automatically from the quantity and unit cost entered. Add as many rows as needed and duplicate rows for the same product when licence tiers differ.
Subscription and licence inventory
Product or service name | Vendor or provider | Category | Billing frequency | Quantity of licences | Unit cost per licence per year | Calculated annual cost | Auto-renews? | Next renewal or expiry date | Proposed action | ||
|---|---|---|---|---|---|---|---|---|---|---|---|
A | B | C | D | E | F | G | H | I | J | ||
1 | Team collaboration suite | Example Software Co. | Productivity and office suites | Annual | 25 | $120.00 | $3,000.00 | Keep and review tier | |||
2 | Cloud storage plan | Example Cloud Services | Storage, hosting and cloud infrastructure | Monthly | 10 | $60.00 | $600.00 | Renew — negotiate volume rate | |||
3 | Design tool licence | Example Design Tools | Design, creative and media | Annual | 3 | $240.00 | $720.00 | Downgrade to 2 licences | |||
4 | $0.00 | ||||||||||
5 | $0.00 | ||||||||||
6 | $0.00 | ||||||||||
7 | $0.00 | ||||||||||
8 | $0.00 | ||||||||||
9 | $0.00 | ||||||||||
10 | $0.00 |
How many of the listed items are estimated to be unused or rarely used?
Estimated annual value of unused or rarely used items
Which payment methods are used across the portfolio?
Company or organizational card
Personal card later reimbursed
Bank transfer or direct debit
Invoice with payment terms
App store or platform marketplace billing
Prepaid credits or usage balance
Other:
Are any subscriptions paid on a personal card and reimbursed?
Which subscriptions are paid personally and how is reimbursement handled?
Do any agreements include a minimum term, lock-in period or early termination charge?
Please list the affected agreements, their term end dates and any stated exit conditions
Are any contracts subject to automatic price increases at renewal?
How are the increases described or capped, if at all?
How are renewal notice periods currently tracked?
Calendar reminders set well in advance
Tracked in a shared renewal schedule
Relied upon vendor reminder emails
Not systematically tracked
What would help you track notice periods more reliably?
How many days before a renewal date would you like decision-making to begin?
Have you experienced an unwanted or unexpected renewal charge in the past?
Please describe what happened and how it was resolved
Rate how effectively each area of the subscription portfolio is being used. These ratings help prioritize where deeper investigation or renegotiation is most valuable.
Please rate the following statements about subscription usage
Strongly disagree | Disagree | Neither agree nor disagree | Agree | Strongly agree | Not applicable | |
|---|---|---|---|---|---|---|
Active usage data is available for the tools we pay for | ||||||
Licence counts match the number of people actually using each tool | ||||||
Features included in our plan are being used fully | ||||||
We are not paying for overlapping tools that do similar things | ||||||
Usage reports are reviewed at least twice a year | ||||||
Value received is broadly proportionate to what we spend |
Overall, how would you describe the return on subscription spend this year?
Excellent value — clearly worth the cost
Good value — minor improvements possible
Fair value — several items look over-provisioned
Poor value — significant waste identified
Not yet known — usage data is unavailable
Are there subscriptions that are essential to operations and cannot reasonably be replaced?
Which subscriptions are considered business-critical and why?
Which signs of possible waste have you observed?
Licences assigned to people who have left or changed roles
Duplicate tools serving the same purpose
Plans or tiers above what is actually needed
Rarely or never used add-on modules
Free trials converted to paid plans without review
Shadow subscriptions purchased outside normal approval
Storage or capacity far above current needs
None of these observed
How were shadow subscriptions discovered and how are they being addressed?
Please describe the three subscriptions that deliver the most value and why
Please describe the three subscriptions that deliver the least value and why
Use this table to compare what is currently paid against a proposed or negotiated figure. The variance column calculates automatically so that potential savings or increases are visible at a glance.
Cost comparison and savings tracker
Product or cost line | Current annual cost | Proposed or negotiated annual cost | Variance (positive means saving) | Confidence in achieving this figure (percent) | Owner or responsible person | ||
|---|---|---|---|---|---|---|---|
A | B | C | D | E | F | ||
1 | Collaboration suite renewal | $3,000.00 | $2,700.00 | $300.00 | 75.0 | IT Operations | |
2 | Analytics platform downgrade | $1,800.00 | $1,200.00 | $600.00 | 50.0 | Marketing Lead | |
3 | $0.00 | ||||||
4 | $0.00 | ||||||
5 | $0.00 | ||||||
6 | $0.00 | ||||||
7 | $0.00 | ||||||
8 | $0.00 | ||||||
9 | $0.00 | ||||||
10 | $0.00 |
Total current annual subscription spend identified in this audit
Target annual subscription spend after planned changes
Estimated total annual savings identified
How is the subscription budget typically set?
Fixed annual budget agreed in advance
Rolling budget adjusted during the year
Approved case by case as needs arise
No defined budget
Other:
Are multi-year or bundled agreements being considered to reduce unit cost?
Which agreements are being considered and what trade-offs are acceptable?
Which cost-reduction approaches are you open to exploring?
Reducing licence counts to match real usage
Downgrading to a lower plan or tier
Consolidating overlapping tools into one platform
Negotiating renewal pricing or volume discounts
Moving to annual rather than monthly billing
Replacing paid tools with lower-cost or no-cost alternatives
Pausing or suspending subscriptions temporarily
None at this time
Budget available for new or replacement tools in the coming year
Renewal decisions often depend on the quality of the relationship with the provider as much as the product itself. Rate the following aspects of vendor performance.
Please rate your experience with key providers
Reliability and availability of the service | |
Responsiveness and quality of customer support | |
Clarity and accuracy of billing | |
Quality and frequency of product updates | |
Willingness to negotiate on price or terms | |
Transparency about changes to the service or terms |
Have you experienced significant service disruptions in the past year?
Please describe the disruptions and how the provider responded
Has the provider made material changes to pricing, features or terms during the current period?
What changed and how did it affect your team or budget?
How would you describe the overall relationship with your main providers?
Strong partnership with proactive account management
Professional and responsive when contacted
Adequate but impersonal
Difficult to reach or slow to respond
Varies widely between providers
Do you have a named account manager or support contact for the main agreements?
Please provide the contact name or reference
Any service issues, unresolved complaints or escalations to raise at renewal?
This section collects general observations about how subscription services handle data and access. It is not a legal or compliance assessment. Where specific obligations apply to your organization, consult the appropriate internal or external specialists.
Do the services in scope store or process data that your organization considers sensitive?
Which types of sensitive data are involved?
Personal contact details
Employee or HR information
Customer or client records
Financial or payment information
Health or wellbeing information
Confidential intellectual property or designs
Authentication credentials or secrets
None of these
Which security-related checks have been carried out for these services?
Review of the provider's published security information
Confirmation of where data is stored or processed
Review of data export and deletion capabilities
Multi-factor authentication enabled for administrator accounts
Single sign-on or centralized identity integration
Access reviewed and removed for departed users
Backup or recovery arrangements confirmed
None of these checks have been completed
Is it clear who owns the data entered into each service and how it can be exported?
Please note any services with unusual data ownership or export restrictions
Which services need clarification on data ownership or export?
Are administrator or owner accounts for these services held by people who are still with the organization?
Which services have orphaned administrator accounts and what recovery steps are planned?
How are user accounts deprovisioned when someone leaves or changes role?
Automated through a centralized identity or directory system
Manual checklist completed by a manager or IT contact
Handled reactively when a licence is needed elsewhere
No consistent process
Any security or data-handling concerns to raise with vendors before renewal?
Record the outcome of the audit for each major item and the actions that follow. Use the inventory table earlier for the full list and this section for decisions that need coordination or approval.
Renewal decision log
Product or agreement | Decision | Decision deadline | Estimated financial impact | Action owner | Action completed? | ||
|---|---|---|---|---|---|---|---|
A | B | C | D | E | F | ||
1 | Collaboration suite | Renew at negotiated rate | -$300.00 | IT Operations | |||
2 | Design tool licences | Reduce from 3 to 2 seats | $240.00 | Creative Lead | |||
3 | |||||||
4 | |||||||
5 | |||||||
6 | |||||||
7 | |||||||
8 | |||||||
9 | |||||||
10 |
Which actions will be taken as a result of this audit?
Cancel one or more subscriptions
Downgrade plans or reduce licence counts
Negotiate renewal pricing or terms
Consolidate overlapping tools
Introduce a formal renewal approval step
Improve usage reporting and monitoring
Assign a named owner to each subscription
Create or update a central subscription register
No changes required at this time
Which subscriptions are being cancelled and what is the migration or data export plan?
What negotiation approach will be used and by when?
Is a replacement or alternative tool being evaluated for any current subscription?
Which alternatives are being considered and what are the main selection criteria?
Risks or dependencies to consider before making changes
Target completion date for all agreed actions
Suggested date for the next subscription review
This section records who reviewed the audit findings and agreed the resulting actions. Signing indicates internal review and agreement on the plan described in this form; it does not create obligations toward any third party.
Who needs to review or approve the findings of this audit?
No further approval needed
A direct manager
A finance or procurement function
An IT or security function
An executive or leadership group
An external client or partner
Please name the external party who will review the findings
I confirm that the information provided in this form is accurate to the best of my knowledge
I understand that subscription changes may require notice periods and that timing should be checked with each provider
Name of the reviewer or approver
Role or title of the reviewer or approver
Date of review
Reviewer signature
Additional comments, conditions or follow-up notes from the reviewer
Anything else you would like to record about this audit?
Analysis for Annual Subscription & Software Renewal Audit Form
Important Note:
This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes.
AI-Generated Content: This template and its accompanying guidance are AI-generated to provide a practical starting point for your form-building needs. Please review and customise the content to ensure it is accurate, appropriate and suitable for your intended use.
This guide is provided for general informational and planning purposes only. It does not constitute professional, legal, financial, medical, employment, privacy, regulatory, or advice of any other kind, nor does it certify that this template is suitable or compliant for any particular jurisdiction or purpose.
Laws, regulations, industry practices and business requirements vary. You are responsible for reviewing and customising the template to suit your intended use and obtaining advice from appropriately qualified professionals where necessary.
Please delete this section before publishing your form. See our Terms of Service for further information.
The Annual Subscription & Software Renewal Audit Form is a well-structured, purpose-driven instrument that walks respondents from a high-level portfolio overview through detailed inventory, billing and contract terms, usage and value assessment, cost analysis, vendor performance, security and data-handling observations, renewal decisions and a formal sign-off. The logical progression mirrors how a real audit is typically performed: establish scope and ownership first, capture the facts, evaluate them, decide, and then document agreement. This sequencing reduces cognitive load and helps respondents build answers progressively rather than recalling everything at once.
One of the form's strongest design choices is the use of calculated columns inside the inventory and cost tables (for example, multiplying quantity by unit cost to derive an annual cost, and subtracting a proposed cost from a current cost to show variance). These automatic calculations reduce arithmetic errors, keep totals consistent and make savings visible at a glance. The inclusion of example rows in each table also lowers the barrier to entry by showing respondents exactly what level of detail is expected.
Another notable strength is the extensive use of conditional follow-ups (yes/no branches, single-choice follow-ups and multiple-choice follow-ups). Questions such as "Has a subscription audit been carried out in the past 12 months?" branch into a summary of previous findings or an explanation of what prevented an audit, so respondents only answer what is relevant to their situation. This keeps the form efficient while still capturing context where it matters.
"Audit reference or internal tracking code" gives each completed audit a unique identifier, which supports filing, cross-referencing and follow-up over multiple audit cycles. "Audit period covered" defines the reporting window so that figures collected elsewhere in the form can be interpreted consistently. The supporting start and completion dates are a practical addition for tracking how long an audit takes and for scheduling the next cycle. The introductory paragraphs set expectations clearly and include a helpful tip about marking non-applicable sections in the notes fields rather than leaving them blank — a small but effective way to distinguish "not answered" from "not relevant".
"Name of the person completing this audit" and "Email address for audit follow-up" establish accountability and a communication channel for clarifications after submission. "Which best describes the scope of this audit?" is a particularly useful segmentation question: it lets the reader understand whether the figures relate to one person, a small team, a department or a whole organization, and its follow-up captures the client name when a managed service provider is auditing on behalf of someone else. "Who is the primary budget holder for these subscriptions?" adds financial context that is often missing from subscription inventories and helps route decisions to the right person.
"Approximate number of active subscriptions or software licences in scope" and "Estimated total annual spend on subscriptions and software" provide a quick scale check before detailed rows are entered, making it easier to spot later inconsistencies. "How is the portfolio currently recorded?" surfaces the maturity of existing tracking practices, and its follow-up for organisations with no formal record captures how subscriptions are currently discovered — useful context for planning improvements. The yes/no question "Has a subscription audit been carried out in the past 12 months?" with tailored follow-ups creates a short institutional memory of prior findings or blockers. "Which categories of subscription are included in this audit?" uses a broad, inclusive category list with an "Other" option, which helps respondents map their portfolio without forcing it into unsuitable buckets. "How confident are you that the subscription list is complete?" is a self-assessment that helps readers judge how much weight to place on the figures.
The "Subscription and licence inventory" table is the operational core of the form. Its columns capture product name, vendor, category, billing frequency, quantity, unit cost, calculated annual cost, auto-renewal status, next renewal date and proposed action — the minimum set of facts needed to make an informed renewal decision. The instruction to duplicate rows when licence tiers differ is a thoughtful detail that prevents blended figures. "How many of the listed items are estimated to be unused or rarely used?" and "Estimated annual value of unused or rarely used items" translate the inventory into a tangible waste estimate, which is often the most persuasive output of an audit.
This section addresses the practical realities that often cause surprise costs. "Which payment methods are used across the portfolio?" highlights fragmented billing, while "Are any subscriptions paid on a personal card and reimbursed?" captures arrangements that can fall outside normal records. The questions on minimum terms and early termination charges, automatic price increases at renewal and renewal notice period tracking collectively map the contractual constraints that shape decision timing. "How many days before a renewal date would you like decision-making to begin?" is a forward-looking question that converts the audit into a planning cadence, and "Have you experienced an unwanted or unexpected renewal charge in the past?" captures lessons learned that can inform future controls.
The matrix rating on subscription usage is an efficient way to gather comparable perceptions across several dimensions — usage data availability, licence-to-user alignment, feature utilisation, tool overlap, review cadence and value proportionality — using a consistent scale that includes a "Not applicable" option. "Overall, how would you describe the return on subscription spend this year?" summarises the respondent's overall impression in a single choice. The follow-ups on business-critical subscriptions, observed signs of waste and the two open-ended prompts for the most and least valuable subscriptions add qualitative colour that numeric tables alone cannot provide.
The "Cost comparison and savings tracker" table pairs a current annual cost with a proposed or negotiated figure, calculates the variance automatically and adds a confidence percentage and an owner per line — a practical way to separate realistic savings from aspirational ones. The summary fields for total current spend, target spend and estimated savings give leadership a concise headline. Questions on how the budget is set, multi-year or bundled agreements and acceptable cost-reduction approaches help align the audit's recommendations with the organisation's actual commercial flexibility.
The matrix star rating for provider experience covers reliability, support quality, billing clarity, update quality, negotiation willingness and transparency — dimensions that commonly influence renewal decisions. The yes/no prompts on service disruptions and material changes to pricing, features or terms capture evidence that can be raised during renegotiation. "Do you have a named account manager or support contact for the main agreements?" and the open field for unresolved issues or escalations ensure that relationship context travels with the renewal decision.
The introductory paragraph appropriately frames this section as general observation rather than a compliance assessment, which is a responsible design choice. Questions on sensitive data types, security checks completed, data ownership and export clarity, administrator account ownership and user deprovisioning practices surface practical risks that often surface only at contract end. The final open field for security or data-handling concerns to raise with vendors before renewal turns observations into actionable negotiation points.
The "Renewal decision log" table converts analysis into accountability by recording the decision, deadline, estimated financial impact, owner and a completion checkbox. "Which actions will be taken as a result of this audit?" is a strong closing question because it forces a concrete outcome, and its follow-ups for cancellations and negotiations capture migration plans and timing. The prompts on replacement tools being evaluated, risks or dependencies and target completion and next review dates help the audit produce a forward schedule rather than a static report.
The sign-off section documents internal review and agreement on the plan. "Who needs to review or approve the findings of this audit?" routes the output to the right audience, while the confirmation checkboxes on accuracy of information and notice period awareness reinforce respondent diligence. "Name of the reviewer or approver" provides a clear accountability trail, supported by role, date, signature and free-text fields for conditions or follow-up notes.
From a data-quality perspective, the form collects a balanced mix of structured fields (dates, numbers, currency, single and multiple choice) and open narrative fields. The structured fields support aggregation and comparison across audit cycles, while the narrative fields capture nuance such as negotiation context, migration risks and vendor behaviour. Because the form gathers contact details, cost figures and descriptions of internal systems, it is sensible for the form owner to communicate internally how responses will be stored, who can access them and how long they will be retained, in line with their own data-handling practices.
From a usability standpoint, the form is long but well-signposted: clear sub-headings, introductory paragraphs per section, placeholder examples and a tip about non-applicable sections all reduce ambiguity. Potential friction points include the overall length for respondents with very small portfolios, the effort required to complete both detailed tables, and the number of open-ended narrative prompts which may feel demanding for time-constrained respondents. Mitigations could include allowing respondents to mark sections as not applicable (already suggested in the instructions), pre-filling known figures where possible, and emphasising that approximate figures are acceptable where exact data is unavailable. Overall, the form is thorough, logically sequenced and well-suited to producing an actionable renewal plan, with its calculated tables and conditional follow-ups standing out as particularly effective design choices.
Mandatory Question Analysis for Annual Subscription & Software Renewal Audit Form
Important Note:
This section explains why certain fields in this form are marked as required and provides general guidance on how these requirements may support the collection of complete, accurate and relevant information.
Required fields and information-collection obligations may vary depending on your industry, jurisdiction, business operations and intended use of the form. A field marked as required in this template does not necessarily mean that collecting the information is legally mandatory.
Please review each required field to determine whether it is necessary, appropriate and lawful for your particular purpose. Consider applicable privacy, data protection, consent and industry-specific requirements, and consult an appropriately qualified legal, privacy or compliance professional where necessary.
Please delete this section before publishing your form. See our Terms of Service for further information.
Question: Audit reference or internal tracking code
Recommendation: Requiring a reference or tracking code supports consistent record-keeping and makes it straightforward to file, retrieve and cross-reference this audit with related documents in future cycles. It is especially useful where multiple audits are run across different teams or periods. The necessity of this field depends on how the form owner intends to store and retrieve submissions; smaller or informal audits may find an optional reference sufficient.
Question: Audit period covered
Recommendation: Requiring the audit period helps ensure that all figures, dates and decisions recorded elsewhere in the form can be interpreted against a clearly defined timeframe. Without it, cost and usage data collected in later sections may be ambiguous when compared across cycles. This field is most valuable when audits are repeated regularly or when figures are drawn from different billing periods.
Question: Name of the person completing this audit
Recommendation: Requiring the respondent's name supports accountability and gives reviewers a clear point of contact for clarifications after submission. It also helps distinguish between audits completed by different individuals within the same organisation. Whether a full name or a display name is appropriate depends on the form owner's internal record-keeping conventions.
Question: Email address for audit follow-up
Recommendation: Marking the follow-up email as mandatory provides a reliable channel for raising questions about the submitted information and for coordinating the actions recorded in the decision log. It supports operational continuity after the form is submitted. Form owners should consider how contact details will be stored and accessed, and communicate this internally in line with their own data-handling practices.
Question: Which best describes the scope of this audit?
Recommendation: Requiring the audit scope helps readers interpret the portfolio figures correctly, since a subscription count for a single user means something very different from one covering a whole organisation. It also enables the conditional follow-up that captures the client name when the audit is performed on behalf of someone else. This field is particularly useful where results are shared with stakeholders who were not involved in completing the form.
Question: Approximate number of active subscriptions or software licences in scope
Recommendation: Requiring an approximate count provides an early scale indicator that helps reviewers sanity-check the detailed inventory entered later. It can highlight gaps where the number of listed rows appears inconsistent with the stated total. Because the field asks for an approximation, it should not create significant burden for respondents, though the form owner may wish to confirm whether estimates are acceptable for their intended use.
Question: Estimated total annual spend on subscriptions and software
Recommendation: Requiring an estimated annual spend establishes a headline figure that the cost analysis section can be measured against and helps prioritise where deeper investigation is most worthwhile. It supports budget conversations and gives the audit a clear financial baseline. The necessity of this field depends on whether the form owner intends to use the output for financial planning; for purely informational audits it could reasonably be optional.
Question: How is the portfolio currently recorded?
Recommendation: Requiring this response helps the form owner understand the maturity of existing tracking practices and interpret the reliability of the figures supplied elsewhere. The conditional follow-up captures how subscriptions are discovered where no formal record exists, which is useful context for planning improvements. This field is most valuable when the audit output will inform changes to record-keeping processes.
Question: Which categories of subscription are included in this audit?
Recommendation: Requiring the category selection defines the boundaries of the audit so that readers understand what is and is not covered by the figures. The broad category list with an "Other" option reduces the risk of relevant subscriptions being excluded. This field supports completeness of the inventory and helps identify areas where follow-up may be needed.
Question: Overall, how would you describe the return on subscription spend this year?
Recommendation: Requiring an overall value assessment gives the audit a clear qualitative summary that complements the numeric tables and helps prioritise which items need deeper review. It captures the respondent's considered judgement in a single structured response. The necessity of this field depends on how the form owner intends to use the output; where the audit is purely informational, it could reasonably be left optional.
Question: Which actions will be taken as a result of this audit?
Recommendation: Requiring a selection of follow-up actions helps ensure the audit produces a concrete outcome rather than a static report, and the conditional follow-ups capture migration plans and negotiation timing where relevant. It supports coordination by making intended next steps explicit. This field is particularly valuable where the audit output will be reviewed by others or tracked over time.
Question: Name of the reviewer or approver
Recommendation: Requiring the reviewer's name creates a clear accountability trail and confirms that the findings have been examined by someone other than the person who completed the form. It supports internal record-keeping and follow-up on agreed actions. Whether a formal sign-off step is needed at all depends on the form owner's internal review practices; for informal audits this field could reasonably be optional.
The form currently marks twelve fields as mandatory, spread across the opening identification section, the portfolio overview, the value assessment, the action plan and the sign-off. This distribution is generally sensible: required fields are concentrated where they establish scope, ownership and outcomes, while the many descriptive and narrative prompts remain optional. That said, the number of required fields in the middle sections — particularly the portfolio overview, where four fields are mandatory — may add friction for respondents with very small portfolios or limited data. Consider whether all four are essential for every respondent, or whether some could be relaxed once the audit reference and scope are captured.
Overall, the mandatory field selection is proportionate and aligned with the form's purpose of producing an actionable renewal plan. Organisations using the form at different scales should adjust required fields to match their own review processes and user feedback.
To configure an element, select it on the form.