A professional operating system for using AI responsibly inside modern organizations. Learn to work with AI while protecting company data and maintaining compliance standards.
Every prompt designed to protect sensitive data
All outputs designed for accountability
Real scenarios across all departments
Always maintain oversight and control
Synthesize complex information for strategic decision-making without exposing sensitive data.
The CEO needs to make a strategic decision about entering a new market. You need to synthesize competitive data, financial projections, and risk factors without sharing actual company financials or strategic plans with AI systems.
Use this framework weekly to prepare executive briefings. Gather internal data offline, then use the AI-generated framework to structure your analysis. Present the completed framework with real data only in secure internal systems.
• Never include actual revenue figures or financial projections
• Avoid naming specific acquisition targets or M&A plans
• Don't share competitive intelligence that could identify sources
• Never include board discussion topics or strategic pivots
This prompt asks for a generic framework rather than analysis of specific data. The AI provides structure and methodology, while all sensitive data remains within your organization's secure systems. The output is a reusable template that can be applied to any decision.
Build strategic plans using AI assistance while keeping proprietary strategies confidential.
Your organization needs to develop a 3-year strategic plan. You want AI to help structure the planning process and provide industry best practices without revealing your actual strategic direction.
Use this template to design your annual strategic planning offsite. Customize the exercises offline with your team's specific context. The AI provides structure; your team provides the strategic insights that remain confidential.
• Don't ask AI to analyze your actual SWOT data
• Avoid sharing specific growth targets or revenue goals
• Never include planned product launches or pivots
• Keep competitor-specific strategies internal
This prompt requests a generic planning framework and facilitation guide. It doesn't require any proprietary information to generate useful output. The resulting template is applicable to any organization and reveals nothing about your specific strategic direction.
Write internal updates to leadership without exposing sensitive organizational data.
You need to draft a weekly project status update for the executive team. The update must be professional and structured, but you cannot share actual project names, client names, or specific metrics with the AI.
Use this template every Friday afternoon. Copy the AI-generated structure, then replace all placeholders with actual project data in your internal email system. Keep the template saved for consistency across all your status updates.
• Never paste actual email content for "improvement"
• Don't include real client or project names
• Avoid sharing specific budget figures
• Never include employee names or performance issues
The prompt explicitly uses placeholder syntax for all variable data. The AI generates only the structural template and professional language. All sensitive information is added by you after the fact, in your secure internal systems.
Draft professional client-facing messages while protecting both your organization's and your client's information.
You need to communicate a project delay to a client. The message must be professional, empathetic, and solution-oriented—but you cannot share the client's name, project details, or the specific nature of the delay with AI.
Maintain a library of these templated responses for common client scenarios. The AI provides the emotional intelligence and professional structure; you provide the specific client context and relationship nuances that make each message personal.
• Never share actual client names or company identifiers
• Avoid including contract values or payment terms
• Don't mention specific deliverables that could identify the project
• Never include internal escalation paths or team member names
The prompt uses category-based context (technical/resource/scope) rather than specific details. This gives the AI enough information to craft an appropriate tone while keeping all identifying information private. Client confidentiality is fully protected.
Create comprehensive HR policies using AI while ensuring no employee information is exposed.
HR needs to draft a new remote work policy. The policy must be comprehensive and legally sound, but development discussions and employee-specific concerns must remain confidential.
Use AI-generated policy templates as starting points. Review with legal counsel, customize for your specific jurisdiction, and incorporate feedback from employee focus groups—all done internally after receiving the base template.
• Never share employee complaints or grievances
• Avoid including specific salary bands or compensation details
• Don't mention employees by name or role combination that identifies them
• Never share union negotiation contexts or internal HR disputes
HR policies are procedural documents that can be templated without any personal data. This prompt requests only structure and best practices. All employee-specific information, internal discussions, and company-specific details are added after receiving the template.
Structure performance conversations professionally without exposing employee identities or sensitive feedback.
A manager needs to conduct quarterly performance reviews for their team. They want help structuring the conversation and feedback delivery, but individual employee performance data must never leave the organization.
Use this guide to prepare for each review. The AI provides the structure and language patterns; you fill in specific performance observations and goals in private. Practice difficult conversations using the scripts before the actual meeting.
• Never ask AI to write actual review content for specific employees
• Avoid sharing performance ratings or rankings
• Don't include compensation discussions or raise percentages
• Never mention PIP status or termination considerations
Performance reviews are among the most sensitive HR processes. This prompt strictly requests methodology, conversation frameworks, and example language—never actual employee data. The guide is universally applicable and contains no identifying information.
Learn to extract key points from legal documents while keeping contract details confidential.
The legal team needs to quickly understand key terms across multiple vendor contracts. They want AI to help create a consistent analysis framework, but actual contract terms and counterparty information must remain protected.
Use this checklist to standardize your contract review process. The consistent framework makes it easy to compare terms across vendors and identify negotiation priorities—all without ever sharing sensitive contract details with external AI systems.
• Never paste actual contract clauses into AI for summarization
• Avoid sharing vendor names or contract values
• Don't include negotiation strategies or deal terms
• Never share legal advice received from counsel
Legal documents often contain confidential commercial terms and attorney-client privileged content. This prompt requests only a generic analysis framework—the checklist itself contains no sensitive information. You apply the framework to actual contracts using internal secure tools.
Build compliance checklists and audit frameworks without exposing your organization's compliance gaps.
Your organization is preparing for a SOC 2 Type II audit. You need to create a comprehensive readiness checklist, but your current compliance status and identified gaps are sensitive information.
Use this comprehensive checklist to assess your organization's readiness. Track status, assign owners, and document evidence locations—all within your secure internal systems. The framework accelerates your preparation without revealing compliance posture.
• Never share actual audit findings or deficiency reports
• Avoid discussing specific compliance failures
• Don't include remediation timelines or responsible parties
• Never share auditor communications or reports
Compliance gaps are highly sensitive as they represent potential vulnerabilities. This prompt requests only the standard framework and best practices—information that is already publicly documented in SOC 2 guidance. Your actual compliance status is assessed offline using this template.
Structure financial reports and analyses without exposing actual company financials.
Finance needs to prepare the quarterly board report. The report structure needs to be professional and comprehensive, but revenue figures, margin data, and forecasts must remain strictly confidential.
Use this template as your consistent board report format. The professional structure ensures completeness while all sensitive financial data is populated from your internal financial systems. Board materials should never touch external AI systems.
• Never share actual revenue or profit figures
• Avoid including real growth rates or forecasts
• Don't mention specific customer names or contract values
• Never share runway calculations or fundraising plans
Financial data is among the most sensitive information in any organization. This prompt requests only report structure and presentation guidance. All numerical data uses explicit placeholders, making it impossible to inadvertently leak financial metrics. The template is filled in entirely within secure internal systems.
Build comprehensive risk assessment methodologies without exposing actual organizational vulnerabilities.
The risk committee needs to present an enterprise risk assessment to the board. The assessment framework must be comprehensive, but specific vulnerabilities, incident history, and mitigation gaps are highly confidential.
Apply this framework to standardize risk reporting across the organization. The consistent methodology enables comparison across periods and business units. Populate actual risk data only within your secure GRC (Governance, Risk, Compliance) platform.
• Never describe actual security vulnerabilities
• Avoid sharing real incident reports or breach information
• Don't include specific mitigation gaps or control failures
• Never share insurance coverage limits or claims history
Risk assessments identify organizational weaknesses—sharing these with AI systems would be a significant security exposure. This prompt requests only the framework and presentation format. All actual risk data, scores, and mitigation plans are added internally using secure risk management systems.
Structure market research findings without revealing proprietary insights or strategic focus areas.
Product strategy needs to synthesize market research across multiple sources. The synthesis template should be reusable, but specific market opportunities and strategic conclusions must remain internal.
Use this template to standardize how market research is presented across your product team. The consistent format makes it easier to compare opportunities and make investment decisions. Fill in actual data from your research tools in secure internal documents.
• Never share specific customer interview insights
• Avoid revealing market opportunities you're pursuing
• Don't include proprietary research data or surveys
• Never share strategic conclusions or product roadmap items
Market research often reveals strategic direction and competitive advantage. This prompt requests only the synthesis methodology and presentation structure. Your actual findings, insights, and strategic implications remain completely internal.
Structure competitive analysis without revealing your competitive strategy or proprietary intelligence.
Sales and product teams need a standardized way to track and analyze competitors. The framework should enable consistent analysis, but specific competitive intelligence and win/loss data must remain confidential.
Deploy these templates across your competitive intelligence program. The standardized format ensures sales teams get consistent, actionable information. All competitive insights and deal-specific details are populated internally from your CRM and competitive intelligence platform.
• Never share actual win/loss ratios or deal outcomes
• Avoid revealing specific competitive weaknesses you exploit
• Don't include pricing intelligence or deal structures
• Never share customer names from competitive deals
Competitive intelligence is among your most strategically valuable and sensitive information. This prompt requests only the organizational structure and tracking methodology. Your actual competitive insights, deal data, and strategic positioning remain completely confidential.
Write comprehensive PRDs using AI assistance while protecting product roadmap confidentiality.
A product manager needs to write a detailed PRD for a new feature. The document structure should be comprehensive and follow best practices, but the actual feature details and roadmap information must stay internal.
Use this template as your standard PRD format. The consistent structure helps engineering and design teams quickly find information. Customize and populate with actual feature details in your internal product management tool (Notion, Confluence, etc.).
• Never share actual feature names or capabilities
• Avoid revealing roadmap timelines or priorities
• Don't include technical architecture details
• Never share customer research insights that inform features
Your product roadmap represents future competitive advantage. This prompt requests only the document structure and best practices for PRD writing. The actual features, user research, and strategic decisions are added internally where they belong.
Structure user research findings professionally while protecting user privacy and research insights.
The UX research team has completed a usability study and needs to present findings to stakeholders. The presentation format should be impactful, but specific user quotes, session recordings, and detailed findings must remain confidential.
Apply this template to standardize research deliverables. The professional format helps stakeholders quickly understand insights and take action. All actual user data, quotes, and session recordings are added from your secure research repository—never through AI systems.
• Never share actual user quotes or testimonials
• Avoid including participant demographics that could identify individuals
• Don't share session recordings or screenshots
• Never include specific usability issues that reveal product plans
User research data includes personal information and potentially sensitive feedback. Participants trust that their input remains confidential. This prompt requests only the report structure and presentation methodology—protecting both user privacy and your proprietary research insights.
Create consistent technical documentation without exposing proprietary architecture or code.
Engineering needs to standardize technical documentation across teams. The documentation templates should be comprehensive, but actual system architecture, code patterns, and infrastructure details must remain confidential.
Distribute these templates across your engineering organization. Consistent documentation formats improve knowledge sharing and onboarding. Teams populate templates with actual technical details within your internal documentation systems (Confluence, GitBook, etc.).
• Never share actual code snippets or algorithms
• Avoid including API keys, credentials, or configuration
• Don't reveal system architecture or infrastructure details
• Never share security implementations or vulnerability information
Technical documentation often contains intellectual property, security-sensitive information, and competitive advantages. This prompt requests only formatting templates and structural standards—the actual technical content is written and maintained entirely within your secure development environment.
Structure incident reports professionally without exposing security vulnerabilities or breach details.
Operations needs a standardized incident report format for security and availability incidents. The template must be thorough enough for post-incident review, but actual incident details, affected systems, and customer impact must remain strictly confidential.
Implement this template in your incident management platform (PagerDuty, Jira, etc.). The consistent format enables trend analysis across incidents and improves your organization's reliability culture. All incident-specific details are documented in secure, access-controlled systems.
• Never share actual incident details or root causes
• Avoid including affected customer names or counts
• Don't reveal security vulnerabilities discovered
• Never share internal escalation communications
Incident reports often contain security-sensitive information about vulnerabilities, system weaknesses, and response capabilities. Sharing actual incident details could enable malicious actors. This prompt requests only the documentation format—all incident specifics remain in your secure incident management systems.
Evaluate vendors systematically without revealing procurement strategy or budget constraints.
IT is evaluating multiple vendors for a critical platform purchase. The evaluation framework needs to be comprehensive and defensible, but specific vendor pricing, negotiation positions, and budget details must remain confidential.
Use this scorecard to ensure consistent, defensible vendor selections. The structured approach protects against bias and supports audit requirements. Populate with actual vendor data and pricing in secure procurement systems—never through external AI.
• Never share actual vendor names being evaluated
• Avoid including pricing or contract terms
• Don't reveal your budget constraints or negotiation limits
• Never share reference check feedback or vendor weaknesses discovered
Procurement information could affect vendor relationships and negotiation dynamics. Sharing evaluation details could also create legal or fairness concerns in competitive bids. This prompt requests only the evaluation methodology—keeping all vendor-specific information strictly internal.
Draft professional vendor communications without revealing internal requirements or budget details.
Procurement needs to communicate with vendors at various stages—RFP requests, negotiation follow-ups, contract discussions. These communications must be professional, but internal requirements, budget, and selection criteria must stay confidential.
Build a template library for consistent vendor communication. Professional templates maintain your organization's reputation and ensure compliance with procurement policies. Customize each template with specific vendor and deal details in your secure email system.
• Never include actual vendor names or deal specifics
• Avoid sharing budget figures or negotiation positions
• Don't reveal internal evaluation criteria or timelines
• Never include competitor information or comparison details
Procurement communications can affect negotiating positions and vendor relationships. This prompt requests only template structures with placeholder fields for all specific information. The professional language patterns help you communicate effectively while all deal-specific details are added offline.
Communicate organizational changes effectively while protecting sensitive transition details.
The organization is implementing a significant change (restructuring, new system, policy update). Leadership needs communication templates that address employee concerns professionally, but the specific nature of the change and any sensitive details must remain internal.
Apply these templates to any significant organizational change. The frameworks help ensure consistent, empathetic communication across all channels. Customize with specific change details only in internal HR systems and secure communication platforms.
• Never share specific restructuring plans or layoff information
• Avoid including names of affected employees or teams
• Don't reveal financial rationale or cost-cutting targets
• Never share internal concerns or employee feedback
Organizational changes often involve sensitive personnel and strategic information. Premature disclosure could create legal liability or cause unnecessary employee anxiety. This prompt requests only communication best practices and template structures—all specific details are added within your secure HR systems.
Create effective training content without exposing proprietary processes or internal tools.
L&D needs to develop training materials for a new process or tool. The training structure should follow adult learning principles, but the actual process steps and internal systems must remain proprietary.
Use these templates to accelerate training development while maintaining instructional quality. The frameworks ensure consistent, effective learning design across all topics. Populate with actual process content in your LMS or internal documentation system.
• Never share actual process steps or procedures
• Avoid including screenshots of internal systems
• Don't reveal proprietary methods or techniques
• Never include customer examples or real case studies
Training materials often contain proprietary processes that represent competitive advantage. This prompt requests only the instructional design framework and template structure. Your actual training content—processes, systems, and examples—is developed entirely within your secure L&D tools.
Structure organizational knowledge effectively without exposing proprietary information.
The organization needs to build a comprehensive internal knowledge base. The structure should facilitate findability and maintenance, but actual content and internal procedures must remain within secure systems.
Apply this architecture to organize your knowledge base platform (Confluence, Notion, SharePoint). The consistent structure improves findability and reduces knowledge silos. All actual content is created and maintained within your secure internal systems.
Knowledge bases contain institutional knowledge that represents organizational capability. This prompt requests only the structural framework and best practices for organizing information. Your actual knowledge content remains entirely within secure internal platforms.
Create effective meeting documentation without exposing discussion details to external AI.
Teams need consistent, professional meeting documentation. The templates should capture decisions and action items effectively, but actual meeting content, attendee names, and discussion details must never be shared with AI.
Use these templates for consistent meeting documentation. The standardized format makes it easy to find decisions and track action items. Complete the templates during or after meetings using only internal note-taking systems—never AI transcription of actual content.
• Never paste meeting transcripts into AI for summarization
• Avoid sharing attendee names or org chart details
• Don't include actual decisions or confidential discussions
• Never share client meeting content
Structure board communications professionally while keeping strategic discussions strictly confidential.
The CEO's office needs to prepare briefing materials for board meetings. The format must be executive-grade, but actual strategic discussions, financial data, and board dynamics must remain strictly confidential.
Apply these templates to standardize board communications. Professional format improves governance effectiveness. All actual content is developed within your secure board portal—board materials should never touch external systems.
• Never share any actual board content or discussions
• Avoid including strategic plans or M&A considerations
• Don't mention board member names or voting positions
• Never share executive compensation or succession discussions
Prepare for crisis scenarios without revealing actual vulnerabilities or incident response plans.
Communications needs crisis response templates ready for various scenarios. The frameworks should enable rapid response, but actual crisis scenarios, response capabilities, and stakeholder lists must remain strictly confidential.
Pre-populate these templates for your organization's specific crisis scenarios. Having frameworks ready enables faster, more consistent response when crises occur. All scenario-specific content and actual response plans remain within your secure crisis management system.
• Never share actual crisis scenarios you're preparing for
• Avoid revealing organizational vulnerabilities
• Don't include stakeholder contact lists or escalation paths
• Never share past crisis details or lessons learned
Structure ethical decision-making without exposing actual dilemmas or sensitive situations.
Leadership faces complex ethical decisions regularly. A structured framework helps ensure consistent, principled decision-making, but actual ethical dilemmas and the people involved must remain completely confidential.
Use this framework when facing complex ethical decisions. The structured approach ensures thorough consideration of all perspectives. Actual case details and deliberations are documented only in privileged, secure systems—never shared with external AI.
• Never describe actual ethical dilemmas being faced
• Avoid naming individuals involved in sensitive situations
• Don't share investigation details or findings
• Never include legal strategy or privileged discussions
Facilitate team coordination without exposing internal dynamics or project details.
Multiple teams need to collaborate on a complex initiative. Clear documentation of dependencies and agreements is essential, but team dynamics, resource constraints, and specific project details must remain internal.
Use these templates to structure cross-team collaboration from the start. Clear documentation prevents misunderstandings and enables faster delivery. Populate with actual team details and project information in your internal project management tools.
• Never share actual team names or organizational structure
• Avoid describing interpersonal conflicts or dynamics
• Don't include specific project deliverables or timelines
• Never share resource constraints or staffing concerns
Structure process improvement initiatives without exposing operational inefficiencies.
Operations has identified process improvement opportunities and needs to present proposals to leadership. The proposal format should be compelling, but current process inefficiencies and specific operational data must remain confidential.
Use this template to structure compelling improvement proposals. The consistent format helps leadership quickly understand opportunities and make investment decisions. Populate with actual process data and analysis in your secure operations tools.
• Never share actual process inefficiencies or errors
• Avoid including performance data or benchmarks
• Don't reveal cost savings or productivity gaps
• Never share organizational friction points
Prepare documentation that withstands audit scrutiny while keeping actual findings internal.
Internal audit or external regulators require comprehensive documentation of controls and processes. The documentation format must be professional and thorough, but actual control effectiveness, findings, and remediation status must remain strictly confidential.
Use these templates to standardize audit documentation across engagements. Consistent format improves audit quality and facilitates regulatory review. All actual findings, testing results, and control assessments are documented only in your secure audit management system.
• Never share actual audit findings or deficiencies
• Avoid including control effectiveness ratings
• Don't reveal remediation status or timelines
• Never share auditor-management discussions