Compliance & Assurance
Run compliance work through one clear Map
This Map ran The Work Environment Week at the University of Gothenburg. Each person entered at their stage. Evidence stayed with the Session. The record was written as the week ran.
The policy is clear. The process rarely is.
Evidence lives in inboxes, shared drives and one officer's memory. The work happened. The proof is somewhere else.
Before the auditor arrives, someone rebuilds the week: chasing sign-offs, copying answers into a spreadsheet and hoping the dates still match.
The record should be written while the work happens.
A safety inspection from finding to sign-off
A safety inspection has the same shape: inspector, finding, issue owner, remediation, verification. Each person enters at their stage. The Map carries the evidence and the context forward.
Start the inspection
The inspector opens one link and sees the first required check.
Record the finding
Photos, notes and measurements stay on the stage where they were captured.
Assign remediation
The issue moves to the person responsible, with the finding and evidence attached.
Verify the work
The reviewer sees what changed and either closes the issue or sends it back.
Close the inspection
The completed Session leaves one structured row: who acted, when and which path the work took.
Each completed Session produces a row
As people complete stages, answers, decisions, files and handoff timing become structured data. There is no second admin phase to reconstruct the inspection in a spreadsheet.
The Session and its evidence stay together: who acted, what they submitted, when they acted and which path the work took.
The Map is the process people run
One Map holds the stages, roles and handoff paths. Each Session follows that structure, captures the record and shows where work waits. Eddy coordinates the human work. It does not run automated checks or certify compliance.
Map
Lay out stages, Map Roles, conditions and handoff paths on one canvas.
Execute
Each participant enters at their stage, completes their part and hands off with the previous context attached.
Store
Answers, decisions, files and timing become structured rows as the Session runs.
Analyze
The Operator view shows who is at each stage, how long stages take and where work waits.
One compliance week, then the Maps kept coming
The University of Gothenburg used one Map to run The Work Environment Week across Core Facilities. A link in an email had to carry the week.
After the week, Luciano began mapping onboarding, purchasing, compliance reporting, survey intake and other administrative work that had lived in email and spreadsheets.
One compliance process became a growing set of Maps active or in development.
86.4%
post-pilot satisfaction score
10+
maps now active or in development
Since the pilot, I have been creating many more processes. I see huge potential in this tool and am actively looking for processes where Eddy can improve our administrative life.
Run one real compliance process
Start with the inspection, review or sign-off that currently lives across email and spreadsheets. Build the stages, roles and handoffs as one Eddy Map.