Version control
Store each revision with number, date, change summary and previous-version link.
Organize manuals, procedures and forms, and track their approval and distribution. See which version is current and who has acknowledged it.
A procedure being present in a folder does not prove that the correct version is in use. Author, approver, effective date and vessel distribution must remain traceable.
Faromo separates draft, review, approval, effective and archive states. It creates distribution lists by vessel and role and records acknowledgements in the audit trail.
Store each revision with number, date, change summary and previous-version link.
Define author, reviewer and approver roles by document type.
Make approved documents effective on a defined date and archive older versions in a controlled way.
Target documents to the relevant vessel, department or role.
Record who acknowledged which version and when.
Link procedures to related forms, checklists, audits or actions.
The current version, change history, vessel distribution and user acknowledgement remain on the same controlled record.
No. Older versions are archived in a controlled way and their effective periods are retained.
Acknowledgement can be required by document type, vessel or role, with overdue acknowledgements tracked.
A document hierarchy can link manuals, procedures, instructions and forms as separate controlled records.
Effective documents distributed to a vessel can remain available locally, with new versions synced when connectivity returns.