Product factsheet · Defense & Intelligence · Moraph software

Mission Planning Workflow

The Mission Planning Workflow is a web workspace in Moraph Apps for unclassified administrative planning. Staff build plans from phases, checklist items, resources and movement legs, with march tables and sustainment estimates calculated from the planning factors you set; reviewers answer by area, and a designated approver approves a version, which is then locked. The approved plan downloads as a JSON file and a printable HTML file with a SHA-256 fingerprint, to print or carry on approved media where there is no network. It has no map engine, no offline application and no sync.

Product page

Principal workflows

  • Set up: Product administrators set who approves, how many reviews each round needs, the marking printed on export packages, and the movement and sustainment planning factors, and keep standard checklist sets and planning templates ready.
  • Plan: Planners build the plan as records: phases with objectives and dates, checklist items, resources, and movement legs with places, distances and departure times. Places are described in text; maps stay in your own systems.
  • Approve and issue: Reviewers answer by area, and a designated approver who didn't create the plan approves a version or returns it. The approved version is locked and stored as an export package for issue.
  • Carry and verify: Where there is no network, people use the printed or downloaded package. Back on the network, a package someone holds can be checked against the approved one, and a package from another workspace imported as a new draft. Nothing is synced or merged.

Who uses it

  • Unit and staff planners at battalion, brigade and equivalent echelons
  • Commanders who review and approve plans
  • Logistics and sustainment planners supporting deployed units
  • Expeditionary and disaster-response teams who carry approved plans to places without a network
  • Training and exercise staff who plan and review exercises

Reporting

  • Plans by stage, version and approver
  • Changes made since the last approved version
  • Approval cycle and review turnaround by area
  • Resources not yet confirmed, soonest needed first, by provider
  • Package downloads and issues, by person and plan
  • Plan history for after-action review

Features

  • Export package for use without a network: The approved plan is stored as a JSON file and a self-contained printable HTML file to print or carry on approved media; the product itself runs online in Moraph Apps.
  • Places described in text: Locations, from and to points and distances are entered as place names and kilometres measured in your own map systems; the product has no map engine and stores no map data.
  • Phases and transition criteria: Each phase has a sequence, objective, dates, lead element and the criteria for moving to the next phase, and every phase must be Ready before the plan goes into review.
  • Movement planning: Movement legs with serials, places, distances and departure times, and a march table of driving time, halts, arrival and tail clearance calculated from the planning factors your unit sets.
  • Sustainment planning: Estimates of people × days × the amount per person per day you set for each item, compared with the plan's resources to show any shortfall.
  • Checklists: Checklist items by phase, standard checklist sets applied in one step, and a board to record progress on many items; required items must be done before approval.
  • Courses of action: Several versions of a plan built and compared side by side, with the differences in dates, phases, resources, movement and sustainment listed.
  • Versioned approval: A designated approver approves a specific version, which is then locked; any later change starts a new version.
  • Package verification and import: A package file or fingerprint is checked against the approved package, and a package from another workspace can be imported as a new draft plan. Nothing is synced.
  • Issue log: Each copy of an approved package is recorded with who received it and how, such as a printed copy or approved removable media.
  • Printable products: The plan package prints from its HTML file, and movement tables, checklists, resources and plan history download as CSV for briefings.
  • Plan history: Every change, approval, return, package download and issue is recorded with the person and time, and listed per plan for after-action review.

Integrations

  • Maps and geospatial systems: The product has no map engine and stores no maps, imagery, overlays or coordinates; planners describe places in text and measure distances in your own authorized systems.
  • Unit and equipment data: Resources, checklist items and movement legs loaded by CSV import or through the Work API from your own systems, or entered by planners.
  • Plan exchange formats: Approved plans exported as a JSON package (format moraph-mission-plan-package) and a printable HTML file, for other approved systems to read.
  • Moving plans between workspaces: There is no sync: a JSON package downloaded in one workspace is carried on approved media and imported in another as a new draft plan.
  • Identity and sign-in: Users sign in to Moraph Apps through single sign-on at portal.moraph.com; there is no sign-in on a device and no smart card support.
  • Tactical edge infrastructure: The product installs nothing on devices; approved packages can be carried on approved media to edge devices your unit manages, including with Moraph's Tactical Edge Compute Node Manager.
  • Work API: Plans, phases, checklist items, resources, movement legs and reviews are available to your reporting and archive systems through the Moraph Work API.

Deployment

  • Printable plan package: The approved plan downloads as a fingerprinted JSON file and a printable page that people carry where there is no network; the workspace itself needs a connection.
  • Import at home station: A downloaded package can be imported into another workspace as a new draft; there is no sync service, and changes made elsewhere come back only by import.
  • Exercises: Exercises are planned in the same workspace as operations: each plan names the operation, exercise, deployment or event it supports. Moraph does not host a separate training environment.
  • With edge infrastructure: Can be used alongside Moraph's Tactical Edge Compute Node Manager, which keeps the record of field nodes and their software updates; the two products don't exchange data.

Security and privacy

  • Sign-in: Users sign in to Moraph Apps through single sign-on at portal.moraph.com, and product roles are granted in the Moraph Portal.
  • Role-based access: What each person can do follows their product role; building a plan is separate from approving it, and nobody approves a plan they created.
  • Package integrity: Plans are held in Moraph Apps, not on devices; each approved package carries a SHA-256 fingerprint so a copy can be checked, and files on removable media are protected under your own procedures.
  • Unclassified only: The product is for unclassified administrative planning: classified markings are refused on export packages and imports, and sensitive operational detail stays in your authorized systems.
  • Complete audit trail: Every change, approval, package download and issue is logged with the person and time, and the product offers no way to edit that history.
  • Your authority: The Suite is for unclassified use only and isn't operated on classified networks.

Limitations

  • The Suite is a planning tool. It does not compute firing solutions, control weapons or replace your organization's command and control or fire support systems.
  • It does not track forces and has no map: places and distances are what planners enter, not live feeds.
  • It has no offline application and no sync: a downloaded package is fixed at its version, and changes made elsewhere come back only as a new draft by import.
  • Packages imported from another workspace arrive as new draft plans; nothing is merged, and reviews and approvals are not carried over.
  • Distances, places and planning factors come from your own maps and procedures; Moraph supplies no planning factors and doesn't check them.
  • Devices, removable media and procedures for lost packages are your organization's responsibility; the issue log records who received each copy.
  • It is for unclassified administrative planning only; never enter classified information. Moraph does not claim accreditation for any classified environment.
  • Plans and approvals in the Suite support the commander's decisions; they do not replace orders issued through your organization's procedures.

Next steps

Request a demonstration or a technical briefing at www.moraph.com/solutions/mission-planning-workflow. Purchasing routes and company information: www.moraph.com/how-to-buy. Questions or documents: www.moraph.com/how-to-buy/request.

Generally available. Moraph LLC · Current as of October 2026.