Position Management Software: Build Your Org Structure, Job Grades and Salary Bands

Position management software is the part of an HR system that answers four questions: who works where, who reports to whom, at what grade and salary band, and with what access. Instead of a list of names in a spreadsheet, every position has a place in the org chart, a direct manager, a department and branch, a grade with minimum and maximum pay, and either a current holder or a "vacant" status. This guide explains positions, titles and grades, how to build fair salary bands, what Egyptian and Saudi rules expect from job data, and gives you a step-by-step plan and checklist.

Key takeaways

• Position, job title and grade are three different things. Mixing them up causes most structural mess.
• Salary bands (a min and max per grade) protect internal fairness and keep hiring and raise decisions consistent.
• In Egypt the contract must state the worker's profession, the nature of the work and the wage (Ministerial Decision 214/2025). In Saudi Arabia titles and wages must match the contract documented on Qiwa.
• Tie permissions to roles and data scopes, never to individual names.

Legal information here is general guidance, not legal advice. Check the official text or your adviser before applying it.

What position management software does

A good system answers the questions an owner, CFO or HR manager asks every week:

• How many positions do we have per branch and department? How many are filled, and how many are vacant?
• Who reports to whom, and which manager approves each person's leave and requests?
• Is this employee's pay inside their grade's band?
• Who is allowed to see payroll for a given branch or approve requests for a given department?

When those answers live in one system connected to employee records, payroll and access control, a transfer or promotion updates everything at once: the direct manager, the approval route and the cost line in payroll reports. For the wider HR platform picture, see our HR software guide.

Positions, titles, grades and job descriptions

Rule of thumb: the contract names the title, the structure is made of positions, pay follows the grade, and data access follows the role.

Choosing an organisational structure

• Functional (by department). Finance, HR, sales, operations. This fits most companies up to a few hundred employees.
• By branch or region. Common in retail, restaurants and clinic chains. Each branch manager owns daily operations and attendance, and finance and HR stay central.
• Hybrid or matrix. An employee reports administratively to a branch manager and functionally to a central head. Your system must name one direct manager for approvals, or requests fall between two desks.

Building salary bands

A pay structure doesn't mean identical salaries. It means a band per grade: a minimum, a maximum and usually a midpoint.

1. List current positions with title, department and current basic pay.
2. Evaluate roles relative to each other on responsibility, required qualification, financial impact and people managed.
3. Group similar roles into grades. Six to ten grades is typical for a mid-sized company.
4. Set a min and max per grade using current pay, affordability and whatever market information you have.
5. Fix outliers. Plan a correction for anyone below the minimum. For anyone above the maximum, freeze the basic and give future raises in another form, per your policy.
6. Respect the law. In Egypt no wage may fall below the private-sector minimum of EGP 7,000 a month (gross, from 1 March 2025), and the annual periodic raise is at least 3% of the insurable wage (Articles 12 and 102 of Law 14/2025, which the National Wages Council may waive or reduce in hardship).

Illustrative band (made-up figures)

For illustration only, not market data.

A Grade 4 employee on a basic of 12,000 sits in the lower part of the band. A common measure is the compa-ratio: actual pay ÷ midpoint (here 12,000 ÷ 13,800 ≈ 0.87). Overlapping bands are normal and allow promotions without an illogical pay jump. For net pay after tax and social insurance, see our payroll software guide.

What the law expects from job data

Egypt

• Contract data. Under Ministerial Decision 214 of 2025, the contract includes the worker's name, qualification, profession, insurance number, the nature and type of work, the agreed wage with its payment method and timing, and any cash or in-kind benefits. It is written in Arabic in four copies. Job titles are therefore contractual data, not just internal labels. See our employee contract guide.
• Grades in the disciplinary ladder. Article 139 of Labour Law 14/2025 includes penalties such as deferring a promotion by up to a year and demotion by one grade without a pay cut. You can't apply these fairly without documented grades.
• Employer data statement. Employers file a statement with the Ministry covering headcount, nationality, gender, wages and qualifications, updated every January, as summarised by EY. A clean structure turns this into a report rather than a manual project.
• Retention. Keep the employee file, including position and promotion history, for five years after termination.

Saudi Arabia and the Gulf

• Private-sector contracts are documented on Qiwa, including occupation, wage and contract type. The Wage Protection System, run through Mudad, reconciles paid wages against the Qiwa contract wage and the GOSI wage. Update the Qiwa contract for any promotion or raise before running payroll.
• Some occupations are localised by ministerial decision, and Nitaqat Saudisation is calculated by activity and establishment size. Loose internal titles can distort localisation reporting, so map each position to the documented occupation. Check MHRSD for current rules.

Role-based permissions: security first

1. Define roles: owner, HR manager, payroll officer, branch manager, department head, employee.
2. Give each role a data scope: the whole company, a branch or a department.
3. Assign the role to the position holder, not permanently to the person. Review it on every transfer.
4. Separate duties. The person who prepares payroll should not be the only one who approves it.
5. Enforce two-factor authentication for admin roles and review the audit log regularly.

Vacancies and headcount

A position-based structure exposes vacancies automatically, because every unfilled position is a potential opening. That lets you:

• compare actual headcount by branch and department each month and track turnover;
• link a vacancy to a job post on your careers page and a candidate pipeline;
• see the payroll impact of a hire before the offer goes out, using the grade's band.

Step-by-step rollout and checklist

1. Map the current state as it is, not as you wish it were.
2. Standardise titles. "Sales Rep", "Sales Representative" and "مندوب مبيعات" become one title.
3. Create departments, branches and work locations.
4. Create positions and link each to a department, manager and grade.
5. Write a short description for each title.
6. Build grades and bands.
7. Assign employees and review out-of-band pay.
8. Define roles, permissions and scopes.
9. Approve and publish, with an effective date for every change.

• Every employee has a position and exactly one direct manager.
• The system title matches the contract (and Qiwa in KSA).
• Every position has a grade, and every grade has a band.
• No pay below the legal minimum.
• Permissions follow roles and data scopes.
• Changes are effective-dated and logged.

How BashKatib helps with position management

• Organisation setup. Branches with addresses and work locations, a department tree with a head per department, and positions and titles with a min/max salary band and grade. Cost centres are coming soon.
• Org chart. Built automatically from manager relationships, with zoom, search, department view and PNG/PDF export.
• Employee records. Position, grade, department, branch and manager, with effective-dated changes, salary history and a reason for every change (employee records).
• Bulk updates. Move a group to a new department, manager or shift in one action. Excel import comes with a validation preview.
• Roles and permissions. A fixed permission catalogue with branch or department data scopes, mandatory 2FA for privileged admins and an audit log of sensitive actions. Fully custom roles and workflows are on Pro.
• Approval routes that follow the structure. Direct manager, then department head, then HR, with conditional rules and out-of-office delegation.
• Recruitment. Job posts on your careers page, a candidate pipeline and offers that convert into an employee profile and contract (recruitment). Requisition approval is coming soon.
• Reports. Employee directory and status, headcount and turnover, and payroll cost by department and branch in the report centre.
• A voice briefing for the owner. The AI voice briefing compares attendance across branches and departments (best and worst) and ends with what needs your decision. It respects scopes, so a branch manager hears only about their branch.

Published prices: Starter EGP 25 / SAR 8, Growth EGP 45 / SAR 14 and Pro EGP 75 / SAR 22 per employee per month. Prices are billed annually, exclude VAT, require a 10-employee minimum and were current at the time of writing; see pricing.

Frequently asked questions

What is the difference between a position and a job title?

A position is a slot in the org structure with a department, branch, manager, grade and salary band. One person fills it, or it sits vacant. A job title is the name of the role and can be shared by many positions, such as "Accountant" in three branches.

What are salary bands and why do they matter?

A salary band sets a minimum and maximum basic pay for each grade. Bands support internal fairness, keep hiring, promotion and raise decisions consistent, and stop one-off deals that are hard to defend later.

Does Egyptian law require the job to be stated in the employment contract?

Yes. Ministerial Decision 214 of 2025 on basic contract data requires the contract to include the worker's profession, the nature and type of work and the agreed wage, alongside employer and worker details.

Why do job titles matter for employers in Saudi Arabia?

Private-sector contracts are documented on Qiwa, including occupation and wage, and the Wage Protection System reconciles paid wages against the documented contract. Some occupations are also localised by ministerial decision, so internal titles should map to the documented occupation.

Should permissions be tied to positions?

Tie permissions to roles with a data scope (company, branch or department), then assign the role to whoever holds the position. A branch manager sees only their branch, and access is reviewed when someone moves.

Does BashKatib support org charts, grades and salary bands?

Yes. BashKatib supports a department tree, positions with a min/max salary band and a grade, and an org chart built from manager relationships that you can zoom, search and export to PNG or PDF. All of it connects to permissions, approvals and reports.

Build a structure that makes decisions clearer

A clear structure underpins fair pay, safe permissions and accurate cost reporting. Set up your branches, departments and positions in BashKatib and try every feature free for 14 days, or book a demo and we'll help you move your current structure out of Excel. If you also employ part-timers, read our hourly employee management guide.