Preloads client / organization, sponsor, target impact level, mission context, and notes from a saved cMAP session file - matches what a signed SOW would already have captured, so it doesn't need retyping.
EngageFrame the client contextEngagement identity, mission, scope, and handling contextFramecontextEngage
Engage
Frame the client context.
These fields stay local with the scoring state and flow into JSON and Markdown exports.
EngageMap stakeholders and authorityOwners, domain coverage, and decision rights0stakeholdersEngage
Engage Workflow
Map stakeholders and decision authority.
Capture who owns mission priorities, evidence access, validation, and release decisions before scoring becomes deliverable-facing.
Stakeholder rows are saved in local state and exported with the readout.
| Name | Role | Organization | Decision authority | Domain streams owned | Notes | Action |
|---|
DiscoverChoose the evidence pathApproved custody, collection, and candidate-review controls0%completeDiscover
Discover
Choose how evidence reaches the workbench.
Record the approved handling path first. cMAP stores conclusions and references locally; it does not move client source documents or run an external AI service.
AssessEvaluate the evidence baselineArtifact scoring, rationale, confidence, and follow-up0%scoredAssess
Evidence Engine
Keep manual assessment controls behind the scenes.
The consultant can still inspect every AR row, score, filter, and rationale, but normal review starts from synthesis and opens the manual register only when needed.
Open manual assessment engine AR register, scoring controls, filters, imports, and rationale fields. All generated outputs are cataloged under Reports.
| Rationale / gap / recommendation |
|---|
VerifyConfirm findings with ownersPlayback, interviews, caveats, and evidence closure0%confirmedVerify
Verify
Play back evidence before it becomes a finding.
Confirmation and follow-up queues support SME/client review before deliverable release.
Interview session planner
Review every scheduled, outstanding, follow-up, and completed session in the roster. Select one to load its editable workspace.
SynthesizeForm the decision pictureStrengths, blockers, dispositions, and recommendations0%mappedSynthesize
Synthesize
Turn scores into decision-ready recommendations.
Recommendations are generated from scored artifacts, domain North Stars, MAP dispositions, required floors, peer proof points, and 6R mapping notes.
PlanSequence the roadmapTransition, transformation, dependencies, and specialist scope0%plannedPlan
Plan
Draft the transition schedule and transformation roadmap.
Score 0 items route to the next 0–6 months; score 1–3 items route into H1, H2, or H3 by dependency horizon.
DeliverControl and package the releaseQuality gates, audience choices, reports, and archive0%readyDeliver
Deliver
Release only what survives review.
Deliver status is generated from scored coverage, confirmation, follow-up closure, engagement context, stakeholders, and interview evidence.
Release decision
Release only what survives review.
Close the evidence, confirmation, and follow-up gates before the Executive Modernization Brief, Transformation Report, and Technical Report become sponsor-facing.
Single output registry
Reports
Every generated work product is cataloged here by engagement phase. Imports and active review remain in their working areas; exports, client issues, internal workpapers, final deliverables, and archives start here.
Client issue
Controlled handoff
Internal workpaper
State / record
Select an output below; files are generated locally from the current engagement state.
01Pursuit & contractingPre-sales through signed scope Use before kickoff
InternalStrategy alignmentFunding narrative
Fulcrum alignment and funding narrative
Lead with the DoD-wide Fulcrum strategy, translate findings into an evidence-backed implementation and funding case, then apply service or component mission language as a secondary layer.
Use when: framing a pursuit, sponsor brief, investment request, or modernization decision. This reference does not certify alignment, approve funding, or replace agency governance.InternalPre-salesReference
SOW compliance matrix
Trace the proposed engagement scope to cMAP obligations, assumptions, exclusions, and acceptance boundaries.
Refresh when: scope, deliverables, dependencies, or client responsibilities change before signature.InternalSales closureTemplate
Standard SOW template
Reusable starting language for scope, deliverables, responsibilities, boundaries, and acceptance.
Refresh when: the pursuit changes contract vehicle, delivery model, partner role, or acceptance terms.Client previewPre-salesControlled sample
Sample request package
Show a prospect representative interview questions, data requests, and artifact requests without issuing the full kickoff package.
Refresh when: the baseline request model changes or the pursuit needs a tailored scope preview.Client previewProspective sampleFictional HTML
Prospective client sample report family
Preview the Executive Modernization Brief, Transformation Report, and Technical Report using a dedicated fictional engagement that never reads from the active client workspace.
Release boundary: every sample is visibly marked as illustrative fictional data and is not an assessment, evidence record, compliance determination, or authorization product.02Mobilization & kickoffIssue before or at kickoff Client-start package
Client issueKickoffChecklist
Kickoff request checklist
Confirm points of contact, data stewardship, engagement identifiers, milestones, and escalation routes.
Reissue when: owners, evidence custody, dates, or escalation paths change.Client issueBefore kickoffHTML
Data and artifact request
The complete 51-artifact request package, grouped for client preparation and evidence collection.
Reissue when: scope, target impact level, or agreed evidence sources change.Client issueBefore kickoffHTML
Data-steward file-share taxonomy
Folder, naming, routing, and custody structure for organized client-side evidence collection.
Reissue when: the steward, repository, classification handling, or routing model changes.Controlled handoffKickoffHTML
Methodology and standards guidebook
Explain the assessment model, evidence scale, standards context, and non-authorization boundary.
Reissue when: methodology, standards corpus, or engagement framing changes.Client issueKickoffTXT
Artifact request list
Plain-language request register for email, meeting notes, or a client tracking tool.
Reissue when: the agreed request scope changes.03Assessment tracking & reissueWorking reports throughout collection, interviews, and validation Living workpapers
Controlled handoffEvidence collectionJSON / HTML / CSV
Distributed collection issue package
Send metadata-only collection materials to PMO, data stewards, and tower owners while source evidence remains inside the client environment.
Reissue when: assignees, open artifacts, due dates, routing, or requested clarification changes.InternalAI preparationJSON
AI observation template
Review-only structure for approved AI observations generated inside the client boundary or GCC High.
Reissue when: the artifact subset or approved processing path changes.InternalAssessment trackingCSV / HTML
Assessment control reports
Current score register, evidence-to-recommendation trace, roadmap plan, operator playback, and handoff workpapers.
Reissue when: confirmed scores, evidence references, findings, interview playback, or roadmap sequencing changes.InternalReturn reviewCSV / HTML
Returned-packet review and repair reports
Generate review, quality, follow-up, repair, and acceptance workpapers after importing returned collection material in Verify.
Reissue when: a return is repaired, a classification changes, follow-up closes, or consultant acceptance decisions change.04Closeout & final deliverablesCompose, review, approve, and issue Sponsor-controlled
Client packageInternal reviewAudience-aware HTML
Final decision and evidence package
Print one coordinated PDF package or export any report as standalone HTML after reviewing the release gate, selected audience, and optional-section composition above.
Reissue when: accepted evidence, findings, leadership decisions, roadmap sequencing, report audience, or optional-section disposition changes.
Opens Executive Modernization Brief → Transformation Report → Technical Report in one print-ready document. Choose Save as PDF in the browser print dialog.
05Records, archive & recoveryCheckpoint, package, retain, and close Local / GCC High
State recordCheckpointJSON
Engagement state checkpoint
Portable recovery copy of the complete normalized local engagement state.
Reissue when: completing a material work session, before imports, and before any local-state reset.Local journalMaterial changesCSV
Material activity journal
Metadata-only history of selected imports, assessment controls, consultant dispositions, and report-composition decisions.
Boundary: no source-document content, routine typing, score rationale, or recovery-file content is copied into this journal.Recovery gateRead-only checkJSON
Compare and verify before clearing local work
Select any cMAP checkpoint. cMAP validates and normalizes it in memory, summarizes material differences, and confirms whether it exactly matches the active engagement. It does not import or overwrite anything.
Clear remains locked: export a fresh checkpoint, then verify that downloaded JSON file.InternalProcedureHTML
Archive and SharePoint guide
Portable operating instructions for checkpoints, closeout, folder taxonomy, naming, and GCC High retention.
Reissue when: the archive procedure, taxonomy, retention practice, or administrator guidance changes.
Local archive
Engagement closeout archive
Assemble a recovery-safe ZIP for the GCC High Cloud Consulting delivery area. cMAP downloads locally only; it does not upload, change permissions or retention, or clear this browser.
Reissue when: any selected report changes or a new controlled package version is approved.
Always included
Normalized JSON state
Artifact traceability / evidence index
SHA-256 manifest and archive summary
Current report audience and composition
Requires an engagement ID in CMAP-YYYY-NNN format.