ODNI responsibility for responding to requests for amendment or correction.
32 C.F.R. § 1701.11
in effectEffective: 2024-07-01(a) Acknowledgement of request. The D/IMO shall acknowledge receipt of a request for amendment or correction of records in writing and provide an assigned request number for further reference.
(b) Tasking of component. Upon receipt of a proper request to amend or correct a record, the D/IMO shall forward the request to the POC in the component maintaining the record. The POC shall promptly evaluate the proposed amendment or correction in light of any supporting justification and recommend that the D/IMO grant or deny the request or, if the request involves a record subject to correction by an originating agency, refer the request to the other agency.
(c) Action on request for amendment or correction. (1) If the POC determines that the request for amendment or correction is justified, in whole or in part, the D/IMO shall promptly:
(i) Make the amendment, in whole or in part, as requested and provide the requester a written description of the amendment or correction made; and
(ii) Provide written notice of the amendment or correction to all persons, organizations or agencies to which the record has been disclosed (if an accounting of the disclosure was made);
(2) Where the D/IMO has referred an amendment request to another agency, the D/IMO, upon confirmation from that agency that the amendment has been effected, shall provide written notice of the amendment or correction to all persons, organizations or agencies to which ODNI previously disclosed the record.
(3) If the POC determines that the requester's records are accurate, relevant, timely and complete, and that no basis exists for amending or correcting the record, either in whole or in part, the D/IMO shall inform the requester in writing of:
(i) The reason(s) for the denial; and
(ii) The procedure for appeal of the denial under Sec. 1701.15 of this subpart.
Source: eCFRURL: https://www.ecfr.gov/api/versioner/v1/full/2024-07-01/title-32.xmlFetched: 7/26/2026