Skip to content

Reference

Mission Planning Workflow glossary

Terms used in Mission Planning Workflow and its documentation.

Applies to Mission Planning Workflow as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.

Last reviewed 2 min readReport a problem

Terms used in Mission Planning Workflow and its documentation.

TermMeaning
Plan versionOne mission plan record. Approving it locks it; changes after that start a new version, and approving the new version supersedes the old one.
Review roundThe reviews requested since the plan last went into review. Returning a plan for changes ends the round; only the current round's answered reviews count towards approval.
Readiness checksWhat approval needs: the plan in review, every phase ready, required checklist items done or not applicable, enough answered reviews and, if the settings say so, confirmed resources.
Export packageA JSON file and a self-contained printable HTML file holding the plan for use without a network. The approved package is stored exactly as approved with a SHA-256 fingerprint.
Non-concurA reviewer's recommendation against the plan. The approver can still approve, but must record a note saying how it was addressed.
Course of actionOne of several alternative plans for the same operation, labelled (for example COA 1) and compared side by side.
March tableThe movement legs of a plan with driving time, halts, arrival and when the tail of the column clears, calculated from the distances entered and the planning factors in the settings.
Sustainment estimatePeople × days × the amount per person per day in the settings, compared with the plan's resources of the same category and unit.
Planning templateA plan kept for reuse: copied into new plans and never sent for review.
Issue logThe record of who received each copy of an approved package and how.
Residual riskThe likelihood and severity that remain with the controls in place. Its level is calculated from the thresholds in Planning settings.
Decision pointA decision the plan expects, with its criteria, decide-by time, authority and options.
Synchronization matrixA table of who does what in each phase, built from the plan's records.
LessonAn after-action finding to sustain or improve, with an owner for the corrective action.
Measure of successWhat will show that an objective was achieved (effectiveness) or that the planned tasks were done (performance), with a target, assessed after the mission.
Battle rhythmThe plan's recurring meetings and events, day by day.
Execution logThe dated entries kept while an approved plan is carried out: events, reports, instructions and decisions. Entries stay as written.
Actual datesWhen a phase really started and ended, recorded on the approved plan and compared with its planned dates.

Was this page helpful?

Report a problem with this page
What’s the problem?
Quote the step or heading if you can. Don’t include passwords or personal records.
Only if you’d like a reply. We use it for this report and nothing else.

Need help with your own setup rather than this page? Raise a support ticket.