Skip to content
Chat with MjengoKit on WhatsApp
Construction procurement

Construction requisition management, explained.

By the MjengoKit team. Updated 7 November 2026. 7 min read.

Requisition management is the process that controls how site requests become spending: who can ask, what a request must contain, who approves it, and how it is followed through to an order and a payment. Done well, every shilling that leaves a project can be traced back to a request, a reason and an approval.

What requisition management covers

A requisition is a single request. Requisition management is everything around it:

  1. Raising the request, with the project, items, quantities, rates and reason.
  2. Routing it for approval to the right people, in the right order.
  3. Turning it into action: an LPO for a supplier, a payroll for workers, or a payment.
  4. Closing the loop: recording the delivery, the payment and the effect on the budget.
  5. Reporting what is waiting for approval, approved but unpaid, and complete.

If any step is missing, the record breaks. A request that was approved but never linked to its payment cannot tell you whether you paid for it once, twice or not at all. Broken records like these are where construction cost leakage hides.

Paper, WhatsApp, spreadsheets and software compared

Paper book WhatsApp Spreadsheet Requisition software
Easy to start Yes Yes Fairly Needs set-up
Find a request months later Hard Hard Yes, if kept up Yes
Shows who approved, and when A signature A reply in a chat Typed by someone Recorded automatically
Linked to the payment Manually No Manually Yes
Shows what is still pending No No Partly Yes
Works across several sites No Partly Partly Yes

Paper and WhatsApp are fine for a single small site with an owner who approves everything. They struggle once approvers are away from site, or when you need to prove later who agreed to what.

How to set up a requisition process in a week

  1. Day 1: list your cost types and projects. Materials, casual labour, subcontractors and overheads cover most sites.
  2. Day 2: decide who approves what. Set amount limits and keep asking, approving and paying separate.
  3. Day 3: choose the form. Use our free requisition form on paper, or set up software.
  4. Day 4: brief site staff. Explain what a complete request looks like and how fast it will be approved.
  5. Day 5: tell suppliers. Explain that you will only pay against an LPO. See how to prevent unauthorised spending for a sample letter.
  6. Days 6 and 7: run it on one site. Fix what slows people down before rolling it out to the rest.

What a good requisition contains

The project and site, the cost type, the items with units, quantities and rates, the budget line, the date needed, the reason, and the names of the person asking and each approver. Quotes for larger purchases help the approver judge the price. The requisition form guide explains each field.

Numbers to watch

Measure What it tells you Warning sign
Time from request to approval Whether approvals keep up with the site Routine requests waiting more than a day
Share of spending with a request made before purchase Whether the process is actually used Anything well below 100%
Requests rejected or changed Whether approvers are really checking Zero, month after month
Approved but unpaid amount What you owe, for cash planning Rising while progress stalls
Emergency purchases per site Whether people are going around the process A steady weekly stream from one site

Common problems and how to fix them

  • Requests raised after the purchase. Pay only against requisitions approved before the order.
  • Vague requests such as "materials for the slab". Ask for items, quantities and rates.
  • Slow approvals. Use amount limits, allow approval from a phone, and name a deputy for when approvers travel.
  • Requests with no budget line. Make the budget line a required field, so approvers can see what remains.

Requisition management in MjengoKit

MjengoKit has requisition types for materials, casual labour, subcontractors and overheads. Each request carries its items, quantities and unit costs, with an optional milestone and budget line, and moves from submitted to approved, part-paid and paid. Approvers work from one queue, and reports export to Excel. See construction requisition software.

See it working on your own numbers

Bring a week of your site requests. We will show you how they would move through MjengoKit.

Book a 20-minute demo
FAQs

Frequently asked questions

What is a construction requisition system?

A set of rules, plus a form or software, that every request to spend project money passes through: from the site request to approval, the order or payroll, and the payment.

What is the difference between a requisition and an LPO?

A requisition is internal and asks permission to spend. An LPO goes to a supplier after approval and places the order. Our guide to LPOs, requisitions and invoices explains how they fit together.

Who should be allowed to raise requisitions?

Anyone who needs to spend for the site, such as foremen, site engineers, quantity surveyors and storekeepers. Raising a request is not the same as approving it.

How quickly should requisitions be approved?

Routine requests should be decided the same day. Long delays are the main reason site teams start buying first and asking later.

Do I need software for requisition management?

Not for one small site. Software helps when you run several sites, when approvers are often away from site, or when you want each request linked to its payment.

Book a 20-minute demo and discover your spending confidence.

Bring a week of your site requests. We will show you how they would move through MjengoKit.