skip to Main Content

Review and Recommend Service Offering

Review and Recommend Service Offering


Whether one functional area, or a review of all existing areas, icloudfluence can tailor a review and recommend to your needs. We have seen hundreds of Workday tenants at all stages of deployment, and we understand what configuration works and what features are the best to implement for your unique instance.

With constant releases and patches, many different hands in the system, and years of maintaining Workday, it always pays off to have an architect conduct a review and advise a plan for improvements.


Our proven approach when conducting a review and recommend:

Meeting to Gather Pain Points

Every Workday user in the ecosystem has something they wish they could change. Whether it fell down the priority list or is a system limitation, there are some pain points. That is where we start, and use this list to start our audit off in the right direction.

First Audit

We will complete a first pass through the configuration of the tenant, focusing on configuration that may not be leading practice, scalable, or may have negative, downstream impacts on other areas of the system. We also consider past releases and what new functionality may have been missed that could improve the module overall. Lastly, we focus on reporting and analytics and if you’re truly seeing an ROI on Workday’s analytic abilities.

Review and Questions

We then meet to discuss any outstanding questions from the first review – was there a reason x,y,z was set up in a particular way, was something else considered?

Final Pass

With the initial review completed and questions answered, we will complete a final pass through the tenant to wrap up all review items and organize our recommendations.


We produce a physical deliverable, and review with the client, that outlines:

  1. What we noticed that needs updating or new features that we suggest uptaking. If it is an issue, we will outline why it is an issue and the possible problems it could cause
  2. The correct way to make the fix, level of effort, and skill set required
  3. The priority in which updates should be made and why it makes sense to tackle some items before others

    Back To Top