Records pile up in shared drives, email, and offsite boxes, and most organizations struggle to say who owns them or when they can go. Policies exist, but they often sit in separate documents that don’t agree. When an audit or legal request arrives, teams have to hunt for answers.
An information governance plan brings those decisions together in one place. It sets who decides, which rules apply, and how the work gets done over time. This article explains what a plan contains, how it differs from a policy, and how to build one your organization can carry out.
An information governance plan is a written roadmap for how an organization manages information from creation to disposal. It names the goals, the owners, the rules, and the controls. It also sets a timeline for putting those pieces in place. Some organizations write one after they find their policies, systems, and daily practices don’t line up.
The plan applies to every format. Paper files, email, scanned images, and data in business applications all fall under it. Paper records still matter in many industries, so the plan treats them as part of the same program. They get the same rules for retention and access.
A policy states what the organization requires. A retention schedule lists how long each type of record must be kept and why. Each one is a single document with a narrow job.
A plan connects them. It describes who approves the schedule, how business units apply it, and which systems hold the records. It also shows how the organization proves it followed the rules, and it covers training, funding, and the order of work.
Many teams bring in outside help for this connecting work, including information governance support while the plan is still being scoped.
Most plans include the components below. Each one answers a question auditors, regulators, and counsel are likely to ask.
Start by defining what the plan covers. List the business units, record types, repositories, and jurisdictions in play. Then write objectives someone can check. Two examples are an approved schedule for every major “record series” and a named owner for every repository.
Governance stalls when nobody knows who has approval authority. Name an executive sponsor and a steering group with records, legal, IT, privacy, security, and business representatives. Spell out who approves schedule changes, who grants exceptions, and who answers questions from regulators.
This section holds the schedule and the rules for acting on it. A defensible retention schedule is generally supported by legal research, business need, and review.
The plan should also define disposition, which is the final action taken on a record. Examples include secure destruction or transfer to an archive. Document who approves disposition, how it’s carried out, and what evidence is kept afterward.
A legal hold suspends normal disposition when litigation or an investigation is likely. The plan should say who issues holds, how custodians are told, and how holds are released. Without clear steps, routine deletion can continue while a hold is supposedly in effect.
Records also need a documented chain of custody, a log of who handled a record and where it moved. Log custody for boxes in transit, files moved between systems, and destruction.
Describe how records are classified and who may view or change them. Link these rules to privacy requirements and to the organization’s security standards. Include physical controls for paper and media, since those records face different risks than digital files.
A plan staff never read won’t change behavior. Schedule training for new hires and for staff who handle sensitive records. Then set routine checks, such as sampling disposition logs or reviewing repository inventories. Report the results to the steering group.
A set order helps keep the work organized. The steps below are a practical sequence, and teams can adjust them to fit their size and risk profile.
The inventory step can take longer than expected. Build in time for interviews with business units. Plan walk-throughs of offsite storage and shared drives too. Keep a running list of questions that need a legal opinion so they don’t stall the draft.
Approval marks the midpoint of the work. Once the schedule and policies are signed off, the effort shifts to communication, training, and system changes. The rollout is where those rules have to show up in daily work.
Healthcare adds privacy duties, mixed paper and electronic records, and varied retention rules. Retention periods can vary by jurisdiction and record type, so confirm them with counsel. Many facilities keep both paper charts and electronic systems. Billing, research, and clinical data may each follow different rules.
For these teams, the plan should show how policy turns into evidence. That means logs, approvals, and audit trails that can be produced on request, the same audit-ready record a reviewer will ask for.
A plan can be sound on paper and still be hard to apply when people follow the rules by hand. Software may help apply retention periods and track actions, depending on configuration. The plan should name the systems that do this and explain how they’re configured.
Access Unify includes tools for digitizing paper records and managing files and assets. Access Unify Lifecycle holds the retention schedule, and Access Unify is where paper and digital records can sit in one view. Whatever tools you choose, document how they support each rule in the plan.
A plan that was accurate two years ago may point to repositories that no longer exist. Set a review cycle that fits your risk profile, such as annually. Add an extra review after mergers, new regulations, or major system changes.
Track a few measures that show whether the plan is working. Examples include the share of record series with an approved schedule, the number of repositories without an owner, and the time needed to respond to a hold. Share these with the steering group so decisions rest on current information.
A plan helps teams answer routine retention and access questions and prepares them for audits and legal requests. A first plan needs a clear scope, named decision makers, a defensible schedule, and a review habit. A good first step is confirming an executive sponsor and forming the steering group.
The program is the ongoing set of activities, people, and controls that manage information. The plan is the written roadmap that describes those pieces and sequences the work. Most organizations write the plan first and then run the program against it, using the same sequence as building an information governance program.
An executive sponsor should hold final accountability, often from legal, compliance, or the records function. A steering group then shares decisions across records, legal, IT, privacy, security, and the business units. Day-to-day tasks can sit with named owners for each repository or record series, with information governance support when the team wants help standing that up.
Yes. Paper files, boxes in offsite storage, and media still carry retention, access, and destruction duties. The plan should apply the same schedule and approval rules to them as it does to digital records. It should also record how paper moves, as a chain of custody from pickup through destruction.
Reviewers may ask for the approved schedule and records of who approved it. They also want logs showing disposition was carried out as written. Legal hold notices and release records, training attendance, and results of routine checks are common requests too. Healthcare teams may also be asked how patient-record handling stays audit-ready.
Approval starts the rollout phase. Teams communicate the schedule, train staff, update systems, and begin applying disposition rules. The plan should assign owners and dates for each of those rollout tasks.
Software isn’t required to write a plan, but it makes consistent application easier at scale. Manual tracking of retention dates, holds, and disposition logs gets harder as volumes grow. Access Unify Lifecycle is one option for retention schedules, and the plan should document how any tool supports each rule.
If you’re weighing how to put the retention, hold, and disposition rules in your plan into daily practice across paper and digital records, you can request a demo to see how Access approaches that work with Access Unify.
Share