# How Approval Workflows Work

## How approval workflows work

TZone routes requests through the right reviewers at the right time.

The workflow depends on role, policy, amount, and coding.

### Typical flow

{% stepper %}
{% step %}

### Employee submits

The employee adds details, coding, receipts, and business purpose.
{% endstep %}

{% step %}

### Manager reviews

The manager checks business need, team context, and budget impact.
{% endstep %}

{% step %}

### Finance validates

Finance checks policy, receipts, coding, and reimbursement readiness.
{% endstep %}

{% step %}

### Final status updates

The item is approved, returned, or rejected.
{% endstep %}
{% endstepper %}

### What can affect routing

* expense amount
* department, project, or cost center
* policy rules and exception handling
* multi-step approval chains

### Best practices

* Submit complete information the first time.
* Add clear notes when an item needs context.
* Review status updates often.

{% hint style="info" %}
Returned items usually need updates. Rejected items usually need a new submission.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.techzala.com/getting-started/how-approval-workflows-work.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.