Content Plans in Assette enable investment management firms to automate and control the generation and delivery of client and sales content. Whether it’s a monthly client report, a quarterly factsheet, or a daily flash update, Content Plans determine when, for whom, and under what conditions content is delivered. While closely linked and related, Content Plans should not be confused with Content Types.
This article introduces the fundamental concepts behind Content Plans and how they support scalable, compliant communication. For a technical overview of Content Plans, please see Content Plan Data Model.
What Is a Content Plan? #
A Content Plan is a configuration in Assette that connects the dots between:
- The content being generated (via a Content Type),
- The audience (organization, account, or recipient),
- The timing and conditions for generation,
- And the delivery method (e.g., Email, Portal, FTP).
Content Plans are the operational layer that brings together business rules and data-driven automation for client reporting and communication.
Why Content Plans Matter #
Content Plans enable firms to:
- Automate scheduled and event-based content generation
- Ensure consistency across recipients and time periods
- Support compliance by enforcing approval workflows
- Scale operations by handling hundreds or thousands of content deliveries without manual intervention
By abstracting business logic into a reusable configuration, Content Plans make it easier to deliver the right content to the right audience at the right time.
Key Concepts #
1. Audience Targeting #
Each Content Plan is associated with either:
- A specific recipient, or
- An entire organization (e.g., all clients under a firm)
This makes it possible to tailor delivery based on client-specific preferences or organizational policies.
2. Scheduling and Frequency #
Content Plans define when content should be generated. This can be:
- On a fixed schedule (e.g., the second business day of each month)
- Based on data availability
- Or manually triggered
Frequencies can be daily, weekly, monthly, quarterly, or yearly, depending on business needs.
3. Data Periods and Effective Dates #
Each plan specifies:
- The period the data should cover (e.g., 6 Months)
- The as-of date used to extract and represent the data (e.g., 2025-03-31)
4. Generation Triggers #
Assette supports multiple triggering mechanisms:
- Time-based: Generate on a specific date/time.
- Event-based: Generate when underlying data is ready.
- Manual: Triggered by a user.
This flexibility supports diverse operational models.
5. Delivery Settings #
Defines how and in what format content is delivered:
- Methods: Email, Client Portal, API, FTP, or Postal Mail
- Formats: PDF, Native (PPTX, Word, etc.), or linked via Assette Viewer
- Protections: Passwords or zipped attachments
Common Use Cases #
| Use Case | Example |
|---|---|
| Monthly Client Reports | Sent on the 2nd business day each month to institutional clients |
| Quarterly Factsheets | Generated when performance data is finalized |
| Daily Dashboards | Sent automatically every morning at 7:00 AM |
| Sales Enablement | Custom sales reports generated for prospecting |