This article explains how the legacy (2002) Everett Software Duty Roster Maker implemented DA Form 6 rotation and posting rules, and identifies the updates required to comply with the current Army publications:
AR 220‑45 (9 April 2024) – Policy
DA Pam 220‑45 (10 May 2024) – Procedures
The 2002 version was built under the older AR 220‑45, which contained both policy and procedures. The modern publications separate these responsibilities, and DA Pam 220‑45 now defines the official procedural rules that must be followed.
This article outlines:
What the 2002 version already did correctly
What it lacked
What the modern version must update
How the system handled “U” status and posted rosters
How unit‑level rosters work in the 2002 architecture
How fairness and continuity are preserved
DA Pam 220‑45 states:
“The Soldier who has had the longest break from performing duty… can be the next Soldier detailed.” (para 6)
✔ Correctly selected the Soldier with the highest counter ✔ Correctly skipped unavailable Soldiers ✔ Correctly incremented counters for all eligible Soldiers
Fully compliant. No changes required to the core rotation engine.
“All Soldiers… can be charged on that day… excluding any nonchargeable days.” (para 7b)
✔ Charged all eligible Soldiers when another Soldier performed duty ✔ Excluded Soldiers marked “A” (nonchargeable) ✔ Maintained fairness across the roster
Fully compliant. No changes required.
DA Pam 220‑45 authorizes only three codes:
A – Nonchargeable absence
D – Eligible but skipped
U – Unavailable due to misconduct
✔ Fully supported A ✔ Fully supported D ✖ Did not include a built‑in “U” code (because the older AR 220‑45 did not define one)
Update required:
Add native support for “U”
Ensure “U” Soldiers continue to accumulate chargeable days
Ensure “U” Soldiers are not eligible for selection
“Wherever the abbreviations ‘D’ or ‘U’ are used, the numbering sequence can continue…” (para 7c(4))
This means:
“U” Soldiers must continue to accumulate chargeable days
They must not lose credit
They must not be eligible for selection
They must still appear on the DA Form 6
The 2002 Duty Roster Maker did generate a DA Form 6, but its purpose was to create a plan for the upcoming duty period:
✔ Soldiers could see their scheduled duty dates ✔ Leaders could publish the plan in advance ✔ It provided predictability and transparency
After the duty period was completed, the system expected the roster maintainer to make adjustments.
The original helpfile states:
“If a soldier is a long term AWOL, or etc, remove his qualifications and he will not be scheduled on any more rosters.”
This method:
Removed the Soldier from eligibility
Removed the Soldier from the roster for that duty
Prevented them from being selected
Allowed the roster maintainer to adjust counters afterward
This was the correct workaround under the older regulation, which did not require “U” Soldiers to remain visible on the DA Form 6.
The 2002 version included a powerful Assignment Counter Editor, allowing the user to:
Subtract the point from the Soldier who failed to perform duty
Add the point to the Soldier who actually performed the duty
Maintain continuity between rosters
Ensure fairness going into the next cycle
This meant the 2002 version could handle “U” situations accurately — but only after the posted period, not during planning.
Add native “U” support during planning and posting
Keep “U” Soldiers visible on the DA Form 6
Automatically continue chargeable days
Prevent “U” Soldiers from being selected without removing qualifications
Preserve manual override capability
“A superscript number… can be manually added… to indicate the last number charged…” (para 7c(1))
✔ Treated “A” as nonchargeable ✖ Did not support superscript carryover
Optional update:
Add superscript support when generating a new DA Form 6
DA Pam 220‑45 allows:
Combined weekday/weekend/holiday rosters
Separate numbering sequences
Visual separation of weekend/holiday periods
✔ Supported consolidated weekend/holiday formatting ✔ Supported separate counters for holidays ✔ Printed red‑line separation for holiday periods ✔ Allowed holiday‑specific duty counters
“The DA Form 6 may be used by listing unit designations…” (para 9)
✔ The software can technically generate unit‑level rosters ✔ Units can be entered as roster entities ✔ Units can be marked as qualified for specific duties ✔ The rotation engine, counters, and DA Form 6 output all function correctly ✔ Counters do not mix if duties and qualifications are set up correctly
The system was not originally intended to manage:
Soldier‑level rosters and
Unit‑level rosters
…in the same datafile.
It is possible, but:
The roster list becomes visually confusing
It becomes harder to interpret mixed entities
Absence dates apply only to Soldiers, not units
Users must be careful to keep duties separated
Optional update. The system is capable, but mixed use is not recommended for clarity.
The 2002 Everett Software Duty Roster Maker was highly accurate for its time and aligned closely with the older AR 220‑45. The new 2024 publications introduce procedural requirements that primarily affect:
Native “U” status handling
Keeping “U” Soldiers visible on the DA Form 6
Automatic chargeable day continuation
Superscript carryover for “A”
Optional unit‑level roster enhancements
The legacy version’s manual counter editing ensured fairness and continuity, but the modern version must automate these behaviors to fully comply with DA Pam 220‑45.
Everett Software remains committed to providing Soldiers and leaders with accurate, fair, and regulation‑aligned duty roster tools.
« Go back
Loading knowledgebase suggestions...