The situation before
Trenord operates the regional rail network in Italy’s Lombardy region — the most populous and economically significant region in Italy — carrying roughly 700,000 passengers on a typical weekday across hundreds of kilometers of track, dozens of stations, and a complex fleet of regional and suburban trains. The workforce spans operational roles (train drivers, conductors, station staff, maintenance technicians, control-room operators), engineering roles, and corporate functions (safety, quality, HR, legal, customer operations).
The operational documentation supporting this network is substantial. Safety procedures cover everything from routine train operations to emergency response. SOPs govern station-level customer service, maintenance routines, control-room coordination. Workforce policies cover HR, training, and specific acknowledgment-required procedures. Before the consolidation, this documentation lived in a mix of departmental SharePoint sites, shared drives, and printed binders at specific sites.
The organization’s previous document-control discipline was reasonable for operational purposes. The gaps surfaced at audit time and when specific workforce-awareness questions arose. “Do all 4,500 employees know about the revised emergency-evacuation procedure?” was a question the previous system couldn’t answer with confidence.
Why public-sector transport has specific needs
Trenord operates under ISO 9001 quality certification, ENAC (national civil-aviation authority — also relevant for certain rail/integrated transport oversight), specific rail-sector regulator oversight (ANSF/ANSFISA), GDPR for passenger data, and the broader public-accountability expectations that apply to regional public-service operators. Some procedures require documented workforce acknowledgment — an employee confirming they’ve read and understood a specific update. Others just need to be published and available. Distinguishing which is which, and producing evidence for the acknowledgment-required subset, was the specific capability gap.
What Trenord adopted
Over approximately four months, Trenord rolled out docs365.ai as the unified document-governance platform. The implementation happened inside Trenord’s existing Microsoft 365 tenant — SharePoint Online as the substrate, active-lifecycle layer providing the governance.
Core operational patterns:
- Sequential approval with fixed approvers aligned to organizational structure. Quality Manager and Safety Director are fixed approvers on every safety-related SOP. Head of Operations is a fixed post-flow approver on operational procedures. HR Director is fixed on workforce policies.
- Automatic PDF publication — the moment approval completes, the PDF is available across the organization via SharePoint. Stations, depots, control rooms all pull from the same source.
- Distribution lists configured per document type — when a safety procedure publishes, the relevant operational teams get the notification automatically. When a workforce policy publishes, the affected employee groups get it.
- Read-receipts — the separately purchased sister product — wired into the approval flow for the subset of procedures that require documented acknowledgment. The updated emergency-evacuation procedure doesn’t just get published; each member of the relevant workforce clicks an acknowledgment button, and the aggregate completion dashboard shows who’s done and who’s outstanding.
- Expiration reminders driving review cadence. Safety procedures on annual review. Workforce policies on biennial review. Specific procedures tied to regulatory-change triggers review on change.
- Audit log providing the evidence layer. ISO 9001 clause 8.5 evidence for documented-information control. Regulator-specific evidence for procedures in sector scope.
- Versioning preserving the full history — important for “what procedure was in force when this incident occurred” retrospective reviews.
The read-receipts angle
Read-receipts deserves specific mention because it addresses a compliance pattern that’s common in workforce-intensive operations but rarely well-supported by generic document-management systems.
Trenord has multiple workforce groups that need documented acknowledgment of specific policy updates. Some examples: revised safety procedures for specific operational roles, updated HIPAA-adjacent patient-data-handling rules for staff who interact with passenger medical information, updated emergency-response protocols for station staff, annually-refreshed workplace-conduct policies.
Before adoption, the acknowledgment evidence was captured via a mix of HR systems, department-specific tracking, and occasionally paper sign-off sheets. The evidence existed but wasn’t consistent or queryable. With the active-lifecycle product’s read-receipts integration, acknowledgment works as follows:
- The document owner, when publishing a procedure that requires acknowledgment, selects the recipient workforce group (pre-configured based on role, department, or site).
- Each recipient gets a personalized email with a link to the PDF and an acknowledgment button.
- The recipient reads the procedure in SharePoint and clicks acknowledge. The click is recorded against their Entra identity with a precise timestamp.
- The document owner sees a completion dashboard — who has acknowledged, who hasn’t, who needs a reminder.
- Outstanding recipients can be nudged with one click. The whole process runs to completion without manual tracking.
The aggregate evidence — “97% of 420 affected employees acknowledged the revised emergency-evacuation procedure within two weeks of publication” — is a single query. Before, it was a multi-week reconciliation exercise.
What changed operationally
Workforce-awareness evidence. Previously answerable in principle but not in practice. Now a real-time dashboard query. When ANSFISA or an internal safety-review process asks “do all train drivers know about this procedure revision?”, the evidence is available in seconds.
Cross-site consistency. Stations, depots, and control rooms all pull from the same published PDF library. Site-specific printed binders still exist for specific operational contexts — you can’t put a tablet next to every piece of rail-maintenance equipment — but the master copy that the binders are printed from is definitionally the current approved version.
Regulatory audit retrievals. ENAC surveillance and rail-sector regulator reviews both involve historical document retrievals. The evidence surfaces as queries rather than assembled over days.
Review-cadence visibility. The Power BI dashboard shows cadence adherence across document types. Safety-procedure cadence hovers at 98-99%. Workforce-policy cadence moved from the low 70s (when it depended on HR remembering) to the high 90s (when the reminder system drove it).
What Trenord thinks about in public-sector contexts specifically
Public-sector operators face a specific accountability expectation that private companies don’t always carry. Regional regulators, municipal oversight bodies, and the broader public expect transparency about how the organization is governed. Documented policies and procedures are part of that transparency. “We have policies” isn’t enough; “we have policies that we can demonstrate are being followed” is the posture.
The active-lifecycle architecture matches this expectation naturally. The audit log is the accountability evidence. The review-cadence dashboard is the “we’re actively governing this” evidence. The workforce-acknowledgment tracking is the “our workforce is informed” evidence.
What we’d point other public-sector transport organizations to
If you run a similar profile — regional or national public-transport operator, multi-site workforce, safety-critical procedures, regulator oversight across multiple dimensions, workforce-acknowledgment obligations for specific policy subsets — the Trenord pattern is worth examining.
Key architectural decisions:
- Read-receipts for the acknowledgment-required subset only. Most procedures publish with distribution-list notification; the subset that requires documented acknowledgment gets the read-receipts layer on top.
- Fixed approvers aligned to organizational structure. Quality, Safety, Operations, HR each have defined roles in specific document-type flows.
- Automatic PDF publication eliminates site-level version drift that’s the main operational risk in geographically dispersed operations.
- Power BI dashboard in the quarterly management review — accountability evidence at the program level, not just the document level.
A thirty-minute conversation maps your profile against this pattern.
