Records management in Alfresco is delivered through Alfresco Governance Services (AGS), a module that turns the general-purpose repository into a certified EDRMS. A record is content that has been formally declared - fixed, immutable and governed by a retention schedule - as evidence of a business activity. AGS provides the file plan, classification, declaration, retention, disposition and audit capabilities that international standards require.

The practice rests on recognised frameworks: ISO 15489 defines records management principles; ISO 16175 sets functional requirements for records in digital environments; and DoD 5015.02, against which AGS has historically been certified, gives detailed baseline requirements. Alfresco implements these as concrete, auditable behaviours.

The file plan and classification

The file plan is the hierarchical structure - record categories, record folders and records - that organises content by function and applies retention rules. Unlike an ordinary folder tree, the file plan enforces governance at every level.

  • Record categories: carry the disposition (retention) schedule.
  • Record folders: group related records and inherit or refine the schedule.
  • Declared records: immutable nodes - content and key metadata can no longer be altered.
  • Security classification: optional caveats and clearance levels controlling who can even see a record.

Retention and disposition

Disposition schedules define the lifecycle of a record after declaration - what happens, in what order, triggered by what event or elapsed time.

  • Cut-off: closing a folder to further filing at a defined trigger.
  • Retain / transfer: holding for a fixed period, or moving to an archive or preservation system.
  • Destroy: defensible, audited destruction at end of life.
  • Holds: legal or investigative holds that suspend disposition regardless of schedule.
In practice. Declaration is deliberately irreversible - so validate metadata before a record is declared, not after. Build a review step into the capture workflow that checks mandatory fields and correct file-plan placement, because once declared you cannot simply edit your way out of a mistake.

Audit and defensibility

Every action against a record - declaration, reclassification, disposition, access - is written to an immutable audit trail. This is what makes destruction and transfer defensible: you can prove that the correct schedule was followed, by whom and when. Integrate the audit log with your wider information-governance evidence, and align retention schedules with the legal and regulatory regimes of each jurisdiction you operate in rather than assuming one global rule.

Key takeaways

  • Alfresco Governance Services adds a certified file plan, declaration, retention, disposition and audit to the base repository.
  • Practice aligns to ISO 15489, ISO 16175 and DoD 5015.02; declared records are immutable and governed by disposition schedules.
  • Defensibility comes from the immutable audit trail plus holds that override schedules - validate metadata before the irreversible declaration step.

Check your understanding

Last modified: Saturday, 1 August 2026, 11:56 AM