For ALTRAD Singapore, an inventory total was only the beginning. The team needed to understand which components were in each warehouse, which were allocated to sites and projects, and how that translated into the tonnage used for reporting.
During its CloudScaff onboarding discussions, ALTRAD described an inventory of approximately three million components weighing 12,043 tonnes, spread across three warehouses and its site operations. Those figures describe the stock discussed during setup. Managing that scale meant preserving the detail behind every total: item codes, quantities, weights, locations and movements.
The implementation brought those records into CloudScaff, alongside a move from separate Excel scaffold registers towards a shared digital process. ALTRAD now uses both inventory management and scaffold registers in its day-to-day operations.
| ALTRAD Singapore at a glance | Reported scope |
|---|---|
| Inventory discussed during onboarding | Approximately three million components; 12,043 tonnes |
| Warehouse structure | Three warehouses, including a primary servicing warehouse and two satellite storage facilities |
| Current use | Inventory management and scaffold registers |
| Customer spokesperson | Maha Balasubramanian, Yard Supervisor |
Bringing separate records into a consistent structure
Before onboarding, ALTRAD’s inventory information had been held across spreadsheets associated with different business entities. The team had already begun consolidating those records into a single sheet. It wanted a clearer structure for reporting, with materials brought under ALTRAD Services Singapore Private Limited.
The spreadsheet contained more than a list of equipment. It recorded component codes, descriptions, weights, warehouse stock and quantities allocated to different sites. Some codes reflected supplier references, so retaining them mattered. The weights also needed to remain consistent with the values ALTRAD used to calculate its reported tonnage.
The team distinguished between permanent site operations, temporary projects and rental allocations. A project could sit within a larger site while still needing its own material allocation. That made the relationship between the physical location and the work being performed an important part of the setup.
Starting with the stock ALTRAD already knew
CloudScaff’s onboarding began with ALTRAD’s existing inventory data. The team reviewed how the spreadsheet would map into the system, keeping the component descriptions and reporting values recognisable to the people who used them.
In the following setup session, the imported inventory and site allocations were reviewed together. A key decision was to represent the three warehouses as separate inventory locations, so available warehouse stock could be distinguished from material already issued to a site.
This reflected how the operation worked: one primary warehouse handled servicing, supported by two satellite storage facilities. The training then covered deliveries, returns, transfers and the distinction between available stock and material requiring attention. The starting records provided a basis for tracking subsequent movements through the system.
Making each movement part of the record
The training focused on the handoffs between site teams and the warehouse. Site users worked through requesting material, receiving a delivery, returning components and transferring equipment between sites. Warehouse users covered the corresponding dispatch and receipt steps.
Checking quantities was central to that process. In the delivery walkthrough, the team discussed checking the delivery note against the material received before signing for it. Split deliveries were also covered, allowing a request to be fulfilled over more than one load while keeping the outstanding balance visible.
For returns, the workflow followed the material from the site’s request through collection and warehouse receipt. Transport information, signatures and supporting records could remain attached to the movement. Components needing maintenance or further assessment could be handled separately from stock ready for another job.
Site-to-site transfers received particular attention. Material moving directly between projects still needed a record at both ends. The walkthrough showed how the sending site retained a transfer-out record and the receiving site a transfer-in record, with quantities and movement history available for review.
Reporting in quantities and tonnes
ALTRAD’s reporting requirement was explicit: the operation needed both component quantities and the total tonnage on each site. A weight total alone would not explain which items were there, while a component count alone would not provide the tonnage used in reporting.
The June support call showed the questions becoming more specific as the team used the system. One participant wanted to identify returns for an individual site and understand how many had been made during the year. The session covered reference codes, return records and filtering movement reports, including PDF and Excel output.
Maha Balasubramanian, Yard Supervisor, was also asked about a movement update he had requested and checked. His response was brief and specific:
“Okay, this one is working for me.”
Maha Balasubramanian, Yard Supervisor, ALTRAD Singapore
That feedback concerned the particular movement update discussed in the call. He then raised a further reporting requirement: selecting periods for the tonnage shown on a site dashboard. The exchange illustrates how ongoing support was being shaped by the questions arising in daily use.
Extending the approach to scaffold registers
Inventory was one part of the requirement. ALTRAD also had scaffold registers in Excel, with different sites using different layouts. During setup, the team discussed using a common template to bring those existing registers into CloudScaff.
The conversations established why the detail mattered. Teams needed to distinguish locations within a larger site, understand which scaffolds were approaching inspection, and review scaffolds that had been standing for an extended period. They also raised requirements around inspection checklists and temporary off-hire periods.
These discussions helped define the scaffold-management work alongside the inventory rollout. Training was staged around the information available and the people responsible for it. ALTRAD now uses digital scaffold registers alongside inventory management in its daily operations.
Keeping responsibility clear as more people joined
The rollout included warehouse-focused training and separate sessions for site teams. Access was organised around user permissions and assigned sites, so the training could focus on the actions relevant to each person’s role.
Traceability also mattered when responsibilities changed. During training, ALTRAD requested a separate login for the colleague covering the warehouse supervisor’s duties, so the records would show who had carried out the transactions. This was a practical example of making individual responsibility part of the digital workflow.
What changed for the operation
| Starting point | Position established through the rollout |
|---|---|
| Inventory information consolidated from separate spreadsheets | Imported component records and allocations across three warehouse locations and sites |
| Site scaffold registers in different Excel layouts | CloudScaff scaffold registers now used in daily operations |
| Quantities and tonnage organised in spreadsheet columns | Shared inventory records, with movement reporting reviewed during support calls |
| Training needed across warehouse and site responsibilities | Separate sessions covering each team’s part in deliveries, returns and transfers |
ALTRAD’s story is about connecting the detail of its operation: the component, its warehouse or site, the movement that took it there, and the people responsible for recording it. CloudScaff provides the shared inventory and scaffold workflows around which those teams now work.
Based on ALTRAD’s onboarding, training and support calls, with current use confirmed by CloudScaff in October 2026. Inventory figures describe the stock discussed during onboarding.