Skip to main content
A requisition is how somebody asks for something they need — a part, a service, an asset or anything else. It says what is needed, where, by when and why, and nothing is issued, allocated or bought for it until somebody with authority approves it. Once approved it can be answered from your stores or spare assets as readily as by an order. Requisitions is in the Procurement group of the navigation, for anybody holding View requisitions.
If you don’t see this in your navigation, your administrator can switch the module on under Administration → Modules (it is the Purchasing module), or it may not be included in your plan. Quoting (RFQs), Ordering (purchase orders) and the Catalogue are modules of their own inside Purchasing. Where one is switched off, its buttons are not offered on this screen either.
The requisition register, with one request awaiting approval and two approved and waiting to be sourced The requisition register, with one request awaiting approval and two approved and waiting to be sourced

Where a request goes next

A requisition is the first step of the buying chain. Each later step has its own screen, and the header buttons on this register take you to the neighbouring ones that your organisation uses. An organisation that answers every requisition from its stores and spare assets, and buys through another system, can run steps 1 and 2 alone. It then has no Purchase Orders in its menu and no order buttons anywhere on these screens.

The register

The register opens sorted by Needed by, soonest first, so the requests that are about to be late are at the top. Rows waiting on an approver are tinted amber and rejected requests are tinted red.

Stat strip

Toolbar

Columns

Columns also offers every other question the form asks, off until you turn them on: Request type, Department, Location, Deliver to, Required until, Maintenance plan, Charge to, Cost Center, Indirect project, Indirect task, Projects and Why it is needed. Custom fields your organisation adds to requisitions, and the usual created and updated stamps, are also available as columns. A request with no title is listed under its number.

Statuses

The statuses below are the defaults every organisation starts with. Your administrator can rename them and change the transitions under statuses and state models.
A requisition below every approval threshold goes straight from Submitted to Approved with no signature. An approver who sends a requisition back for revision returns it to Draft, where only the person who raised it can correct it and send it again to the approver who asked. A requisition moves to Fulfilled by itself when its last line is answered, whichever way that was. A Fulfilled requisition reopens to Approved when something comes back — stock given back, or a spare returned to the pool — and a line is asking again. The moves into Closed and Awaiting booking are made by the product itself when the request is raised, and out of Awaiting booking once its last asset is booked or its Required until has passed.
Approved does not mean bought. It means somebody with authority agreed the need may be met. Whether it comes from a store, a spare asset or a supplier — and which vendor and at what price — is decided on Sourcing, RFQs and the purchase order.

Raising a requisition

Click New request on the register, or New → Requisition from the header on any screen. The form is titled New requisition. A new requisition starts at the site and location you are Based at on your workforce record, which you can change; one raised from a job, a plan or a reorder starts where that record is. A requisition goes up with its lines in one step — a request with no lines is one nobody can price. Checking out the Catalogue’s cart opens the same form with the cart’s lines already in it. The New requisition form, with the header fields above and one blank line below The New requisition form, with the header fields above and one blank line below Your administrator arranges the whole form — which questions it asks, in what order, which must be answered and what each starts on — with Edit form, which opens Form Studio for this record type. The lines are a form of their own there, opened with Edit line form beside them. The tables below describe the form as every organisation starts with it.

Header fields

Where your organisation has set a starting answer for a question in Form Studio, a new requisition opens with it filled in, and you can change it. Catalogue limits count against the person a request is for, and its Cost Center is theirs. The person a requisition is for can follow it under My requests on the Catalogue even without access to this register.

Request type

Where your organisation has set up requisition types, the form asks Request type — Decides what each line may ask for. It decides what each line may ask for: What it is on every line offers only the kinds the type allows, and is fixed where it allows one. Only the types offered to your roles are listed. You can leave it on Any request for a request of no particular type, unless your organisation insists on a type in Form Studio; then one has to be chosen, and where only one type is offered to you it is chosen for you. Choosing a type moves any line it does not allow onto the first kind it does, and clears prices already typed where the type leaves them to the buyer. Where your organisation has switched the Copilot on, Describe a new requisition out loud or Read a new requisition off a photograph or a document reads a quotation or an email and fills in the header for you. It never invents quantities: lines are always typed or pulled.

Where this came from

Lines

Click Add line for each item. Remove a line with the bin icon on its row. Each line is two rows: what is being asked for, then how many and at what price. Where your organisation asks more of each line, a third row follows. What it is comes first, because it decides what the line asks next. A line from the catalogue is drawn differently: its description says From the catalogue, at the price procurement agreed, and only its quantity can be changed. Its unit, its price (Each) and its Line total are the item’s. The form adds up an Estimated total — labelled as an estimate, not a price — under the lines. When the requisition is raised from a maintenance plan that covers several assets, a Buy enough for every asset in scope tick box multiplies each quantity from one round’s worth to the whole fleet. Click Raise request to save. It is held, with a Still needed line saying what is missing, until every required question — a part line’s part, an asset line’s asset and an asset category line’s category included — has an answer. The requisition is created as a Draft, unless it books assets as described below. If any attached file fails to upload, the requisition is kept and you can choose Go to the request or Try those again, which resends only the files that failed.

Booking assets by category

A line that is An asset category is answered by booking assets your organisation already holds, not by buying them. When the request is raised, that many free assets of the category are booked at the request’s location — or anywhere at its site where it names no location — from Needed by to the end of Required until. Both dates are then required, and Required until is asked even where your organisation has taken it off the form. A request type can switch this off, and then the line is an ordinary open line that goes to Sourcing. Once the site and both dates are chosen, the hint beside the category says how many are free there for those dates. Fewer free than asked for does not stop the request: what is free is booked now, and the hint says how many more will wait for a booking. A category your organisation’s booking settings never offer for booking is not listed, and one already on the line says why it will be refused.

Booking the rest

A request with assets still to book shows how many in the register’s To book column, and on each waiting line inside it, with Create booking for people who may raise bookings, and for the person who raised the request or is it for where they may raise requisitions. Create booking opens New booking for that line — For the requisition, its line and its category — with Line to book where more than one line is waiting. Every box starts on what the request said: the Kind, What it is for (left blank, it is named for what it holds), Booked for, From, Until, Purpose, Site and Charge to, with Projects and tasks or Which one under it. What is being held lists the free assets of the category for those dates, with how many you have chosen against how many are still to book; where none is free yet, the request keeps waiting. Raise it books them. You can change any box. A box changed from the request says what the request had, with Put it back, and the form then asks Why it differs from the request, which is recorded with the changes on both the booking and the requisition.

Inside a requisition

Open a requisition from the register to see everything about it on one screen. An approved requisition, showing its approval, lines, sourcing, details, budget and history An approved requisition, showing its approval, lines, sourcing, details, budget and history

Header actions

Approval

The Approval section shows the chain itself, not just the current step: every step in order, its threshold rule (for example Over 500), whether it is pending, approved or rejected, and who signed and when, with any comment they left.
  • Before submission it says Not submitted yet — the chain is built at submission, from the requisition’s value against your organisation’s approval rules. See workflows.
  • A requisition under every threshold says No signature was required.
  • A step nobody can clear as configured says so, rather than waiting silently.
Each step carries its level (Level 1, Level 2 and so on; steps decided side by side share a level) and says in words where it stands — for example Waiting, Waiting its turn, Rolled back, Sent for revision or Asked again after a rollback — so you can see who signs next. Under the chain, Rollbacks and revisions lists every time the requisition was rolled back, sent back for revision or sent again, who did it, and what changed, across every request it has had. Somebody holding the step’s permission sees Approve and Reject on it, and, where your workflow allows them, Send back for revision (to whoever raised it, who alone may correct it and send it again) and Rollback (to the level before). Approve opens a short panel first — it says your signature is recorded against your name and cannot be taken back, offers an optional A note, and signs when you press Approve it. Reject asks Why is it being rejected? — the person who asked has to know what to change. Approvals can also be decided from Approvals.

Lines

Sourcing

Once a requisition is Approved, a Sourcing section lists each line with Asked for and Still needed, and what has already been done for it (on order, from stock, allocated, called off). The buttons on each line are the same as on Sourcing: The Answer from stock dialog, choosing which store a bearing comes out of The Answer from stock dialog, choosing which store a bearing comes out of

Details

Requested by, Requested for (only when it is for somebody else), Request type (where it was raised as one), Site (with the location beside it), Department (where it names one), Deliver to, Needed by, Required until (where it was given), Estimated total, Submitted, Approved (who signed it off and when, where somebody did), For (the job or plan), Charge to (naming the projects, where it is charged to a project), Cost Center and, for a request charged to its Cost Center, the Indirect project and task it is booked through — followed by the justification. A draft with no justification says Why it is needed has not been said yet. A withdrawn request says why under Withdrawn:. Below the details are the answers to your organisation’s own questions, which can still be changed while the request is a Draft, and Projects, listing each project and task the request is bought for, where it names any.

Budget

A requisition can name the budget head its spend belongs to with Name a head. Only heads with nothing carved out under them are offered, each showing what it has left. A requisition reserves nothing on its own. The order raised from it inherits the head and reserves its value when the order is submitted — so naming the head here saves the buyer finding it again. If the head has less left than the requisition is estimated at, the screen warns you, but nothing is refused at this stage.

History

Every status the requisition has passed through, with who moved it, when, and how long it spent in the previous status.

Activity

Everything that happened to the request rather than only its status moves — for example a booking raised for one of its lines on other dates, another machine or another payer, with the reason the booker gave — and any comments. People holding the permission to view the audit trail also see the Audit trail, field by field.

Catalogue

Choosing agreed items with a picture and a price, and checking out as a requisition.

Sourcing

Answering approved lines from stock and spares before anything is bought.

Requests for quotation

Asking vendors to price an approved requisition.

Budgets

What a head has available, and when an order reserves against it.

Reorder recommendations

Where reorder-point requests come from.