In short

Broken lights, a boiler that won't fire, a parcel nobody signed for and a supplier who never called back. Office requests arrive by email, chat and in passing, and are easy to lose. The improved process logs every request in one place, sorts it, drafts the message to the right supplier or landlord and keeps track until it is done.

The system keeps the list and drafts the chasers. Any order, call-out or cost is approved by a person before it goes ahead.

  • Sector Small and medium-sized organisations
  • Role Office manager
  • Job Handling facilities requests and deliveries

The job today

The office manager keeps requests in their head, a notebook and their inbox. Some go to the landlord, some to a contractor, some to a colleague. Deliveries arrive while they are out. Chasing happens when someone complains, and there is no record of how long things took or what they cost.

Where it breaks

  • Requests come in by too many routes and some are forgotten.
  • Nobody can see what is open, who it is with and how long it has been waiting.
  • Suppliers and landlords are chased late or not at all.
  • Spending on repairs and supplies is hard to see until the invoice arrives.

The improved process, step by step

  1. Log every requestRequests by email, form or chat are recorded in one list with who asked, what for and when.
  2. Sort and routeEach request is given a type and an owner using simple rules: landlord, contractor, IT, supplies or the office manager.
  3. Draft the message AI preparesAn assistant drafts the request to the supplier or landlord with the details filled in, and records any delivery to expect.
  4. A person approves messages and costs A person approvesThe office manager approves each message before it is sent, and anything that commits money, books a contractor or places an order.
  5. Chase what is overdueRequests that pass their expected date are listed, with a chaser drafted for approval.
  6. Send a weekly digestA short digest shows what was done, what is open and what is waiting, for the office manager and, if wanted, the team.
Office, facilities and deliveries requests at a small office: process diagramSteps: 1. Log every request; 2. Sort and route; 3. Draft the message (AI prepares); 4. A person approves messages and costs (a person approves); 5. Chase what is overdue; 6. Send a weekly digest 01 Log every request 02 RULES CHECK Sort and route 03 AI PREPARES Draft the message 04 A PERSON APPROVES A person approves messages and costs 05 RULES CHECK Chase what is overdue 06 Send a weekly digest
The process at a glance. Teal steps are prepared with AI help; the amber step is where a person approves.

Where a person must approve

A person approves

Every message, order, booking and cost is approved by a person first. Anything that sends, changes or cannot be undone waits for that approval.

Health and safety issues are always passed straight to a named person, not queued.

The data boundary

  • The system can read requests sent to it and your list of approved suppliers. It cannot place orders or make payments.
  • Messages to suppliers are sent from your own account after approval.
  • Only the details needed for the request are shared with a supplier.
  • Every request, message and approval is logged.

Checklist before you start

  • We know every way people raise office requests today.
  • We have a list of approved suppliers and contacts.
  • We know who can approve spending, and up to what amount.
  • We know which issues are health and safety matters.
  • We know what our lease says the landlord must fix.
  • We are happy to share a weekly digest with the team.

This is an illustrative walkthrough of a common pattern. It is not a client case study, and the details will differ in your organisation.