> ## 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.

# The cost overruns: the papers a project goes back to the committee with when it will cost more than its approved…

> The cost overruns: the papers a project goes back to the committee with when it will cost more than its approved approval note sanctioned, a row per overrun. overrun_no is its SL, one count across your organisation, 1 for the first raised and one more for each raised after. An approval note may have several; capex_approval_note_id says which note a row overruns (see capex_approval_notes), note_no which of its proposal's notes that is, and capex_plan_line_id the proposal. overrun_type is what is overrunning, always COST.

What the note and its proposal decided is read off them and cannot be changed here: scheme_code (the Request ID), the unit and location (site_name, location_name), implementing_unit_name (the proposal's location, or its unit where it names no location), category (PROJECT, SPECIFIED or FLEXIBLE), item_description (as the consolidated plan has it), project_name (the note's) and original_cost_amount (the Original Cost of Project: the note's Cost of project proposal).

What the overrun says is its own. overrun_amount is the Value of Overrun, more than zero and up to 99,999,999.99, null until it is given, and overrun_percent is it as a percentage of original_cost_amount, to two places, null until both are known. policy_relevant, policy_modification, sanction_sought, relevant_decisions, financial_implications and recommendation are bulleted text: plain text a line at a time, a point being a line that starts "• " or "1. ". background (the Salient Features of the Proposal, including Background and Justification), supplementary_information and annexures are documents: markup with pictures and PDFs named by file id, as a capex proposal's justification is.

The overrun is approved in a workflow of its own, sent with submit_capex_cost_overrun once it is written; overrun_needs lists the columns it still needs before it can be sent or approved, empty when nothing. overrun_status is OPEN until it is decided, APPROVED when the last level approves it (or at once when sent with no workflow to ask) and REJECTED when a level rejects it, which is final, with overrun_status_reason what was said. request_id and request_display_status are its approval request, the open one where there is one; last_approved_by_name and last_approved_at who last approved a level of it, and when. may_edit says whether you may change it now: while it is with its approvers only the approver it waits on may, and otherwise anybody holding finance.capex_cost_overrun.edit, until it is decided. may_send says whether you may send it.

created_at, created_by_id and created_by_name say when the overrun was raised and by whom. created_source says what raised it where nobody signed in did, and is null where created_by_name has the answer. updated_at, updated_by_id and updated_by_name say when it was last changed and by whom, and until then when it was raised and by whom. The last level's approval is carried out in the name of the person who sent the overrun, so on an approved overrun it is last_approved_by_name, not updated_by_name, that says who approved it.

You see every overrun if you may view cost overruns. Without that, you see one only while a step of its approval is waiting on you under your own authority.



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