Activity
Mon
Wed
Fri
Sun
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
What is this?
Less
More
9 contributions to Records Information Management
Getting Teams to Actually Follow Retention Policies
Writing a clean retention schedule or standard policy is usually the easy part. The real friction starts when other departments have to actually follow it instead of dumping files into whatever random folder is closest. You can hand teams the best ISO-aligned workflows in the world, but daily habits usually win over compliance rules. How do you get non-records teams to actually take ownership of their own document organization?
0 likes • Oct 7
@Paul Mullon 100% on the ROT nightmare. Left wide open, people spin up a new Team for a two-week task and abandon it full of sensitive files. 100% on the ROT nightmare. Left wide open, people spin up a new Team for a two-week task and abandon it full of sensitive files.
One workflow distinction I've found useful is separating the information that needs to be formally managed from the work happening around it.
For example, I might use chatgpt.com to help summarize or work through non-sensitive material, then floment.ai to track the tasks and next steps that come out of that work. The actual governed records still stay in the organization's approved records system. It sounds simple, but keeping “the record” separate from “the work I need to do about the record” makes things much cleaner. How do you handle that separation in your organization?
0 likes • Oct 1
@Abdoulaye Barthelemy That’s a critical distinction. It’s so easy for people to treat task descriptions or AI chat threads as informal throwaways, forgetting that an approved action or decision made there is often a record in itself.
The M&A Records Clean-Up
Migrating an acquired company's entire historical database onto your active servers without filtering out their redundant, obsolete, and transient (ROT) data is a costly mistake. Executing a defensible data clean-up purges useless files while preserving the historical, legally vital assets of the acquired brand. 1. What is your defensible plan to purge the acquired company's redundant, obsolete, and transient (ROT) data before migrating their systems to your cloud? 2. How do you ensure that you don't accidentally delete critical historical records that contain the founding decisions of the acquired brand? Action Item: Write a 1-page "M&A Defensible Disposition Authorization" form to secure final executive sign-off before purging inherited ROT data.
1 like • Sep 30
Getting executive sign-off on disposition is usually where clean-up projects hit major bottlenecks without clear documentation. When auditing legacy data pools, we keep the legal authorization files in Google Drive and run the review phases through Floment AI project cards. That clean separation keeps track of what has been reviewed without mixing operational checklists into official compliance stores.
The "Shadow IT" Audit
Employees often use unauthorized apps or personal cloud drives to bypass clunky internal systems, creating massive, unmanaged record silos. Identifying these rogue applications allows you to capture missing records and understand where your official systems are failing users. 1. Have you noticed employees conducting official business on personal messaging apps or unauthorized cloud accounts? 2. Why do your users feel the need to bypass the approved Electronic Records Management System? Action Item: Survey three colleagues to find out what unofficial tools they use to share large files.
0 likes • Sep 23
People usually turn to shadow tools simply because their daily work moves faster than the official archive systems allow. Auditing where the friction lives in their routine tasks usually highlights what features they actually need to be productive. We keep high friction compliance checkpoints in Google Sheets and handle daily task tracking in Floment AI so our team stays organized without feeling the urge to use unauthorized apps.
Managing Systemised Records and the File Plan
Dear colleagues I’d appreciate your professional views on how you manage systemised records in relation to the file plan. In our organisation, we use Sage for various business processes. For example, employees apply for leave through Sage, and performance appraisals are also created and maintained on the system. My question is: Should records that are created and maintained in a system such as Sage be reflected/classified on the organisation’s file plan, or should they be managed separately as systemised/electronic records? For example: - Leave applications and approvals - Performance appraisals - Payroll records - Financial transactions - Employee-related records How do you handle the classification, retention and disposal of these records in your organisations? I’d particularly appreciate hearing from colleagues who have dealt with similar systems and how you align the file plan, systemised records and disposal requirements. Thank you in advance for sharing your experience.
0 likes • Sep 16
Keeping system records aligned with the organizational file plan works best when the classification rules stay centralized while the daily transactions remain inside the source tool. Leaving line-of-business activity in Sage while referencing the primary retention schedules centrally prevents teams from having to double handle routine documents. I track cross-functional compliance tasks and procedural documentation inside Floment AI while leaving the official data backups in Google Drive. That separation keeps the operational oversight organized without creating redundant record repositories.
1-9 of 9
Tony Iverson
2
15 points to level up
@tony-iverson-7089
Building things online and trying to optimize my daily workflow. Here to learn from founders who are a few steps ahead.

Active 34d ago
Joined Jul 4, 2026