Introduction

Partner Renewal Workspace (PrW) is StrataVAR’s renewal management solution that provides a unified platform to handle complex, multi-vendor contract renewals efficiently. It connects siloed systems, offers visual insights, and enables seamless collaboration between Renewal Managers and Engineers.

In this article, we focus on a core concept that shapes how renewals are viewed and processed across related customers—Account Family. Account Family determines which related customer accounts are grouped together for renewal planning, Asset Lists, Pricing Requests, and Renewal Projects.

By the end of this article, you will understand:

• What an Account Family is and why it exists in PrW.
• How Account Family influences what Renewal Managers and Renewal Engineers see in dashboards and consoles.
• How Account Family affects Asset Lists, Pricing Requests, and Renewal Projects.
• When it makes sense to use Account Family in your renewal workflows.

Next step: How to identify and prioritize renewals using PrW Dashboard

Key Terms

Table of Contents

1. What is an Account Family

In many real-world customer scenarios, “one customer” is represented by multiple Accounts—for example:

• A global parent account with several regional child accounts.
• Separate legal entities that always negotiate renewals together.
• Sites or branches that are administered centrally.

Account Family is how PrW groups related Accounts into a single logical customer group for renewal planning and execution.

At a high level:

• Each Account can belong to a broader Account Family, defined by the relationships in your CRM (for example, parent/child structure).
• When you select an Account as your working context, PrW can optionally include data from other Accounts in the same family, depending on the screen and configuration.

2. How Account Family Impacts What You See

Account Family influences the scope of data visible in consoles for both Renewal Managers and Renewal Engineers.

Account Context vs. Account Family

When you open a console or dashboard in PrW, you typically start by selecting an Account or by filtering on accounts. Once that context is chosen:

• Some views show only data for the selected Account.
• Other views are designed to show data for the selected Account plus Accounts in the same Account Family (for example, contracts across child accounts).

This behavior is intentional and depends on how that specific console is designed.

Examples in the Renewal Journey

• On a Renewal Manager Assign Contracts/Subscription to Project console, Account Family lets you view all upcoming renewals for a customer group, not just one account at a time.
• On a Renewal Engineer console, Account Family can allow you to pick and process contracts that span multiple related Accounts in one workflow.

You will usually see the originating Account on each item (for example, as a column), so you can distinguish where that contract or subscription “lives” while still viewing it as part of the same grouped customer.

3. Account Family in Asset Lists

Asset Lists are often the first structured deliverable Renewal Engineers prepare for customer validation. Account Family affects Asset Lists in two key ways:

Item Selection

When Account Family is supported, you can select contracts and subscriptions from:

• The current Account, and
• Other Accounts in the same Account Family.

This allows you to build one Asset List that represents the full scope of renewals for a customer group.

Header Ownership

• Even if items come from multiple Accounts, the Asset List header is tied to a single owning Account.
• This Account typically represents the primary entity for reporting and communication (for example, the parent account or main operating entity).

From the customer’s perspective, the Asset List shows all relevant assets and subscriptions for their group; from an operational perspective, PrW still maintains precise Account-level attribution at the line item level.

4. Account Family in Pricing Requests

Pricing Requests are often generated from Asset Lists and can inherit Account Family behavior.

A Pricing Request is always owned by one Account in its header. Items included in the request can originate from multiple Accounts within the same Account Family.

This provides several advantages:

• Vendors receive a single, consolidated request for all sites or entities that renew together.
• Internal teams manage one Pricing Request instead of many parallel requests, reducing risk of misalignment.
• Reporting still recognizes which underlying Account each priced item belongs to.

5. Account Family in Renewal Projects

Renewal Projects are the primary work containers for tracking renewal execution. Account Family influences how you populate these projects, while still maintaining clear ownership.

Project Ownership

• A Renewal Project header always belongs to one specific Account.
• When you create or assign items to a project, you select the owning Account as part of the process.

Including Items from the Account Family

Where supported:

• You can select Internal Contracts or subscriptions from multiple Accounts within the same Account Family.
• All selected items can be added to a single Renewal Project, even though they come from different underlying Accounts.

However, when you search for or select a Renewal Project:

• You see only projects belonging to the currently selected Account, not all projects across the entire family.
• This ensures that ownership and reporting remain clear and that users don’t inadvertently mix unrelated projects.

6. When to Use Account Family

Account Family is most useful when:

• A customer has multiple branches, regions, or legal entities, but renewal decisions are made centrally.
• You want to conduct a single renewal review meeting that covers all contracts for the customer group.
• Vendors expect one consolidated Pricing Request, rather than separate requests for each underlying Account.
• Your internal teams want a unified view of renewal risk and opportunity across a customer group.

You might use Account Family more cautiously when:

• Each Account negotiates renewals independently, with separate budget, approvals, or decision makers.
• Legal, financial, or reporting requirements demand a strict separation of contracts by individual Account.
• The customer explicitly prefers separate documentation per entity and sees them as independent.

In those cases, you can still use PrW effectively while focusing on individual Accounts rather than the broader family.

7. Common Questions and Troubleshooting

“Why do I see items from multiple Accounts in one list?”

If a console or selection screen is configured to respect Account Family, selecting one Account as context can automatically show items from that Account and its related Accounts.

This is expected and designed to support group-wide renewals. You can use columns and filters to see which Account each item originates from.

“Why does my Asset List / Pricing Request / Renewal Project show only one Account in the header?”

Every header record (Asset List, Pricing Request, Renewal Project) is owned by a single Account. This Account is used for reporting, routing, and integration with other systems.

Items inside the record maintain their link to their original Account, so analysis and reporting can still be performed at the individual Account level.

“I can’t find the Renewal Project I expect to see.”

Check which Account you have selected in the console. Only Renewal Projects owned by the current Account are displayed. 

If the project was created under a related Account in the same Account Family, switch the context to that Account and search again.

“Our customer is confused about which Account appears on the document.”

You can explain that:

• The Account in the header is the administrative owner (for example, head office or main entity).
• The content may include assets and subscriptions from related branches, sites, or subsidiaries.

This structure simplifies communication and ensures that renewals are managed consistently across their organization.

8. Summary

Account Family is a foundational concept in Partner Renewal Workspace that allows you to manage renewals the way customers actually operate—across related entities, not just one account at a time. By grouping related Accounts into an Account Family:

Renewal Managers can see and prioritize work for the entire customer group.

Renewal Engineers can build Asset Lists, Pricing Requests, and Renewal Projects that include items from multiple related Accounts while maintaining clear ownership and reporting.

Understanding Account Family will help you interpret what you see in dashboards and consoles, make better renewal decisions, and organize work around how your customers buy and renew.

Related Learning

• End-to-End Workflow in PrW
• How to identify and prioritize renewals using PrW Dashboard