Skip to main content
Category: Retention and Scheduling

General Records Schedule

Also known as: GRS, General Records Schedules, General Record Schedules
Simply put

A General Records Schedule is a standardized set of rules that tells government agencies how long they must keep certain common types of records and what to do with them afterward. Rather than each agency creating its own rules for routine records, a GRS provides shared retention requirements for functions that many or all agencies perform, such as administrative and support activities. The term can refer either to the entire set of schedules or to an individual schedule within that set.

Formal definition

A General Records Schedule (GRS) is an authoritative disposition instrument that establishes retention periods and disposition authority for records common to multiple or all agencies within a given jurisdiction, typically covering administrative or support functions rather than records documenting an agency's specific mission or program. GRS instruments promote consistency in recordkeeping across agencies by providing uniform retention and disposition requirements for shared functions and activities. In practice, the term 'the GRS' may denote the complete set of schedules issued by a records authority, while 'a GRS' may denote a single schedule within that whole. Coverage, scope, and the issuing authority vary by jurisdiction; some GRS instruments address administrative functions only, while others may extend to program functions common to several agencies. Records tied to an agency's unique mission generally fall outside GRS coverage and are typically addressed by agency-specific schedules.

Why it matters

General Records Schedules address a practical problem that arises across public administration: many agencies perform the same routine functions and generate the same kinds of administrative and support records, yet without shared rules each agency would have to determine retention and disposition independently. This duplication invites inconsistency, wasted effort, and the risk that similar records are kept for widely different periods or disposed of on incompatible terms. By providing standardized retention requirements for common functions, a GRS promotes consistency in recordkeeping across agencies that perform overlapping activities.

Because a GRS carries disposition authority, it also helps agencies act defensibly. Retention and disposition decisions for covered records can rest on an authoritative instrument rather than on ad hoc judgment, which supports orderly retention and, where authorized, lawful disposition. It is important to keep the scope in view: GRS instruments typically cover administrative or support functions and generally do not extend to records that document an agency's unique mission. Those mission-specific records are usually addressed through agency-specific schedules, so a GRS is best understood as one component of an agency's broader retention and disposition framework rather than a complete solution on its own.

Coverage, scope, and the issuing authority vary by jurisdiction. Some GRS instruments are confined to administrative functions, while others extend to program functions common to several agencies, as reflected in differing practice across jurisdictions. Professionals should therefore consult the specific GRS applicable to their jurisdiction and sector rather than assuming that the boundaries or authority in one regime carry over to another.

Who it's relevant to

Records managers in government agencies
Records managers apply GRS instruments to determine retention periods and disposition for common administrative and support records, reducing the need to develop independent rules for routine functions. They also identify where GRS coverage ends and agency-specific schedules must take over, particularly for records documenting the agency's unique mission.
Records authorities and archival institutions
The bodies that issue GRS instruments are responsible for defining their scope, establishing retention and disposition authority for shared functions, and promoting consistency in recordkeeping across the agencies they oversee. Their decisions on whether a GRS covers only administrative functions or extends to common program functions shape practice across an entire jurisdiction.
Compliance and governance officers
Those responsible for defensible recordkeeping can rely on a GRS as an authoritative basis for retention and disposition of covered records, supporting consistency and orderly decision-making. They should confirm the scope and issuing authority applicable to their jurisdiction, since coverage varies and a GRS typically does not address mission-specific records.
Agency staff who create and manage routine records
Staff who handle common administrative and support records benefit from standardized rules that specify how long such records are kept and what happens to them afterward, rather than requiring case-by-case judgment. Understanding that a GRS covers shared functions but generally excludes mission-specific records helps staff route records to the correct schedule.

Inside GRS

Records series or category coverage
A General Records Schedule typically identifies classes of records that are common across many organizational units, grouping them into series or categories rather than addressing individual documents. Coverage is generally limited to records deemed common or administrative in nature, so records unique to a particular function usually fall outside its scope.
Retention periods
For each covered class, a GRS commonly specifies how long the records should be retained before disposition may occur. These periods depend on jurisdiction, sector, and organizational policy, and represent minimum or prescribed durations rather than universal figures.
Disposition instructions
A GRS typically indicates the disposition action to be applied at the end of the retention period. Disposition should be understood broadly, as it may involve transfer to an archive, permanent preservation, or authorized destruction, and is not synonymous with destruction alone.
Scope and applicability statements
A GRS usually defines which bodies, units, or record types it applies to, and notes exclusions. Because it addresses records common to multiple entities, it is generally supplemented by agency-specific or function-specific schedules for records not covered.
Authorizing basis
A GRS is often issued or endorsed under the authority of a national archives, records authority, or comparable governing body, giving it a mandating or advisory status that varies by jurisdiction. The precise legal weight depends on the applicable regime.

Common questions

Answers to the questions practitioners most commonly ask about GRS.

Is a General Records Schedule the same as an organization's own records retention schedule?
No, though the two are related and often work together. A General Records Schedule is typically a schedule issued by a central authority to cover records that are common across many organizations, such as routine administrative, financial, or personnel records. An organization's own retention schedule, sometimes called an agency-specific or program schedule, addresses records that are unique to that body's particular functions and activities. In many jurisdictions, an organization applies the General Records Schedule to its common records and develops its own schedules to cover what the general schedule does not reach. The precise relationship, terminology, and authority depend on the jurisdiction and the governing recordkeeping regime, so the two should not be treated as interchangeable.
Does listing a record series in a General Records Schedule mean those records should be destroyed once the period ends?
Not necessarily. A General Records Schedule specifies the disposition of covered records, and disposition is a broader concept than destruction. Depending on the series and the governing regime, the authorized disposition may be destruction, transfer to an archival institution, or permanent preservation. The end of a stated retention period signals that a disposition action becomes permissible or required under the schedule, but the nature of that action is what the schedule prescribes for each series. Treating every scheduled disposition as destruction is a common misreading that the schedule itself is intended to prevent.
How does an organization determine whether its records fall under a General Records Schedule or require a separate schedule?
This generally involves mapping the organization's record series against the categories described in the applicable General Records Schedule to identify which common records are covered. Records that reflect functions and activities unique to the organization typically fall outside the general schedule and may require a separate, organization-specific schedule. The scope of coverage, the criteria used, and the process for confirming applicability depend on the jurisdiction and on any guidance issued by the authority responsible for the schedule, so organizations often confirm coverage rather than assume it.
What should an organization do when a General Records Schedule is updated?
When a General Records Schedule is revised, organizations typically review the changes to identify affected record series and reconcile them against their current classification and retention practices. This may involve updating internal schedules, reclassifying certain series, or adjusting disposition timing. Because retention and disposition decisions can carry legal and regulatory consequences that vary by jurisdiction and sector, changes are usually assessed carefully before being applied, and prior disposition actions taken under an earlier version are generally not reopened unless the governing regime directs otherwise.
How does a legal hold interact with records governed by a General Records Schedule?
A legal hold generally suspends the disposition of records that are relevant to actual or anticipated litigation, investigation, or similar matters, regardless of what a General Records Schedule would otherwise permit. In practice, this means the scheduled disposition action is paused for the affected records until the hold is lifted. The precise obligations, triggers, and scope of a hold depend heavily on jurisdiction and sector, so organizations typically treat holds as an override of routine scheduled disposition rather than as an exception the schedule itself provides.
Who is typically responsible for applying a General Records Schedule within an organization?
Responsibility is often shared. Records management staff commonly interpret the schedule, map it to the organization's record series, and coordinate disposition, while business units that create and hold the records may carry out or authorize specific actions. Within a broader information governance framework, accountability for policy, risk, and compliance may sit with governance or compliance functions. The specific allocation of roles depends on organizational structure and policy, so the schedule sets the disposition rules while internal governance determines who executes and oversees them.

Common misconceptions

A General Records Schedule covers all of an organization's records.
A GRS typically addresses only records that are common across many units, such as routine administrative records. Records tied to an organization's unique functions generally require separate agency-specific or function-specific schedules and are usually outside the GRS scope.
Reaching the end of the retention period under a GRS means the records must be destroyed.
The disposition specified in a GRS may include transfer to an archive or permanent preservation, not only destruction. Retention and disposition are distinct concepts, and disposition should not be equated solely with destruction.
A GRS overrides other legal obligations such as legal holds.
Scheduled disposition is generally suspended where a legal hold, litigation, investigation, or other statutory obligation applies. Such requirements vary by jurisdiction and sector and typically take precedence over routine schedule-driven disposition.

Best practices

Confirm which of your records actually fall within the GRS scope, and identify records unique to your functions that require separate agency-specific or function-specific schedules.
Treat the GRS as one instrument within a broader retention framework rather than a complete schedule, and reconcile it against organizational policy and applicable jurisdictional requirements.
Verify the authorizing basis and current status of the GRS with the issuing records authority or national archives before relying on it, since its legal weight varies by jurisdiction.
Apply the specified disposition action precisely, distinguishing transfer, permanent preservation, and authorized destruction rather than defaulting to destruction.
Suspend scheduled disposition where a legal hold or other statutory obligation applies, and document the basis for any suspension.
Document disposition decisions and actions to support the authenticity, integrity, and defensibility of your recordkeeping over time.