> ## Documentation Index > Fetch the complete documentation index at: https://docs.bluegenai.com/llms.txt > Use this file to discover all available pages before exploring further. # Path B: Government Office Stakeholder Alignment > Use BlueGenAI to build internal stakeholder alignment and obtain leadership approval before development work begins under an existing contract. Path B is for government offices and contracted teams who already have resources in place. The contract is awarded, the team is assembled — but development has not started because stakeholders have not aligned on what the modernized system should look like. Phase 1 in this context is not a proposal tool. It is an alignment tool. The goal is to get leadership and stakeholders to agree on the vision before development begins — preventing costly rework later. Phase 1 Path B is optional. If stakeholder alignment already exists and requirements are clear, you can skip directly to [Phase 2 — Requirements Refinement & CAB](/building-web-apps/phase-2-requirements-refinement-cab). *** ## Before you start You will need: * A BlueGenAI account and an active project * Any existing documentation about the current system — process flows, screenshots, user guides, or requirements documents * A plain language description of what the modernized system should do *** ## How to generate a stakeholder alignment prototype Open BlueGenAI and click **+ Create Project**. Name it for the modernization effort. Click the **Files** icon and upload any documentation you have about the current system and the desired future state — requirements documents, process flows, screenshots of the existing system, user guides. Describe what the modernized system should do. Focus on the user experience and key capabilities — not technical implementation details. **Example:** ```text theme={null} Generate a prototype of a modernized permit tracking system for a state agency. The current system is a legacy desktop application. The modernized version should be web-based, accessible, and allow residents to submit and track permit requests online. Agency staff should be able to review submissions in a queue and approve or deny requests with supporting notes. ``` Review the generated Draft App. Continue prompting to refine until the prototype reflects the agreed-upon vision for the modernized system. The Draft App generated in the Prototype tab is functional rendered code — not a static image or wireframe. It is one click away from becoming a fully deployed production application by switching to the Build tab. Stakeholders reviewing the prototype are seeing something very close to what the production system will look like. *** ## How to generate a concept of operations document A concept of operations (ConOps) document describes the current state, the future state vision, key stakeholders, and the high-level implementation approach. It is a standard artifact for leadership review and approval. Reference any uploaded documentation so the agent generates content aligned to your specific system. **Example:** ```text theme={null} Generate a concept of operations document for the modernization of our permit tracking system. Include: current state summary, future state vision, key stakeholders, high-level implementation approach, and expected outcomes. ``` Review the generated document. Continue prompting to adjust language, add sections, or align to your agency's document standards. Click the save icon on the generated file card. The document is saved to your project's Files panel and can be downloaded for leadership review. *** ## How to use the prototype for leadership approval Open the **👤 Manage Collaboration** panel and toggle **Shareable Link Access** to On. Copy the shareable URL and distribute it for asynchronous review. Recipients must be logged in to BlueGenAI to view the link. Use the prototype in a presentation or meeting to walk stakeholders through the proposed modernized system. The prototype is interactive — stakeholders can click through it in real time. Gather feedback from stakeholders and continue prompting to adjust the prototype until alignment is reached. Once the review period ends, toggle **Shareable Link Access** to Off in the Manage Collaboration panel. *** ## When to skip Phase 1 and go directly to Phase 2 Phase 1 Path B is the right starting point when stakeholders need to see something before they can agree. If that alignment already exists, skip it. Go directly to Phase 2 if: * Stakeholders are already aligned on the future state vision * Requirements exist from a previous effort or discovery phase * The modernization scope is already documented and approved Proceed here once stakeholders are aligned. Phase 2 transforms your existing system artifacts and approved vision into structured, traceable requirements. *** ## Tips for effective stakeholder alignment * **Show, don't tell.** A working prototype drives faster alignment than a slide deck. Stakeholders can click through the proposed system and react to something concrete. * **Start with one workflow.** Prototype the most contentious or highest-priority workflow first — the one most likely to generate disagreement. Resolve that alignment before expanding scope. * **Document decisions as you go.** Use the Prototype tab to generate a running requirements or decisions document alongside the prototype. This becomes the input for Phase 2. * **The prototype is production-ready.** Remind stakeholders that what they are reviewing is functional code — not a mockup. Their feedback directly shapes the application that gets built. *** ## Related pages Responding to an RFP or building a proposal? Use Path A instead. Once alignment is reached, move to Phase 2 to develop structured requirements.