CROS3Consulting

The Methodology

The Consulting C™

Six phases that help people and organizations turn a meaningful objective into practical action and a repeatable rhythm of improvement.

Meaningful change rarely begins with a complete picture. A client, leader, or team may know that something matters but still be uncertain about the objective, the evidence, the people involved, or the right first step.

The Consulting C™ exists to make that work practical. It creates sequence: clarify the objective before proposing solutions, comprehend the situation before selecting a strategy, construct a plan before asking for commitment, and prepare for action before expecting momentum.

The method is domain-neutral. It can support personal, career, executive, team, and organizational work because it starts with the conditions people actually face: incomplete information, competing priorities, constrained resources, and a need for shared ownership.

The six phases describe what clients are doing together: Clarify, Comprehend, Construct, Contract, Commit, and Commence. The work does not end when action begins. It becomes a rhythm of review, learning, re-charting, and improvement through The Operational O™.

Why the C opens instead of closing

The Consulting C™ separates the work that establishes an objective and current understanding from the work that turns that understanding into action. Clarify and Comprehend create the foundation. Construct, Contract, Commit, and Commence translate it into a practical and reviewable rhythm.

The phases are sequential, but the method is not one-directional. Evidence gathered during Commence informs the next chart, so each new cycle begins with a clearer understanding of what is working, what needs to change, and what matters now.

That is why the C opens rather than closes. A closed circle suggests returning to the starting point. The open shape makes room for a Decision Point: review the evidence and decide whether to Continue or Conclude.

The process of walking through the phases and producing the plan is Charting the MAP™. A MAP is not a static document. It is a Motivational Action Plan that can be revisited and re-charted whenever the evidence calls for another decision.

The Shape

Six phases, one opening

Clarify and Comprehend are walked once. Construct, Contract, Commit, and Commence cycle every block. The opening is the Decision Point, and it resolves to Conclude or Continue.

  1. ClarifyIdentify the trigger. Understand why now.
  2. ComprehendEstablish what is actually true.
  3. ConstructBuild the MAP.
  4. ContractEstablish mutual commitment.
  5. CommitCross from planning into doing.
  6. CommenceExecute, report, correct, repeat.
  7. The Decision PointThe opening in the C. Two answers only: Conclude or Continue.

Phase 1 of 6 · One to two sessions

Clarify

Identify the trigger. Understand why now.

What actually happened, and why are you doing something about it today?

Nobody hires a coach or a consultant because of a problem. People live with problems for years, sometimes decades, with remarkable tolerance. They hire help because of a trigger: a specific, datable event that made the problem impossible to keep tolerating. A board asks a question the executive team cannot answer. A physician says a number out loud. A competitor ships the feature you have been discussing for eighteen months. A retirement date appears on a calendar and suddenly the identity that came with the uniform has an expiration date.

The trigger matters more than the problem, for three reasons. First, it dates the urgency, which tells you how much energy is available to spend and how quickly it will decay. Second, it reveals the real stakeholder — the person whose opinion actually moved, which is frequently not the person who booked the call. Third, and most importantly, the trigger identifies which problem to solve. A leader who says "we need better strategic alignment" after a board meeting where they were unable to explain a revenue miss does not have an alignment problem. They have a measurement problem that alignment language is being used to cover.

Clarify is a deliberately slow phase, and clients often push against it. They arrive with a diagnosis already in hand and want to move directly to solutions. The work of Clarify is to hold that impulse off long enough to separate three things clients routinely conflate: the presenting complaint, the underlying condition, and the triggering event. The presenting complaint is what they say on the first call. The underlying condition is what has actually been true for years. The trigger is what changed. All three get written down, in the client's own words, and read back to them.

The phase also establishes something with no equivalent in most consulting methods: an honest accounting of what happens if nothing changes. Not a scare tactic — a specific, written forecast. If the current trajectory continues for twelve months, what does the client's business or life look like? Clients who cannot answer that question are not ready to commit resources, and discovering that in week one is far cheaper than discovering it in month four.

Clarify ends with a single written sentence that both parties agree to: the engagement statement. It names the trigger, the objective, and the consequence of inaction. If that sentence cannot be written, the engagement does not proceed. This is the most common point at which a prospective client is turned away, and turning them away is the correct outcome. An engagement built on a fuzzy statement of purpose will consume months before failing, and the failure will be attributed to the method rather than to the foundation.

Doctrinal origin

ICS Initial Response and Assessment; the Incident Briefing

In incident command, the first arriving responder performs an initial assessment and takes whatever immediate action is possible — but the pivotal step is the incident briefing, which FEMA doctrine describes as marking "the transition from reactive to proactive incident management." Clarify is that briefing. Before it, the client is reacting to their circumstances. After it, they are managing them. Nothing about the underlying situation has changed; the posture has.

What gets produced

  • Trigger Discovery Worksheet, completed in the client's own words
  • A written engagement statement naming the trigger, the objective, and the cost of inaction
  • Explicit separation of presenting complaint, underlying condition, and triggering event
  • A twelve-month no-change forecast the client has read and agreed is accurate
  • Named decision-makers and the stakeholder whose position actually shifted

Exit criteria

The phase is not complete until all of these are true.

  • The trigger can be stated as a specific event with a date, not a general condition
  • The client can articulate the cost of inaction without prompting or hedging
  • The engagement statement fits in one sentence and both parties have signed off on it
  • Any party with veto authority over the outcome has been identified by name

Portal instrument: Trigger Discovery Worksheet

Clarify in practice

Three engagements from different domains, each showing what this phase actually produces.

Professional services firm, 40 employees

Situation
The managing partner requested help with "partner compensation redesign," citing dissatisfaction among senior staff. Three prior attempts at a new compensation model had been drafted and abandoned.
Applied
Clarify traced the trigger to a specific event eleven weeks earlier: a high-performing senior associate resigned and, in the exit conversation, said the firm had "no path to ownership." Compensation was never mentioned. Three failed compensation redesigns had been attempts to answer a question about advancement using the language of pay.
Outcome
The engagement was rewritten around partnership track definition and advancement criteria. Compensation was addressed later, as a downstream consequence of the track structure rather than as the primary objective. The fourth compensation model was the first one adopted, because it was finally answering the right question.

Individual executive coaching

Situation
A newly promoted vice president sought coaching on "executive presence," describing feedback that she was "not strategic enough" in leadership meetings.
Applied
The trigger was a single meeting six weeks prior in which her CEO interrupted her twice and redirected the discussion. Clarify separated the presenting complaint — presence — from the underlying condition, which was that she had inherited a function whose metrics she did not yet trust and was therefore speaking tentatively about her own numbers. The hesitancy read as a lack of strategic thinking. It was actually a lack of verified data.
Outcome
The engagement objective became data ownership in her first ninety days rather than communication coaching. Presence improved as a byproduct of certainty, which no amount of presence training would have produced.

Personal reconditioning engagement

Situation
A forty-two-year-old client with a demanding career sought help building an exercise habit, describing a decade of failed starts.
Applied
Clarify identified the trigger as a scheduled retirement date fourteen months out, not a health event. The client had built an identity around an operational role that was ending. The presenting complaint was fitness; the underlying condition was an identity transition with a hard deadline. A decade of failed starts made sense: each was an attempt to solve a motivation problem that was actually a purpose problem.
Outcome
The engagement was structured around capability required for the next chapter rather than around weight or appearance. The objective became measurable performance standards tied to a post-retirement identity, and adherence stabilized for the first time in ten years because the goal was finally connected to something that mattered on a bad day.

Phase 2 of 6 · One to three sessions, plus verification time

Comprehend

Establish what is actually true.

What are the facts, the constraints, and the resources — before anyone proposes a solution?

Comprehend is the phase clients most want to skip and the one that most reliably determines whether the engagement succeeds. Its purpose is narrow and absolute: establish what is true right now, in writing, before anyone is permitted to propose a solution. Not what the client believes is true. Not what was true at the last planning cycle. What is verifiably true today.

The phase is organized around three distinct inventories, and conflating them is the most common analytical error in both business and personal planning. Facts are conditions that can be independently verified — a revenue figure, a headcount, a lab value, a contract end date, a scheduling reality. Constraints are conditions that cannot be changed within the engagement's horizon, or cannot be changed without costs the client is unwilling to pay. Resources are assets available to be deployed: time, money, authority, skill, equipment, relationships, and goodwill.

The discipline is in the classification. Clients routinely present constraints that are actually preferences, and preferences that are actually constraints. A leader who says "I cannot cut that program" may be describing a genuine board mandate or a personal reluctance to have a difficult conversation. Those two situations demand entirely different plans. Conversely, a client who says "I can find the time" while holding a fourteen-hour workday and a two-hour daily commute is describing a preference to believe something that the calendar does not support. Comprehend forces each item into the correct column, with evidence.

Resource inventory receives more attention here than in conventional consulting practice, because underestimated resources are as damaging as overestimated ones. Organizations regularly possess authority they have not exercised, data they have not examined, and relationships they have not asked anything of. Individuals regularly possess equipment they own, benefits they are entitled to, and support they have never requested. A plan built on the assumption of scarcity when capability exists is a plan that underperforms for no reason.

This phase also establishes the baseline, which is non-negotiable and frequently uncomfortable. If the objective is measurable, its starting value gets measured and written down before work begins. Organizations discover their reporting cannot produce the number they manage by. Individuals discover the honest baseline is worse than the one they had been carrying in their head. Both discoveries are valuable, and both are far cheaper in week two than in month six. A plan without a baseline cannot be evaluated, and an engagement that cannot be evaluated cannot be corrected.

Where verification requires an outside authority, Comprehend hands off and waits. Medical clearance, legal review, financial audit, and technical assessment are all appropriate gates. A coach is not a physician, an attorney, or an auditor, and a framework that pretends otherwise is a liability. The engagement pauses at the gate. It does not route around it.

Doctrinal origin

ICS Phase 1 — Understand the Situation; Information and Intelligence Management

Incident action planning begins with Understand the Situation, and NIMS treats information and intelligence management as a core management characteristic rather than a support function. Responders do not commit resources based on the initial report; they commit them based on verified situational awareness. Comprehend applies the same standard: the client's opening account of their circumstances is the initial report, not the situation.

What gets produced

  • Current State Assessment separating facts, constraints, and resources with evidence for each
  • Documented baseline measurements for every metric the engagement will be judged by
  • A resource inventory including unexercised authority, unexamined data, and unasked-for support
  • Reclassification of stated constraints that are actually preferences, with the cost of each made explicit
  • Identification of any external clearance required before execution may begin

Exit criteria

The phase is not complete until all of these are true.

  • Every baseline metric has a recorded starting value and a stated measurement method
  • Each constraint is documented as either immovable or movable-at-a-known-cost
  • The resource inventory is complete enough that the plan will not assume capability the client lacks
  • Required external clearances are either obtained or scheduled with a date

Portal instrument: Current State Assessment

Comprehend in practice

Three engagements from different domains, each showing what this phase actually produces.

Regional manufacturer, $60M revenue

Situation
Leadership sought a plan to improve on-time delivery, which they reported at approximately 82 percent based on a monthly management report.
Applied
Comprehend attempted to establish the baseline and found that on-time delivery was calculated against the most recently revised promise date rather than the original commitment to the customer. Measured against original commitments, performance was 61 percent. The reporting had been quietly absorbing every schedule slip.
Outcome
The engagement objective shifted from a nine-point improvement to a definitional correction plus a twenty-one-point improvement, with an entirely different scope and timeline. Had the plan been built on the 82 percent figure, every intervention would have been calibrated to a problem one third the actual size.

Nonprofit executive director, 12 staff

Situation
The director described being unable to delegate because "the team is not ready," and sought help with time management.
Applied
The resource inventory revealed two program managers with prior supervisory experience at larger organizations and a board chair with three decades of operational leadership who had never been asked for anything beyond meeting attendance. "The team is not ready" was reclassified from constraint to preference, with the cost stated plainly: roughly eleven hours per week of the director's time, indefinitely.
Outcome
The plan addressed delegation authority and defined decision rights rather than calendar technique. Time management was never the constraint; unexercised delegation authority was, and it was visible in the resource column the moment anyone bothered to inventory it.

Personal reconditioning engagement

Situation
A client with a home gym and a history of former athletic performance planned a five-day training week.
Applied
Comprehend documented hard facts the plan had ignored: a two-hour daily commute, a prior abdominal mesh repair, cervical arthritis, and a current medication protocol. Available training time was four days, not five, and the exercise selection required medical clearance rather than optimism. The baseline fitness test was administered and recorded before any programming was written.
Outcome
Execution proceeded on a four-day structure with a documented physician sign-off gate before load progression. The recorded baseline made the first block's results measurable, which meant the second block could be corrected on evidence rather than on how the client felt about it.

Phase 3 of 6 · Two to three working sessions

Construct

Build the MAP.

Given what is true, what is the plan — specific enough to execute on a bad day?

Construct produces the engagement's central artifact: the Motivational Action Plan, or MAP. The name is precise. It is motivational because it connects every action to the trigger and the objective the client established in Clarify — the reason this matters on a day when nothing feels compelling. It is an action plan because it specifies what will be done, by whom, by when, and to what standard. A document that inspires without specifying is a poster. A document that specifies without connecting to purpose is a task list that will be abandoned by week three. The MAP does both, which is the only reason it survives contact with a difficult month.

The MAP borrows its architecture directly from the Incident Action Plan. Objectives are written first and written to be measurable. Strategies describe the approach. Tactics describe the specific assignments for the current operational period. In an engagement, the operational period is called a block — typically four to six weeks — and each block has its own defined objectives, assignments, and measures of performance. Nothing in a MAP is scheduled indefinitely. Every commitment has a horizon and a review date.

The objective count is deliberately capped, and the cap comes from doctrine rather than preference. ICS teaches manageable span of control: experience shows an effective supervisor manages three to seven people or resources, with fewer than three producing inefficiency and more than seven exceeding what one person can effectively manage. The same ceiling governs concurrent objectives. Fewer than three and the plan is under-ambitious relative to the energy the trigger produced. More than seven and something will be dropped, without a decision being made about which thing. The MAP therefore holds three to five active objectives per block. Everything else goes on a deferred list, visibly, so that deferral is a choice rather than an accident.

Every assignment in a MAP is written to a standard that would survive a shift change. The test is whether a competent stranger could read the assignment and execute it correctly without asking a question. "Improve customer onboarding" fails. "Reduce median time from contract signature to first successful login from eleven days to four, by pre-provisioning accounts at signature — owner: Director of Operations, measured weekly from CRM timestamps" passes. This specificity is not bureaucratic. It is what makes accountability possible without supervision, and it is what allows a client to execute at seven in the morning without re-deciding anything.

The MAP also plans for its own failure, which conventional plans almost never do. Each objective carries a documented contingency: what happens if the assignment is missed once, what happens if it is missed twice, and what specifically triggers a re-plan rather than a push-harder response. Deciding these rules while calm is enormously more effective than deciding them in the middle of a bad week, when the available options are all colored by guilt. This is the single most distinctive feature of a MAP against an ordinary action plan, and clients consistently report it as the element that kept them in the engagement.

Construct is collaborative but not democratic. The consultant owns the structure and the standard; the client owns the content and the commitment. A MAP written entirely by the consultant will be complied with rather than executed, and compliance decays the moment supervision lapses. A MAP written entirely by the client will reproduce the constraints that made help necessary. The document that works is drafted together, in session, with the consultant enforcing specificity and the client supplying reality.

Doctrinal origin

ICS Phases 2 and 3 — Establish Objectives and Develop the Plan; Management by Objectives; Manageable Span of Control

The Incident Action Plan documents objectives for a defined operational period, along with the strategy and tactical assignments to achieve them. NIMS pairs this with management by objectives and manageable span of control. The MAP inherits all three: bounded operational periods, measurable objectives, and a hard ceiling on concurrent priorities derived from the three-to-seven span of control range.

What gets produced

  • MAP Blueprint Worksheet with three to five measurable objectives for the current block
  • Block structure with defined start and end dates and a scheduled review
  • Specific assignments naming owner, action, standard, frequency, and measurement source
  • Measures of performance and measures of effectiveness for each objective
  • Documented contingency and re-plan triggers for each objective
  • A visible deferred list capturing everything intentionally not being done this block

Exit criteria

The phase is not complete until all of these are true.

  • Each objective is measurable and traceable to the engagement statement written in Clarify
  • Every assignment would be executable by a competent person without further clarification
  • The plan's total time and resource demand fits inside the verified capacity from Comprehend
  • Contingency rules and re-plan triggers are written for each objective
  • The client can state the current block's objectives from memory

Portal instrument: MAP Blueprint Worksheet

Construct in practice

Three engagements from different domains, each showing what this phase actually produces.

SaaS company, Series B, 90 employees

Situation
Leadership had a fifteen-item strategic initiative list carried over from the prior year, with eleven items showing no measurable progress.
Applied
Construct forced the list into a four-objective block with explicit deferral of the remaining eleven, each with a named revisit date. Every objective received a measurement source and a designated owner with actual authority. Two initiatives were discovered to have no owner at all, which explained their eighteen months of inactivity better than any capacity argument.
Outcome
All four block objectives were met within the six-week period. More significantly, the deferred list eliminated the ambient guilt that had been attached to fifteen simultaneous half-commitments, and leadership meetings shifted from status recitation to decision-making.

Family-owned distributor, leadership transition

Situation
A founder intended to transfer operational control to his daughter over eighteen months but had no plan beyond the intention.
Applied
The MAP structured the transition as four blocks, each transferring a defined decision domain — purchasing, then personnel, then banking relationships, then strategic direction — with written criteria for what "transferred" meant and a contingency for the founder reasserting control, which both parties acknowledged was likely.
Outcome
The contingency rule was invoked twice in the first two blocks. Because the response had been decided in advance, each instance became a scheduled conversation with a defined resolution rather than a family conflict. The transition completed on schedule.

Personal reconditioning engagement

Situation
A client returning to training after years of inactivity wanted a twelve-month body composition and strength plan.
Applied
The MAP replaced the twelve-month plan with a six-week Block 1 carrying three objectives: establish a four-day training frequency, complete baseline testing, and obtain physician clearance as a hard gate before any load progression. Contingency rules specified exactly what happened after one missed session versus two consecutive, and what triggered re-planning rather than intensification.
Outcome
Block 1 adherence held at a level the client had not sustained in a decade. The gating structure prevented the pattern of aggressive early progression followed by injury and abandonment that had ended every previous attempt.

Phase 4 of 6 · One session

Contract

Establish mutual commitment.

What is each party obligated to do, and what happens when either falls short?

Contract converts a plan into an obligation. The distinction is not legal — most coaching engagements already have a services agreement in place — it is behavioral. A plan describes what someone intends to do. A contract describes what they have promised to do, to a specific person, with named consequences. Intentions and promises produce measurably different follow-through, and this phase exists to move the engagement from the first to the second.

The defining feature of this phase is that commitment runs both directions. The client's obligations are the visible half: the assignments in the MAP, the SITREP cadence, session attendance, and honest reporting even when the report is unflattering. The consultant's obligations are made equally explicit and equally binding: response times for messages, session preparation, deliverable turnaround, confidentiality boundaries, and the specific commitment to say the uncomfortable thing rather than protect the relationship. Most coaching agreements enumerate only what the client owes. The Mutual Commitment Agreement enumerates both, because a client who has watched the consultant meet their own obligations under load has a materially different relationship with their own.

Accountability structure is specified rather than assumed. The agreement names how performance will be reported, at what frequency, through what channel, and to whom. It defines what constitutes a missed commitment and what happens on the first, second, and third occurrence — escalating not to punishment but to diagnosis, because a pattern of missed commitments is data about the plan at least as often as it is data about the person. It also identifies who else, if anyone, has visibility into the client's performance. Accountability with an audience of one is a different instrument than accountability with an audience of a leadership team or a spouse, and the choice should be deliberate.

The agreement carries an explicit exit. Either party may end the engagement, and the conditions are written down: notice period, treatment of prepaid fees, disposition of documents and work product, and a required closeout conversation. Engagements that can only end in failure or completion trap both parties. A client who knows they can leave cleanly is significantly more willing to commit fully, because commitment is no longer indistinguishable from entrapment.

Signature is a real event, not a formality. In the portal, the Mutual Commitment Agreement is executed with an electronic signature, timestamped, and stored permanently in the client's document library. Clients receive a copy immediately. The ritual weight is intentional. The moment of signing is where a substantial share of the engagement's eventual adherence is generated, and treating it as paperwork forfeits that leverage. Clients regularly report returning to the signed agreement during difficult blocks — not for the terms, but because they signed it.

Doctrinal origin

ICS Accountability; Chain of Command and Unity of Command; the Operational Period Briefing

Accountability is a named NIMS management characteristic, supported by unity of command — the principle that every individual reports to one supervisor and knows precisely who that is. Incident personnel receive assignments through a documented plan and acknowledge them at the operational period briefing. Contract reproduces that structure: obligations are documented, acknowledged, and attributed to named parties on both sides.

What gets produced

  • Mutual Commitment Agreement executed with electronic signature and timestamp
  • Explicit enumeration of client obligations and consultant obligations
  • Defined accountability cadence, reporting channel, and escalation sequence
  • Written definition of a missed commitment and the graduated response to it
  • Named accountability audience beyond the consultant, where the client elects one
  • Exit terms covering notice, fees, work product, and required closeout

Exit criteria

The phase is not complete until all of these are true.

  • The agreement is signed by both parties and stored in the client's document library
  • The client can state their reporting cadence and what happens if they miss a commitment
  • Consultant obligations are documented in the same specificity as client obligations
  • Exit conditions are understood by both parties before execution begins

Portal instrument: Mutual Commitment Agreement

Contract in practice

Three engagements from different domains, each showing what this phase actually produces.

Private equity portfolio company, new CEO

Situation
A newly installed CEO engaged consulting support for a first-hundred-days plan, with the sponsor expecting monthly progress visibility.
Applied
The agreement specified a reporting structure with two distinct channels: a weekly internal SITREP between CEO and consultant that remained confidential, and a monthly sponsor-facing summary the CEO authored and the consultant reviewed. Confidentiality boundaries were written explicitly, including what the consultant would and would not disclose to the sponsor.
Outcome
The bifurcated structure allowed candid weekly problem-solving without the CEO managing sponsor perception in every conversation. The explicit confidentiality boundary was cited by the CEO as the reason the weekly sessions had any value at all.

Team consulting engagement, engineering department of 24

Situation
A department-wide process change had failed twice previously, both times fading after initial enthusiasm.
Applied
Rather than a single organizational commitment, the agreement was executed by each of the six team leads individually, each naming their specific obligations and the escalation path for missed commitments. The department head signed a separate agreement covering the resources and decision support she owed the leads.
Outcome
Distributed signature converted an abstract organizational initiative into six personal commitments with named owners. Two leads invoked the escalation path in Block 1, which surfaced a resourcing gap the department head resolved — a gap that had silently killed both previous attempts.

Personal reconditioning engagement

Situation
A client with a documented history of abandoning programs around week three requested a coaching relationship with genuine accountability.
Applied
The agreement specified a weekly SITREP due every Monday, a defined escalation on the second consecutive missed session, and an explicit consultant obligation to name slippage directly rather than soften it. The client elected to include a family member as a secondary accountability audience for training-day completion only.
Outcome
The consultant's documented obligation to be direct removed the ambiguity that had previously allowed drift to go unmentioned. The week-three abandonment pattern did not recur.

Phase 5 of 6 · One session plus a twenty-four hour window

Commit

Cross from planning into doing.

What is the first action, and is it happening today?

Commit is the shortest phase and the one that most determines whether everything preceding it produces any result. Its entire function is to move the engagement across a specific line: from a state where the client is preparing to act, to a state where the client is acting. That line is real, and a substantial number of well-planned engagements never cross it. The MAP is excellent. The agreement is signed. And then a week passes, then two, and the plan begins its slow conversion into a document that describes a version of the client that does not exist.

The mechanism is a Day 1 Action Assignment: one specific action, assigned in session, executed within twenty-four hours, and reported on completion. The action is chosen for symbolic and practical value rather than for magnitude. It should be unambiguously part of the plan, completable in under an hour, and independent of anyone else's cooperation. Sending a single email. Booking one appointment. Executing one training session. Pulling one report. The point is not the output. The point is that the client's own behavior has changed within a day of signing, which converts the plan from a description into a record.

This works because of how commitment actually forms. Motivation is a state, and states decay — reliably, within days, regardless of how compelling the original trigger was. Commitment is a structure, and structures are built from completed actions rather than from intentions. The first completed action is disproportionately valuable because it establishes the client as someone who does the things in this document. Every subsequent action inherits from that precedent. Conversely, a plan that sits unexecuted for two weeks establishes the opposite precedent, and it is remarkably durable.

Commit also establishes the battle rhythm, which is where the phase does its quieter and more consequential work. Session times are placed on calendars for the entire block. SITREP due dates are scheduled with reminders. The block review is booked before the block begins. Nothing in the operating cadence is left to be arranged later, because "later" competes with everything else on a busy calendar and reliably loses. In the portal, this is the moment recurring reminders are activated and, if the client has enabled notifications, push alerts for session times and SITREP due dates begin.

There is a diagnostic function here as well. A client who will not complete a one-hour action within twenty-four hours of signing a commitment agreement is providing important information, and the correct response is to return to an earlier phase rather than to push. Either the plan does not fit the verified capacity established in Comprehend, or the objective is not connected to the trigger identified in Clarify, or the client is not in a position to commit for reasons that have not surfaced. All three are recoverable in week one. None are recoverable in month four, by which point both parties have invested enough to make honest reassessment socially expensive.

Doctrinal origin

ICS Phase 4 — Prepare and Disseminate the Plan; the Operational Period Briefing

An approved Incident Action Plan has no effect until it is disseminated and briefed. Each operational period begins with an Operational Period Briefing, after which supervisors brief assigned personnel on their specific assignments. Commit is that briefing: the plan is transmitted, assignments are acknowledged, the operational clock starts, and the first shift goes to work.

What gets produced

  • Day 1 Action Assignment, completed and reported within twenty-four hours
  • Full block calendar with sessions, SITREP due dates, and block review scheduled
  • Activated reminders and, where enabled, push notifications for sessions and SITREP deadlines
  • Confirmed measurement mechanism producing its first data point
  • Client-stated confirmation of the current block's objectives and the first week's assignments

Exit criteria

The phase is not complete until all of these are true.

  • The Day 1 action is complete and reported, not merely scheduled
  • All block sessions and reporting deadlines exist on both parties' calendars
  • The measurement mechanism has produced at least one real data point
  • The client has articulated what they are doing this week without referring to the document

Portal instrument: Day 1 Action Assignment

Commit in practice

Three engagements from different domains, each showing what this phase actually produces.

Healthcare services organization, 300 employees

Situation
A twelve-week operational improvement plan was approved by the executive team, whose two prior improvement initiatives had never progressed past approval.
Applied
The Day 1 action was assigned to the COO personally: send a single all-staff message naming the initiative, its objective, and the first measurable milestone, within twenty-four hours of the approval meeting. No committee, no review cycle, no communications plan.
Outcome
The message went out the following morning. Both prior initiatives had died in the interval between approval and announcement, where they had accumulated stakeholder review until the momentum was gone. Public commitment within a day removed that interval entirely.

Independent consultant, solo practice

Situation
A consultant had spent seven months developing a productized service offering without releasing it, citing incomplete materials.
Applied
The Day 1 action was to send a description of the offering to three existing contacts and ask a single question: would this be useful to you? The materials remained incomplete by design, because completing them had become the mechanism of avoidance.
Outcome
Two of three responded within a week and one became the first engagement. Seven months of preparation had been optimizing an offering against imagined objections. Twenty-four hours of exposure produced the only feedback that mattered.

Personal reconditioning engagement

Situation
The MAP was complete and the agreement signed on a Monday evening, with the client's instinct to begin training the following week after equipment adjustments.
Applied
The Day 1 action was a single abbreviated training session within twenty-four hours, using existing equipment in its current state, with no programming optimization permitted. The block calendar and SITREP reminders were configured in the same session.
Outcome
The session occurred Tuesday. Every prior attempt in a decade had begun on a future Monday, which functioned as a permanent postponement device. Starting inside twenty-four hours broke the pattern that had defeated ten years of sincere intentions.

Phase 6 of 6 · Continuous, in four-to-six week blocks

Commence

Execute, report, correct, repeat.

What actually happened this week, and what does that tell us to change?

Commence is where the engagement lives. The five preceding phases exist to make this one possible, and the majority of an engagement's calendar time is spent here. It is not a maintenance phase or a follow-up period. It is a governed operating cycle with its own required artifacts, its own cadence, and its own discipline, and it continues until the objective is met, superseded, or the client no longer needs external structure to hold it.

The cycle rests on two instruments borrowed directly from operational practice. The Situation Report, or SITREP — the client's Weekly Scorecard — is submitted weekly and answers four questions: what was accomplished, what was not accomplished and why, what has changed in the operating environment, and what support is required. It is short by design — ten minutes to complete — because a reporting instrument that takes an hour will not be submitted during a hard week, which is precisely when the report matters most. The SITREP is not a progress performance. Its value is highest when the news is bad, and the Contract phase established that honest reporting is an obligation rather than a courtesy.

The After Action Review closes each block. Its structure is deliberately borrowed from military practice and asks four questions: what was supposed to happen, what actually happened, why was there a difference, and what will be done differently. The AAR is explicitly not an evaluation of the client. It is an evaluation of the plan, conducted by both parties, on the assumption that a gap between intent and outcome is information about the plan's design at least as often as it is information about the client's effort. This framing is what makes honest reporting sustainable. A client who believes the AAR is a performance review will manage their SITREPs, and the moment reporting becomes managed, the engagement loses the only signal it has.

Course correction follows the AAR, and this is where the C completes its loop. Objectives that were met are either retired or advanced. Objectives that were missed are diagnosed rather than repeated with more intensity — the wrong plan executed harder produces the same result and additional discouragement. New conditions discovered during the block feed back into the current-state picture established in Comprehend. Then a new block is constructed, a revised commitment is affirmed, and execution resumes. The engagement moves through Construct, Contract, Commit, and Commence again, from a materially better starting position each time.

This is the structural reason the C opens rather than closing. In incident action planning, the leg of the Planning P is walked once while the loop repeats every operational period, informed by ongoing situational awareness. The Consulting C™ inherits that shape exactly. Clarify and Comprehend are walked once. The remaining four phases cycle. The opening in the C is the Decision Point at the top of each cycle, and it resolves to one of two answers: Conclude or Continue. Continuing may mean running the next block on a materially revised MAP — revision is a form of continuing, not a third option — while concluding means the client has internalized the discipline and no longer requires external structure to hold it.

Conclude is the actual goal, and it is worth stating plainly because the incentives run the other way. A coaching relationship that continues indefinitely is a business success and a methodological failure. The purpose of Commence is to install a battle rhythm the client can run without a consultant — their own SITREP discipline, their own AAR honesty, their own willingness to correct a plan rather than defend it. When that is in place, the engagement graduates. Clients frequently return for a new trigger, which is the correct reason to return.

Doctrinal origin

ICS Phase 5 — Execute, Evaluate, and Revise the Plan; the recurring loop of the Planning P

FEMA doctrine is explicit that once the initial steps in the leg of the Planning P are complete, incident management "shifts into a cycle of planning and operations, informed by ongoing situational awareness and repeated each operational period." Commence is that cycle. The SITREP maintains situational awareness; the AAR drives the revision; the next block is the next operational period.

What gets produced

  • Weekly SITREP submissions across the full block
  • Block-End After Action Review completed jointly by client and consultant
  • Documented course corrections with the evidence that justified each
  • Updated baseline and current-state picture reflecting the block's findings
  • A Decision Point record stating Conclude or Continue, with the reasoning behind it
  • A revised MAP for the subsequent block where the engagement continues

Exit criteria

The phase is not complete until all of these are true.

  • SITREP submission rate is high enough that the record is trustworthy
  • Each block closes with a completed AAR rather than an informal check-in
  • Course corrections trace to documented evidence rather than to impression
  • The Decision Point is recorded explicitly instead of the engagement drifting forward

Portal instrument: Weekly SITREP and Block-End AAR

Commence in practice

Three engagements from different domains, each showing what this phase actually produces.

Logistics firm, 140 employees

Situation
A cost reduction initiative showed positive weekly reports for five consecutive weeks while the target metric remained flat.
Applied
The Block 1 AAR compared reported activity against measured outcomes and found that assignments were being completed as written while the underlying assumption was wrong: the targeted cost category was driven by customer order patterns rather than internal process. The plan was well executed and aimed at the wrong lever.
Outcome
Block 2 redirected entirely toward order pattern management and customer conversations. The AAR's separation of adherence from effectiveness prevented a full quarter of diligent work on an irrelevant variable.

Executive coaching engagement, division president

Situation
SITREPs were consistently submitted late and described accomplishments in general terms.
Applied
Rather than escalating on adherence, the consultant treated the reporting pattern as data. The AAR revealed the SITREP format required information the client's systems could not produce weekly, so each submission involved manual assembly he was quietly resenting. The instrument, not the client, was the problem.
Outcome
The SITREP was redesigned around three metrics his existing dashboards produced automatically. Submission became consistent and on time. The general language had been concealing a data access problem, not disengagement.

Personal reconditioning engagement

Situation
Block 1 completed with strong training adherence but with one objective — the physician clearance gate — unmet.
Applied
The AAR recorded honest results across all objectives and held the clearance gate as a hard stop on load progression into Block 2, despite the client's strong performance and desire to advance. The gap was diagnosed as a scheduling failure rather than a motivation failure, and the corrective action was a specific appointment date entered into the plan.
Outcome
Block 2 proceeded with volume adjustments only, holding load constant until clearance was documented. The client's expressed frustration was recorded in the AAR without changing the decision, which established that the gates in the plan were real.

Questions

What people ask about the framework

Is The Consulting C™ a coaching method or a consulting method?
Both, because the underlying sequence does not change with the client's size. An individual working through a career transition and a leadership team working through a strategic reset both need the same things in the same order: an honest account of why now, a verified picture of current conditions, a specific plan, a real commitment, a first action, and a governed execution cycle. What changes is the scale of the artifacts and the number of people who sign. The phases do not change.
How long does a full engagement take?
Clarify and Comprehend typically occupy two to five sessions across the first three to four weeks. Construct, Contract, and Commit generally complete within two additional weeks. Commence then runs in four-to-six week blocks for as long as the objective requires. Most engagements run three to four blocks, placing a typical full engagement between four and seven months. Engagements with a hard external deadline compress the front end; engagements with a significant identity or capability change extend the number of blocks.
What happens if a phase reveals the engagement should not proceed?
It stops, and that is a functioning outcome rather than a failure. Clarify sometimes reveals that the trigger belongs to someone other than the person who called, or that the cost of inaction is genuinely low. Comprehend sometimes reveals constraints that make the objective unreachable within the stated horizon, or a required external clearance the client is unwilling to obtain. Discovering either in the first month is inexpensive. Discovering it in the fourth month is not, and by then both parties are invested enough that the conversation rarely happens.
Why borrow from the Incident Command System specifically?
Because ICS was designed for exactly the conditions that make ordinary planning fail: incomplete information, decaying attention, competing authorities, and consequences for getting it wrong. It is also field-proven at enormous scale across every level of American government, and its doctrine is public, teachable, and internally consistent. Most business frameworks are derived from case studies of successful companies, which is a selection-biased evidence base. ICS is derived from the requirements of operating under pressure, which generalizes considerably better.
Does this require military experience to understand or apply?
No. The vocabulary is translated deliberately, and every borrowed term is defined in plain language at the point of use. SITREP means a short weekly status report. AAR means a structured look back at what happened versus what was planned. A block is a four-to-six week operational period. Clients with no service background use these instruments comfortably within one block, and the structure is frequently cited as the reason the engagement held together during a difficult stretch.
What makes a MAP different from any other action plan?
Three things. It caps concurrent objectives at three to five, based on the span of control range that incident command doctrine establishes for effective supervision. It connects every assignment back to the trigger identified in Clarify, so the plan answers the question of why this matters on a day when nothing feels compelling. And it plans for its own failure in advance, with written rules for what happens after a missed commitment and what specifically triggers a re-plan rather than a demand for more effort. Clients consistently identify that third feature as the reason they stayed in the engagement through a bad month.

Next Step

Start with the objective in front of you

Tell us about the objective, transition, challenge, or opportunity that matters now. We will use that context to determine whether this method is a useful next step.

Start a ConversationExplore The Operational O™

CROS3 Consulting is a private practice. References to Ryan Crose's U.S. Coast Guard service and public federal doctrine describe professional background only; they do not imply endorsement by the U.S. Coast Guard, the Department of Homeland Security, FEMA, or any government agency.