--- title: "SafeCode Consulting - Phase 2: Scoping" description: "How do you work with SafeCode? What would it look like? This page describes the engagement model, and grants access to the phase descriptions." url: "https://safecodetech.com/work/working-with-safecode/scoping.html" date: "2026-10-11T11:26:37-04:00" language: "en-US" --- ## Breadcrumbs [Home](https://safecodetech.com/) > [Work](https://safecodetech.com/work/case-stories.html) > [Working with SafeCode](https://safecodetech.com/work/working-with-safecode.html) > Phase 2: Scoping # Phase 2: Scoping ![Scoping Phase](https://safecodetech.com/work/working-with-safecode/images/sc_theme/Icons/ScopingPhase_120x120.png) Phase 2 Scoping is where shared understanding becomes a defined plan. By the end of this phase, both parties know exactly what work will be performed, what the client will contribute, what the commercial arrangement will be, and whether SafeCode Consulting is the right fit for the engagement. There is an explicit off-ramp here — if a different path makes more sense, that conversation happens now, before commitments are made. A good scope is not just a list of deliverables. It is a shared understanding between SafeCode and the client about what the engagement is designed to accomplish, what each party will contribute, where the boundaries of the work lie, and what a successful outcome looks like. Scoping exists to produce that shared understanding before any further commitments are made. This phase begins with the findings from Discovery & Diagnosis and translates them into a concrete plan — the work to be performed, the client inputs required, the expected outputs, the timeline, and the commercial structure. Scoping itself is conducted under the initial consulting agreement on a time basis, consistent with its exploratory nature. Scoping concludes with a proposal and Statement of Work for the phases that follow. The commercial structure for the Solution phase and beyond is defined here: fixed-price for well-bounded scopes, time-based for evolving or ongoing work, supplemental staffing for programs that need embedded technical capability, or an advisory retainer for programs that need periodic access to senior expertise without a full-time commitment. The nature of any post-delivery Support is agreed at the same time. That proposal is a decision point, not a formality. If the right answer is a modified scope, a different commercial structure, a referral to a better-suited supplier, or no engagement at all, that conversation happens here — before expectations have been set that cannot easily be revised. This off-ramp is not a failure of the process. It is the process working correctly. How this phase varies: - For well-defined, bounded engagements — a specific analysis, a certification readiness assessment, a requirements review — Scoping may be brief, resulting directly in a fixed-price proposal. - For complex or recovery engagements, Scoping may itself involve some preliminary technical work to bound the problem before a reliable scope can be defined. - For supplemental staffing arrangements, Scoping focuses on role definition, technical environment, and integration with the client's existing team rather than a deliverable-by-deliverable plan. - For advisory retainers, Scoping establishes availability, response expectations, areas of focus, and the conditions under which a separate project engagement might be warranted. | | | | | | | --- | --- | --- | --- | --- | | [!\[Solution Phase\](https://safecodetech.com/work/working-with-safecode/images/sc_theme/Icons/DiscoveryPhase_300x120_Flow.png#joomlaImage://local-images/sc_theme/Icons/DiscoveryPhase_300x120_Flow.png)Discovery & Diagnosis](https://safecodetech.com/work/working-with-safecode/work/working-with-safecode/discovery-diagnosis.html) | [!\[Scoping Phase\](https://safecodetech.com/work/working-with-safecode/images/sc_theme/Icons/ScopingPhase_300x120_Flow.png#joomlaImage://local-images/sc_theme/Icons/ScopingPhase_300x120_Flow.png)Scoping](https://safecodetech.com/work/working-with-safecode/work/working-with-safecode/scoping.html) | [!\[Solution Phase\](https://safecodetech.com/work/working-with-safecode/images/sc_theme/Icons/DevelopmentPhase_300x120_Flow.png#joomlaImage://local-images/sc_theme/Icons/DevelopmentPhase_300x120_Flow.png)Solution](https://safecodetech.com/work/working-with-safecode/work/working-with-safecode/solution.html) | [!\[Solution Phase\](https://safecodetech.com/work/working-with-safecode/images/sc_theme/Icons/AcceptancePhase_300x120_Flow.png#joomlaImage://local-images/sc_theme/Icons/DevelopmentPhase_300x120_Flow.png)Acceptance](https://safecodetech.com/work/working-with-safecode/work/working-with-safecode/acceptance.html) | [!\[Support Phase\](https://safecodetech.com/work/working-with-safecode/images/sc_theme/Icons/SupportPhase_120x120.png#joomlaImage://local-images/sc_theme/Icons/SupportPhase_120x120.png)](https://safecodetech.com/work/working-with-safecode/work/working-with-safecode/support.html) [Support](https://safecodetech.com/work/working-with-safecode/work/working-with-safecode/support.html) | ## JSON-LD Schema ```json { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://safecodetech.com/#organization", "name": "SafeCode Consulting", "url": "https://safecodetech.com/" }, { "@type": "WebPage", "@id": "https://safecodetech.com/work/working-with-safecode.html#webpage", "url": "https://safecodetech.com/work/working-with-safecode.html", "name": "Engagement Model | SafeCode Consulting", "description": "How SafeCode Consulting structures engagements for safety-critical software programs: Discovery & Diagnosis, Scoping, Solution, Acceptance, and Support.", "isPartOf": { "@id": "https://safecodetech.com/#website" }, "about": { "@id": "https://safecodetech.com/#organization" }, "inLanguage": "en-US" }, { "@type": "HowTo", "@id": "https://safecodetech.com/work/working-with-safecode.html#howto", "name": "SafeCode Consulting Engagement Model", "description": "The five-phase engagement model used by SafeCode Consulting for safety-critical software programs.", "step": [ { "@type": "HowToStep", "position": 1, "name": "Discovery & Diagnosis", "text": "Understand the program, identify real pain points, and distinguish the stated problem from its underlying cause.", "url": "https://safecodetech.com/work/working-with-safecode/discovery-diagnosis.html" }, { "@type": "HowToStep", "position": 2, "name": "Scoping", "text": "Turn shared understanding into a defined plan, commercial arrangement, and clear decision point.", "url": "https://safecodetech.com/work/working-with-safecode/scoping.html" }, { "@type": "HowToStep", "position": 3, "name": "Solution", "text": "Execute the agreed work — engineering, requirements, verification, certification support, or process work.", "url": "https://safecodetech.com/work/working-with-safecode/solution.html" }, { "@type": "HowToStep", "position": 4, "name": "Acceptance", "text": "Review and formally accept the deliverables against the agreed scope and objectives.", "url": "https://safecodetech.com/work/working-with-safecode/acceptance.html" }, { "@type": "HowToStep", "position": 5, "name": "Support", "text": "Knowledge transfer, advisory access, retainer support, or continued embedded relationship as agreed.", "url": "https://safecodetech.com/work/working-with-safecode/support.html" } ] } ] } ```