CloudScaff questions and answers
Returns over-returns and reconciliation
Answers to 14 questions about returns over-returns and reconciliation.
14 questions
Questions in this topic
14 answersHow do we return equipment from a site?
Create a return against the originating site and record the equipment coming back. The return can follow a site-initiated collection process or be handled by the yard when the load arrives, depending on your agreed workflow.
Check the quantities and allocate items to the appropriate condition before completing the process. Serviceable equipment, material needing maintenance, damaged items, and unexplained extras should not all be treated as immediately available stock.
Does the site have to request a return before a truck comes back?
No. CloudScaff supports a yard-led return process for operations where equipment is collected or arrives without a formal site request.
The yard still needs to identify the source site and record what was actually received. This is useful when the first reliable count happens during unloading rather than before the truck leaves the project.
Can we schedule a collection from site?
A structured return workflow can include arranging the collection and recording the release and receipt of the equipment. This gives the site and yard a clearer view of where the return is in the process.
Recording a collection date or transport detail is not the same as a complete fleet scheduling system. If you need route planning, driver allocation, or a dispatch calendar, include those requirements in your product review.
Can we return only part of the site's equipment?
Yes. Returns can be partial. Record only the quantities coming back, leaving the remaining stock allocated to the site.
This suits phased dismantles, surplus equipment collections, and projects that remain active after some material is recovered. Check the residual balance afterwards so the team understands what is still expected to be on the project.
Can a project have several returns?
Yes. Equipment can return over multiple loads or at different stages of a project. Each return contributes to the site's recorded movement history.
Use the actual quantities for each load and avoid re-entering a previous return. At project closeout, review the remaining site balance along with unresolved transfers, losses, and over-returns rather than assuming the last truck cleared every item.
Can we count the equipment after it arrives in the yard?
Yes. The yard-led workflow supports recording and checking returned equipment at the yard. Your team can use the return record and supporting count information to establish the final quantities.
Keep unverified counts distinct from the completed return. Completing the process before sorting and checking the load can make equipment appear available even though the quantities or condition have not been confirmed.
What is an over-return?
An over-return occurs when the quantity coming back exceeds the quantity recorded against the site, or when an item is returned that the site was not recorded as holding.
For example, a site may be recorded as holding 10 units but return 11. That extra unit needs review because it may represent an unrecorded transfer, an earlier count error, supplier equipment, or another issue rather than a genuine increase in owned stock.
How does CloudScaff handle over-returns?
Extra quantities can be recorded through the over-return workflow for review. An authorised person can investigate the source and determine how the exception should be resolved.
This separates ordinary return processing from a decision that may change overall stock. Keep notes and supporting evidence where useful so the reason for accepting, correcting, or otherwise resolving the extra quantity remains understandable later.
What if equipment comes back from the wrong site?
Investigate whether the equipment was moved between sites without a recorded transfer or whether the return was assigned to the wrong project. Compare the relevant delivery, transfer, and return records before changing balances.
Do not automatically increase stock because one site appears to have returned extra equipment. If it remains recorded on another site, accepting the extra as new stock could leave the business counting the same equipment twice.
What if an item is returned that was never listed on the site?
Record it as an exception for review rather than forcing it into an unrelated line item. The return workflow can account for components that were not part of the site's recorded inventory.
Check the item's identity and ownership before accepting it into available stock. It may belong to another supplier, have been transferred informally, or result from a resized component that needs a different reconciliation treatment.
Can we attach a paper count sheet to a return?
Yes. Supporting count sheets and photographs can provide evidence for the quantities entered during return processing.
Use the attachment to explain the final record, not as a substitute for entering the actual quantities. If the count changes during checking, make sure the approved return and the retained evidence tell a consistent story.
What happens when the returned quantity differs from the expected quantity?
Review the difference before treating it as loss or new stock. The cause might be a partial return, a pending transfer, a count error, damage, or an over-return.
Record the quantity actually returned and use the appropriate process for any remaining exception. This keeps the site balance meaningful and makes it easier to distinguish equipment still on the project from equipment that has genuinely become unaccounted for.
How do we know what is still outstanding on a project?
Review the site's inventory balance together with its movement history. Deliveries and incoming transfers add equipment to the site's record; completed returns and outgoing transfers account for material leaving it, with other adjustments handled through their relevant workflows.
If the remaining quantity seems wrong, trace the underlying records. A pending or unrecorded movement can explain a difference that would otherwise look like missing equipment.
Can CloudScaff help us reconcile a project before closing it?
Yes. Site inventory, return records, transfers, and exception information give you a basis for checking what has been accounted for and what remains unresolved.
Before closing a project, review outstanding equipment and incomplete movements. Document how any damage, loss, supplier stock, or over-return was resolved. Closing the project should be the result of that review, not a substitute for reconciling it.
No matching questions. Try another search or topic.