# Federal privacy impact assessments, SORNs, routine uses and matching agreements, explained

Before a federal agency builds or buys a system holding personal information, it owes a privacy impact assessment and, for a system of records, a Privacy Act notice with fixed waiting periods. OMB's 2025 Do Not Pay memorandum applies those rules.

Explainer · Government · Regulation & Compliance. Published November 14, 2026. Last reviewed November 14, 2026.

## At a glance

- An agency must conduct a privacy impact assessment before developing or procuring IT that collects, maintains or disseminates information in identifiable form [1].
- A new or revised SORN is effective on publication, except new or significantly modified routine uses, which need at least 30 days after publication [3].
- Agencies report a new or significantly modified system of records to OMB and Congress at least 30 days before sending the notice to the Federal Register [3].
- A computer matching agreement lasts no more than 18 months and may be renewed once for up to one additional year [2].
- OMB M-25-32 (August 20, 2025) gives agencies a standard routine use for disclosures to Treasury to review payment and award eligibility through Do Not Pay [5].

A federal agency that handles personal information works under two statutes with separate documents. Section 208 of the E-Government Act of 2002 requires a privacy impact assessment (PIA) before the agency develops or procures information technology that collects, maintains or disseminates information in identifiable form [1]. The Privacy Act of 1974, at 5 U.S.C. 552a, requires a system of records notice (SORN) in the Federal Register when an agency establishes or revises a system of records [2]. OMB Circular A-108 sets out how agencies review, report and publish under the Privacy Act [3], and Circular A-130 ties both duties into agency privacy programs [4].

This explainer covers four documents in order: the PIA, the SORN, the routine use, and the computer matching agreement, then the August 2025 memorandum that put the last two to work for payment integrity. The waiting periods for each are listed in our [comparison of federal privacy compliance documents](https://insights.moraph.com/compare/federal-privacy-act-pia-and-sorn-duties).

## The privacy impact assessment

The PIA duty has two triggers: developing or procuring IT that handles information in identifiable form, and starting a new collection of information that uses IT and includes identifiable information permitting the physical or online contacting of a specific individual, where identical questions go to 10 or more persons outside the federal government [1]. Before either, the agency must conduct the PIA, have it reviewed by its Chief Information Officer or equivalent official, and, if practicable, make it public through its website, the Federal Register or other means [1]. Publication may be modified or waived for security reasons or to protect classified, sensitive or private information in the assessment [1]. Agencies must also give OMB's Director a copy of the PIA for each system for which funding is requested [1].

The statute tells OMB that its PIA guidance must require the assessment to address seven points: what information is collected, why, the agency's intended use, with whom it will be shared, what notice or consent opportunities individuals get, how it will be secured, and whether a system of records is being created under the Privacy Act [1]. Circular A-130 defines a PIA as both an analysis and a formal document detailing the process and outcome of that analysis [4]. It directs agencies to conduct PIAs when developing, procuring or using IT, and to make them available to the public in accordance with OMB policy [4].

## The system of records notice

A system of records is a group of records under an agency's control from which information is retrieved by an individual's name or by an identifying number, symbol or other particular assigned to the individual [2]. The SORN must state the system's name and location, the categories of individuals and records, each routine use, the agency's storage, retrieval, access control, retention and disposal practices, the responsible official, the procedures for notification, access and contesting content, and the categories of record sources [2].

The timing runs in two stages. Under the Privacy Act, an agency that proposes to establish or significantly change a system of records must give advance notice to the House and Senate committees named in the Act and to OMB [2]. Circular A-108 sets that report at least 30 days before the agency submits the notice to the Federal Register, gives OMB 30 days to review, and says that review period may not run concurrently with the Federal Register publication period [3]. A new or revised SORN is then effective on publication, except for new or significantly modified routine uses [3]. When an agency stops maintaining a system of records, it publishes a notice of rescindment [3]. Each agency must keep a privacy page at www.[agency].gov/privacy that lists and links to all of its SORNs [3].

## The routine use

For a disclosure of a record, a routine use means using the record for a purpose compatible with the purpose for which it was collected [2]. The Privacy Act requires notice of any new use or intended use in the Federal Register at least 30 days before the information is published as a routine use in the SORN, with an opportunity for the public to comment [2]. Circular A-108 adds that an agency may not disclose records under a new or modified routine use until the 30-day comment period has ended and it has considered any comments and decided no further changes are needed [3]. If public comments lead the agency to decide that significant changes to the routine uses, or additional routine uses, are needed, it provides an additional 30-day public comment and review period [3].

## The computer matching agreement

A matching agreement takes effect no earlier than 30 days after a copy is sent to the congressional committees named in the Act [2]. It remains in effect for a period set by the agency's Data Integrity Board, not exceeding 18 months [2]. Within 3 months before it expires, the Board may renew it without further review for not more than one additional year, if the program continues without change and each party certifies compliance in writing [2]. At the end of each calendar year, the Data Integrity Board of each agency that took part in a matching program reviews that year's programs, and the report for the preceding calendar year goes to OMB by June 1 [3].

The duties have teeth. An officer or employee who willfully discloses protected records knowing the disclosure is prohibited is guilty of a misdemeanor and fined not more than $5,000 [2].

## The Do Not Pay memorandum

OMB issued M-25-32, Preventing Improper Payments and Protecting Privacy Through Do Not Pay, on August 20, 2025 [5]. It gives guidance to help agencies implement sections 3(c) and 3(d) of Executive Order 14249, signed March 25, 2025 [5]. As the memorandum quotes it, the order requires agency heads to “review and modify, as applicable,” their relevant SORNs to include a routine use allowing disclosure of records to the Department of the Treasury for identifying, preventing or recouping fraud and improper payments, to the extent permissible by law, within 90 days of the order [5]. The memorandum gives the text of a standard routine use that agencies must include in relevant SORNs, and says reviewing and modifying relevant SORNs to implement that routine use is a responsibility of Senior Agency Officials for Privacy [5].

The memorandum keeps the ordinary Privacy Act steps. It treats changing a routine use as generally a significant change that requires a report to OMB and Congress and a Federal Register notice, and repeats that a new or modified routine use must be published at least 30 days before it takes effect [5]. Agencies adding the routine use to several SORNs may send one consolidated report to OMB and one to Congress [5]. Its second appendix describes a forthcoming four-year waiver, to be granted by Treasury in consultation with OMB, of the matching agreement requirement for matching programs that meet criteria tied to prepayment and pre-award eligibility checks through Do Not Pay [5]. The memorandum says agencies should keep observing existing matching agreements until they expire [5]. We did not find the waiver itself among the sources opened for this page, so its status is not stated here.

## Where this lands for agency programs

In our view, the documents work best as a design sequence. The PIA questions about sharing and security shape the SORN's routine uses and safeguards, and the reporting and comment periods set a floor on how fast a new system or new data flow can go live. Program offices that bring the privacy office in at acquisition planning, rather than at authorization to operate, avoid finding that a planned disclosure needs a new routine use and a further 30-day wait.

This explainer describes the statutes and OMB guidance; it is not legal advice, and agencies should confirm with their Senior Agency Official for Privacy and counsel how they apply.

Moraph’s teams help organizations with work like this. [See our solutions](https://www.moraph.com/solutions).

## Sources

1. U.S. Congress, govinfo.gov. E-Government Act of 2002, Public Law 107-347, section 208 (Privacy Provisions). <https://www.govinfo.gov/content/pkg/PLAW-107publ347/html/PLAW-107publ347.htm> Checked November 14, 2026.
2. Office of the Law Revision Counsel, govinfo.gov. 5 U.S.C. 552a, Records maintained on individuals (United States Code, 2024 edition). <https://www.govinfo.gov/content/pkg/USCODE-2024-title5/html/USCODE-2024-title5-partI-chap5-subchapII-sec552a.htm> Checked November 14, 2026.
3. Office of Management and Budget. OMB Circular No. A-108, Federal Agency Responsibilities for Review, Reporting, and Publication under the Privacy Act. <https://www.whitehouse.gov/wp-content/uploads/legacy_drupal_files/omb/circulars/A108/omb_circular_a-108.pdf> Checked November 14, 2026.
4. Office of Management and Budget. OMB Circular No. A-130, Managing Information as a Strategic Resource. <https://www.whitehouse.gov/wp-content/uploads/legacy_drupal_files/omb/circulars/A130/a130revised.pdf> Checked November 14, 2026.
5. Office of Management and Budget. M-25-32, Preventing Improper Payments and Protecting Privacy Through Do Not Pay (August 20, 2025). <https://www.whitehouse.gov/wp-content/uploads/2025/08/M-25-32-Preventing-Improper-Payments-and-Protecting-Privacy-Through-Do-Not-Pay.pdf> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/privacy-act-sorns-routine-uses-and-e-government-act-pias-explained>
Publisher: Moraph Insights
