> For the complete documentation index, see [llms.txt](https://docs.travelauthority.gov.zm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.travelauthority.gov.zm/getting-started/roadmap.md).

# RoadMap

This roadmap guides you through the key layers of the Travel Authority System: the User Interface Layer, Workflow & Logic Layer, and Data & Reporting Layer.

## **Overview**

The Travel Authority System is structured across three key layers:

* The **User Interface Layer** ensures a smooth and intuitive user experience.
* The **Workflow & Logic Layer** ensures structured, policy-compliant processing of requests.
* The **Data & Reporting Layer** ensures accurate tracking, transparency, and informed decision-making.

## **User Interface Layer**

The **User Interface Layer** focuses on how users interact with the system. It includes all visual components, navigation elements, and user interactions that make the system intuitive and easy to use.

### **Dashboard & Navigation**

* Dashboard with summary cards (Total Requests, Approved, In Progress, Rejected).
* Navigation Bar (Dashboard, My Profile, Reports, Documentation, Settings and Log Out button).
* Header (Search Bar, New Request Button, Notifications Button and Light/Dark Mode Switch).

<div><figure><img src="https://2831731376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWZTrHtnwhk3hnhzBxC9p%2Fuploads%2F6tZLKbmAVoTgDtpkXebG%2FDashboard%20UI.png?alt=media&amp;token=aa39d693-ab88-4257-b261-fd7a2240ba16" alt=""><figcaption><p>Dashboard for a user with the Client role</p></figcaption></figure> <figure><img src="https://2831731376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWZTrHtnwhk3hnhzBxC9p%2Fuploads%2FeDYPEnX1j6I2wn0BW3o5%2FDashboard%20UI%20(DD).png?alt=media&amp;token=dfa2c63d-f089-43dd-b98d-57ff78478c7b" alt=""><figcaption><p>Dashboard for a user with the Department Director role</p></figcaption></figure></div>

### **Request Interface**

* Request creation forms (Local, International, Workshop)
* Request Details page (travel info, budget, attachments, activity log)
* Action buttons (Approve, Reject, Assign Officer, Upload Documentation)

<div><figure><img src="https://2831731376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWZTrHtnwhk3hnhzBxC9p%2Fuploads%2Fu3idpk7c880GsNYx3HwV%2FRequest%20Type.png?alt=media&amp;token=df4b5707-64b5-44cc-a6f7-84cb428e495a" alt=""><figcaption></figcaption></figure> <figure><img src="https://2831731376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWZTrHtnwhk3hnhzBxC9p%2Fuploads%2Fa8kVfrGayuEBZLxkfGMz%2FRequest%20Details%20(page).png?alt=media&amp;token=7e076222-c06e-45aa-86d7-5b02881a983c" alt=""><figcaption></figcaption></figure></div>

### **User Experience (UX)**

* Responsive design for different devices
* Clear visual indicators (status, roles, workflow stages)
* Interactive components (buttons, modals, toggles)
* Notifications and alerts

## **Workflow & Logic Layer**

The **Workflow & Logic Layer** manages how requests move through the system and how decisions are made at each stage.

### **International Travel Request**

{% stepper %}
{% step %}

#### **Request Submission**

The traveller completes and submits a travel request form detailing the purpose of travel, destination, dates, and estimated costs for approval.
{% endstep %}

{% step %}

#### **Department Director Consideration**

Evaluates the request, assesses its necessity and alignment with departmental priorities, then approves or rejects it.
{% endstep %}

{% step %}

#### **Sent to Director - Finance for Action**

The approved request is forwarded to the Finance Director to verify budget availability, validate cost estimates, and authorize funding.
{% endstep %}

{% step %}

#### **Controlling Officer Consideration**

The Controlling Officer exercises oversight by examining the financial authorization and ensuring the request complies with government travel policies and regulations before it proceeds.
{% endstep %}

{% step %}

#### **Secretary to the Cabinet Consideration**

Evaluates the request, ensuring it aligns with national priorities and cabinet policy.
{% endstep %}

{% step %}

#### **Travel Office Processing**

The Travel Office handles all logistics — booking flights, accommodation, and insurance — and issues travel advance payments and relevant travel documents to the traveller.
{% endstep %}
{% endstepper %}

### **Local Travel Request**

{% stepper %}
{% step %}

#### **Request Submission**

The traveller completes and submits a travel request form detailing the purpose of travel, destination, dates, and estimated costs for approval.
{% endstep %}

{% step %}

#### **Department Director Consideration**

Evaluates the request, assesses its necessity and alignment with departmental priorities, then approves or rejects it.
{% endstep %}

{% step %}

#### **Sent to Director - Finance for Action**

The approved request is forwarded to the Finance Director to verify budget availability, validate cost estimates, and authorize funding.
{% endstep %}

{% step %}

#### **Controlling Officer Consideration**

The Controlling Officer exercises oversight by examining the financial authorization and ensuring the request complies with government travel policies and regulations. As the final approver for local travel, the Controlling Officer either grants approval for the travel to proceed or rejects the request, at which point the process concludes.
{% endstep %}
{% endstepper %}

### **Workshop Request**

{% stepper %}
{% step %}

#### **Request Submission**

The traveller completes and submits a travel request form detailing the purpose of travel, destination, dates, and estimated costs for approval.
{% endstep %}

{% step %}

#### **Department Director Consideration**

Evaluates the request, assesses its necessity and alignment with departmental priorities, then approves or rejects it.
{% endstep %}

{% step %}

#### **Sent to Director - Finance for Action**

The approved request is forwarded to the Finance Director to verify budget availability, validate cost estimates, and authorize funding.
{% endstep %}

{% step %}

#### **Controlling Officer Consideration**

The Controlling Officer exercises oversight by examining the financial authorization and ensuring the request complies with government travel policies and regulations before it proceeds.
{% endstep %}

{% step %}

#### **Secretary to the Cabinet Consideration**

Evaluates the request, ensuring it aligns with national priorities and cabinet policy.
{% endstep %}
{% endstepper %}

### **Role-Based Actions**

* Assigning officers (Accountants, Travel Officer, Ticketing Officers)
* Approving, rejecting, or requesting corrections
* Budget preparation and review
* Travel logistics processing

### **Business Rules & Logic**

* Role-Based Access Control (RBAC)
* Conditional actions (Approve, Reject, Correction)
* Budget validation and financial checks
* Priority handling through Ticketing

### **Notifications & Alerts**

* Real-time notifications for all workflow actions
* Assignment notifications
* Budget updates and approvals
* Request status changes

## **Data & Reporting Layer**

The **Data & Reporting Layer** manages how data is stored, processed, and presented for analysis and decision-making.

### **Reporting & Analytics**

* Quarterly Reports
* Distribution Reports
* Travel Expenditure Reports
* High Flyers Reports
* Top Destinations Reports
* Institutional and Departmental Reports

<div><figure><img src="https://2831731376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWZTrHtnwhk3hnhzBxC9p%2Fuploads%2FHz0TkhqVScZYq3fLOhMj%2FReports%20(SC).png?alt=media&amp;token=6d214b76-504e-42a6-b178-37bc4e12c55c" alt=""><figcaption><p>Reports Dashboard for a user with the Secretary to the Cabinet role</p></figcaption></figure> <figure><img src="https://2831731376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWZTrHtnwhk3hnhzBxC9p%2Fuploads%2FlXZ5fuiCDx3WossSUA4K%2FReports%20(DTO).png?alt=media&amp;token=d8bbd611-ae23-4424-80f3-122041cd6175" alt=""><figcaption><p>Reports Dashboard for a user with the Director - Travel Office role</p></figcaption></figure></div>

### **Compliance Data**

Compare institutional compliance against required travel-approval and reporting standards.

* Rank institutions by completed approvals, supporting documents, and timely submissions.
* Identify low-compliance institutions that need follow-up, training, or corrective action.
* Filter results by reporting period, institution, department, or travel-request type.

For example, an institution with complete documentation and on-time submissions ranks highly. An institution with frequent missing attachments or overdue reports ranks lower.

{% hint style="warning" %}
Access to the Reports module depends on a user's role. See **User Roles & Permissions** for more details.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.travelauthority.gov.zm/getting-started/roadmap.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.