The supervisory organisation can be split into levels. For example, the customer may be structured into Divisions, Departments, Sections and Teams. These are known as sub-types.

Grade Profiles

Each grade can have variations that may depend on geographic location, function, job profile/family, or other category. For instance, while a grade may be £50k - £100k in UK, it may be $75k - $150k in US; a sales exec in Europe may have a different range to one in APAC etc.

Grade profiles may exist in, for example, global organisations that operate a global grading system.

This will then be the language in which Workday is displayed, unless a user changes preferences to a licensed language.

1. Typically Job Requisitions can be:Mandatory – a requisition is required for any event that occurs (if deploying Recruiting, this will be the only option allowed)
2. Rules based – rules will be defined when job requisitions are required
3. Disabled – not used

If you are not familiar with job requisitions, you can discuss with the partner at a later date.

When documentation is produced, of course you will be able to change this as you require, or even remove entirely.

More commonly, though, there is no existing job catalogue that is formal enough to use. Perhaps job descriptions are of different quality; exist in some cases but not others; are held in disparate systems, even technology (from paper based; to electronic documents; to system based).

In the worst case scenario, a job catalogue can be established by simply using the job titles that every one has, and creating a very basic job profile based on that. A one-to-one relationship between worker record and this job profile “skeleton” is then established.

Data migration will require workbook/s with job descriptions that can be tied to every worker. In cases where a job description doesn't exist, there will be an expectation that pseudo or dummy entries will be added. For instance, a job description could be created that is simply a placeholder for all those without one, this is assigned in data migration, and is then tidied up post go live.

There can be no gaps that mean a worker cannot be associated with an entry in the workbook.