Start with the repeat company information and the live people and places your team actually uses.
Fabora resources
Getting started with Fabora RAMS.
Fabora RAMS is designed to start from a practical company base rather than a blank file every time. For steel fabricators, site welders, steel erectors, and related site-working metal trades, the clean first path is to set the company details, build the reusable libraries, draft the first site or workshop RAMS, review it internally, then issue the output that is right for the job.
Short answer
The safest quick start is to set the company structure once, reuse it sensibly, and keep final review, approval, and job-specific judgement with your business.
- Start with the repeat company information and the live people and places your team actually uses.
- Build the reusable libraries around common work, then edit each RAMS around the real job instead of relying on one generic draft.
- Review the finished pack internally before you export the branded PDF or share the RAMS link.
General product guidance only. Fabora RAMS supports drafting and reuse, but final review, approval, and job-specific judgement still stay with your business.
Practical summary
What to take from this page
The safest quick start is to set the company structure once, reuse it sensibly, and keep final review, approval, and job-specific judgement with your business.
General product guidance only. Fabora RAMS supports drafting and reuse, but final review, approval, and job-specific judgement still stay with your business. For official detail, use the HSE links later on this page.
Build the reusable libraries around common work, then edit each RAMS around the real job instead of relying on one generic draft.
Review the finished pack internally before you export the branded PDF or share the RAMS link.
Starting point
Start with the company base you will keep reusing
The first setup is easier when it stays practical. Build the core company information that will keep appearing in future RAMS instead of trying to fill every field and library at once.
Set the company details and logo
Start with the business name, branding, and other repeat company information needed for cleaner output. This gives the team a proper base before the first live RAMS is drafted.
Add the people and places you return to
Save the customers, sites, contacts, and operatives the business regularly works with so new RAMS can start from live records instead of repeated typing.
Keep ownership clear inside the business
It helps to decide who is setting up the initial company content, who is building the RAMS drafts, and who is carrying out the internal review before issue.
Reusable content
Build the reusable libraries around real repeat work
The value comes from setting up the repeat content once, then selecting and editing it in later RAMS rather than typing it out again.
Method presets
Build method presets around the fabrication, erection, delivery, welding, and remedial tasks your team actually repeats. They should save time, not force every job through the same wording.
Hazards, COSHH, PPE, and equipment
Add the core supporting libraries your business uses most often so the first draft can be built from sensible saved content instead of blank fields.
Start with common jobs first
There is no need to build every possible library entry on day one. Start with the activities, materials, and equipment that come up most often, then widen the setup over time.
Treat the libraries as working company content
The saved libraries should stay editable and improve as the team learns what wording, controls, and method steps are most useful on real jobs.
First draft
Use the first live RAMS to prove the structure
Once the company base is in place, build a real site or workshop RAMS in the browser and use it to test whether the setup is helping or slowing the team down.
Choose the right route for the job
Start from the workshop or site context that best matches the live task. That usually gives a cleaner first draft than forcing one generic starting point onto every job.
Pull in saved records and edit the sequence
Use the saved customers, contacts, operatives, methods, and supporting libraries to build the draft faster, then edit the task order and wording so it reflects the actual work.
Add the live job detail
Site conditions, access, permits, supervision, lifting, deliveries, temporary arrangements, and working notes still need to be checked and edited around the real job before issue.
Keep the pack readable
The goal is a draft the team can actually follow. Clear steps, sensible controls, and practical job detail are more useful than a longer file filled with generic wording.
Review and issue
Review internally before the pack goes out
Fabora RAMS can speed up the drafting side, but the finished pack still needs the same sensible review discipline inside the business before it is issued.
Check the method and controls against the live job
Before issue, review the method, hazards, controls, permits, and supporting notes against what is really happening on the job rather than assuming the first draft is ready as-is.
Export or share only after review
Once the pack has been checked internally, export the branded PDF or share the RAMS link through the channel that suits the job and the people receiving it.
Keep revisions under control
If the job changes, revise the pack from the saved RAMS record rather than letting multiple uncontrolled copies drift around email chains or shared drives.
Use early jobs to sharpen the setup
The first few live jobs usually show which method presets, hazards, and saved records are already useful and which ones still need tightening.
First-week checks
What to check while the team is getting comfortable with Fabora RAMS
A short review after the first few live jobs usually shows where the setup is already working and where the company libraries still need tightening.
Are the saved records reducing repeat typing?
If the team is still re-entering the same customer, site, or operative detail each time, the company records may need cleaning up or expanding.
Are the method presets close enough to real delivery work?
A preset should save time and still read like the kind of work the business actually does. If every preset needs heavy rewriting, the base wording probably needs improving.
Are site and workshop jobs starting from the right base?
If the same draft keeps carrying the wrong assumptions between workshop and site work, tighten the starting routes before the next batch of jobs.
Is final review still clearly owned inside the business?
The software helps with drafting speed and reuse, but the review, approval, and job-specific decision-making should still be clearly owned by competent people in the business.
Official guidance
Relevant HSE links
These links point to the underlying official guidance. This page is a practical summary, not a replacement for those sources or for competent job-specific review.
HSE: Method statements and administration
Useful background on how method statements support planning, communication, and control on live work.
HSE: Planning for construction work
Useful context where the RAMS needs to sit properly inside the wider planning and coordination of the job.
HSE: Site rules and induction
Useful if the first live jobs need to reflect inductions, permit systems, site rules, and emergency arrangements more clearly.
FAQ
Common questions
Short answers on practical use, review expectations, and where this guidance stops.
Important note
Final review, suitability, and approval still remain with the customer's business and the people responsible for the job.
Do we need to build every library before the first RAMS?
No. It is usually better to start with the company details and the repeat content the business uses most often, then expand the libraries as real jobs show what still needs to be added.
Should each RAMS still be edited around the live job?
Yes. Saved content is there to give the team a cleaner starting point, but each RAMS still needs job-specific editing, internal review, and approval before it is issued.
Who should review the pack before issue?
That depends on the business and the job, but the review should sit with competent people who understand the work, the site or workshop conditions, and the live project requirements.
Can the same company base support workshop and site RAMS?
Yes. Shared company content is useful, but the live RAMS should still start from the right workshop or site context and then be edited around the actual task.
Related reading
Continue from here
These links keep the topic moving, either into related guidance or into the Fabora RAMS product pages.
RAMS guide for steel fabricators and site welders
Use this if you want the wider practical picture on what a usable RAMS pack normally needs to cover.
Workshop RAMS vs site RAMS
Useful if you are deciding how the team should separate workshop and site starting points.
Fabora RAMS
Return to the product page to see the live workflow, pricing, and access route.