216 Hours
Saved per week on manual work
88%
Less time processing SITREPs
90%
Less time preparing the commander's update
Legion software is used by the U.S. Army, proven by 20,000+ users across U.S. Special Operations Command, and deployed on-prem at a U.S. Department of Energy national laboratory.
What does the Current Operations Officer Pack do?
Built for the J-3, G-3, N-3, A-3, and S-3 sections running current operations from battalion to joint headquarters.
See what changed against the plan
New reporting checked against the order, with the source behind every element.
- Reads current reporting against the baseline order, the decision support matrix, and running estimates, and names what changed
- Shows the tasks, timelines, assumptions, and decision points each change touches
- Every element cites the report or paragraph behind it, so the officer can verify it
Know what needs the commander
Triggered CCIRs and unit status in one view, checked on the schedule your staff sets.
- CCIR Status View shows which CCIRs current reporting has triggered, which are on watch, and which are clear
- Force Posture View carries subordinate unit locations, activity, and status, with the time each report came in
- Where the evidence can’t support a confident call, Legion says so and names the gap
Draft the products from the decision
The FRAGO, sync package, and DSM updates start from the decision the staff made.
- Drafts the FRAGO, sync package, ISR request, and DSM updates for the staff to edit and approve
- Each draft carries the facts established, the assumptions still open, and the conflicts still unresolved
- Rapid Operational Decision-Making holds the decision cycle, so each step opens with what the last one produced, including RDSP for Army staffs
Agents do the work. You stay in charge.
Nothing becomes a staff product until a person approves it.
Works with the systems you already use
Orders and guidance
- Baseline order and annexes
- Commander’s guidance
- Decision support matrix
- FRAGOs
Current reporting
- SITREPs
- ISR reporting
- Staff chat
- Trackers
Situational awareness
- Unit locations
- Activity
- Status
- Report times
Staff products
- Running estimates
- Sync products
- Commander’s update
- Draft orders
Deployment and security
- Same Pack, same governance in cloud, on-prem, and air-gapped deployments
- IL2 through IL6 for DoW networks, FedRAMP High for the cloud platform, ready to manage ITAR data
- Honors your existing access controls, with audit trails and full attribution including agent actions
- Your data stays in your environment. Models never train on it.
See the Current Operations Officer Pack in your environment
- A working session on an approved sample of your own orders and reporting
- A change assessment with its sources attached
- A pilot scoped to one staff section and one recurring workflow, measured on one number
FAQs
What is the Current Operations Officer Pack?
The Current Operations Officer Pack is a set of Legion apps for military operations sections. It reads current reporting against the plan you already have, sets out the decision the commander faces, develops and compares options, and drafts the products, with your staff approving at each step.
Who is it for?
J-3, G-3, N-3, A-3, and S-3 sections running operations from battalion to joint headquarters, and the commanders who decide whether to fund it. The staff you have spends more of the day on judgment and less on finding and formatting, without adding people.
How is this different from a general-purpose AI assistant our staff already has?
An assistant may retain a conversation and retrieve the same documents, but that history isn’t the section’s approved shared state. The Pack holds the section’s reading of the plan under the unit’s approval gates and permissions. The facts, assumptions, and unresolved source conflicts established at assessment are still attached when the FRAGO is drafted three steps later.
How does Legion decide what needs the commander?
Legion shows what each change touches: tasks, timelines, assumptions, CCIRs, decision points, and running estimates. What has triggered a CCIR, what is on watch, and what is clear sits in one view. Where the evidence can’t support a confident call, Legion says so and names the gap. Your staff decides what goes to the commander.
What results has the Pack delivered?
The Pack has saved 216 hours a week of repetitive manual work. SITREP processing dropped from 8 hours to under 1 hour (88% less), and commander’s update brief preparation time dropped by 90%.
What is RDSP, and does the Pack support it?
RDSP is the rapid decision-making and synchronization process, the Army’s doctrinal method for updating an existing plan when conditions change. The Pack supports it, and it supports the same work under other services’ terminology. That means assessing what changed, developing and validating options where needed, and producing the decision products, with each step starting from what the last one produced.
Does the Pack support MDMP and MCPP?
Yes. Legion reads the higher headquarters order and its annexes, then identifies the mission, intent, constraints, and the tasks that fall to your unit. Deliberate planning starts from that baseline. MCPP, the Marine Corps expression of the same process, uses the same workflow with different terminology.
Does Legion replace our systems of record?
No. Your orders, reporting, and staff products stay where they live. Legion reads from the sources your staff names as authoritative and drafts products from that context. Your staff decides what is issued and what goes into your systems of record.
Who approves what Legion produces?
Your staff does. Recommendations, decision packages, and draft orders all wait for a person. Legion prepares the work and states what it rests on. Full attribution records what was done, by which agent or person, and on whose behalf.
What happens when the officer who set this up rotates out?
The approved workflow stays with the unit through PCS, change of command, and unit rotation. Authorized owners control changes and those changes are logged. Incoming staff inherit the approved version along with the record of what was produced under it.
Does Legion monitor our reporting continuously?
No. Legion checks incoming reporting against your CCIRs on a schedule your staff configures. What has been triggered is there when you look. Legion doesn’t send alerts.
Our information is scattered across email, chat, and file shares. Does this still work?
Yes, within the sources your staff names. Legion reads from the systems it is connected to, and your staff decides which those are. The Pack is explicit about what it is and isn’t reading.
What systems does the Current Operations Officer Pack connect to?
TAK, Microsoft SharePoint, and Microsoft Teams are connected today. Legion reads from them through the identities, permissions, and access your organization approves. Additional integrations are built where demand is confirmed.
What does Legion need from our systems to deploy?
Read access through organization-approved identities and permissions, and a named set of authoritative sources: the baseline order, commander’s guidance, the decision support matrix, current reporting, and running estimates. Your systems stay the master copy.
Can the Pack run on a DoW network or in an air-gapped environment?
Yes. The same apps and the same governance run in cloud, on-prem, and air-gapped environments. Legion operates across IL2 through IL6 for DoW networks, and cloud deployments carry FedRAMP High authorization.
How do we start?
Bring an approved sample of your orders and current reporting to a working session. Legion runs it through the Pack and returns a change assessment with its sources attached. A pilot on one recurring workflow is up and running in weeks.