-
Replicate the Today() Function in Anaplan
Author: Robin Drinkall is a Certified Master Anaplanner with 9 years' experience in the finance industry.
Today() is an extremely useful function within spreadsheet / database applications that will return the current system date. This function is used very commonly seen and used extensively with general functions including switching from actuals > forecast, triggering conditional formatting and triggering events based on inputted dates. This function is not currently available as a formula within Anaplan, but there is a workaround that can be used to achieve the same result.
To set this up, you will require:
* Workspace administrator rights in each model you set this up in.
* CloudWorks access, and an integration user able to run the process.
The best way to achieve this is as follows:
* Create a non-production list in the system section called ‘Today’ — I usually use the ‘Organization’ list because it cannot be deleted and appears cleaner when not in use.
* Create a system module with two dated formatted line items, ‘Today’ and ‘Today + 1’. Today is an input with no formula and Today +1 has the formula Today + 1. Note when setting this up for the first time, you will need to manually enter today’s date into the Today input line item.
* Create a saved view within the system module using rows and columns rather than context.
* Create an import action from the saved view created in 3 into the today system module, mapping the system list to itself and then column headers for the line items. Within the Line items mapping, manually map Today + 1 into the Today line item.
* Create a process named ‘Today’ and add this action to the process. This can be manually triggered on a dashboard but realistically you might as well manually type in the date if you were going down that route – the better solution is to set up the process within Cloudworks.
* Navigate to Cloudworks using the drop-down menu top left of the screen, then head to ‘Integrations & Processes’, then ‘New Integration’, then Process.
* Give the process a name e.g. Data Hub Today, select the relevant workspace, model and the process created in step 5.
* Search for the new integration and on the sidebar select ‘Schedule’ then ‘Create Schedule. Select for the integration to run daily at 00:00 on your desired timezone:
* The following day, test that the date has correctly imported from Today +1 into Today/.
Things to note
* One of the best use cases for the today functionality is to track when a user (or the system) last uploaded a file. This can be achieved by importing the date into a table containing a line item for each data file and displaying this on a data management dashboard.
* Because the import window is 15 minutes, there’s a chance that a file upload could be holding the previous day’s date until 00:15. Ensure any overnight data loads that use the date are scheduled afterwards, or the action is put within the data load process itself.
* Note that this will need to be repeated in Cloudworks for each model and if using ALM it would need to be repeated for DEV / TEST / PROD within each model.* You could theoretically do this process within the data hub and then create a processes to import the date within each spoke model (and schedule in Cloudworks using the same method) to avoid having to repeat the Today SYS module in each model.
* This process will not self correct — if the wrong date is entered initially or if a scheduled run fails then the incorrect date will carry forward. This should be occasionally checked to see that everything is flowing as expected.
* If a model is used by users across different timezones, ensure there is agreement as to when the ‘master’ timezone is to avoid confusion.
Questions? Leave a comment!
-
How I Built It: Circular references
Author: Andrew Tye is a Certified Master Anaplanner and Technical Lead at Aviva.
In this 'How I Built It' video I go through the steps I followed to resolve a circular reference issue in a time series cash-flow module using LAG and strict.
Often in modeling you're trying to achieve something that is easy to achieve within Excel and a workaround is needed to get the same end result within Anaplan but that can be easily explained.
One key takeaway when trying to resolve a circular reference is to remove the onward calculation links and only reintroduce once you believe the issue has been resolved to prevent the dreaded toaster time, which even in a DEV model can be quite time consuming.
Check it out and leave a comment with questions!
https://play.vidyard.com/gUT8tWTs6jYVW5PHdoFGne
-
How I Built It: Building a dynamic calendar in Anaplan
Author: Jason Zhang is a Certified Master Anaplanner and a Manager at PwC.
Have you ever wanted to visualize upcoming events and milestones directly in Anaplan? While Anaplan provides powerful planning and modeling capabilities, it does not offer a native calendar view for displaying events in a traditional calendar format.
In this ‘How I Built It’ demonstration, I walk through how to create a dynamic calendar in Anaplan, allowing users to visualize upcoming events and milestones in a more intuitive and user-friendly way.
The challenge
When managing projects, planning activities, or tracking important milestones, users often need a clear view of what is coming up and when. Without a calendar-style interface, it can be challenging to visualize events chronologically and quickly understand the timing of upcoming activities.
The solution
I developed a dynamic calendar in Anaplan to provide users with a visual representation of upcoming events and milestones. The solution demonstrates how Anaplan's existing modeling and UX capabilities can be leveraged to create a calendar-style experience, helping users navigate dates and understand scheduled activities more intuitively.
Benefits
* Improved visibility: View upcoming events and milestones in a familiar calendar format.
* Enhanced user experience: Make it easier for users to understand the timing of activities.
* Flexible design: Demonstrate how Anaplan can be customized to support user requirements beyond its out-of-the-box functionality.
Check it out and leave a comment with questions!
https://play.vidyard.com/8VCa9hwqWxViqL7seYbtsD
-
Constraining demand in the Anaplan Inventory Planning Application: Part II
Author: James Synder is a Certified Master Anaplanner and Associate Director at Accenture.
Bridging the gap
Where we left off
In Part I of this series, we explored three gaps that emerge when inventory constraints are not fully represented in the Anaplan Inventory Planning application: (1) the customer-facing shortage can be hidden, (2) external capacity is not automatically a planning constraint, and (3) demand and inventory may live at different levels. This article examines strategies that have been deployed in practice to close each of those gaps.
Before diving in, two important caveats apply. First, one of the approaches described below is not feasible in a Polaris workspace and requires a Classic workspace; this distinction is explained where relevant. Second, for scenarios where weekly forecasting and external processes are operationally practical, the out-of-the-box application can partially address some of these gaps without custom development. That option is covered as well.
We will move from the most straightforward approach to the most complex.
1️⃣ Allocating inventory to customer-facing locations
Recall the first gap: a customer-facing distribution center assumes it can receive inventory from an upstream DC, but if that upstream DC is constrained, the shortage appears there rather than at the customer-facing location. The customer-facing DC continues to plan against expected receipts that may not materialize.
To resolve this, allocation logic can be applied across the multi-tier structure, drawing on the same framework that IVP200 uses to roll up inventory need across tiers out of the box. Using the native Tier 1 version as the starting point, a custom allocation layer is built to distribute available inventory based on documented need.
The recommended allocation priority order is:
* Planned transfers: deliberate, system-configured movements that should be honored first.
* Simulated network replenishment: the rolled-up need from customer-facing DCs.
* Customer demand: direct demand to be satisfied from the DC's remaining available inventory.
For each allocation tier, the logic determines whether a shortage exists and distributes what is available proportionally. Because this is a planning projection, a simple pro-rata reduction is recommended for clarity and consistency. For example: if 1,000 units are needed across three planned transfers and only 800 units are available, each transfer receives 80% of its request. Which transfers are fulfilled completely versus partially is an execution decision that will be resolved when the actual movement occurs.
The key technical mechanism is the PREVIOUSVERSION() formula. As documented in Anaplan's formula reference, PREVIOUSVERSION() returns the value of an expression from the version that precedes the current one in the model's version ordering. In the context of the supply chain application, versions are used structurally, not as planning scenarios, to sequence calculation passes without creating circular references.
The practical application works as follows: allocation outputs calculated in the "Tier 1" version are staged there. The "Tier 1 & 2" version then uses PREVIOUSVERSION() to pull those values and incorporate the allocated inventory as receipts at the receiving DC, mirroring how IVP200 handles the network replenishment roll-up natively. A DC receiving an allocated transfer in the Tier 1 & 2 pass treats that quantity as available inventory when calculating its own downstream obligations.
Mastering this pattern, stage in Tier 1 and retrieve via PREVIOUSVERSION() in Tier 1 & 2, is foundational. It underpins the allocation logic across all three gap scenarios discussed in this article.
2️⃣ Applying constraints with the out-of-the-box configuration
Before building custom allocation logic, it is worth considering whether the standard application configuration can address the second gap: unconstrained capacity from a central purchasing authority or contract manufacturer.
The Inventory Planning application calculates suggested receipts based on inventory policy and lead time parameters, treating future supply as unconstrained. However, the application can be configured in a scenario where suggested receipts are suppressed, limiting the inventory flow calculation to what is actually on order in the transactional system. When coupled with a weekly forecasting and ordering cadence, where supply transactions are refreshed weekly, this approach gives planners a near-real-time view of constrained inventory position in the short term.
The trade-off is visibility beyond the ordering horizon. Once the horizon is exceeded, shortages will accumulate because the model is no longer projecting future receipts. This approach works well for near-term constraint visibility, but planners should be aware that it does not provide a full long-range supply picture. Applied appropriately, this configuration is a practical mitigation for Gap 2, particularly for organizations with the operational discipline to maintain weekly order placement.
3️⃣ Allocating constrained supply from a central authority or contract manufacturer
When the out-of-the-box configuration is not sufficient, for example when a central purchasing team or contract manufacturer is allocating finite supply across multiple international regions, a more structured allocation model is required.
In one client engagement, multiple regional entities were competing for supply from a limited set of contract manufacturers. The standard Rough-Cut Capacity Planning (RCCP) and Production Planning applications were not a good operational fit given how the business managed its central buying process. Instead, demand was aggregated from region-level SKUs up to a global SKU level to assess total need against manufacturer capacity. The central authority then reviewed the aggregate need and returned an allocation of available supply back to each region.
Because the central review process operated on a monthly cadence, the model needed to project where inventory was likely to land in each region after the allocation was applied. The allocation output was then fed back into the regional inventory model using the same tier-based approach described in the first section. The returned allocation was treated as a constrained receipt and processed through the Tier 1 / Tier 1 & 2 version structure.
4️⃣ Allocating demand to the level of inventory: A note on Polaris vs. Classic
The most complex gap involves a mismatch between the level at which demand is planned and the level at which inventory is held. In the engagement described here, sales were planned at an aggregate main SKU level, while inventory existed at a more granular variant SKU level. This created two distinct challenges: determining which variant SKU to replenish, and simulating the depletion of variant-level inventory in age order.
The complexity was compounded by the need to account for inventory transfers and routine network replenishment simultaneously. The solution was approached in order:
* Calculate simulated receipts, routine network replenishment, and planned transfers at the main SKU level.
* Establish rules for which variant SKU would be replenished (in full or split across variants).
However, allocating across several variant SKUs proved to be a barrier in a Polaris workspace. While Polaris uses the same formula syntax and modeling interface as the Classic Engine, certain calculation patterns behave differently. Specifically, Polaris has limitations with non-winding iterative calculations; the sequential, pass-by-pass depletion logic required for variant-level allocation could not be resolved within the Polaris engine despite multiple implementation attempts.
The decision was made to stand up a dedicated allocation model in a Classic workspace. Data and lists were synchronized to the Classic model, where concatenated lists and allocation rules were built to manage inventory across transfers, network replenishment, and customer demand. The inventory aging and depletion order logic for variant SKUs was also housed in the Classic model.
The allocation logic in the Classic model relied on three sequential passes using the RANKCUMULATE function to deplete inventory in priority order. Each pass followed the allocation sequence used throughout this series: (1) Planned Network Transfers, (2) Routine Network Replenishment, and (3) Customer Demand.
The Tier 1 / Tier 1 & 2 version structure was applied here as well. Tier 1 handled the allocation of variant SKUs for inventory transfers, both planned and routine network replenishment. The Tier 1 & 2 version then received those values and treated the allocated transfer quantity as available inventory for downstream obligation calculations. Only customer demand at the DC level would surface any shortage; the allocation logic ensured that upstream transfers were withheld when inventory was unavailable, and the shortage was recorded at the DC supporting the end customer.
In closing
The four approaches described in this article, multi-tier allocation at customer-facing DCs, out-of-the-box constrained receipt configuration, central authority allocation, and variant-level depletion modeling, demonstrate that the gaps identified in Part I are addressable through deliberate design. None of these solutions requires replacing the core inventory planning logic. Each extends it in a targeted way to represent the constraints that the standard application does not automatically capture.
Two principles carry through every approach. First, the Tier 1 / Tier 1 & 2 version structure, combined with the PREVIOUSVERSION() formula, is the foundational pattern for sequencing multi-pass calculations without circular references. Second, implementation decisions about engine selection (Polaris versus Classic) matter: some allocation patterns that are natural to implement in Classic require architectural workarounds or separate models in Polaris.
This is not an exhaustive list of strategies. Supply chain networks vary widely, and the right design will depend on the specific constraints, planning cadences, and data structures of each organization. But the patterns here offer a starting point and a demonstration that visible, actionable constraint planning is achievable within the Anaplan platform.
In supply chain planning, the most dangerous constraint is not the one you can see. It is the one your planning system does not know exists, until you build the model that makes it visible.
-
Constraining demand in the Anaplan Inventory Planning Application: Part I
Author: James Synder is a Certified Master Anaplanner and Associate Director at Accenture.
Where is the gap?
A strong foundation and a familiar planning challenge
One of the most rewarding aspects of implementing the Anaplan Supply Chain Applications is seeing how quickly an organization can connect demand, inventory, and supply planning. The application suite provides a pre-built foundation for demand analysis, demand planning, inventory planning, rough-cut capacity planning, and production planning. Rather than beginning with a blank model, implementation teams configure the applications, test them against business requirements, and identify extensions through fit-gap analysis.
That acceleration does not eliminate the complexity of the real supply chain. In several client situations, replenishment recommendations were mathematically consistent with the information in the model, but critical operating constraints were managed elsewhere. Contract-manufacturer capacity, upstream inventory shortages, or SKU-transition rules were known to planners, yet not fully represented in the standard planning flow.
This distinction matters: the issue is not necessarily that the planning logic is wrong. The issue is that a feasible plan requires visibility to every material constraint. When a constraint is absent, the plan may look achievable in the model while remaining difficult to execute operationally and support anticipated demand.
How the standard planning flow works
The process begins with demand. Demand is forecast by product and customer(or demand-generating entity). Inventory Planning maps those demand-generating entities to the locations that supply them, such as distribution centers. The application then projects inventory and applies policy settings to determine target inventory and replenishment need.
Those policies can incorporate product segmentation, including ABC-XYZ classifications, together with planning parameters such as order frequency, lead time, minimum order quantity, and order multiples. Based on projected need, the application produces suggested orders intended to maintain the target inventory position.
The planning flow becomes more sophisticated in a multi-tier network. A customer-facing distribution center may be replenished by an upstream distribution center rather than directly by a vendor or manufacturer. In that configuration, the downstream inventory requirement is passed upstream so the supplying node can incorporate network demand into its own replenishment calculation.
The elegance of multi-tier replenishment
Multi-tier inventory planning introduces a classic dependency: the downstream location needs a planned receipt from the upstream location, while the upstream location needs the downstream requirement to calculate how much inventory it must procure. The Inventory Planning design addresses this through successive calculation passes.
In the IVP200 inventory forecasting module, the Tier 1 calculation determines inventory need at each node. Where a distribution center is resupplied by another distribution center, that need is shifted to the supplying location using the associated lead time. The Tier 1 & 2 calculation then incorporates the passed requirement, while the receiving location recognizes the expected inbound quantity as Planned Receipts from Network Replenishment.
This is a powerful design pattern. It allows the downstream need to be fed back into the network calculation without creating a circular reference, and it gives the upstream purchasing or manufacturing node visibility to the inventory it must source for the broader network.
Where the gaps begin to appear
1️⃣ The customer-facing shortage can be hidden.
A downstream distribution center may assume that inventory will arrive from its supplying distribution center within the configured transfer lead time. The shortage, however, is calculated at the upstream supplying node. If upstream inventory is insufficient, the receiving location can still reflect the planned network receipt even though the transfer may not be fully achievable.
The practical blind spot is customer impact. The network recognizes a shortage at the supplying location, but the model may not directly express that shortage as constrained sales at the customer-facing location. Planners therefore need a way to trace upstream scarcity back to the demand it may prevent the network from serving.
2️⃣ External capacity is not automatically a planning constraint.
Many organizations manage capacity with contract manufacturers, co-packers, plants, or central purchasing teams. Those groups may allocate a finite quantity across products, locations, or periods. If that capacity is not represented in the Inventory Planning process, the replenishment algorithm can recommend supply based on need without knowing whether the manufacturer or plant can produce the required volume.
This creates a gap between unconstrained replenishment need and executable supply. The requirement is visible, but the scarce capacity must still be allocated deliberately.
3️⃣ Demand and inventory may live at different levels.
A third challenge occurs during SKU transitions. A business may forecast demand at an aggregate SKU or product level while holding inventory at a more detailed variant level. Older variants may need to be depleted before the organization procures the replacement variant.
In that situation, aggregate demand must be allocated across eligible variants according to lifecycle rules. Standard inventory policy parameters determine when and how much to replenish, but they do not, by themselves, define which version of a product should satisfy demand first or when procurement should shift to the new variant.
A fit-gap opportunity, not a failure of the application
These scenarios should not be interpreted as evidence that the Supply Chain Applications are ineffective. They illustrate why application implementations still require business discovery, configuration, fit-gap analysis, extension design, and regression testing. The standard application provides the planning engine and connected data flow. The implementation must then represent the constraints that are distinctive to the company, industry, and operating model.
Framing the issue this way also protects the value of the standard application. The objective is not to replace the core replenishment logic with custom development. It is to add targeted extensions that expose constraints, allocate scarce supply, or translate shortages to the level at which planners make decisions.
What comes next
Each of these gaps can be addressed through thoughtful Anaplan design patterns. Part 2 explores approaches for translating upstream shortages to customer-facing demand, constraining replenishment with manufacturer or plant capacity, and managing allocation across SKU variants during a product transition.
Because in supply chain planning, the most dangerous constraint is not the one you can see. It is the one your planning system does not know exists.
-
Leveraging Anaplan Workflow and ADO for controlled financial sign-off reporting
Author: Dinesh Gupta is a Certified Master Anaplanner and Lead of the Anaplan CoE at PTSB Ireland.
Financial planning models are constantly evolving throughout forecast and budget cycles. New requirements, model enhancements and business changes are essential to support better decision making. However, these ongoing developments can create a challenge when approved numbers used for management reporting remain directly linked to live planning calculations.
To address this challenge, the Finance Transformation team has designed a governed reporting process using Anaplan Workflow and Anaplan Data Orchestrator (ADO). The solution introduces a structured approval framework that separates active planning activities from approved reporting outputs, ensuring that stakeholders always have access to trusted and auditable financial information.
The challenge
During the planning cycle, P&L and Balance Sheet forecasts are continuously updated and refined. While this flexibility is critical for planning, it can also result in previously reviewed and approved numbers changing due to subsequent model developments.
This creates a risk where management information, dashboards and reporting packs may no longer reflect the exact figures that were formally approved by business stakeholders.
The solution
The new process establishes a controlled end-to-end workflow for forecast review, approval and publication.
Business users create and update forecasts within Anaplan planning models. Once forecasts are ready, they are submitted through Anaplan Workflow, where they progress through multiple review and approval stages.
After the final executive approver signs off on the forecast, Workflow automatically triggers the creation of a Snapshot, capturing the approved P&L and Balance Sheet values at that specific point in time.
The approved snapshot is then extracted using Anaplan Data Orchestrator (ADO) and loaded into a dedicated Reporting Module. This reporting layer is maintained as a read-only environment, ensuring that approved numbers remain unchanged even when further development activities continue within the planning models.
Key benefits
Single source of approved numbers
Only formally approved forecasts are transferred into the reporting layer, ensuring consistency across management reports and dashboards.
Stable and read-only reporting
Once published, approved figures remain protected from subsequent model changes, preserving reporting integrity.
Enhanced governance and auditability
Every submission, review, approval and publication step is tracked, creating a transparent audit trail and strengthening governance controls.
Separation of planning and reporting
The solution decouples active planning models from approved reporting outputs, allowing model development to continue without impacting signed-off results.
Reusable reporting foundation
The approved reporting dataset can be leveraged across MI packs, executive dashboards and regulatory reporting processes, improving efficiency and consistency.
Business impact
By combining Anaplan Workflow and ADO, the Finance team has established a robust framework that supports both agility and control. Planning models can continue to evolve while approved reporting remains stable, trusted and fully auditable.
This approach strengthens stakeholder confidence, improves reporting reliability and provides a scalable governance pattern that can be extended across future Finance Transformation initiatives.
Conclusion
The combination of Anaplan Workflow, Snapshot Management and Anaplan Data Orchestrator creates a controlled bridge between dynamic planning and dependable reporting. The result is a trusted, read-only reporting dataset that preserves the integrity of approved financial information while enabling continuous innovation within the planning environment.
Develop dynamically. Approve formally. Report with confidence. 🚀
Finance Transformation Spotlight | Anaplan Workflow & ADO | Trusted Numbers.
Better Decisions. Stronger Business.
-
2026 certificate maintenance for Certified Master Anaplanners
The 2026 Certified Master Anaplanner Program has begun, and there is incredible opportunity for 2026 Certified Master Anaplanners (CMAs) to demonstrate their thought leadership, technical expertise, Anaplan championship, and mentorship capabilities across the entire Anaplan ecosystem.
At their core, a Certified Master Anaplanner is someone who elevates others across the Anaplan ecosystem through the many ways they share their expertise. This includes mentoring others, sharing community perspective and technical architecture thought leadership, demonstrating innovative solutions, providing product feature insight, ideating and inspiring others in the Anaplan Community to help define the future of the platform, leading CoE development, building innovative roadmaps to scale the platform for business decision-making, and championing Anaplan in the competitive market.
Engagement zones
The 2026 CMA contribution activities list is attached to this post and available for CMAs to download:
Download the list of 2026 Contribution Activities
2026 CMA Contribution Activities.pdf
Each contribution activity is mapped to four engagement zones to help articulate how Certified Master Anaplanners are driving impact within the Anaplan ecosystem. As mentors, thought leaders, Anaplan Champions, and technical experts, Certified Master Anaplanners play a critical role in elevating the broader ecosystem and driving value through the ways they share their expertise.
Each engagement zone is important to the Certified Master Anaplanner community, the entire Anaplan ecosystem, and the Anaplan Community. Highlighting these zones is intended to help you easily align your experience and interests with activities that best suit where you want to make impact. CMAs are encouraged to focus on a primary engagement zone or pursue a blend of activities across zones — with the opportunity for some to complete activities in all four engagement zones during 2026.
Contribution activities will continue to be reviewed and updated throughout 2026 to reflect evolving priorities and areas of impact across the Anaplan ecosystem.
Contribution activities will continue to evolve throughout 2026, with new opportunities introduced regularly to reflect where Certified Master Anaplanners can have the greatest impact. This list will be refreshed at least quarterly, giving CMAs ongoing ways to engage, contribute, and be recognized for the value they deliver across the Anaplan ecosystem.
CMAs are encouraged to check back regularly and plan contributions early to take advantage of new opportunities as they are introduced.
Certification maintenance requirements
Certified Master Anaplanners are expected to actively contribute throughout 2026 and must meet two requirements to renew certification for 2026. These requirements remain consistent with prior years.
Contribution activity requirement
* Complete contribution activities totaling 400 points by December 15, 2026.
* The full contribution activity requirement is due in December; however, CMAs are strongly encouraged to show progress or have a communicated plan in place by the mid-year check-in.
* To support proactive planning and visibility, a mid-year check-in will be conducted between June and July 2026, with 200 points completed or confirmed by July 31, 2026 through planned, communicated activities
* CMAs are encouraged to report contribution activities as they are completed rather than waiting until deadlines
Technical (recertification exam) requirement
* Pass the proctored Certified Master Anaplanner recertification exam by December 31, 2026 (the exam must be passed, not just scheduled)
* The study guide and recertification exam will be available beginning July 8, 2026
* Recertification exam details are available in the 2026 Recertification Information resource
* CMAs should review the Recertification Exam Registration Instructions course in the Anaplan Academy CMA Program Maintenance learning path, which includes step-by-step guidance and the required registration code
Important clarification on recertification exam timing
The Certified Master Anaplanner recertification exam is required every two years. For 2026, the following applies:
* Certified Master Anaplanners who did not take the proctored recertification exam in the prior year — including Japanese-language learners awaiting the release of the Japanese exam and individuals who were granted a one-year extension due to extenuating circumstances — will need to complete and pass the proctored recertification exam in 2026.
* Certified Master Anaplanners who took and passed the proctored recertification exam to renew certification for 2026 have fulfilled the technical requirement for the two-year cycle.
* Newly certified Master Anaplanners in 2025 or 2026 have two years from the date of their initial exam before their first recertification exam is required.
If you are unsure if you need to take action to fulfill the technical requirement in 2026, please contact MasterAnaplanners@anaplan.com for confirmation.
Program terms, conditions, and contact information
Certified Master Anaplanners are responsible for remaining informed of the program policies and requirements that govern certification maintenance and participation.
Please review the 2026 Certified Master Anaplanner Program Terms and Conditions.
Please download and review the 2026 Certified Master Anaplanner Program Terms and Conditions
2026 Certified Master Anaplanner Terms and Conditions.pdf
CMAs must also ensure their contact information remains accurate and up to date, including the email address associated with their Certified Master Anaplanner Program participation. Changes to employment or email address should be addressed promptly to avoid disruptions to program communications.
For guidance on updating your email address, including temporary updates during employment transitions, DO NOT CREATE A NEW ACCOUNT. Instead, email the Academy help desk (academy@anaplan.com) to request an update to your learner and Community email address.
If you are a Certified Master Anaplanner who has any questions about the requirements for annual certification maintenance, your status, or how to engage, please email MasterAnaplanners@anaplan.com
If you are interested in the Certified Master Anaplanner Program and wish to learn more about how to become a Certified Master Anaplanner, please review the resources here.
-
Beyond the build: Sustaining user adoption through CoE governance
Author: Ajinkya Pawar is a Certified Master Anaplanner and Senior Manager at Genpact.
Most Anaplan practitioners focus on four cornerstones, data, process, model, and deployment, throughout the engagement journey. In an ideal implementation, data ownership is clearly defined, processes are agreed upon, the model is built with best practices, deployment is closely monitored and go-live is celebrated. In two of my past engagements, platform usage looked healthy after go-live, but six to eight months down the line we noticed login frequency decline, business users resorted to Excel for quick reconciliations, and leadership started questioning the gap between platform investment and the value delivered.
This pattern is common across many Anaplan engagements, and it points to foundational problems rather than isolated exceptions. The essence is to ensure deployment is not treated as the finish line. It is a starting point to maintain solution relevance and platform trust. The decline in adoption does not happen in a single moment but is a series of unchecked and unaddressed gaps.
Root causes for the decline
In my experience, there are many reasons that can cause adoption deficit but following are the usual suspects:
* Inconsistencies or delays in data pipelines causing numbers to be questioned and trust collapsing fast.
* Challenges faced in UX application navigation impacting ease of use.
* User feedback not addressed in ongoing releases making them feel unheard.
* Training/workshops delivered only once, at project launch, and never refreshed thereby new joiners never really get acquainted with the solution whereas long-time users forget about valuable features they seldom use.
* The business case made for the platform investment at start of the project was never revisited so whenever budget conversations resurface there is inability in the room to convey clear story with a consensus of value delivered.
All these issues may appear unrelated, but they are connected and call for a coordinated governance approach. The goal is to overcome the misconception that go-live equals success and usage equals value. This is exactly where you need Center of Excellence (CoE) governance to play a pivotal role in preserving adoption.
Six governance pillars to sustain adoption
1️⃣ Technical UX design: Adoption depends on daily user experience. UX design must include role-based landing pages, simple navigation, unambiguous instructions, sensible filters and process buttons aligned to planning workflow creating an intuitive and efficient user experience. Moreover, this should not be one time exercise but paired it with governance discipline via ALM hygiene, proper revision tags and production data rules so that consistency survives through every new release.
Role of CoE:
* Draft and maintain a working design playbook built on Planual standards, naming conventions, page templates on when and how to use board/worksheet/report, type of filters, charts and corresponding relevance, navigation patterns that can be reused by model builders rather than reinvent.
* This is more beneficial in a federated CoE structure to ensure UX consistency and uniformity as a byproduct across models through various use cases.
* CoE can spot check few UX dashboards in quarterly audits reviewing adherence to playbook standards.
2️⃣ Data quality and integrity: Polished UX and fancy reporting dashboards can never compensate for inaccurate numbers. Clear data lineage, automated reconciliation routine, visible data quality checks instill confidence amongst end users persistently reinforcing platform as a single source of truth in lieu of competing with parallel planning systems.
Role of CoE:
* Promote data integration initiatives (among internal tech teams) to run automated data reconciliation jobs to tie-out source systems totals to spoke models totals.
* This is a proactive measure to ensure errors are flagged to respective data owners/model builders with a defined SLA resolution.
* This closes the gap before users catch it and promotes usage of the platform.
* Incorporation of new features like ADO, Workflow, Anaplan XL should be encouraged in these data quality checks.
3️⃣ Change management: Technically sound solutions are necessary but not sufficient to preserve adoption. A human layer in the loop is essential for communication, periodic end user training and change management planning.
Role of CoE:
* Disseminate requisite knowledge on maintaining fixed checklists of training plan, change management plan, feedback channel before and after any use case goes live.
* Establish and promote practice of structured intake of end user requests amongst tech teams to see their input/requests reflected in upcoming sprints.
* Invest early in internal model builders so that once they combine platform fluency with business context, they can run training sessions reducing CoE’s workload over time.
4️⃣ Model governance and security: Absence of access control, workspace segregation, model governance has negative implications in preserving platform adoption. Users facing permission errors, access to unauthorized data or experiencing constant outage are bound to lose trust on the platform.
Role of CoE:
* Automate access provisioning either via custom APIs, or identity providers like SailPoint, Okta or a dedicated central security hub automation depending on the convenience, cost and scale of your business.
* Institutionalize mandatory peer reviews for compliance checks of PLANS methodology, model performance logging tests on intermittent basis.
* Seek support from Anaplan customer success Business partner on a quarterly basis to pull Best practices Infraction (BPI) score tracking breaches against Anaplan Planual standards.
5️⃣ Executive ROI: Sponsorship is not secured once but is renewed yearly. The leadership needs to see constant tangible value from the investment made. Performance metrics such as forecast accuracy, planning cycle time reduction, reduction in efforts, speed to outcome must be tracked and reported on a cadence.
Role of CoE:
* Build a value scorecard or performance dashboard accessible to executive leadership that reflects top 5 key metrics (example: # of business process supported, planning cycle duration) that get calculated based on data pulled automatically each month from existing models.
* This way CoE can eliminate the need of justifying every new initiative from scratch and helping leadership get answer to “What are we getting out of this investment?” with a single click.
6️⃣ Continuous enablement: As business evolves, use cases expand, new platform capabilities released, it becomes imperative to maintain ongoing enablement through periodic training sessions, role-based learning paths keeping model builders aligned with end users and stakeholder expectations.
Role of CoE:
* Launch an internal champion network that encourages model builders, architects build accelerators or MVPs on new use cases using new platform features. This fosters innovation and opens avenues to translate into positive business impact.
* Release biweekly/monthly newsletter to stakeholders, end users, model builders, capturing “what’s new” in the Anaplan space, internal innovation initiatives, cross-unit success stories to aid drive engagement.
Measuring adoption
Experience says if you can’t measure it, you can’t improve it. Following table gives my perspective on few KPIs that can be internally tracked by a CoE to measure platform adoption and not just rely on numbers of users logged in:
* Number of data quality incidents
* Number of enhancements in the backlog and Average resolution time
* Active usage by role/business unit
* Training completion and proficiency
* Number of recurring excel workarounds
* Business value delivered in USD
Bringing it all together
Together, these pillars address usability, enablement, trust and sponsorship, essential for driving adoption over time, not just at launch. The intent is not for CoE to own everything, but it is to define standards and establish guardrails to be followed. The path forward is to perform transparent assessment on each of the pillars, identify weakest of them, create an action plan to address them and prioritize execution to see right results.