Group

Submitting an Item

Submitting an item to the Roadmap is straightforward. Here's how it works, step by step.

Step 1: Choose a type

When you click Submit New Item, you'll first be asked to choose the type of submission. Types are categories that describe what kind of item this is, for example a policy proposal, an operational change, a training request, or a technical improvement.

Each type may have its own set of fields and prompts to help you provide the right information. Pick the one that best fits what you're putting forward. If you're not sure, read the description shown for each type. It'll point you in the right direction.

Step 2: Fill in the details

Once you've picked a type, you'll see the submission form. Depending on the type, this might be a simple free-text description, or it might include structured fields asking specific questions (like "What problem does this solve?" or "Who would this affect?").

Either way, write clearly and give enough detail that someone unfamiliar with the idea can understand what you're proposing and why. You don't need to have every answer. That's what the later stages are for. But the more context you give up front, the smoother things will go.

Step 3: Submit

Once you're happy with what you've written, hit submit. Your item will land in the Received stage, where it'll be picked up and assessed. You'll be listed as the Originator, the person who brought this forward.

From here, you can follow along as it progresses through the stages. You'll be automatically subscribed to updates, and you can always come back to check on things, add comments, or respond to questions.

Above: Creating a new item on the roadmap, by selecting a template

Each Roadmap item has a type, which determines how the submission form looks and what information you're asked to provide.

What types are for

Types group items by purpose. They help us organise submissions and make sure the right information gets captured early on. For example, a "Policy Proposal" type might ask you to describe the current situation and what you'd like to change, while a "Technical Request" type might ask for details about the system involved and the expected outcome.

When you pick a type during submission, you may see a short prompt or description explaining what this type is for and what kind of information to include. Read it. It's there to help.

Structured fields

Some types use structured fields instead of (or alongside) a free-text description. These are specific questions or input fields tailored to that type of submission. They make it easier to provide the right information in a consistent format, and they make it easier for reviewers to understand your proposal quickly.

The fields might include text inputs, longer text areas, dropdowns, checkboxes, dates, or URLs, whatever makes sense for that type of item.

Automatic titles

Some types will automatically generate a title for your item based on what you fill in. This keeps titles consistent across similar items. If the type you chose does this, you won't need to write a title yourself. It'll be assembled from your answers.

Tags

Items can also be tagged with additional categories, like which branch or area of UNITAF the item relates to. Tags help with filtering and make it easier to find related items later. You'll have a chance to add these during submission.

Who manages the templates?

Item types and their templates are managed by J11 Command Support. They can create new types, modify the structured fields, update prompts and descriptions, configure default Chain of Responsibility assignments, and set up child item templates. If you think a type is missing or a template could be improved, that's a good thing to raise with J11 or submit as a Roadmap item itself.

The better your submission, the smoother the process. Here are some practical tips for writing something that's easy for others to engage with.

Explain the "why" first

Before diving into your idea, set the scene. What's the situation right now? What's the problem or opportunity you've noticed? Help the reader understand the context so your proposal makes sense.

Be specific, but don't overthink it

You don't need a polished plan. What you do need is enough detail that someone can understand what you're proposing without having to guess. If there are open questions you haven't answered yet, that's fine. Flag them. The later stages exist for exactly that kind of thing.

Keep it grounded

Write about what you've actually observed or experienced. "During recent operations, our squad frequently ran into X" is much stronger than "It would be nice if we could improve Y." Concrete examples help people understand the real-world impact.

One idea per item

If you have three separate suggestions, submit three separate items. Bundling multiple ideas into one submission makes it harder to discuss, decide on, and track each one properly.

You can always add more later

Your initial submission doesn't need to cover everything. Once the item moves into Review or Consultation, there'll be room for discussion, follow-up questions, and refinement. Get the core idea across clearly, and the rest will follow.