DIGIT HR · Core HR & Organization
Every decision starts with a trusted record
From organizational structure and positions to employee records, appointments and contracts—one reference gives every process its context.
- Organization
- Job and position
- Employment relationship
- Contract and document
- Organization
- Job
- Position
- Employee
- Contractual relationship
The real business problem
The foundation for HR decisions
Structure, companies, jobs, positions, employees and contracts are not isolated records; their relationships define the context of every action.
The business journey
How do the parts connect to reach a decision?
- Stage 1:Company and structure
- Stage 2:Job and position
- Stage 3:Employee record
- Stage 4:Employee movement and appointment
- Stage 5:Contract and document
- HR manager
- Organizational structure administrator
- Personnel administration
Explore the operations
The capabilities behind this journey
Choose any area to see its inputs, actions, documents and the decision it supports.
Organizational structure and entities
Fragmented company and branch data leaves hiring and planning decisions open to inconsistencies across departments.
When companies, branches and departments are managed in separate records, it becomes difficult to identify which entity each employee or position belongs to. The journey starts by defining entities, structure and responsibility centers, then presenting their relationships in a navigable view. HR administrators can see the organization before making an appointment or transfer decision, while gaps and conflicts highlight records that need review.
How does the process move?
We start with the organizational map—companies, units, branches and departments—then move to the people and positions within it.
OutcomeOne organizational reference clarifies reporting lines, responsibilities and where every employee fits.
Inputs and data
- Company/legal entity
- Branch
- Department
- Business unit
- Manager
- Location
- Cost center
Outputs and documents
- Org chart tree
- Documented reporting lines
- Traceable reference data
Cases that need review
- Conflicting reporting lines
- Unit without a manager
- Record assigned to the wrong entity
Reporting and follow-up questions
- Organizational structure readiness
- Headcount distribution by unit
- Items outside the organizational structure
Explore the detailed capabilities 5
- Organizational structure wizard (organization › departments › legal entities › business units) with linked master record creation within the wizard and a summary report
- Legal entity with registration details and employer flag
- Reference data sets (shared / entity-specific)
- Structure master records: location, business unit, department with its manager and cost center, job
- Organization and department tree with grouping
Screens and documents in this journey 3
- Org structure explorer
- Legal entities and companies
- Departments and branches
Job classification and profiles
Without job standards, comparisons, promotions and hiring lack consistency.
- Inputs and data
- Job family
- Job title
- Job description
- Grade
- Skills and requirements
- How does the process move?
We define the job title, description, family and grade, then link them to the position and employee.
- Outputs and documents
- Job dictionary distinguishing job titles from actual positions
- Duplicate job titles
- Job without a description
- Confusion between job and vacancy
Before a company compares candidates or defines a career path, everyone must agree on what the job title, family, grade and requirements mean. This section standardizes job terminology without confusing a job, as an occupational definition, with a position, as a place in the organization occupied by a person. Recruitment, assessment and development needs can then be understood through clear descriptions rather than inconsistent, free-form titles.
OutcomeA shared job vocabulary for recruitment, development and compensation.
Reporting and follow-up questions
- Job distribution by family/grade
- Gaps in occupational definitions
Who works here
- HR manager
- Organizational development officer
Screens and documents in this journey 2
- Job families
- Job profiles
Positions and budgets
A vacancy may arise without a budget or an allocated position.
Management needs to know how many positions were planned, which were approved, who occupies each position and where actual vacancies exist. This section distinguishes between Job, Position, Vacancy, Requisition and budget; they are not different names for the same thing. Decisions to create and approve a position and link it to recruitment appear in a record that can be referenced. A planning scenario does not become financial approval simply because it is displayed on a screen.
How does the process move?
Starting from the plan, we identify the position and whether it is filled or vacant, then link it to the hiring need and approval.
OutcomeVisibility into vacancies and staffing needs while keeping positions and recruitment as distinct concepts.
Inputs and data
- Organizational structure
- Job Profile
- Position
- Approved budget
- Position holder status
Outputs and documents
- Position list
- Available vacancy
- Request to open a job or review the budget
Cases that need review
- Position over budget
- Multiple position holders not permitted
- Distinction between a vacancy and a job title
Reporting and follow-up questions
- Approved, vacant and filled positions
- Planned vs. actual variance
Explore the detailed capabilities 5
- Position with its profile and qualifications
- Position hierarchy and position holders + position-to-assignment synchronization
- Position approval
- Transition: position → job requisition → vacancy
- Clear concepts: position ≠ job ≠ vacancy ≠ job requisition, with visible definitions and links between them
Screens and documents in this journey 3
- Position register
- Position profile
- Position budgets and approvals
Employee records and Employee 360
Employee data is often scattered across files that are difficult to track.
Finding employee information takes time when it is spread across assignments, contracts, attendance, leave and documents. Employee 360 serves as a gateway to related records, not another copy of every document. Authorized staff can see the context their permissions allow and navigate to the original source for case details. The aim is not simply to bring ten tabs together, but to show the employee history and documents relevant to the decision at hand.
How does the process move?
Open Employee 360 to view job details, data, documents, relationships, leave and attendance according to your role.
OutcomeA unified profile that reduces search time and links directly to the source document.
Inputs and data
- Identity and contact details
- Company
- Assignment
- Contract
- Linked documents
Outputs and documents
- Employee 360
- Record links, status history and change log
Cases that need review
- Expired document
- Missing data
- Assignment discrepancies across documents
Reporting and follow-up questions
- Employee profile completeness
- Missing items
- Workforce changes
Explore the detailed capabilities 1
- Employee 360 sections (job, salary, benefits, performance, learning, succession, personal details, identity, emergency contacts, dependents, communication preferences)
Screens and documents in this journey 2
- Employee directory
- Comprehensive employee profile
Relationships, assignments and transfers
Transfers and promotions may lose their historical trail or be linked to an incorrect date.
A promotion, transfer or change in reporting line should not erase the previous assignment. The process starts by identifying the employee, change type, reason and effective date. It then goes through authorized review before being reflected in the assignment history upon execution. You can follow the sequence chronologically and explain why today's status differs from an earlier period, rather than leaving the employee profile with only a current value and no history.
How does the process move?
Start with the employee, prepare a dated change, review eligibility and approval, then view the change log.
OutcomeFull tracking of career progression, with a preserved record of every action.
Inputs and data
- Employee
- Current assignment
- Change type
- Reason and effective date
- Approvals
Outputs and documents
- Promotion/transfer/termination request
- Change record with effective date
- New assignment
Cases that need review
- Conflicting date
- Change without approval
- Insufficient permissions
Reporting and follow-up questions
- Pending changes
- Transfers and promotions
- Changes in job holders
Explore the detailed capabilities 3
- Person › Employment relationship › Assignment layers, with multiple assignments and a primary assignment
- Effective-dated data + step-by-step job data updates and timeline
- Categorized employment actions (promotion, transfer, termination) with reasons and reversal capability + all-actions bar
Screens and documents in this journey 3
- Contractual relationship record
- Dated assignment history
- Transfers and promotions
Contracts and documents
Contract and document expiry dates can pass without a clear alert.
A contract is more than a PDF stored in a folder. The HR administrator needs to link it to the employee, validity period, amendments, addenda and required documents. This section explains how to distinguish the original contract from an amendment and review expiry dates, while keeping a simple alert or renewal record creation distinct from a signature or legal action whose completion has not been verified.
How does the process move?
Bring together contracts, documents and files linked to the employee, and display upcoming dates and actions.
OutcomeTrack contracts and renewals without searching through separate files.
Inputs and data
- Employment contract
- Contract terms
- Start and end dates
- Attachments
- Amendment request
Outputs and documents
- Contract/amendment record
- Saved copy
- Renewal alert when configured
Cases that need review
- Potential expiry
- Number/date discrepancy
- Unlinked document
Reporting and follow-up questions
- Contracts by status
- Upcoming renewals
- Missing attachments
Explore the detailed capabilities 2
- Employee documents
- Saudi identity completeness (national ID/Iqama) — proposed, not observed on a screen
Screens and documents in this journey 3
- Employment contract register
- Contract and amendments
- Document expiry and renewal
Outcomes and reporting
What does the decision-maker see in the end?
Results are read from the document, not from a number detached from its context.
Outputs and documents
- Org chart tree
- Documented reporting lines
- Job dictionary distinguishing job titles from actual positions
- Position list
- Open vacancy
- Employee 360
Reporting and follow-up questions
- Organizational structure readiness
- Headcount distribution by unit
- Job distribution by family/grade
- Gaps in occupational definitions
- Approved, vacant and filled positions
- Planned vs. actual variance
These are business questions, not operational data.
Exceptions that should never disappear
- Conflicting reporting lines
- Duplicate job titles
- Position over budget
- Expired document
- Conflicting date
A demo built around your work
Start from the work scenario that matters to your team.
We walk through one specific journey: the input, the user, the action, the status, the document and the report. Then we scope the demo to what your organization needs.
DIGIT · Every decision starts with a trusted record

