CONOP and MFR practical preparation guide

The real problem: the product is due before the inputs are gathered

Most late CONOPs and weak memos are not a writing problem. They are an inputs problem. The mission statement lives in a voice note. The timeline lives on a whiteboard. The risk call lives in a group chat. The enclosure someone promised is still on a personal drive. The night before the brief, a well-meaning NCO writes from memory and hopes the S-3 will not notice the gaps.

Counseling and evaluation writing solve a different job: developing a Soldier against a standard and keeping accomplishments. If that is what you need, use the Army counseling and MFR guide. This page is for the ops and admin product that has to survive a rehearsal, a staff huddle, or a later “who approved this?” question.

What CONOP and MFR preparation mean in practice

A CONOP, in everyday unit language, is the short concept of how an event or operation will run: purpose, situation, mission, and enough execution and sustainment detail that another leader can brief it without calling you. Army planning doctrine lives in ADP 5-0 (The Operations Process) and FM 5-0 (Planning and Orders Production). This page does not reprint those publications. Confirm the current titles and any order or annex format your unit actually uses on Army Publishing Directorate.

An MFR is still a memorandum for record: a written lock of facts, decisions, or coordination. AR 25-50 (Preparing and Managing Correspondence) governs Army memorandum structure. Staffing a packet for signature or concurrence often uses the DA Form 5 class of records (Army Staffing Form). Headquarters, Department of the Army actions use HQDA Form 5 instead. Neither form is a CONOP, and neither is a counseling form.

Keep the jobs separate. Write a CONOP when leaders need a shared concept they can brief and adjust. Write an MFR when you need a durable administrative record. Staff the packet when someone must concur or sign. Do not mash all three into one blurry document.

• CONOP: shared concept for an event or operation, in unclassified language your unit allows.
• MFR: facts, times, decisions, and identifiers that chat will not preserve.
• DA Form 5 / HQDA Form 5: staffing and concurrence, not the concept itself.
• Counseling stays on the counseling path; do not use an ops memo to develop a Soldier.

Planning inputs to gather before you write

Start with a short intake, not a blank page. You do not need a full military decision-making process for a Saturday range or a change-of-responsibility ceremony. You do need the facts that later become purpose, mission, time, place, tasks, and constraints.

Write only what your classification and OPSEC rules allow in the system you are using. If the real overlay, frequencies, or movement details belong on a government system, keep this working copy at the unclassified “who, what, when, where, and what is still unknown” level.

• Purpose in one sentence: why this event exists, not a slogan.
• Higher intent or tasking you can cite without inventing an order number.
• Time, place, and audience: who must be there, who only needs to know.
• Constraints you already know: licenses, range windows, transportation, weather abort.
• Open questions: anything still “TBD” that would change the concept if it flips.
• Who must review before anyone treats the draft as ready to brief or sign.

A practical structure that stays readable

Doctrine publications describe planning methods and order formats. Local SOPs decide which headings your S-3 expects. A useful working outline is smaller than a full order and larger than a chat dump. For a CONOP-style product, most units can brief from purpose, situation, mission, execution, tasks, coordinating instructions, sustainment, command and signal, timeline, risk, and points of contact. Use only the headings that carry facts. Empty sections waste attention.

For a memorandum, AR 25-50 awareness means a header that identifies the office, a clear subject, numbered paragraphs, and a signature block the unit can actually use. An MFR is usually purpose, background or facts, and what was decided or recorded. Do not reprint regulation examples here. Confirm spacing, office symbols, and memorandum versus letter rules with the current AR 25-50 edition and your S-1.

• One purpose sentence that a substitute NCO can read aloud.
• Mission or subject line that names the event, not a vibe.
• Execution or facts in dated, checkable statements.
• Tasks with an owner, not “all leaders will ensure.”
• A short list of what is still unknown, so the next rehearsal has a target.

Headers, office symbols, and branding

Leaders lose time dressing a draft that still has the wrong office symbol. Header work is not decoration. It tells the reader who owns the product and whether it is a working concept or correspondence ready for a signature block.

Apply unit letterhead, crests, and office symbols only when your SOP allows those marks on the product you are making. A commercial draft with a unit crest is not an official memorandum. A user-selected “working draft” label is not a classification marking and does not make a file CUI or classified. If your unit requires official letterhead or a specific header block, add it in the approved channel before the product leaves your desk.

• Office symbol and subject first; logos last.
• Do not invent an official-looking header to make a draft feel finished.
• Unit branding follows local policy; this site does not issue letterhead.
• Handling labels you type yourself are reminders, not Army markings.

Attachments, enclosures, and the staffing packet

The concept is only half the product. The other half is what travels with it. Enclosures and attachments are how a CONOP or memo stays honest: the sketch, the timeline, the risk worksheet, the task list, or the concurrence trail. Name each enclosure in unclassified language and say what question it answers. “See attached” with no title is how packets die in a shared drive.

When the job is staffing rather than briefing, the DA Form 5 class of records (or HQDA Form 5 at Headquarters, Department of the Army) is the cover that routes concurrence. Confirm the current edition on the Army Publishing Directorate DA forms catalog. This page does not reprint form blocks. Do not treat a commercial outline as a completed staffing form.

• List enclosures by title and purpose, not by file-name leftovers.
• Keep the working copy and the official packet aligned: same facts, same dates.
• If an enclosure is still missing, write that as an open due-out, not as if it exists.
• Staffing forms and the CONOP or MFR are different records; do not merge them into one file “for convenience.”

Review and export workflow

Export is the last step, not the first. A useful loop is gather inputs, write the working outline, walk it with a second leader, fix the official facts, then produce the file your unit actually files or briefs. Printing or exporting a pretty draft does not create command approval.

Review for three things: missing inputs, claims you cannot source, and language that does not belong on the device you used. Then apply the header and enclosure list your SOP requires. Only after that should you export or transfer into the unit template. Whatever tool produced the working copy, the official product still needs local review, the right letterhead, and the routing your S-3 or S-1 already uses.

• Read it out loud once; if a substitute NCO cannot brief it, it is not ready.
• Check names, times, and grid or place names against a second source.
• Strip anything that should not live in a commercial or personal file.
• Export after review. Do not brief from the first dump.

How Green Book can hold an unclassified working copy

Green Book is an independent productivity workspace. It does not replace CPOF, command-post systems, IPPS-A, GCSS-Army, or your S-3 / S-1 tracker, and it does not file an official CONOP, memorandum, or DA Form 5. After you sign in, existing modules can hold the unclassified working copy a paper leader book or a chat thread tries to hold.

Use a CONOP or memorandum workspace, when your account includes one, as a local organizer for headings and facts you are allowed to keep unclassified. Use notes for short observations that would otherwise live in a chat. Use Planner for due-outs: “confirm transportation Wednesday,” “get S-3 eyes before Friday,” “attach the timeline before the rehearsal.” The workspace holds a working copy. Unit process still owns approval, letterhead, and filing.

• Working outline: purpose, mission or subject, and the headings you will actually brief.
• Tasks and reminders: owners and dates for missing inputs and reviews.
• Notes: unclassified facts and open questions, not CUI dumps.
• Any file you export still needs local review before official use.

Common CONOP and MFR preparation mistakes

Most failures are habits, not a missing software license and not a missing regulation title.

• Starting the document before the time, place, and purpose are confirmed.
• Copying last month’s CONOP and changing only the date.
• Using an MFR to counsel performance that belongs on the counseling path.
• Treating a unit crest on a commercial draft as official letterhead.
• Exporting before a second leader walks the facts.
• Storing classified, CUI, or operationally sensitive overlays in a commercial app.
• Assuming a Green Book draft is filed in CPOF, IPPS-A, or the S-1 correspondence log.
• Downloading a random fillable memo packet and treating it as the current AR 25-50.

Example use (illustrative)

A platoon sergeant has a Saturday land-navigation and recovery window. Monday, they write four inputs: purpose (rehearse movement and casualty collection), time and place, licensed drivers still unconfirmed, and a weather abort they already know. They put two planner due-outs: confirm transportation by Wednesday, and walk the outline with the platoon leader Thursday.

Thursday the transportation is real and one lane is still short a safety vehicle. They update the working concept and write an MFR that records the safety-vehicle gap and who will close it Friday. They do not put grid overlays or frequencies in the commercial file. Friday they apply the office symbol their SOP uses, list the timeline as an enclosure, and only then produce the file the S-3 asked for. None of that replaces FM 5-0 or AR 25-50. It keeps the product from being invented the night before. This page on purpose does not include sample names, unit identifiers, or operational details.

Who this helps

Team leaders and squad leaders who have to brief a small event without a full staff.

Platoon sergeants and platoon leaders who need a working concept before the S-3 asks for the product.

S-3 and training-room NCOs who want Soldiers to arrive with dated facts, not a blank slide.

Anyone whose current system is a chat thread, last month’s file, and a hope that the rehearsal is kind.

Educational guidance vs official policy

Green Book is not an official Army or DoD product and is not endorsed by the U.S. Army or the Department of Defense. Planning doctrine, correspondence rules, form editions, and filing systems are governed by your unit and current publications, not by this website.

This is not a certified compliance product, not a CPOF or command-post interface, and not a guarantee of approval or a successful event. Always verify current procedures with official publications and your chain of command. Start with Army Publishing Directorate when you need the current ADP 5-0, FM 5-0, AR 25-50, or DA Form 5 / HQDA Form 5 edition your unit requires.