/ RIB Candy & BuildSmart Integration
Connect estimating and project information with actual costs to create a clearer view of commercial performance.
RIB Candy Assist helps contractors assess and establish practical working processes between Candy and BuildSmart, including aligning coding structures, budgets, actual costs and reporting.
* Graphics are for illustrative purposes only and may differ from the actual software interface.
RIB Candy and BuildSmart perform different but related roles within a construction business. Candy supports estimating, planning and project controls, while BuildSmart holds important financial and actual-cost information.
RIB Candy Assist helps contractors assess and establish practical working processes between the two systems. This can include aligning coding structures, budgets, actual costs and reporting so that information can be compared and used more consistently.
Integration is not simply about moving data from one screen to another. The information needs to be structured, understood and maintained by the people responsible for estimating, project delivery, commercial control and finance.
Where does the information flow break down?
Integration problems often begin with differences in how information is organised or understood across departments and systems.
Coding structures
Review how trades, resources, activities, cost codes and other project information are organised in Candy and BuildSmart.
Codes and structures need to support meaningful comparison. Matching two labels does not necessarily mean the information behind them represents the same thing.
Estimate and budget information
Establish which information from the accepted estimate should contribute to the project budget and how it needs to be structured for ongoing commercial control.
The tender estimate may require review before it is suitable for this purpose.
Actual-cost information
Clarify how actual labour, material, plant, subcontractor and other project costs recorded in BuildSmart relate to the budget and control information in Candy.
The accuracy of any comparison depends on costs being captured against suitable codes and projects.
Budget-to-actual comparisons
Bring relevant budget and actual information together so that the project team can identify differences, investigate causes and review the likely outcome.
A variance highlights where attention may be needed. It does not explain the reason without input from the people responsible for the work.
Forecasting and reporting
Use aligned information to support project reports and forecasts that consider the original allowance, actual performance and remaining work.
The reporting structure should be based on the decisions the business needs to make rather than every figure the systems are capable of producing.
Responsibilities and controls
Define who owns each part of the information flow, including setup, data capture, review, corrections, updates and reporting.
Without clear responsibilities, even a well-designed process can slowly become an expensive exchange of questionable spreadsheets.
Integration begins before the transfer
Before information can be compared reliably, the business needs agreement on what the information represents.
For example:
- Which Candy estimate becomes the approved project budget?
- How will tender resources and activities relate to BuildSmart cost codes?
- Who confirms that budgets and actual costs have been allocated correctly?
- How frequently will information be updated and reviewed?
- How will changes to the project budget or remaining forecast be controlled?
- Which reports are required by project, commercial and financial teams?
These questions are as important as the technical movement of information. A working integration depends on suitable structures, reliable data and cooperation between the people using both systems.
What we’ll need from your team
Depending on the engagement, this may include:
- Access to the relevant Candy and BuildSmart information.
- The accepted estimate and approved project budget.
- Existing coding and cost structures.
- Examples of actual-cost information and current reports.
- Details of existing imports, exports or manual processes.
- Input from estimating, project, commercial and finance teams.
- Clarification of who owns and approves each type of information.
- Details of the comparison or report management needs to produce.
Confidential financial and commercial information should only be shared after the appropriate scope, access and arrangements have been agreed.
How Candy and BuildSmart integration assistance works
Build the right foundations first
Integration cannot correct an estimate, programme, budget or coding structure that is not fit for purpose. It can only move or compare the information available.
Where the foundations need attention, it may be more practical to address those areas before establishing the wider workflow.
Does the Candy setup need improvement?
RIB Candy Setup & Implementation can help establish suitable resources, Masters, coding structures, projects and working processes.
Do you need better project reporting and forecasts?
Planning, Forecasting & Project Controls can help connect budget, programme, resources, progress and remaining work.
Does the accepted estimate need attention?
Tender Estimating Support can assist with agreed BOQs, resource build-ups, calculations and estimate reviews.
Frequently asked questions
What does Candy and BuildSmart integration involve?
It can involve aligning coding structures, budgets, actual costs and reporting processes so that relevant information from the two systems can be compared and used more consistently. The precise scope depends on the existing setup.
Can you connect our Candy estimate to BuildSmart?
Potentially. The estimate, budget structure, BuildSmart setup and required information flow first need to be reviewed. The tender estimate may need to be reorganised or approved before it is used as a project budget.
Can integration show budget versus actual costs?
It can support comparisons between appropriate budget and actual-cost information. The usefulness of the comparison depends on accurate coding, data capture, updates and review.
Is the information transferred automatically?
That depends on the systems, versions, configuration, access and agreed workflow. We assess the existing environment before confirming what is technically and practically appropriate.
Can integration fix incorrect project information?
No. Integration does not make inaccurate or inconsistent information reliable. The source information and coding must still be reviewed and maintained by the responsible teams.
Who needs to be involved?
The engagement may require input from estimating, project, commercial, finance and IT or software-support teams. The people responsible for approving budgets and actual costs should be involved in the relevant decisions.
Can you help improve the reports produced from the information?
Yes. Reporting requirements can form part of the agreed scope, provided the necessary budget, actual and project information is available and suitably structured.
Do you provide training on both systems?
Formal RIB Candy training is delivered and administered through Best Training. Any BuildSmart-specific training or technical responsibilities would need to be separately confirmed. Workplace mentoring may be suitable where team members need help applying an agreed workflow to live work.
Start with the information you need to connect
Tell us how Candy and BuildSmart are currently used, where the information flow is breaking down and what your team needs to compare or report.
We’ll assess the current setup and help identify the structures, information and responsibilities required for a practical way forward.
When contacting us, please include:
- Which versions or parts of Candy and BuildSmart are in use.
- The types of information currently exchanged.
- Whether a coding structure already exists.
- The report or comparison you need to produce.
- The teams involved in the current process.
- Any live project or reporting deadline.