What is the convention followed for generating Emp Id if the office is located in multiple geographical location?

Totally depends on how you want it to be codified and depending on your HRMS

@S M In all of my previous jobs, we used employee IDs that began with the alphabets of the company name and ended with a number based on when the employee joined. For instance, if my company’s name is ABCD and I am the sixth employee, my employee id is AB6.

right,so as we are seggregating 2 entities, I'll have to define the fresh set of Emp ID for 1 of the entity. So I did define it as 1st 3 letter of the company ABC0001, but now we need to defien it for the employees in US as well. So was in a fix as I can't put it as IND and US because convention should be aligned.

Yes we do for indian employees IND we have initials of company first then IND and then the number as wristy mentioned

We haven’t separated employee ids based on geography. For example, the employee who came in before me (the fifth employee) came in the United States, and the seventh employee came in Canada; their employee IDs were AB5 and AB7, respectively.

Ok,thank you.

Since the entities are different, I think it'd be wise to do different IDs. If you're already doing ABC0001 for India entity, you can do something like ABUS001 for the US, @S M 👍🏻

I had the same thing running in my mind @Anshul 🙂. Thank you.

Only from my experience working with global companies with multiple entities, having a consistent employee id positively impacts employee experience and improves data management.

Do you see any challenge in the convention as mentioned above @Wristy?

Whose suggestion are you referring to @S M?

@Wristy For Ind it is ABC0001 and for US it is ABCUS001.

There is no legal or compliance issue. As a human resources professional, you are (unconsciously) rooting differences among employees from various locations. Following a consistent employee id provides employees with the same sense of acceptance (psychologically) and makes a company inclusive.

Yes, I agree,which is why I was hesitating including country initials as such. What could be more intuitive numbering mechanism @Wristy?

Employee ids are used for a variety of purposes. I might be able to recommend something depending on the same.

@S M different entities would be having different names, so you can have different emp id’s. I am assuming your HRMS will have employee data separately for each entities depending upon location/business/etc. In my previous organisation, we used different emp id’s. ABC001 for one entity and DEF001 for another irrespective of their locations. (initials stands for name of entities)

At my previous org irrespective of entities we went by the following code - Year of joining + Employee number. It'd look something like this, assuming I joined in 2023 as the company's 100th employee (overall). -> 20230100

Wouldn't it be easier to segregate the group if they have different IDs while implementing any policy or benefit for that particular entity? Considering the 2 entities are in India and US as in question, where benefits may be the same but have to be implemented with different guidelines and processes owing to ease of usage by what's conventional regionally? @Joel Johnson @Wristy

Hi @Anshul - sure this makes sense. But I'm also sure, there are other fields in one's HRMS tool to filter based on this condition - it doesn't necessarily have to be incorporated into the ID in itself. TLDR; you can use whatever nomenclature that works best for the team. There are different templates that one can use here..

Makes sense 👍🏻

@Joel Johnson What in absence of an HRMS tool, we are start up adding flocks, this is manual, and don't have as much of a growth plan in terms of adding talent?

Still applicable. If you're managing on Excel today, add another column which defines which office/geo the employee is a part of.