When are Salesforce performance reviews? (2026)
Salesforce runs on a fiscal year that ends in January, and its planning vocabulary is built around a published goal-setting method. Cycle dates vary by org, so tie your record to the goals you signed up for and the numbers attached to them.
Twice a year
No specific review month is published for this company, because none could be sourced from the company's own material. What follows is the cycle shape, which is what is actually knowable. Your own manager is the authority on this year's dates.
How the cycle works
Salesforce is a sales-led enterprise company with a fiscal year that does not match the calendar year, ending at the end of January. That single fact reorganizes everything: the fourth quarter push, the annual kickoff, and the goal-setting that follows all sit in a different place than they would at a company running on a calendar year. When you think about "the year" here, think fiscal.
The company also has a well-known internal goal-setting method, published and taught, that cascades objectives from the top of the company down to the individual. The important consequence for you is that your goals are supposed to be traceable upward. A contribution that maps cleanly onto a stated organizational objective is legible in a way that an equally good contribution outside that map is not.
Formal review timing varies by organization and role family. Confirm the dates with your manager rather than assuming your team runs the same schedule as an adjacent one.
What actually gets weighed
Attributable numbers dominate. In a sales-led organization, the strongest evidence is a figure with your name attached: attainment, pipeline you influenced, renewals you saved, deals you unblocked with technical work. Even in engineering and support roles, the framing that travels is revenue-adjacent — the outage you prevented during a quarter-end, the feature a named account required to renew, the onboarding friction you removed that shortened time to value.
Goal traceability is the second axis. If you can point at the organizational objective your work rolled up to, you have done half of your manager's argument for them.
Cross-cloud and partner ecosystem work is the third. This is a large product surface with a large partner network, and someone who made two clouds work together, or who unblocked a partner implementation, has done something the org has no easy substitute for.
What to have ready
- Your stated goals for the fiscal year, and the outcome of each, stated in the same words they were written in.
- Every number you can legitimately attach your name to, with the mechanism by which you influenced it.
- Named accounts or partners where your work was a specific dependency, and what changed for them.
- Quarter-end and fiscal-year-end moments where you carried unusual load, since those are the weeks the organization remembers.
- Any objective that changed mid-year, with what you did in response — reacting well to a reprioritization is evidence, not an excuse.
Because the fiscal year ends in January, the useful time to assemble this is during the holiday lull, not after kickoff when everyone has already moved on to next year's goals.