PackOS
Contractor compliance workspace

RAMS and Site Packs without the paperwork scramble.

Create RAMS, manage evidence, approve revisions, and share branded Site Packs from one focused workspace.

Reviewed recordsProject photosBranded packs
PACKOS / SITE PACK OPERATING LAYERRAMS -> EVIDENCE -> APPROVAL -> EXPORTREVISION LOCKED

PackOS workspace

PackOS dashboard
Approved RAMS
Site Pack ready
Photos attached

The old way

Site paperwork moves through too many places.

Word templates
PDF folders
Phone photos
Email attachments

The new way

One workspace keeps the package connected.

RAMS revisions
Project photos
Evidence records
Site Pack sharing

The PackOS map

A controlled path from draft to client-ready package.

The site does not need another file dump. It needs a clear operating layer for the documents around the work.

01

Draft

Create RAMS from templates, defaults, or a guided blank draft.

02

Context

Add site photos, certificates, COSHH, permits, and company evidence.

03

Approve

Submit and protect the reviewed revision before export.

04

Package

Build a Site Pack from approved and active records.

05

Share

Export the ZIP or send a read-only package snapshot.

Project Media

Photos become part of the RAMS context.

Add site frontage, access routes, work areas, hazard areas, and project photos to the revision being reviewed.

Site frontageAccess routeWork areaHazard area

Project Media

PackOS Project Media tab

What PackOS connects

The workflow around the work.

PackOS focuses on the paperwork pain around RAMS, evidence, packages, exports, sharing, branding, and team controls.

RAMS revision workflow

Draft, review, approve, export, and create new revisions without editing the approved record.

Project Media

Structured site photos stay attached to the exact RAMS revision being reviewed.

Evidence workspaces

Company documents, certificates, COSHH, permits, operatives, and equipment context stay close to the package.

Site Pack sharing

Send organised exports or stable share snapshots instead of loose email attachments.

Site Pack Create

PackOS Site Pack creation workflow

Site Packs

Build the package from records that have actually been reviewed.

Select approved RAMS and active evidence, review the package contents, then export an organised ZIP or share a read-only snapshot.

Approved RAMSActive evidenceBranded manifestSecure sharing

Professional controls

A cleaner layer for teams, branding, sharing, and review.

The product stays practical: permissions protect sensitive actions, branding improves the client-facing pack, and draft assistance never replaces review.

Approved records

Exports come from reviewed revisions.

Private storage

Files remain API-mediated and access controlled.

Brand layer

Customer-facing documents use your company identity.

History foundations

Lifecycle and package movement stay visible.

Pricing

Simple plans for contractor teams.

Start with one live project, prove the workflow, then scale into team and evidence operations.

Full pricing

Starter

from GBP 39/mo

For small contractors getting RAMS and basic packs organised.

Business

from GBP 149/mo

For growing teams needing controlled review, sharing, and package activity.

Enterprise / Bespoke

Contact us

For larger onboarding, migration, training, integrations, or custom workflow needs.

Founding Contractor Programme

Run one real project through PackOS.

Bring the documents you already use. Build the first PackOS Site Pack with guided setup, direct feedback, and early pricing.

Explore the programme
Guided setupOne project workflowFeedback sessionsFounding pricing

Questions

Straight answers before a pilot.

PackOS is workflow software. It helps organise and present the paperwork, while review and responsibility stay with the contractor.

Does PackOS guarantee compliance?

No. PackOS is workflow software. It helps organise, draft, review, approve, export, and share documents. The contractor remains responsible for suitability, accuracy, and final approval.

Can we use existing templates?

Yes. Repeat wording and job/trade patterns can become reusable starting points while staying editable and reviewable.

Can clients access packs?

Yes. Site Pack share links provide a read-only package snapshot without inviting the client into your workspace.

Does AI approve anything?

No. Draft assistance is a starting point only. Users review, submit, approve, and export final records.

Next step

See PackOS with a real Site Pack workflow.

The strongest first demo is one real project, one RAMS, and one package you would normally prepare for a client.

Book a demoLogin

PackOS helps organise and prepare documents. It does not guarantee legal compliance or replace competent review.