Common use of RECORDS DESCRIPTION Clause in Contracts

RECORDS DESCRIPTION. The Privacy Act at 5 U.S.C. § 552a(o)(1)(C) requires that each CMA specify a description of the records that will be matched and exchanged, including each data element that will be used, the approximate number of records that will be matched, and the projected starting and completion dates of the program.

RECORDS DESCRIPTION. The Privacy Act Act, at 5 U.S.C. § 552a(o)(1)(C) ), requires that each CMA specify a description of the records that will be matched and exchangedmatched, including each data element that will be used, the approximate number of records that will be matched, and the projected starting and completion dates of the matching program.

RECORDS DESCRIPTION. The Privacy Act at 5 U.S.C. § 552a(o)(1)(C) requires that each CMA for protected data specify a description of the records that which will be matched and exchanged, including each a sample of data element elements that will be used, the approximate number of records that will be matched, and the projected starting and completion dates of the program.

RECORDS DESCRIPTION. The Privacy Act at 5 U.S.C. § §552a(o)(1)(C) requires that each CMA specify a description of the records that will be matched and exchangedmatched, including each a sample of data element elements that will be used, the approximate number of records that will be matched, and the projected starting and completion dates of the program.

RECORDS DESCRIPTION. The Privacy Act at 5 U.S.C. § Act, subsection 552a(o)(1)(C) ), requires that each CMA specify a description of the records that will be matched and exchangedmatched, including each a sample of data element elements that will be used, the approximate number of records that will be matched, and the projected starting and completion dates of the program.

RECORDS DESCRIPTION. The Privacy Act at 5 U.S.C. § 552a(o)(1)(C552a(o)(l)(B) requires that each CMA specify a description of specifically describe the records that will be matched and exchanged, including each data element that will be used, the approximate number of records that will be matched, and the projected starting and completion dates of the program.