In SAP SuccessFactors, Route Maps are the workflow rules that control how a form moves from one person to another during a process—most commonly in Performance Management, Goals, and 360 Reviews. Think of a route map as the form’s GPS, it defines who gets the form, in what order, and what they’re allowed to do at each step.


What Route Maps Do:

A route map defines:

  • Who the form goes to (employee, manager, HR, custom roles)
  • When it moves (submission, completion, manual send)
  • What actions each person can take
  • (edit, view only, approve, sign, etc.)
  • Whether steps are sequential or collaborative

Common Use Cases:

  • Annual performance reviews
  • Mid-year check-ins
  • Goal setting and approvals
  • Compensation planning reviews
  • 360 feedback cycles

Typical Route Map Steps:

Employee Self-Assessment:

  • Employee fills out their review

Manager Review:

  • Manager evaluates and adds comments

HR Review (optional):

  • HR checks for consistency/compliance

Employee Acknowledgement:

  • Employee signs off

Completed:

  • Form is locked and archived

Each step can have permissions (edit, view, route forward, etc.).


Key Components of a Route Map:

  • Steps – The stages in the workflow
  • Roles – Who owns each step (e.g., E, EM, HR)
  • Actions – What the user can do at that step
  • Entry / Exit rules – Conditions for moving forward
  • Routing type – Sequential vs. collaborative

Where Route Maps Are Used in SuccessFactors:

Route maps are assigned to forms in:

  • Performance Management (PM)
  • Goal Management
  • 360 Reviews
  • Calibration & Compensation (indirectly via workflows)

They are configured by admins in:

Admin Center → Manage Route Maps

Why Route Maps Matter:

  • Enforce process consistency
  • Ensure correct approvals
  • Control data security and visibility
  • Support audit and compliance needs

One-line summary:

Route Maps in SAP SuccessFactors define the approval and review workflow for forms—who touches them, in what order, and with what permissions.