> ## Documentation Index
> Fetch the complete documentation index at: https://docs.assetinfinity.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Cost Overrun Requests

> The paper a project goes back to its committee on when it will cost more than its approved approval note sanctioned — raised from the note, written over several sittings, and approved in a workflow of its own.

Cost Overrun Requests is where you ask the committee again when a project will cost more than its approved [approval note](https://docs.assetinfinity.ai/finance/capex-approval-notes.md) sanctioned: how much over, in what proportion, under which policy and why. The committee is not asked to approve the project, which it already did, but to accept the overrun.

**Cost Overrun Requests** is under the **Capex** heading in the **Finance** group of the navigation, for people holding **View the Cost Overrun Requests**. Raising, writing and sending an overrun needs **Raise, write and send a cost overrun on an approved approval note**. You see the overruns on the units you can reach.

> [!NOTE]
>
> If you don't see this in your navigation, your administrator can switch the module on under **Administration → Modules** (it is part of **Capex planning**), or it may not be included in your plan.

## Raising an overrun

An overrun is not started on this screen. It is raised on [Capex - Approval Note - (P/ S/ F)](https://docs.assetinfinity.ai/finance/capex-approval-notes.md#the-list), with **Raise Cost Overrun** in the row's **⋯**, once the note is **Approved**. The new overrun opens for you to write.

![Cost overrun requests, with one approved cost overrun for replacing an air compressor](https://mintcdn.com/assetinfinity/Nh_CqE52Bv2V-FCv/images/finance/capex-cost-overruns-light.png?fit=max\&auto=format\&n=Nh_CqE52Bv2V-FCv\&q=85\&s=da214cdf1a1311b1700f9b84761d3253)

A note has one overrun at most, whether it is still being written, approved or rejected. Once it has one, the note's **⋯** offers **Open Cost Overrun** in place of **Raise Cost Overrun**. A proposal with several notes can have an overrun on each.

## The list

**Search the cost overruns**, saved **Views**, **Filter**, **Columns** and **Amounts shown in** work as on any register, and **Export** (needs **Download a plan's proposals and phasing as a spreadsheet**) downloads the rows the list is showing. The newest overrun is first.

| Column | What it shows |
| - | - |
| **SL** | The overrun's number, counted across your organisation in the order overruns are raised |
| **Request ID**, **Note No.** | The proposal, and which of its approval notes the overrun is on |
| **Overrun Status** | **Draft** until it is sent, **Sent for Approval** while a request holds it, then **Approved** or **Rejected**, with the reason under a rejection |
| **Approval Status** | The overrun's approval request, which opens it in Approvals |
| **Type of Overrun** | **Cost** |
| **Item Description**, **Unit and Location**, **Implementing Unit**, **Category (Projects/Specified/Clubbed)**, **Project Name** | What the proposal and its note decided |
| **Original Cost of Project** | The note's **Cost of project proposal** |
| **Value of Overrun** | How much more the project will cost |
| **% Overrun** | The value of the overrun as a share of the original cost |
| **Last Approved By**, **Last Approved Date** | Who last approved a level of the overrun, and when |
| **Created By**, **Created Date**, **Modified By**, **Modified Date** | Who raised the overrun and when, and who last changed it and when |

**Columns** also offers the overrun's bulleted headings, off until you turn them on. Every date and time is written to the second on a 24-hour clock.

Clicking a row opens the overrun to read, as **View Cost Overrun**. The row's **⋯** offers **Edit** where you may change it, and **Send for approval** where you may send it and it has everything it needs.

## Writing an overrun

**Edit** opens **Edit Cost Overrun**, with its SL, Request ID, note number and item description under the title. Your administrator arranges the form, and can insist on further answers, in [Form Studio](https://docs.assetinfinity.ai/config/form-studio.md) under **Cost Overrun**, which **Edit form** opens.

| Section | What it asks | Notes |
| - | - | - |
| **Project** | **SL**, **Request ID**, **Note No.**, **Approval Status**, **Type of Overrun**, **Item Description**, **Unit and Location**, **Implementing Unit**, **Category (Projects/Specified/Clubbed)**, **Budget Ref No. (In-Principle Budget)** and **Project Name** | Shown, not asked. **Type of Overrun** is always **Cost**. **Budget Ref No. (In-Principle Budget)** is left blank for now |
| **Cost Overrun** | **Original Cost of Project**, **Value of Overrun** and **% Overrun** | Only the value is typed: more than zero and at most 9,99,99,999.99. The percentage is worked out from it as you type |
| **Policy and Sanction** | **Policy Relevant to Subject Matter**, **Modification Sought to the Policy**, **Sanction/Resolution Sought** and **Relevant Board/CMC/DMC Decisions on the Matter, if any** | Bulleted text: a box with **Bullets** and **Numbering**, read back as a list |
| **The Case** | **Salient Features of the Proposal, including Background and Justification**, **Financial Implications**, **Recommendation**, **Supplementary Information, if any** and **List of Annexures, if any** | **Financial Implications** and **Recommendation** are bulleted text. The other three are document editors with pictures and PDFs, as the approval note's are; pictures and PDFs are sent when you save, with a progress line |

An overrun is written over several sittings, so nothing is required to save it.

| Button | When | What it does |
| - | - | - |
| **Save as Draft** | The overrun is not with its approvers | Saves the overrun |
| **Save & Submit** | The same, for somebody who may send it | Saves the overrun and sends it for approval. If the send is refused, what you typed is still saved |
| **Save** | The overrun is with its approvers, for the approver it waits on | Saves the overrun |

Before an overrun can be sent or approved it needs the **Value of Overrun**, and any other heading your organisation insists on in Form Studio. One still missing any says **Before it can be sent it still needs:** and names them.

## Approving an overrun

An overrun is approved in your organisation's workflow for **Cost Overrun**, set up in the [Workflow Studio](https://docs.assetinfinity.ai/config/workflows.md), level by level, sent in the name of whoever sends it; a rejection at any level is final. Where no workflow applies, sending it approves it at once, and the screen says so. Approving or rejecting an overrun does not change the note it is on, which stays approved either way.

The approver an overrun is waiting on opens it from **Approval Status**, or from [Approvals](https://docs.assetinfinity.ai/work/approvals.md). Opened from the list, it says **This cost overrun is waiting on you. Correct it here and save, then approve it in Approvals.** The approval dialog draws the overrun's form — **The cost overrun you are approving. Correct what it needs here and save it before you approve.** — with **Save cost overrun** to save what you changed. **Approve** waits until the overrun is saved and complete, and says **Before it can be approved it still needs:** with what is missing. Somebody reading a request they raised sees the same form greyed. Once an overrun is approved or rejected, nobody can change it.

> [card] [Approval notes](https://docs.assetinfinity.ai/finance/capex-approval-notes.md)
>
> The approved note an overrun is raised on.

> [card] [Change Logs](https://docs.assetinfinity.ai/finance/capex-change-logs.md)
>
> Who changed what on each overrun, and how it went through approval.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.