Pros/cons of having a field in Job info vs. in the Position (and then syncing to Job Info) ?

[dllaverias]

My company has EC implemented and we use position management. Often times, me and my team find ourselves questioning whether a field/data point is supposed to be added to the position object(and then sync to Job Info) or just stored in job info.

We are trying to add a field in the system that indicates what template of performance evaluation to assign to someone, depending on the nature of their job. Something like a cost center, or a department makes sense that its in the positions object. This particular field, not sure. Are there any benefits or downsides of having something just in Job info? In which option is easier to get rid of this field if we no longer need the field? Any best practices or rule of thumbs?

[karenperez]

Dear dllaverias,

Trying to answer your question on when to create a field at position level and when at job info, here some considerations:

• Position: Create fields at the position level when the information is specific to individual positions within your organization. For example, fields related to position location, department, manager, or unique responsibilities.
• Job Information: Create fields at the job information level when the information is common across multiple positions that share the same job role and are related to the employee in your company. For example, fields related employment type.

I hope this helps you.

Thank you.

Best Regards,

Karen Perez