Records Subject to FOIA

Provided by The Reporters Committee for Freedom of the Press
Jump to navigation Jump to search

Introduction

Not every thing that the federal government has is subject to disclosure under FOIA. Only "agency records" that already exist are subject to FOIA's mandate of access. Agencies are not required to create new records to fulfill a FOIA request.[1]

Defining Agency Records

The FOIA does not specifically define “agency record,” although it defines a “record” as “any information that would be an agency record subject to the requirements of [FOIA] when maintained by an agency in any format, including an electronic format; and any [such] information . . . that is maintained for an agency by an entity under Government contract, for the purposes of records management.”[2]

In U.S. Dep’t of Justice v. Tax Analysts, the Supreme Court provided a two-part definition for what constitutes an “agency record” under FOIA.[3] To satisfy this definition, an agency must

  1. “‘create or obtain’ the requested materials,”[4] and
  2. “be in control of the requested materials at the time the FOIA request is made.”[5].

Create or Obtain

As noted above, an agency must either "create or obtain" a record in order for it to be an "agency record" subject to FOIA under the first prong of the Tax Analysts test.

Create

An analysis of whether an agency has created a record focuses on “the process by which the records are generated,” rather than who provides “the contents of the records.”[6] As one court explained, “[t]his distinction is important, because ‘[t]he FOIA deals with documents, not information.’”[7] For example, one court held that White House visitor logs were created by the Secret Service (a component of the Department of Homeland Security) — even though much of the visitors’ information was provided by Presidential and Vice-Presidential staff members — as the agency “largely generated” the logs themselves.[8] Since Secret Service officials entered visitors’ information into a computer system, processed it to conduct background checks, and used it in verifying visitors when they arrived, the court found that the records were created by the Secret Service, “[r]egardless of what information may be supplied by outside actors.”[9] You should likewise argue that the way in which the records are generated within an agency — for example, with the involvement of agency personnel — shows that it is a record created by that agency.

Just because a private entity, such as a government contractor, is involved with certain records does not mean they are not created by the agency. Even where records are “neither created by agency employees” nor “currently located on agency property,” they are still “created” by the agency so long as the contractor “acted on behalf of [the agency] in creating the” records at issue.[10]

If the agency exercised “extensive supervision and control” over the contractor in its development of the records, they can qualify as agency records.[11]For example, a court ruled that records that a company “produced in connection with” its contract with a government agency were generated “on behalf of” the agency, where the agency hired a private company to audit an agency study and reproduce the study results — using specific agency-prescribed methods — for the purpose of validating their accuracy.[12]

Similarly, a court held that records in the physical possession of a contractor operating a government-owned animal facility were records created “on behalf” of the agency.[13] The court pointed to the facts that the agency owned the building where the records were housed, the agency required the contractor to maintain the records, the records related to animals owned by the agency, and the files were subject to agency inspection.[14]

In contrast, a court held that the Small Business Administration did not have to produce the cell phone records of a former employee from Verizon Wireless, as the agency did not “extensively supervise[]” or become “otherwise significantly entangled with Verizon’s production and management of the records.”[15]

Obtain

An agency “obtains” a record if it physically has possession of it.[16]

Control

The Supreme Court has explained that “control” means “the materials have come into the agency's possession in the legitimate conduct of its official duties.”[17]. It further specified that the whether an agency has "control" of a record is determined at the time of the request.[18]

Courts generally evaluate four factors in determining whether an agency “controls” requested records:

  1. the intent of the document's creator to retain or relinquish control over the records;
  2. the ability of the agency to use and dispose of the record as it sees fit;
  3. the extent to which agency personnel have read or relied upon the document; and
  4. the degree to which the document was integrated into the agency's record system or files.[19]

Consistent with courts’ emphasis on the agency’s actual use of the records in this four-part analysis, they have held that ownership is not the same as control,[20] so it will likely not be enough to merely assert that the agency has control over a record because it owns the record. For example, in one case, a requester unsuccessfully argued that since the Federal Housing Financial Authority held “title” to certain Freddie Mac or Fannie Mae records when the agency became conservator of the companies, the court did not need to consider the four control factors.[21] The court rejected this proposition, stating that “our cases have never suggested that ownership means control.”[22]

Looking next to the four factors, the court found that agency personnel never used the records, and stated that “an agency cannot integrate into its record system a document created by a third party that none of its employees have read.”[23] Although the companies — the documents’ creators — had “intentionally relinquished control over the records when they agreed to the conservatorship,” and the agency could freely use and dispose of the records, the court found the fact that there had been no actual use of the records to be “fatal” to the requester’s control argument.[24]

In Doyle v. U.S. Dep't of Homeland Sec., the court found that the Secret Service did not have control over Presidential Schedule Documents, because it "...only passively received them from the White House." [25] The court noted that "the considerations that render FOIA inapplicable to WAVES and ACR records apply with equal force to the Presidential Schedule Documents." [26]

The Ninth Circuit has declined to adopt the four factor test outlined above, finding it in tension with Supreme Court precedent. Instead, it held that "a court may consider a range of evidence to determine whether specified records are in the agency’s possession in connection with agency-related business, or instead involve personal matters not related to the agency’s 'transaction of public business,'" which could include documents which are used by an agency employee in connection with agency business but relate to misconduct. The Court noted that if an agency and another outside party engage in communications, those are also agency records. [27]

Searching/querying databases is not creating a "new record"

Some courts have struggled to analogize some of these principles, which were developed in the context of paper records, to computer databases and other electronic records. But according to the Ninth Circuit, the only federal appellate court to address the issue in depth, “using a query to search for and extract a particular arrangement or subset of data already maintained in an agency’s database does not amount to the creation of a new record.”[28] "So long as the relevant information and data fields already exist in the database maintained by the agency, the result produced by a query is an existing record, regardless of the form it takes."[29]

The Second Circuit has adopted this standard and actually gone further.[30] The Second Circuit ordered an agency to find a reasonable way to substitute non-exempt data points in place of exempt data points, since the data was essentially useless otherwise. The court emphasized the agency was obligated to offer the public "equal access to non-exempt records" as the agency itself enjoyed in the ordinary course of its business, including both content and functionality.[31]

Some courts have found, however, that agencies are not required to produce a screenshot or printout of electronic databases, as opposed to exporting the actual database contents.[32]

Agency records vs. Congressional records

While FOIA applies to most executive branch entities, it does not apply to Congress.[33] A question can arise, however, as to the scope of FOIA's disclosure requirements when an executive branch entity either possesses records sent from Congress or creates records in response to a request from Congress.

In United We Stand America v. IRS, the Court of Appeals for the D.C. Circuit confirmed that the four-part Burka[34] test applies in the context of determining whether a record is an "agency record" subject to FOIA or a Congressional record that is not.[35] The primary analysis in this context is whether Congress has expressed an intent to control the document as compared with the agency's ability to control and use the document.[36]

At issue in United We Stand were a number of documents related to a request from the Joint Committee on Taxation to the IRS, including a letter from the Joint Committee to the IRS requesting specified categories of documents and information and a seventeen-page letter with three attachments that the IRS prepared in response.[37] In evaluating who had control over the records, the Court held that there was "sufficient indicia of congressional intent to control, but only with respect to the Joint Committee's April 28 request and those portions of the IRS response that would reveal that request."[38] The letter from the Joint Committee, for example, stated that "[t]his document is a Congressional record and is entrusted to the Internal Revenue Service for your use only. This document may not be disclosed without the prior approval of the Joint Committee."[39] The Court reasoned, however, that the reference to "[t]his document" referred only to the letter from the Joint Committee, and did not apply to the IRS's response except to the extent that the response would reveal the Joint Committee's request.[40] Those records were, therefore, required to be released.[41]

A number of arguments raised by the IRS were rejected by the Court, including (1) that the Joint Committee believed the IRS's internal manual would ensure the confidentiality of its response,[42] (2) that the Joint Committee's past dealings with the IRS led it to believe the records would remain confidential,[43] and (3) that the continued objection of the Joint Committee to the release of the records demonstrated its intent to control them.[44]

In rejecting the second argument, the DC Circuit stated that any "understanding" between the Joint Committee and the IRS based on past dealings "is far too general to remove the IRS response from FOIA's disclosure requirement. Skeptical of such pre-existing agreements, we have required a more specific showing of congressional intent to control documents sought by FOIA requesters."[45]

In rejecting the third argument raised by the IRS, the Court noted that it had previously emphasized that "the absence of contemporaneous and specific instructions from [Congress] to the agencies limiting either the use or disclosure of the documents[]” can defeat a claim of Congressional control.[46] In other words, "post-hoc objections to disclosure cannot manifest the clear assertion of congressional control" that are required to take a document outside of FOIA's scope.[47]

Agency records vs. personal records

Agencies sometimes contend that a particular record is a personal record of an employee, not an agency record subject to FOIA.

The DC Circuit has adopted a totality of the circumstances test to distinguish “agency records” from personal records, which “focus[es] on a variety of factors surrounding the creation, possession, control, and use of the document by an agency.”[48]. The test specifically examines:

  1. “the purpose for which the document was created,”
  2. “the actual use of the document,” and
  3. “the extent to which the creator of the document and other employees acting within the scope of their employment relied upon the document to carry out the business of the agency.”[49]

In one case, a court applied these factors in finding that five agency officials’ electronic calendars were agency records, but a sixth was not, based on the way in which they were used. The court ruled that five electronic calendars of agency officials were agency records, rather than personal records, because they were “continually updated and used to conduct agency business.”[50] The officials made the calendars available to other agency employees to enable them to determine the officials’ availability, and the officials themselves relied on the calendars to organize their business appointments.[51] These factors distinguished the calendars from “a personal diary containing an individual’s private reflections on his or her work-but which the individual does not rely upon to perform his duties.”[52] To the extent that the calendars also included personal appointments, the court explained, this did not make the calendars non-agency records; instead, the agency could redact the personal entries.[53] However, the court ruled that the calendar of an agency assistant administrator was not an agency record because he distributed it only to his secretary and any temporary secretaries to communicate his availability to them.[54] Other than the secretaries, no agency employees relied on his calendar.[55]

The Ninth Circuit has declined to adopt the above test, finding that DC Circuit's approach is in tension with Supreme Court precedent. Instead, the court held that it "may consider a range of evidence to determine whether specified records are in the agency’s possession in connection with agency-related business, or instead involve personal matters not related to the agency’s “transaction of public business.[56]

Recent district court cases on agency records

Recent district court cases regarding this topic from TRAC's FOIA Project. Visit their issue search page for more options.

External Links

References

  1. Kissinger v. Reps. Comm. for Freedom of the Press, 445 U.S. 136, 152, 100 S. Ct. 960, 969, 63 L. Ed. 2d 267 (1980).
  2. 5 U.S.C. § 552(f)(2)
  3. U.S. Dep’t of Justice v. Tax Analysts, 492 U.S. 136 (1989)
  4. Tax Analysts, 492 U.S. at 144 (quoting Forsham v. Harris, 445 U.S. 169, 182 (1980))
  5. Tax Analysts, 492 U.S. at 145
  6. Judicial Watch, Inc. v. U.S. Secret Serv., 803 F.Supp.2d 51, 57 (D.D.C. 2011) (quotingCitizens for Responsibility & Ethics in Wash. v. Dep’t of Homeland Sec., 527 F.Supp.2d 76, 90 (D.D.C. 2010)) (internal quotation marks omitted).
  7. Judicial Watch, Inc., 803 F.Supp.2d at 57 (quoting Citizens for Responsibility & Ethics in Wash., 527 F.Supp.2d at 90)).
  8. Judicial Watch, Inc., 803 F.Supp.2d at 57.
  9. Id.
  10. Burka v. U.S. Dep’t of Health & Human Servs., 87 F.3d 508, 515 (D.C. Cir. 1996).
  11. Burka v. U.S. Dep’t of Health & Human Servs., 87 F.3d 508, 515 (D.C. Cir. 1996).
  12. Chicago Tribune Co. v. U.S. Dep’t of Health & Human Servs., No. 95 C 3917, 1997 WL 1137641 at *13-14 (N.D. Ill. Mar. 28, 1997).
  13. In Def. of Animals v. Nat’l Insts. of Health, 543 F.Supp.2d 70, 77 (D.D.C. 2008).
  14. Id.
  15. Am. Small Bus. League v. U.S. Small Bus. Admin., 623 F.3d 1052, 1053 (9th Cir. 2010), cert. denied, 131 S.Ct. 2460 (2011).
  16. Tax Analysts, 492 U.S. at 143-44.
  17. Tax Analysts, 492 U.S. at 145.
  18. U.S. Dep't of Justice v. Tax Analysts, 492 U.S. 136, 145, (1989)
  19. Burka, 87 F.3d at 515 (quoting Tax Analysts v. U.S. Dep’t of Justice, 845 F.2d 1060, 1069 (D.C. Cir. 1988), aff’d on other grounds, 492 U.S. 136 (1989))
  20. Judicial Watch, Inc. v. Fed. Hous. Fin. Agency, 646 F.3d 924, 927 (D.C. Cir. 2011).
  21. Judicial Watch, Inc. v. Fed. Hous. Fin. Agency, 646 F.3d at 927.
  22. 'Judicial Watch, Inc. v. Fed. Hous. Fin. Agency, 646 F.3d at 927.
  23. 'Judicial Watch, Inc. v. Fed. Hous. Fin. Agency, 646 F.3d at 928.
  24. 'Judicial Watch, Inc. v. Fed. Hous. Fin. Agency, 646 F.3d at 927.
  25. Doyle v. U.S. Dep't of Homeland Sec., 331 F. Supp. 3d *19 (S.D.N.Y. 2018).
  26. Id.
  27. Rojas v. FAA, No. 17-17349, 2019 WL 5382055 (9th Cir. Oct. 22, 2019) https://law.justia.com/cases/federal/appellate-courts/ca9/17-17349/17-17349-2019-10-22.html
  28. Ctr. for Investigative Reporting v. United States Dep't of Just., 14 F.4th 916, 938 (9th Cir. 2021).
  29. Ctr. for Investigative Reporting v. United States Dep't of Just., 14 F.4th 916, 939 (9th Cir. 2021)
  30. Am. C.L. Union Immigrants' Rts. Project v. United States Immigr. & Customs Enf't, 58 F.4th 643, 659 (2d Cir. 2023).
  31. Am. C.L. Union Immigrants' Rts. Project v. United States Immigr. & Customs Enf't, 58 F.4th 643, 656 (2d Cir. 2023).
  32. See Rutila v. United States Dep't of Transportation, 72 F.4th 692, 697 (5th Cir. 2023).
  33. 5 U.S.C. § 552(f)
  34. Burka, 87 F.3d at 515
  35. See United We Stand Am., Inc. v. I.R.S., 359 F.3d 595, 598-601 (D.C. Cir. 2004)
  36. United We Stand Am., Inc. v. I.R.S., 359 F.3d at 599-600
  37. United We Stand Am., Inc. v. I.R.S., 359 F.3d at 597
  38. United We Stand Am., Inc. v. I.R.S., 359 F.3d 595, 600 (D.C. Cir. 2004)
  39. United We Stand Am., Inc. v. I.R.S., 359 F.3d 595, 600–01 (D.C. Cir. 2004)
  40. See United We Stand Am., Inc. v. I.R.S., 359 F.3d 595, 600 (D.C. Cir. 2004)
  41. See United We Stand Am., Inc. v. I.R.S., 359 F.3d 595, 605 (D.C. Cir. 2004) (remanding "with instructions to determine whether the IRS response can be redacted to protect the confidentiality of the Joint Committee's April 28 request and, if so, to order the IRS to release any segregable portions that are not otherwise protected by one of FOIA's nine exemptions . . . .")
  42. United We Stand Am., Inc. v. I.R.S., 359 F.3d 595, 601 (D.C. Cir. 2004)
  43. United We Stand Am., Inc. v. I.R.S., 359 F.3d 595, 602 (D.C. Cir. 2004)
  44. United We Stand Am., Inc. v. I.R.S., 359 F.3d 595, 602 (D.C. Cir. 2004)
  45. United We Stand Am., Inc. v. I.R.S., 359 F.3d 595, 602 (D.C. Cir. 2004)
  46. United We Stand Am., Inc. v. I.R.S., 359 F.3d 595, 602 (D.C. Cir. 2004)(quotation and citation removed)
  47. United We Stand Am., Inc. v. I.R.S., 359 F.3d 595, 602 (D.C. Cir. 2004)
  48. Bureau of Nat. Affairs, Inc. v. U.S. Dep't of Justice, 742 F.2d 1484, 1490 (D.C. Cir. 1984)
  49. 'Bureau of Nat. Affairs, Inc. v. U.S. Dep't of Justice, 742 F.2d 1484, 1493 (D.C. Cir. 1984).
  50. Consumer Fed’n of Am. v. Dep’t of Agric., 455 F.3d 283, 292 (D.C. Cir. 2006).
  51. Id.
  52. Id. (quoting Bureau of Nat’l Affairs, Inc., 742 F.2d at 1493).
  53. Consumer Fed’n of Am., 455 F.3d at 293.
  54. Id.
  55. Id.
  56. Rojas v. Fed. Aviation Admin., 941 F.3d 392, 409 (9th Cir. 2019)