Skip to content
Established in 2008Cairo, Egypt
Flags of Arab countries
الاتحاد العربي لتنمية الموارد البشريةArab Union for Human Resources DevelopmentVisitor Register
Programme profile

Building a unified file design and coded institutional structure

Programme code: U27-S03-T02-P004

An applied specialist course in Records Governance, Archives and the Records Lifecycle leading to the preparation of a classification plan, retention register and version controls to address the task covered by “Building a unified file design and coded institutional structure”.

Information to help you choose

Dates
2027-01-24 — 2027-01-28
Venue
Cairo — Arab Union for Human Resources Development headquarters
Programme fee
USD 600
Duration
One week · 5 training days
Delivery language
Arabic — English delivery is available by agreement
Delivery mode
In person
Training hours
25 training hours

Submitting a request does not confirm a place or booking. The administration will review availability, dates and arrangements.

The programme fee includes

  • Training
  • Training materials
  • Certificate
  • Session breaks
  • Lunch
  • Airport arrival and departure transfers

The advertised fee is the total amount payable by the participant. No additional fees are charged.

Request an invoice or official quotation — Include the programme name or number in your request.

Certificate of completion of the programme, workshop or training course

The participant receives a certificate of completion of the programme, workshop or training course issued by Arab Union for Human Resources Development. The certificate is awarded on the basis of attendance.

A programme in Libraries, Records, Archives and Information / Records Governance, Archives and the Records Lifecycle in the Union Plan for 2027.

Programme brochure

Building a unified file design and coded institutional structure

Introduction

The programme “Building a unified file design and coded institutional structure” addresses a practical task within Records Governance, Archives and the Records Lifecycle. Training draws on records, their creation context, versions and access permissions and uses techniques for classifying a record and tracking its version and lifecycle to link the analysis to a traceable decision and action.

The participant develops a classification plan, retention register and version controls over 5 training days, then tests it in a practical case on “Building a unified file design and coded institutional structure” involving conflicting versions, lost context or an incomplete disposal request. The output is reviewed against metadata completeness, version integrity and retrieval speed and the next step for applying it in the workplace is identified.

Objectives

By the end of the programme, participants work towards the following:

  1. Define the scope of Building a unified file design and coded institutional structure and the requirements for completing the task.
  2. Prepare and check the practical exercise inputs using records, their creation context, versions and access permissions.
  3. Apply the following method: classifying a record and tracking its version and lifecycle to produce a classification plan, retention register and version controls.
  4. Test the outcome in the event of conflicting versions, lost context or an incomplete disposal request and document the correction.
  5. Present and assess the output using metadata completeness, version integrity and retrieval speed and define an implementation plan.

Programme topics

Day 1: Defining the scope of the exercise and completion requirements

  1. Translate the programme title “Building a unified file design and coded institutional structure” into a task, a defined scope and a reviewable output
  2. Identify the required inputs and evidence using records, their creation context, versions and access permissions
  3. Identify the data and stakeholders required from records, their creation context, versions and access permissions

Day 2: Preparing data and evidence and establishing a baseline

  1. Prepare case data for “Building a unified file design and coded institutional structure” and check its completeness and consistency
  2. Document assumptions and the source of each input in a classification plan, retention register and version controls
  3. Identify the gap between the current situation and the target outcome using metadata completeness, version integrity and retrieval speed

Day 3: Developing the solution and carrying out the specialist task

  1. Apply the following method: classifying a record and tracking its version and lifecycle to the programme case
  2. Produce the first version of a classification plan, retention register and version controls to support “Building a unified file design and coded institutional structure”
  3. Link each result to its source using classifying a record and tracking its version and lifecycle

Day 4: Testing alternatives and exceptions and reviewing the output

  1. Complete a practical case on “Building a unified file design and coded institutional structure” involving conflicting versions, lost context or an incomplete disposal request
  2. Interpret the result using metadata completeness, version integrity and retrieval speed
  3. Record discrepancies, errors, validity limits and corrective decisions in a classification plan, retention register and version controls

Day 5: Presenting the practical output and workplace transfer plan

  1. Present a classification plan, retention register and version controls resulting from “Building a unified file design and coded institutional structure” and review it with the training group
  2. Measure completion of the practical exercise using metadata completeness, version integrity and retrieval speed and trace the evidence
  3. Develop an implementation plan specifying the responsible person, deadline, approval decision and outcome monitoring mechanism

Outputs

  1. a classification plan, retention register and version controls tailored to the subject of “Building a unified file design and coded institutional structure”, with traceability of data, assumptions and decisions.
  2. Results of testing a practical case on “Building a unified file design and coded institutional structure” involving conflicting versions, lost context or an incomplete disposal request, with documented findings and how they were addressed.
  3. An implementation plan that measures metadata completeness, version integrity and retrieval speed and identifies the responsible person, deadline and review mechanism.

Who should attend

  1. Document, archive, records and compliance officers
  2. Team members assigned to implement or review “Building a unified file design and coded institutional structure” whose responsibilities relate to Records Governance, Archives and the Records Lifecycle.

Participation requirements and delivery methodology

  1. Experience or a work assignment related to Records Governance, Archives and the Records Lifecycle that enables participation in practical exercises and discussion of alternatives.
  2. Training and hypothetical data are used. Personal data and confidential documents are excluded from classroom exercises.
  3. Practical workshops, evidence reviews and case simulations addressing Building a unified file design and coded institutional structure, with the output developed progressively throughout the programme.
  4. The output is assessed for completeness, consistency of sources and its ability to measure metadata completeness, version integrity and retrieval speed.

Conclusion

The programme “Building a unified file design and coded institutional structure” concludes with a presentation of a classification plan, retention register and version controls and an explanation of the underlying evidence, decisions and alternatives. Application limits and outstanding findings are recorded and converted into a follow-up plan with a responsible person, a deadline and a clear measure.

Request participationProgramme participation requestArab Union for Human Resources Development
Programme

Building a unified file design and coded institutional structure

Dates: 2027-01-24 — 2027-01-28

Submitting a request does not confirm a place or booking. The administration will review availability, dates and arrangements.

7–15 digits. Include the country code for international contact.

Your request is saved in the visitor database and a copy is directed to [email protected].

The Union administration reviews your request and contacts you to confirm availability, dates and arrangements. Submitting a request is not final confirmation of participation.

We use the name, job title, employer, country, contact information and participation details you provide to process this request and contact you. Records are retained permanently under Union policy. You may contact the administration to request access, correction or review of a deletion request. Details and contact preferences

How do we use your information?

Your request is submitted when a save confirmation and reference number appear. The result shows the email notification status; saving the request or acceptance by the mail server does not prove inbox delivery. A request does not confirm participation, a price or a booking before the administration replies. The Union team will contact you to follow up.

← Back to the 2027 plan