Army annual training and AR 350-1 tracking guide

The real problem: the training picture is split

Most units do not miss Cyber Awareness or SHARP because nobody cares. They miss them because the working picture is split. Completions live in an official training system. The next due date lives on a shared drive. A schoolhouse certificate lives in a personal email. A command policy letter lives in a group chat. A new arrival’s gaps live in someone’s head until the week of a gate: a board, a school packet, or a deployment checklist.

A useful leader habit is smaller than a training-management system. It answers four questions before the next admin huddle: what is required for this Soldier in this unit, who said so, when is it due under the command’s actual window, and what still needs a person and a date. Official systems still file the legal record. The leader’s job is to see the gap early enough to act.

What annual training and AR 350-1-related tracking mean in practice

Annual training, in everyday unit language, is the recurring individual and collective work a Soldier must complete on a cycle the command can brief. Some items truly reset every year. Some are biennial, one-time plus refreshers, or commander-owned. Calling everything “annual” is how people invent a false +365 due date and then argue with the official tracker.

AR 350-1 is the Army Training and Leader Development regulation. Units cite it when they talk about mandatory individual training, additional individual training the commander owns, and the broader training-management process. This page does not reprint tables, frequencies, or delivery notes. Confirm the current edition, any ALARACT or fragmentary change, and the list your unit actually uses on Army Publishing Directorate.

Keep the jobs separate. Tracking is a visibility habit. Completing the course is a delivery event in the official schoolhouse or unit program. Filing the completion is an official-system event. Green Book can help only with the first job: an unclassified working copy you will actually look at.

• Required: someone can name the item and the class of source, not just “it is on the slide.”
• Provenance: headquarters publication, command policy, local SOP, or schoolhouse, stated in one line.
• Due window: the date your command or current policy actually uses, not a guessed anniversary.
• Evidence: the official system or unit process shows complete before you mark the local note done.

Provenance: where a requirement actually comes from

A tracking row without a source is a rumor. Before you put a due-out on a calendar, write the class of authority in unclassified language. Headquarters publications (AR 350-1 and the other regulations it points to) are one class. Command policy letters and the unit training calendar are another. MOS, additional-skill, or schoolhouse prerequisites are a third. Local “we always do this in January” habits are a fourth, and they are the easiest to confuse with Army-wide rules.

Component and duty status change the picture. Active and Reserve or National Guard windows are not always the same. A civilian or contractor item on a headquarters table is not automatically a Soldier item. A commander-owned additional task is not the same as a headquarters-mandatory cycle. If you cannot say which class you are looking at, you are not ready to assign a date.

Confirm current text where the public can actually reach it. Army Publishing Directorate hosts the current AR 350-1 edition and related training publications. Your S-3, training NCO, or first-line leader still decides which local list applies this quarter. This page does not extract table rows or quote regulation paragraphs.

• Headquarters publication: Army-wide individual training the current AR 350-1 edition organizes.
• Command or component policy: the window and delivery method your unit actually uses.
• Local SOP or calendar: a schedule, not proof the Soldier is complete.
• Schoolhouse or MOS add-on: required for a course or duty, not automatically Army-wide CMT.
• If two sources disagree, the official training system and your chain of command win.

Update cadence: how often to refresh the working picture

A working copy goes stale in two ways. The publication changes, or the Soldier’s situation changes. You do not need a daily scrape of Army systems. You do need a rhythm that catches both kinds of drift before a gate.

Refresh the source list when Army Publishing Directorate posts a new AR 350-1 edition, when the command publishes a new policy letter, or when the S-3 changes the training calendar. Refresh the person list when someone arrives, PCSs, changes duty, goes on a profile that affects delivery, or finishes a course that should close a due-out. Refresh the dates at least monthly, and again two weeks before any board, school packet, or deployment checklist you already know is coming.

Do not treat “annual” as a rolling plus-365 formula unless your command told you that is how they compute the window. Fiscal-year batches, calendar-year gates, and “complete it in the birthday month” rules are all common. Enter the deadline the official process is using, then set your local reminder earlier than that deadline.

• Source refresh: new APD edition, ALARACT, or command policy letter.
• Person refresh: arrival, PCS, duty change, or a course that should close a row.
• Date refresh: monthly look, plus a second look before a known gate.
• Move dates on purpose when the field week slips. Do not let verbal “we will get it next drill” vanish.

Classes of recurring training, without reprinting tables

Leaders do not need a regulation excerpt to run a section. They need categories they can sort. Most AR 350-1-related tracking falls into a short set of public, unclassified buckets: information and cyber hygiene, security and insider-threat awareness, equal opportunity and SHARP, substance-misuse and suicide-prevention programs, and antiterrorism or operations-security refreshers. Units also track items that sit beside that set: weapons and CBRN currency, licenses, and collective events on the training calendar.

Name the bucket, then name the official place the completion should appear. A digital course usually closes in ALMS, JKO, or the system your command names. A platform or range event closes in the unit training process. A medical or personnel readiness item may close in MEDPROS or a personnel system, not in the training tracker. Mixing those buckets is how a leader marks “done” in a notebook while the official gate still shows red.

This page does not list frequencies, table numbers, or delivery scripts. Those change, and they differ by component. If you need the current headquarters list, open the current AR 350-1 on Army Publishing Directorate and confirm the local overlay with your training room.

• Information and cyber hygiene: usually a digital course with an official completion record.
• Security, OPSEC, and insider-threat awareness: often annual or otherwise cyclic, command-windowed.
• People programs: EO, SHARP, substance-misuse prevention, and suicide-prevention or ACE delivery.
• Force-protection awareness: antiterrorism and related command programs.
• Beside the mandatory set: qualifications and collective training that still need an owner and a date.

How to run a monthly training visibility loop

Pick one review moment that already exists: the first admin hour after recovery, the same desk time you already use for counseling follow-ups, or the training meeting you already attend. Do not invent a second formation. Walk the short list, not every publication the Army has ever issued.

First, confirm who is on your working roster this month and whether anyone new arrived. Second, scan open due-outs: anything still “waiting on a slot,” “certificate in email,” or “we will get it next drill” gets a next look date and an owner. Third, check provenance on anything you added from memory: is this headquarters, command, or local? Fourth, update official systems or turn in the evidence your S-3 actually accepts before you mark the local note complete.

• One monthly pass beats a heroic scramble the week of a board.
• Start with items that expire this month or block a known gate, not a vanity list of every course title.
• Write the official system you will check, not “training is done.”
• Official record first, local working copy second, leftover chat screenshots last.

How Green Book can hold an unclassified working copy

Green Book is an independent productivity workspace. It does not replace DTMS, MEDPROS, ALMS, ATRRS, JKO, or your S-3 training calendar, and it does not determine whether a Soldier is compliant. After you sign in, existing modules can hold the unclassified working copy a paper leader book or a chat thread tries to hold.

Use Planner for due-outs: “confirm Cyber Awareness window Friday,” “walk the new arrival’s training gaps after in-processing,” “check the official tracker before the board packet.” Use notes for short unclassified observations that would otherwise live in a chat. Use roster and leader workflow to remember who you need to talk to, not to build a shadow DTMS. If your workspace includes a training area, treat it as a local organizer for dates and unclassified evidence references you are allowed to keep, then update the official record first. Green Book does not auto-assign requirements from rank, MOS, or unit text.

• Tasks and reminders: owners and dates for expiring items and new-arrival gaps.
• Notes: unclassified course names, due windows, and follow-up facts, not certificate dumps.
• Roster / leader workflow: who to counsel or coordinate with after a missed window.
• The workspace holds a working copy. Unit process still owns official completions and compliance calls.

Common annual-training tracking mistakes

Most failures are habits, not missing software and not a missing regulation title.

• Treating every recurring item as plus 365 days from the last completion.
• Copying last year’s slide deck and calling it the current AR 350-1 list.
• Keeping due dates only in a group chat that scrolls away before the next gate.
• Marking a local note complete before the official training system shows the same story.
• Mixing medical, personnel, and training gates into one “red or green” slogan.
• Building a second DTMS in a spreadsheet “just in case.”
• Storing certificates, CUI, or sensitive personal details in a commercial app.
• Assuming a Green Book task, note, or training row is filed in DTMS, MEDPROS, or ALMS.

Example use (illustrative)

A squad leader starts the first admin Monday of the month with three open items: a new arrival still in-processing, a digital course that expires before a school packet, and a command-directed refresher the platoon sergeant mentioned in passing. They put two tasks on the planner: confirm the official tracker for the new arrival by Wednesday, and walk the expiring course with the Soldier before Friday close of business. They write a one-line note that the command refresher is a local calendar item, not something they invented from memory, so the next huddle stays specific.

Wednesday, the official system shows the new arrival still missing one headquarters-mandatory course. They keep that row open and add a next look after the scheduled computer-lab hour. Friday the digital course is complete in the official system; they mark the local task done. The command refresher stays on the calendar until the training meeting records attendance. None of that replaces DTMS or AR 350-1. It keeps the leader from discovering all three problems the morning of the packet. This page on purpose does not include sample names, unit identifiers, or certificate numbers.

Who this helps

Team leaders and squad leaders who have to brief who is current before a gate without living in the S-3 shop.

Platoon sergeants and platoon leaders who need a monthly visibility loop without pretending they are the training officer.

Training-room NCOs who want Soldiers to arrive with dated facts, not “I think I did it last year.”

Anyone whose current system is a chat thread, a last-year slide, and a hope that the next board packet is kind.

Educational guidance vs official policy

Green Book is not an official Army or DoD product and is not endorsed by the U.S. Army or the Department of Defense. Training policy, frequencies, delivery methods, and filing systems are governed by your unit and current publications, not by this website.

This is not a certified compliance product, not a DTMS, MEDPROS, ALMS, or ATRRS interface, and not a guarantee of a green training gate. Always verify current procedures with official publications and your chain of command. Start with Army Publishing Directorate when you need the current AR 350-1 edition your unit requires.