CloudScaff questions and answers

Requests orders and deliveries

Answers to 18 questions about requests orders and deliveries.

← All FAQ topics

18 questions

Questions in this topic

18 answers
How does a site request equipment?

An authorised site user creates a material request for the relevant project and selects the components and quantities needed. Supporting notes or information can help the yard understand the requirement.

The inventory team then reviews the request and processes the supply. This creates a clearer handoff than a material list spread across messages, while keeping the site request distinct from what is ultimately picked and delivered.

Can the yard create a delivery without a site request?

Yes. The inventory team can create an order or delivery directly where that matches your workflow. A site request is useful when the field team initiates the need, but it is not the only starting point.

For example, the office may already have an approved material list. The responsible user can select the destination site, source stock, and quantities, then complete the appropriate dispatch steps.

Can the inventory team change a requested quantity?

The request can be reviewed before dispatch so the delivery reflects the equipment that should actually be supplied. This is useful when a request contains an error, the site changes its needs, or stock availability requires a different fulfilment plan.

Keep the reason for a material change clear. Requested, ordered, and delivered quantities should not be treated as interchangeable when reviewing what happened on the job.

Can a site request an item that is currently out of stock?

A request can identify demand even when the required equipment is not currently available. The inventory team can then decide how the requirement will be fulfilled.

That may involve waiting for stock, moving equipment from another location, arranging supplier stock, or agreeing a revised requirement. Recording demand does not mean the item has been reserved, purchased, or physically supplied.

Can we import a material list instead of entering every line?

Yes. Material lists can be prepared for the supported import workflow using mapped component identifiers and quantities. This is useful for larger lists produced in spreadsheets or exported from design and planning tools.

The mapping must identify the correct CloudScaff item and source location. Review unmatched components, duplicate codes, and quantities before dispatch. Uploading a list saves entry time, but it does not remove the need to check the order.

Can CloudScaff use a material list from scaffold design software?

A structured material export can be mapped to the CloudScaff catalogue for import into the inventory workflow. The practical work is matching the design software's item references to your equipment records and the relevant yards.

This is a file-based workflow unless a separate integration has been agreed. It should not be assumed to provide automatic design synchronisation or to generate an engineered scaffold from the imported list.

Can we print a pick list for the yard?

Yes. Pick lists help the yard identify the equipment needed for an order. They are useful when the picking team works from paper while an authorised user manages the digital transaction.

Check that the list reflects the correct order and source location. If the load changes during picking, update the delivery quantities so the final movement record matches what actually leaves the yard.

Can we reserve equipment before dispatch?

Yes. Stock can be placed on reserve as part of preparing an order. This helps distinguish equipment committed to planned work from stock available for another job.

Agree when your team should reserve items and when reservations should be reviewed. An old or abandoned order can make equipment appear unavailable until its allocation is resolved.

Can one order be supplied from more than one yard?

Yes. Delivery preparation can account for equipment coming from different source locations. This is useful when the required quantity is spread across yards or a delivery combines your stock with supplier stock.

Review the source for each line rather than assuming all equipment comes from the same place. The source information is important later when investigating balances, returns, and ownership.

Can we make a partial delivery?

Yes. You can record the quantity being delivered now while keeping visibility of the remaining requirement. This suits situations where only part of the order is available or fits on the vehicle.

For example, an order for 100 units may be delivered as 60 units first and 40 later. The important point is to record each actual delivery against the outstanding requirement rather than marking the full order as supplied at the first dispatch.

What happens to items that have not yet been delivered?

Outstanding quantities remain part of the order fulfilment process so the team can see what still needs to be supplied. CloudScaff supports split deliveries and delivery from backorders.

Review these outstanding requirements regularly. If the customer no longer needs the balance, resolve the order accordingly; if it is still required, use the remaining quantity to plan the next supply rather than relying on a separate reminder.

Can one order be delivered over several truckloads?

Yes. Split deliveries can reflect successive loads against the same underlying requirement. Record the quantity carried on each load so the delivery history explains how the order was fulfilled.

This is especially useful when the truck capacity, stock availability, or site programme prevents a single delivery. Avoid recording the total order quantity as dispatched when only the first vehicle has left.

Can we record driver, vehicle, and reference information?

Movement records can include supporting details such as references, notes, and transport information. These help your team identify the load and connect the operational record to existing paperwork.

Use a consistent convention for references such as a purchase order, dispatch ticket, or container number. Agree which fields carry those details so people can find the same information when investigating a delivery later.

Can we attach photos and paperwork to a delivery?

Yes. Supporting files can be attached to delivery records. A load photograph, signed paper ticket, or relevant document can provide useful context when a quantity or condition is questioned.

The attachment should support the structured record. If a paper ticket shows a different quantity from the system, resolve that difference rather than leaving two conflicting versions of the delivery without explanation.

Does the site have to sign for every delivery?

CloudScaff supports a workflow in which material is released and the receiving team acknowledges it. There is also an immediate-completion workflow for operations that do not require a separate receipt step.

Choose the process that matches your actual responsibility and evidence requirements, and restrict the relevant permissions. A delivery completed by the dispatching team is not the same evidence as a separate acknowledgment from the site recipient.

What if nobody is available on site to receive the delivery?

Agree in advance who may acknowledge an unattended delivery and what evidence your business requires. The configured process may involve later receipt by the site or an authorised immediate-completion workflow.

Keep the record truthful about who performed the action. Do not record an absent customer or site representative as having signed. Photographs, notes, and the transport record can help document what physically happened.

When should we mark a delivery as sent?

Complete the dispatch action at the point defined by your agreed operational process, when the recorded quantities represent the actual material being released. Reserving or picking equipment is different from sending it.

This distinction matters because a movement action can change the inventory state and what other users see. Train the team to avoid completing a delivery simply because the pick list has been prepared.

Can we compare what was requested with what was delivered?

Yes. The order and delivery workflow helps distinguish the original requirement from the quantities actually supplied and those still outstanding.

This is useful when a project reports that material is missing. Review the request, any agreed changes, the dispatched quantities, and receipt information together. That makes it easier to determine whether the issue is a backorder, a picking difference, a receipt discrepancy, or a changed requirement.

A real team, ready to help

Let’s talk about your operation.

Get help with a workflow or find out how CloudScaff fits your business.

Contact our team

Contact us

How can we help?