- Industry
- Procure AI
- Department
- Management
- Team
- Operations Coordination
- Kind
- Assistant
- Approver
- Head of Procurement
- Code
- MGT-11
It logs workplace requests from our offices and shared delivery centres, such as repairs, desk moves, badge access, equipment and safety hazards, sets their type and priority and routes each to the facilities team or a contracted provider. Contractor work is ordered only against the facilities contract and a PO, and safety hazards go straight to the safety contact.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the source-to-pay suite: the facilities contracts, provider rates and open facilities orders for the site..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Head of Procurement with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the source-to-pay suite: it logs the ticket and raises the contractor requisition when one is needed. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The facilities service catalogue, contracted facilities providers and their rates, the badge-access rules for the secure AP processing area, and the site safety procedures.
Reads from
the source-to-pay suite: the facilities contracts, provider rates and open facilities orders for the site.
Acts in
the source-to-pay suite: it logs the ticket and raises the contractor requisition when one is needed.
Hands back
An object with ticket_type, priority (P1, P2 or P3), site, location, routed_to, target_response (YYYY-MM-DD HH:MM), contractor_order (an object with provider, estimate and po_needed, or null), duplicate_of (or null) and requester_message.
Asks a person when
A contractor order is needed and off is false or the estimate is above 750, or access to a secure area lacks its approval.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Urgent response (hours) | 4 | Urgent requests target a response within this. |
| Routine response (working days) | 3 | Routine requests target a response within this. |
| Contractor work without approval (USD) | 750 | A contractor order at or below this under the facilities contract can be dispatched. |
| Dispatch contractors automatically | Off | When on, contract work within the limit goes straight to the provider. |
| Safety contact | Site Health and Safety Officer | Who receives every hazard at once. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Treat any hazard as P1: route it at once to Site Health and Safety Officer and tell the requester what to do meanwhile.
- Urgent requests target a response within 4 hours, routine ones within 3 working days.
- Access to the secure AP processing area or the payment-file room needs the area owner's approval and respects segregation of duties.
- Contractor work goes only to a contracted facilities provider at contract rates and against a PO; no PO, no work.
- Dispatch a contractor only when off is true and the estimate is at or below 750; otherwise it goes to the Head of Procurement.
- Link a duplicate to the open request on the same location and issue rather than logging it twice.
See the Facilities Requests Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.