Ready to get started? This is the place to get answers to your questions and review requirements for creating, integrating and submitting content in collaboration with The Army Distributed Learning Program (TADLP). Below you will find a comprehensive index of detailed instruction and guidance on content development. Documents are tailored to specific needs and are housed on the Central Army Registry (CAR). Each section offers a wealth of resources and information on regulations, workflow, documentation and requirements. Headings below are hyperlinks on mouseover.
Army distributed learning follows a series of technical standards and specifications throughout the design, development, and implementation process. Army guidance as presented in TRADOC Regulation 350-70 and associated pamphlets. Links to current versions of this guidance is found in REFERENCES in this website. This guidance is part of the Army’s centralized contract and are presented here for a quick reference check by process.
DL products are accepted in accordance with the Army Acceptance Criteria. Acceptance Criteria 3.0 was developed in early August and any new course development starting 1 October will be required to use ACTS and CCTL Parser tool to create files for certification. Courseware in development prior to 1 October 22 will be required to use ACTS and CCTL Parser beginning 1 Jan 23:
The following are stand-alone products to assist in DL development:
Alerts provide latest guidance from TADLP on emerging software requirements for DL products, including software updates and updated standards:
Please Note: This is not the contact number for elearning students, but for TADLP developers.
Students should contact the The Army Training Help Desk (ATHD) for help with DL courseware by using the ATHD icon below.
TADLP Office Telephone:
CIV. 757 878-4516
Proponent in-house development teams can use the Courseware Assistance Request Support (CARS) system for assistance.
Electronic delivery is available to DL Developers for submission of group trials and functional test files as well as final “gold” copy deliverables using Distributed Enterprise Asset Repository (DEAR)