CloudScaff questions and answers
Getting started and moving your data
Answers to 14 questions about getting started and moving your data.
14 questions
Questions in this topic
14 answersWhat do we need before getting started?
Prepare your inventory list, yard or storage locations, active projects, opening quantities, and the names of the people who will use the system. Existing delivery notes, return forms, scaffold registers, and inspection checklists are also useful.
Choose someone internally who understands the operation and can make decisions about item names, stock balances, permissions, and workflows. That person can help resolve questions during setup and support the team after training.
Can you import our existing Excel inventory list?
Yes. Existing stock lists can be prepared for import instead of typing every item manually. The preparation normally involves mapping your item codes, descriptions, locations, quantities, and other relevant fields to the import format.
An import is only as reliable as the source data. Review duplicate items, inconsistent codes, missing locations, and uncertain quantities before using the imported figures as your operational starting point.
Can we use information exported from another system?
Often, yes. A structured export such as a spreadsheet or CSV can provide the starting point for migration. The important questions are which records are available, what each field means, and whether the quantities represent total stock, yard stock, or stock already on site.
Share a sample export during onboarding. Historical transactions, attachments, and scaffold records may need a different migration approach from the opening inventory catalogue.
Do we have to change our existing item codes?
Not necessarily. Existing codes can be retained when they identify your equipment consistently. Familiar descriptions can also make it easier for your yard and site teams to find the right components.
Check for codes reused across different items, differences between supplier and internal codes, and duplicates created by older imports. Agree on the correct mapping before migration so the same component is not accidentally created several times.
What if our current stock list is messy or out of date?
Start by separating catalogue cleanup from quantity verification. Catalogue cleanup resolves item names, codes, categories, and duplicates. Quantity verification establishes what is physically in each yard and on each site.
CloudScaff onboarding can help prepare the information, but your team needs to confirm which items and counts are correct. Do not carry an unexplained discrepancy into the new system simply because it appears in an old spreadsheet.
Can we start with equipment that is already on site?
Yes. You do not need to wait for every project to finish before introducing CloudScaff. Existing site balances can form part of the opening setup.
Choose a clear starting date and establish what is in each yard and on each active site at that point. Agree how movements around the cutover will be recorded so equipment is not counted twice or missed between the old records and the new system.
Do we need a stocktake before going live?
A verified opening balance is the strongest starting point. If the current figures are uncertain, a stocktake helps establish what your team can rely on before new movements begin.
The count can be planned around your operation. Some businesses count by yard, equipment category, or site. Keep a record of the count date and any deliveries or returns happening during the count so the final balance has a clear basis.
Can existing scaffold registers be brought into CloudScaff?
Existing scaffold information can be reviewed as part of onboarding. Provide the register and identify which scaffolds remain active, their site references, dimensions, dates, and supporting records.
Agree the import scope before rollout. Bringing in a scaffold record does not itself perform a physical inspection, verify its location, or replace a required handover. Your responsible team should validate the live records and complete the appropriate operational steps.
Will you help configure our forms and permissions?
Yes. Setup can include preparing roles, site access, and the inspection and handover templates your team needs. Sharing your current paperwork and explaining who performs each step makes that configuration more useful.
A practical approach is to test the proposed setup with one person from the yard, one from the site, and one from the office. Their feedback helps identify missing permissions or unnecessary steps before wider rollout.
How long does implementation take?
Implementation time depends on the number of yards and projects, the condition of your existing data, the workflows you introduce, and the availability of the people involved.
A clean catalogue and a small pilot need less preparation than a coordinated rollout across several branches. Agree the scope, data responsibilities, training sessions, and go-live criteria at the start so everyone understands what needs to happen before the system becomes the working record.
Can we roll CloudScaff out in stages?
Yes. A staged rollout can begin with a small set of projects or a specific workflow, such as deliveries and returns. Once the team is comfortable, you can introduce more sites or scaffold management processes.
Define which system is authoritative for each part of the pilot. Running two incomplete records without clear ownership can create confusion, especially when equipment moves between projects that are at different rollout stages.
Can multiple branches go live together?
A coordinated rollout can be planned where the business needs a common start date. This requires agreement on account structure, item naming, opening balances, permissions, training, and how branch-to-branch movements will be handled.
Nominate a central rollout owner and a responsible person at each branch. Test a complete delivery, transfer, and return before the cutover so the shared process is understood across the operation.
Is training available for our team?
Yes. Training can focus on the work each group actually performs. Yard staff may need requests, picking, dispatch, returns, and stock conditions. Site teams may need receipt, transfer, scaffold, and inspection workflows. Administrators may need permissions, setup, and reporting.
Using your own equipment and project examples makes training easier to apply. Include the exceptions your team encounters, such as a partial delivery or a return that arrives without notice.
What happens after the initial training?
Your team can use the help centre and contact CloudScaff for further assistance as questions arise. Follow-up sessions can address workflows that become clearer once the system is being used on live work.
Keep a short list of recurring questions, screenshots, and example records. This makes it easier to distinguish a training issue from a setup problem or a workflow that needs adjustment.
No matching questions. Try another search or topic.