CoreConstruction operating system

How approvals work

Who gets asked to approve a document, in what order, and how Core chooses them.

Who does this: Everyone

Indents, daily reports, purchase orders, measurements, client bills, vendor bills, work orders, subcontractor bills, variations, payroll, leave, petty cash and stock count corrections all go through approval before they take effect.

Who is asked#

When you submit a document, Core reads the approval rules for that kind of document and its amount. Each step names a position, such as project manager. Core then looks for the nearest person holding that position:

  1. At the place the document belongs to (the site or store).
  2. If nobody holds it there, at the place above (the project), then the region, then the head office.
  3. If nobody holds it anywhere above, the director decides.

So a site's indent goes to that site's project manager, not to every project manager in the company.

Steps in order#

A rule can have several steps (for example project manager, then director). The next step is asked only after the one before approves. Anyone at any step can send it back with a reason; it then returns to the person who raised it.

Limits and amounts#

Rules can depend on the amount. For example, purchase orders up to ₹5 lakh need the project manager, and above that also the director. The amount is the document's total including tax.

Never approving your own#

Core never asks you to approve something you raised. If you are the only holder of the position, the step moves to the next person up.

What happens on approval#

The document takes effect at once: stock moves, the BOQ progress updates, the ledger posts, or the order can be sent to the vendor. The person who raised it is told.