Skip to content
ENS.EG

Internal Approvals: Request, Review, Approve, and a Record Afterward

31 Oct 2026

An approval is a short path with an owner at each stop: a request is filed, a person reviews it, it is approved or refused, and a trace remains of who did what and when. That is narrower than the guide to automating the whole company, and it is built as a system rather than as an automation slogan.

An internal approval today is often a message: agree the discount, or sign the purchase. The message gets lost, or someone agrees aloud and later denies it, or a person approves beyond the limit they hold. Automating this path means the request is a record with fields, every move has an actor and a time, and the final decision can be read a month later without opening old chats.

The process automation guide draws the whole company: where a step repeats and where it should leave paper. This page does not redraw that map. It is one kind of step: a request that needs yes, no, or a change, from a named person, with a limit if a limit exists. Read the guide if every department still has no path. Start here if one approval repeats every week and that is the pain.

The four stops

  • Request: who created it, which fields are required, and which file.
  • Review: who checks completeness before it reaches the decider.
  • Decision: approve, refuse, or send back, with a reason when it is not approved.
  • Trace: who made each move and when, visible to people allowed to look.

Not every request needs a review separate from the decision. In a small team the decider may also be the reviewer. Write that down so two screens are not built for one person. In a larger team, the reviewer stops an incomplete request reaching a manager who will only return it days later. The split saves time. It is not ceremony.

The limit, and the stand-in when someone is away

Many approvals have a limit: a discount above an amount, a purchase above an amount, or leave longer than a number of days you set. Under the limit a direct manager may be enough. Above it the request moves one level up. You write the numbers in the table. This article sets no default limits. Absence is a rule too: if the decider is away, who stands in, and does the stand-in see every request or one type. Without a stand-in the path stops at the first trip, and people return to the side channel the system was meant to close.

Sending back is not a refusal. Sending back means the missing field is completed and the path returns to the same decider without counting as a refusal on the report. A refusal closes the request with a reason. Mixing the two makes the report shout refusal when the manager only asked for a file.

Examples that stay inside this shape

A discount a seller requests and a person with discount authority approves. A purchase the store raises and a person who holds the budget approves. Leave a staff member raises and a manager approves. The three are the same machine with different fields. You do not need a system per department if the stops are the same. You need fields and a notice for each type. Start with the one type that hurts every week, and add the second after the team trusts that the trace can be read.

The notice reaches the owner of the next stop with a link to the request, not with a picture inside a chat. The decision is made inside the record so the trace remains. A notice without a link sends people back to copying into a message. A link without permission opens the request to the wrong person. Both are tested with real names before launch.

What we ask in order to build the first type

  • The name of the request as the team calls it.
  • The required fields and the attachments.
  • The limit table and who approves above and below it.
  • The stand-in when the decider is away.
  • Who may read the trace a month later for an internal review.

Questions about the path

Is an electronic signature required?

Not in the first version. The user name, the time, and the status are enough for many internal approvals. If you have a legal requirement for a specific signature, write it down. A signature tool is not assumed and not claimed as included.

Does it connect to current mail?

A notice can arrive by mail or by a channel you already use, as long as the decision counts only inside the record. Replying "approved" on a mail without entering the record is not a path, because the trace disappears.

Where does this sit in the company system?

If you already have a system, the screen is built there. If you do not, the path itself is a small system for this request type and can grow later. The estimate starts from one type, not from every approval at once.

The wider map is in the business process automation guide. Building the approval path starts from custom software development.

Name the first approval type through start your project. The WhatsApp button under the article can take one real request with the amount removed if you prefer.

Have an idea or a system that needs building?

Tell us about your project in three short steps. We will review it and contact you to agree on the next step.

Start a project