Short, straight answers - the same questions real builders ask.
What is swiftRMS best at?
swiftRMS is best for teams that create a lot of safety documents and want AI help with RAMS, COSHH, SSOW, manual handling, HAVS, and toolbox talks. Its public pricing also highlights video hazard analysis, Word and PDF export, and higher-tier workflows for permits and incident reporting. It is more focused on document creation than the whole CDM site pack.
How much does swiftRMS cost compared with The Site Book?
swiftRMS publishes Pro at GBP49 per month, Business at GBP149 per month, and Enterprise at GBP249 per month when billed monthly. The Site Book starts from GBP30 per month and includes RAMS, CPPs, COSHH, inductions, worker sign-off, and site management in one plan. For a small builder, the starting monthly difference is meaningful before usage or team size grows.
Does swiftRMS replace a full CDM compliance system?
Not by itself, based on the public feature set reviewed. swiftRMS covers several important document types, including RAMS, COSHH, SSOW, and toolbox talks, and higher tiers add permits and incident reporting. The public pricing page does not list Construction Phase Plans, site inductions, worker certificate tracking, or a site diary, which are core parts of The Site Book workflow.
When should I choose The Site Book instead?
Choose The Site Book when you want the project pack and worker trail, not just a safety-document generator. The Site Book creates RAMS, CPPs, COSHH assessments, emergency plans, and inductions, then lets workers sign from their phone. It also keeps certificate tracking, permits, diary entries, and toolbox talks together so the audit pack is assembled as the job runs.
Can I switch from swiftRMS to The Site Book?
Yes. The simplest route is to finish any live swiftRMS documents, then create the next project in The Site Book and upload any existing PCPP or project information you want reused. The day-to-day workflow moves into a plain-English project brief, with documents, sign-off, and worker records managed together instead of split across separate exports and site folders.