Narrative:

On the flight in question; as captain; my responsibilities included verification of effective dates of the data and other company documents onboard the aircraft efbs against the dispatch release. Although I do not remember the exact dates; I do recall that the effective dates were within the tolerances stated in the dispatch release and marked a check next to each document. Furthermore; I asked my first officer to confirm my verification by checking the effectivity of the documents on his efb as well. Both efbs were within tolerance to the best of my knowledge. The two programs in question also include a warning flag; indicating that the effective dates have been exceeded; no warnings were observed on either program.

Google
 

Original NASA ASRS Text

Title: An A319 Captain's check of the effective dates of the EFB data was questioned after the fact. The reporter remembers no error was indicated by the self monitoring warning system.

Narrative: On the flight in question; as Captain; my responsibilities included verification of effective dates of the data and other company documents onboard the aircraft EFBs against the dispatch release. Although I do not remember the exact dates; I do recall that the effective dates were within the tolerances stated in the dispatch release and marked a check next to each document. Furthermore; I asked my First Officer to confirm my verification by checking the effectivity of the documents on his EFB as well. Both EFBs were within tolerance to the best of my knowledge. The two programs in question also include a warning flag; indicating that the effective dates have been exceeded; no warnings were observed on either program.

Data retrieved from NASA's ASRS site as of April 2012 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.