Managing multiple hierarchy in location table

[Roshmin Ramesan]

In my organization location table, there are Territorial Head Quarters, Departmental Head Quarters for different divisions (provinces in Canada) different ministry units, and under each ministry unit - there are multiple buildings - which are the individual locations in the location table. There is a request to classify the ministry units in ServiceNow, to manage and maintain them. What is the ServiceNow best practices / recommendation from the two options? Option 1: Create all the buildings as individual location records, and mark the corresponding Ministry Unit as the parent. Ministry Unit is also an individual location record - with parent as the division. Option 2: Only to have the buildings as location records. Ministry Unit is created as a Company, and associated with the location record.

[AnjalPDijo]

Hi @Roshmin Ramesan ,

If your Ministry Units represent physical locations, then it's best to go with Option 1 - model them as Location records and use the parent field to build the hierarchy (e.g., Building → Ministry Unit → Division).

However, if Ministry Units are organizational entities, then Option 2 is more aligned with ServiceNow best practices - use the Company table for Ministry Units and associate buildings (Location records) with them.

Hope this helps clarify the approach!

Best Regards,
Anjal

[Sarthak Kashyap]

Hi @Roshmin Ramesan ,

In my opinion Option 2 is best — Create Ministry Units as Companies and associate their Buildings as Locations under them.

For example you have one ministry and that particular ministry is located multiple location you can manage them easily with OOTB solution 

Please mark my answer correct and helpful if this works for you

Thanks and Regards,

Sarthak