40 ChatGPT-5.5 Prompts for Non-Technical Teams: Legal, HR, Recruiting, and Operations Workflows That Replace Manual Processes

Non-technical departments are rapidly adopting advanced AI to eliminate low-value, repetitive tasks and accelerate decision-making. OpenAI’s usage data highlights the shift: legal teams generated 13x more tokens than before, and non-developer Codex usage rose 137x—clear signals that professionals in legal, HR, recruiting, and operations are applying AI to real work, not just experimentation. This guide delivers 40 ready-to-use ChatGPT-5.5 prompts (10 per department) that replace manual processes with structured, auditable outputs your stakeholders can trust.

Table of Contents

• How to Use This Prompting Guide
• Legal Department: 10 Prompts That Streamline Contracting, Research, and Risk
• HR Department: 10 Prompts for Policy, Performance, and People Analytics
• Recruiting: 10 Prompts for Screening, Interviewing, and Employer Brand
• Operations: 10 Prompts for SOPs, Forecasts, and KPI Visibility
• Implementation Patterns and Workflow Tips
• Guardrails, Compliance, and Responsible Use
• Measurement, Iteration, and ROI Tracking
• Key Takeaways

How to Use This Prompting Guide

Each prompt below is designed for ChatGPT-5.5 and includes explicit context, inputs, constraints, and output formats. Non-technical teams can paste the prompt, fill in the requested variables, and receive structured, reusable outputs (e.g., JSON, tables, checklists, or stepwise plans). To maximize value, follow these principles:

• Set the role: Specify “You are [function]” to align tone and domain reasoning.
• Provide constraints: Jurisdiction, policies, brand guidelines, or compliance requirements.
• Require structures: Ask for bullet lists, JSON, tables, or IRAC/STAR frameworks to standardize outputs.
• Include verification steps: Prompt for assumptions, edge cases, and confidence levels to aid review.
• Request a final checklist: Summarize actions, owners, and due dates.

For readers who want to go deeper on reusable patterns, the resource at The 2026 Prompt Library: 5 Templates for Prompt Engineering covers role prompting, chain-of-thought safety, and structured output techniques to drive consistent results across departments.

Legal Department: 10 Prompts That Streamline Contracting, Research, and Risk

Legal teams use AI to accelerate standardization without compromising rigor. The prompts below focus on reproducibility, auditability, and attorney review—using structured outputs, risk tiers, and comparisons. Insert your jurisdiction, governing law, and policy references for best results. Always have a licensed attorney review generated artifacts.

1. Contract Review with Risk Tiers, Clause Extraction, and Redline Suggestions

   You are a senior commercial counsel. Review the contract for material risks, extract key clauses, and propose redlines aligned to our policy.
   
   Inputs you will receive:
   - Contract text: <paste full contract>
   - Jurisdiction and governing law: <e.g., New York, USA>
   - Company policy references: <paste summary or key clauses we require>
   - Counterparty profile: <industry, size, risk posture if known>
   
   Instructions:
   1) Identify and rate risks as Low/Medium/High across categories: liability/indemnity, payment terms, termination, data privacy, IP, warranties, SLAs, audit, governing law/dispute resolution.
   2) Extract and summarize the exact text of key clauses: limitation of liability, indemnification, data processing, confidentiality, assignment, termination for convenience, force majeure.
   3) For each High or Medium risk item, propose a redline with rationale aligned to our policy references.
   4) Flag missing clauses that are standard for our templates and propose language.
   5) Provide a compact executive summary (5–8 bullets) for business stakeholders.
   
   Constraints:
   - Do not fabricate laws or cite jurisdictions not provided.
   - If content is ambiguous or missing, explicitly note “insufficient detail.”
   
   Output format:
   - Section A: Executive Summary (bullets)
   - Section B: Risk Register (table with category, risk level, clause text excerpt, proposed change, rationale)
   - Section C: Missing/Mismatched Clauses (bullets with suggested language)
   - Section D: Clause Extracts (verbatim with location references)
   - Section E: Assumptions/Open Questions (numbered list)
   - Section F: Next Steps Checklist (owner, action, due date)

2. Compliance Check and Gap Analysis Against Specific Regulations

   You are a compliance analyst. Compare our policy or contract against named regulations and produce a gap analysis.
   
   Inputs:
   - Policy/contract text: <paste>
   - Applicable regulations/standards: <e.g., GDPR Art. 28, CCPA 1798, SOC 2 Security, PCI DSS 12>
   - Company controls summary (if available): <paste>
   
   Instructions:
   1) Map each regulatory requirement to relevant excerpts in our document (or mark “not addressed”).
   2) Rate coverage as Full/Partial/None with a brief rationale.
   3) Propose remediations for Partial/None with pragmatic steps and owners.
   4) Highlight conflicts or inconsistencies across sections.
   5) Provide a concise summary for leadership.
   
   Constraints:
   - Only evaluate against regulations provided.
   - If a requirement is jurisdiction-specific, flag potential applicability.
   
   Output format:
   - Matrix table: requirement | document location | coverage level | rationale | remediation | owner
   - Summary (bullets): top 5 gaps by risk and effort
   - Assumptions and scope notes

3. Policy Drafting with Sectioned Template and Defined Terms

   You are a policy drafter. Create a policy document that is clear, consistent, and ready for attorney review.
   
   Inputs:
   - Policy topic: <e.g., Vendor Security Policy>
   - Scope and audience: <e.g., Applies to all third-party vendors processing personal data>
   - Jurisdiction(s): <list>
   - Company style or template notes: <paste key preferences>
   
   Instructions:
   1) Include: Purpose, Scope, Definitions, Roles/Responsibilities, Policy Statements, Procedures, Exceptions, Enforcement, Review Cycle, Revision History.
   2) Use defined terms consistently and include a Definitions section.
   3) Insert bracketed placeholders where legal citations or cross-references are needed.
   4) Provide a 1-page executive summary for non-legal stakeholders.
   
   Output format:
   - Policy document (sectioned)
   - Executive summary (bulleted)
   - Change log recommendations (bulleted)

4. Legal Risk Assessment by Category with Severity and Mitigation

   You are a legal risk manager. Evaluate legal risks in a proposed initiative and produce a categorized risk assessment.
   
   Inputs:
   - Initiative description: <paste>
   - Jurisdictions: <list>
   - Known constraints: <e.g., data residency, export controls>
   - Risk appetite notes: <paste>
   
   Instructions:
   1) Identify risks across categories: regulatory, contractual, privacy, IP, employment, litigation exposure.
   2) For each, assign severity (H/M/L) and likelihood (H/M/L) and propose mitigations.
   3) Note dependencies and sequencing (e.g., policy first, then contract addendum).
   4) Provide a summary for executives.
   
   Output format:
   - Risk register table: category | description | severity | likelihood | mitigation | owner | target date
   - Narrative: top 3 residual risks and tradeoffs
   - Open questions

5. Targeted Regulatory Research Summary (with Scope and Limitations)

   You are a research assistant for counsel. Summarize targeted regulatory requirements based on provided materials.
   
   Inputs:
   - Regulations or guidance to summarize: <e.g., key obligations of GDPR Art. 28 for processors>
   - Context: <company role, data types, industries>
   - Jurisdiction(s): <list>
   
   Instructions:
   1) Provide a structured overview: applicability, core obligations, documentation requirements, enforcement posture.
   2) Map obligations to typical contract clauses or internal controls.
   3) Flag areas requiring attorney interpretation.
   4) Include a “Limitations” note stating that this is a synthesis for orientation and not legal advice.
   
   Output format:
   - Structured summary (headings)
   - Obligation-to-control mapping (table)
   - Limitations and open issues

6. NDA Generation (Mutual or Unilateral) with Variable Inputs

   You are a contracts specialist. Draft an NDA tailored to inputs and aligned to our template baseline.
   
   Inputs:
   - NDA type: <Mutual or Unilateral>
   - Parties and addresses: <names and jurisdictions>
   - Purpose of disclosure: <brief>
   - Term and survival: <e.g., 2 years term, 5 years confidentiality>
   - Governing law and venue: <specify>
   - Template preferences: <any must-have clauses>
   
   Instructions:
   1) Generate a clean NDA with standard sections: Definitions, Confidentiality, Exclusions, Term, Use Restrictions, Return/Destruction, Compelled Disclosure, Remedies, No License, No Assignment, Entire Agreement.
   2) Use clean, concise language. Insert bracketed placeholders for party details.
   3) Include an annex summarizing deviations from our baseline and rationale.
   
   Output format:
   - NDA text (numbered sections)
   - Annex A: Deviations and rationale (bulleted)

7. IP Analysis: Potential Trademark or Patent Conflict Review

   You are IP counsel support. Summarize potential conflicts based on provided search results.
   
   Inputs:
   - Proposed mark/invention summary: <paste>
   - Search results or references: <paste excerpts or links summaries>
   - Jurisdiction: <list>
   
   Instructions:
   1) For trademarks: assess similarity (visual, phonetic, conceptual), goods/services overlap, and risk tier.
   2) For patents: identify closest prior art concepts and note novelty/obviousness risks at a high level.
   3) Clearly state that this is a preliminary, non-exhaustive analysis pending attorney review.
   
   Output format:
   - Risk summary (bulleted)
   - Comparison table: reference | similarity/overlap | notes | risk tier
   - Next steps (e.g., comprehensive clearance, counsel review)

8. Litigation Prep: Deposition Outline and Discovery Requests

   You are litigation support. Create a structured deposition outline and initial discovery requests.
   
   Inputs:
   - Case background and claims: <paste>
   - Jurisdiction and rules reference: <paste if relevant>
   - Witness profile: <role, relationship>
   
   Instructions:
   1) Draft a deposition outline: topics, sub-questions, exhibits placeholder.
   2) Propose initial discovery requests (RFPs, interrogatories) aligned to claims.
   3) Summarize potential objections and foundation elements.
   4) Include a chronology of key events.
   
   Output format:
   - Deposition outline (headings, bullets)
   - Discovery draft (numbered lists)
   - Event timeline (table: date | event | source)
   - Issues/objections checklist

9. Legal Memo Writing (IRAC) with Facts and Authorities Placeholders

   You are a legal writer. Draft a legal memorandum using IRAC.
   
   Inputs:
   - Facts: <paste>
   - Legal question(s): <paste>
   - Jurisdiction(s) and applicable bodies of law: <list>
   
   Instructions:
   1) Use IRAC: Issue, Rule (with placeholders for authorities), Analysis (apply facts), Conclusion.
   2) Clarify assumptions and identify where citations are required.
   3) Provide a one-paragraph executive summary for non-lawyers.
   
   Output format:
   - Executive summary
   - IRAC sections with citation placeholders [Authority: ...]
   - Assumptions and open research items

10. Clause Comparison and Delta Analysis with Recommendations

    You are a contracts analyst. Compare two versions of a clause and propose a reconciled version.
    
    Inputs:
    - Clause A: <paste>
    - Clause B: <paste>
    - Policy preferences: <key must-haves>
    
    Instructions:
    1) Highlight substantive differences (not just wording) and categorize: risk, scope, remedy, definitions, procedure.
    2) Explain implications of each difference.
    3) Propose a reconciled clause that balances risk and counterpart feasibility.
    
    Output format:
    - Difference table: category | A text | B text | implication
    - Reconciled clause (clean text)
    - Rationale (bulleted)

HR Department: 10 Prompts for Policy, Performance, and People Analytics

HR teams can accelerate policy updates, improve review quality, and make people analytics accessible. The prompts below emphasize fairness, consistency, and compliance awareness. Provide your company’s values, local labor laws, and any collective bargaining constraints as inputs.

1. Job Description Optimization with Skills and Outcomes

   You are an HR business partner. Optimize a job description to be inclusive, outcome-driven, and compliant.
   
   Inputs:
   - Current job description: <paste>
   - Level and job family: <e.g., Senior IC, Software>
   - Location(s) and applicable pay transparency requirements: <list>
   - Inclusive language guidelines: <paste if available>
   
   Instructions:
   1) Rewrite the summary to emphasize outcomes and impact.
   2) Separate must-have vs. nice-to-have skills; avoid degree inflation unless required.
   3) Remove biased or exclusionary language; add inclusive alternatives.
   4) If pay transparency applies, include a salary range placeholder and factors.
   5) Add measurable success criteria for 30/60/90 days.
   
   Output format:
   - Optimized job description (sections: Summary, Responsibilities, Qualifications, Success Criteria)
   - Table: must-have | nice-to-have | interview signal

2. Employee Handbook Update Drafting with Redlines Log

   You are an HR policy editor. Update handbook sections for clarity and compliance.
   
   Inputs:
   - Current section(s): <paste>
   - Policy changes required: <bullets>
   - Jurisdiction(s): <list>
   - Style guide: <paste if any>
   
   Instructions:
   1) Provide a clean rewrite and a tracked-changes log (describe what changed and why).
   2) Insert placeholders for legal citations or localized exceptions.
   3) Add a plain-language summary for employees.
   
   Output format:
   - Clean section text
   - Change log table: line/paragraph | change | rationale
   - Employee summary (bullets)

3. Performance Review Template Pack (Role- and Level-Specific)

   You are an HRBP. Create performance review templates aligned to competencies and bias-mitigation.
   
   Inputs:
   - Role family and levels: <e.g., Sales IC L2-L4>
   - Core competencies: <list>
   - Review cadence: <e.g., semi-annual>
   - Company values: <paste>
   
   Instructions:
   1) Build templates with sections: Results, Behaviors, Growth, Peer Feedback, Manager Summary.
   2) Provide behaviorally anchored rating scale descriptors per level.
   3) Include guidance for managers to avoid common biases (recency, halo/horns, similarity).
   4) Add optional calibration notes.
   
   Output format:
   - Templates (one per level) with prompts/questions
   - Rating scale table (level | descriptor | example behavior)
   - Bias-mitigation checklist

4. Onboarding Workflow Design with Day-1 to Day-90 Plan

   You are a people operations specialist. Create an onboarding workflow.
   
   Inputs:
   - Role: <e.g., Customer Success Manager>
   - Location(s): <list>
   - Systems access requirements: <list>
   - Training modules: <list>
   
   Instructions:
   1) Outline tasks by timeline: pre-boarding, Day 1, Week 1, Day 30, Day 60, Day 90.
   2) Assign owners (IT, HR, Manager, Buddy) and dependencies.
   3) Add measurable outcomes and check-ins (e.g., shadow calls, first deliverables).
   4) Include an offboarding checklist structure for completeness.
   
   Output format:
   - Timeline table: date window | task | owner | dependency | notes
   - Success metrics (bulleted)
   - FAQs and escalation paths

5. Benefits Comparison Brief for Employee Communications

   You are HR Communications. Build a benefits comparison that is accurate and easy to understand.
   
   Inputs:
   - Current benefits: <paste summary>
   - Proposed changes: <paste>
   - Regions: <list>
   
   Instructions:
   1) Compare plan features: premiums, deductibles, OOP max, networks, Rx, telehealth, mental health, parental leave, retirement match.
   2) Highlight changes by persona (single, family, frequent Rx, out-of-network risk).
   3) Provide an employee-facing FAQ.
   
   Output format:
   - Comparison table (plan | key parameters)
   - Persona-based highlights (bulleted)
   - FAQ (Q/A)

6. Policy Compliance Checklist for Managers

   You are a compliance partner in HR. Turn a policy into a manager-friendly checklist.
   
   Inputs:
   - Policy text: <paste>
   - Manager responsibilities: <bullets>
   
   Instructions:
   1) Translate requirements into checkable items with cadence (e.g., monthly, quarterly).
   2) Clarify documentation expectations and acceptable evidence.
   3) Flag items requiring HR or Legal escalation.
   
   Output format:
   - Checklist table: item | cadence | evidence | owner | escalation
   - Quick-start guide (bulleted)

7. Exit Interview Analysis and Theme Detection

   You are an HR analyst. Analyze exit interview notes to detect themes and action items.
   
   Inputs:
   - Exit interview transcripts/notes: <paste>
   - Team/org context: <paste>
   
   Instructions:
   1) Thematically cluster feedback: compensation, manager, workload, career growth, culture, tools, benefits.
   2) Extract direct quotes as evidence.
   3) Propose prioritized actions and owners.
   4) Provide a summary suitable for leadership.
   
   Constraints:
   - Anonymize individual identifiers if present.
   
   Output format:
   - Theme table: theme | frequency | representative quotes | impact | action
   - Leadership summary (bulleted)
   - Risks and watchlist

8. Compensation Benchmarking Brief (Data-Informed Summary)

   You are a compensation analyst. Summarize comp benchmarks using provided market data.
   
   Inputs:
   - Roles and levels: <list>
   - Market data excerpts or ranges: <paste>
   - Locations: <list>
   
   Instructions:
   1) Summarize base, bonus, equity bands and geographic differentials from the provided data.
   2) Highlight compression risks and internal equity considerations.
   3) Provide talking points for recruiter/manager use.
   
   Output format:
   - Table: role-level | location | base | bonus | equity | source notes
   - Risks and recommendations
   - Talking points

9. Diversity Reporting Narrative (Using Provided Metrics)

   You are an HR analytics communicator. Create a DEI narrative for stakeholders.
   
   Inputs:
   - Diversity metrics: <paste> (e.g., representation, hiring, promotion, attrition by group)
   - Time window: <e.g., FY to date>
   - Initiatives: <list>
   
   Instructions:
   1) Summarize key movements with context and caveats; avoid over-attributing causality.
   2) Highlight statistically meaningful changes based on provided thresholds.
   3) Propose next steps with hypotheses to test.
   
   Output format:
   - Executive narrative (plain language)
   - Chart-ready table(s) (group | metric | value | delta | note)
   - Initiatives and experiments backlog (bulleted)

10. Training Needs Assessment from Performance and Survey Inputs

    You are an L&D specialist. Recommend training priorities based on input signals.
    
    Inputs:
    - Performance trends: <paste>
    - Skill inventory or survey results: <paste>
    - Strategic priorities: <list>
    
    Instructions:
    1) Identify capability gaps by function and level.
    2) Map gaps to training modalities (self-paced, ILT, cohort, coaching).
    3) Estimate effort and impact; propose a 90-day pilot.
    
    Output format:
    - Priority matrix table: capability | audience | modality | effort | impact | owner
    - 90-day pilot plan (timeline with milestones)
    - Success measures and data sources

Recruiting: 10 Prompts for Screening, Interviewing, and Employer Brand

Recruiting teams can expedite screening, standardize interviews, and amplify employer brand content—while maintaining candidate experience. Provide your hiring criteria, structured interviews frameworks, and ATS conventions for optimal use.

1. Candidate Screening Criteria and Rubric Builder

   You are a recruiting operations specialist. Build a screening rubric tied to job outcomes.
   
   Inputs:
   - Role and level: <paste>
   - Must-have skills and outcomes: <list>
   - Disqualifiers: <list>
   
   Instructions:
   1) Define evaluation dimensions with behaviorally specific signals.
   2) Create a weighted scoring rubric for resume and phone screen.
   3) Add pass/fail guardrails to reduce false positives.
   
   Output format:
   - Dimensions table: dimension | signals | weight | pass/fail criteria
   - Phone screen script outline (bullets)
   - Notes template (structured fields)

2. Interview Question Generation (Structured, Level-Appropriate)

   You are an interview design partner. Generate structured questions.
   
   Inputs:
   - Competencies: <list>
   - Seniority: <e.g., Mid-level>
   - Role context: <brief>
   
   Instructions:
   1) Provide 3–5 questions per competency using the STAR approach.
   2) Include acceptable ranges of responses and red flags.
   3) Add follow-ups to probe depth.
   
   Output format:
   - Table: competency | primary question | good signals | red flags | follow-ups

3. Job Posting Optimization for Reach and Inclusion

   You are a talent marketer. Optimize a job posting.
   
   Inputs:
   - Draft posting: <paste>
   - Channels (e.g., LinkedIn, niche boards): <list>
   - Brand voice: <brief>
   
   Instructions:
   1) Craft an opening that highlights mission and outcomes.
   2) Remove jargon/buzzwords; clarify impact and growth.
   3) Add inclusive statements and benefits highlights aligned to target channels.
   4) Provide a short and long version.
   
   Output format:
   - Short version (~150–180 words)
   - Long version (~350–450 words)
   - Channel-specific tweaks (bulleted)

4. Talent Pipeline Analysis from ATS Exports

   You are a recruiting analyst. Analyze pipeline stages and yield rates.
   
   Inputs:
   - ATS stage counts and conversion rates: <paste>
   - Role(s) and timeframe: <list>
   
   Instructions:
   1) Compute stage-to-stage conversion, time-in-stage, and drop-off reasons (from provided notes).
   2) Identify bottlenecks and propose experiments.
   3) Provide a leadership summary.
   
   Output format:
   - Metrics table(s)
   - Bottlenecks and hypotheses (bulleted)
   - 30-day experiment plan

5. Offer Letter Drafting with Variable Clauses

   You are a recruiting coordinator. Draft an offer letter.
   
   Inputs:
   - Candidate details: <placeholders>
   - Compensation components: <base, bonus, equity>
   - Location and employment type: <exempt/non-exempt>
   - At-will language and conditions: <paste template preferences>
   
   Instructions:
   1) Generate clean offer letter text with sections: Position, Compensation, Equity, Benefits, Start Date, Conditions (background check, eligibility), At-will statement (if applicable), Confidentiality/IP.
   2) Insert bracketed placeholders for variable fields.
   3) Add an annex with a summary of contingencies and next steps.
   
   Output format:
   - Offer letter text
   - Annex: contingencies and next steps (bulleted)

6. Skills Gap Analysis for a Hiring Plan

   You are a workforce planner. Analyze skills gaps to inform hiring.
   
   Inputs:
   - Team objectives and deliverables: <paste>
   - Current team skills inventory: <paste>
   - Time horizon: <e.g., 2 quarters>
   
   Instructions:
   1) Map objectives to required capabilities and capacity.
   2) Identify gaps and recommend build/buy/borrow (train, hire, contract).
   3) Prioritize roles by impact and urgency.
   
   Output format:
   - Gap matrix: capability | current capacity | required | gap | recommendation
   - Hiring plan (roles, sequences, rationales)
   - Risks if unfilled

7. Employer Branding Content Calendar

   You are an employer brand strategist. Create a content calendar.
   
   Inputs:
   - Talent personas: <list>
   - Channels: <list>
   - Themes: <list>
   - Assets available: <list>
   
   Instructions:
   1) Propose 6–8 weeks of content mapped to personas and channels.
   2) Include topics, formats, and CTAs.
   3) Add repurposing ideas and measurement suggestions.
   
   Output format:
   - Calendar table: week | persona | topic | format | channel | CTA | metric
   - Repurposing notes (bulleted)

8. Referral Program Design with Incentive Modeling

   You are a talent programs manager. Design a referral program.
   
   Inputs:
   - Hiring goals: <paste>
   - Budget constraints: <paste>
   - Roles targeted: <list>
   
   Instructions:
   1) Propose incentive options (cash tiers, recognition, charitable match) with pros/cons.
   2) Define eligibility, process, and anti-abuse guardrails.
   3) Create comms plan and FAQ.
   
   Output format:
   - Program design document (sections)
   - Incentive options table: option | cost | expected participation | pros | cons
   - Communications plan (timeline and templates)

9. ATS Optimization: Stage Definitions, SLAs, and Notes Hygiene

   You are a recruiting ops consultant. Standardize ATS usage.
   
   Inputs:
   - Current stages and definitions: <paste>
   - Pain points: <list>
   
   Instructions:
   1) Propose cleaned stage definitions and entry/exit criteria.
   2) Define SLAs for scheduling, feedback, and offer processes.
   3) Create a notes taxonomy and templates to improve signal quality.
   
   Output format:
   - Stage definitions table
   - SLA matrix (owner | action | time window)
   - Notes templates (structured fields)

10. Candidate Communication Templates by Stage

    You are a candidate experience lead. Draft communications.
    
    Inputs:
    - Role(s) and tone/voice: <brief>
    - Stages: <Applied, Screen, Interview, Offer, Rejection>
    - Legal disclaimers or region specifics: <paste>
    
    Instructions:
    1) Provide templates for each stage, including response time expectations.
    2) Offer variations for sensitive situations (delays, rescheduling).
    3) Ensure inclusive, respectful language.
    
    Output format:
    - Templates (stage-labeled)
    - Personalization fields checklist
    - Accessibility and inclusivity notes

Operations: 10 Prompts for SOPs, Forecasts, and KPI Visibility

Operations teams orchestrate processes across functions. These prompts emphasize documentation quality, measurable outcomes, and cross-functional clarity. Provide existing SOPs, vendor lists, and budget models where asked to ensure accurate outputs.

1. Process Documentation Blueprint (As-Is and To-Be)

   You are a business operations analyst. Document an as-is process and propose a to-be model.
   
   Inputs:
   - Process description and artifacts: <paste>
   - Roles and systems: <list>
   - Pain points: <list>
   
   Instructions:
   1) Describe the as-is process in numbered steps with RACI.
   2) Identify bottlenecks and failure modes with quantitative/qualitative evidence (from inputs).
   3) Propose a to-be process with changes, expected benefits, and metrics.
   4) Include a transition plan.
   
   Output format:
   - As-is steps with RACI table (step | R | A | C | I)
   - Bottlenecks/failures (bulleted)
   - To-be steps with metrics (baseline vs. target)
   - Transition plan (timeline, owners)

2. SOP Creation with Safety and Exception Handling

   You are an operations writer. Produce an SOP.
   
   Inputs:
   - Procedure name and scope: <paste>
   - Preconditions and required tools: <list>
   - Compliance or safety constraints: <list>
   
   Instructions:
   1) Include sections: Purpose, Scope, Definitions, Responsibilities, Materials/Systems, Step-by-Step Procedure, Quality Checks, Exceptions/Escalations, Records/Documentation, Revision History.
   2) Use numbered steps with decision points.
   3) Add a quick-reference checklist.
   
   Output format:
   - SOP document (sectioned)
   - Quick-reference checklist (bulleted)
   - Training notes (if any)

3. Workflow Optimization and Queue Design

   You are a process engineer. Redesign workflow for throughput and quality.
   
   Inputs:
   - Current workflow steps and SLAs: <paste>
   - Volume and variability data (if available): <paste>
   - Constraints: <list>
   
   Instructions:
   1) Identify parallelization opportunities, WIP limits, and handoff reductions.
   2) Propose queue policies (FIFO, priority classes) and capacity plans.
   3) Define metrics and leading indicators.
   
   Output format:
   - Proposed workflow diagram description (text)
   - Policy table: queue | rule | rationale | risk
   - Metric plan (bulleted)

4. Vendor Evaluation with Weighted Scoring

   You are a vendor management analyst. Evaluate vendors using provided criteria.
   
   Inputs:
   - Vendors and brief descriptions: <list>
   - Criteria and weights: <e.g., Cost 30, Reliability 25, Security 25, Support 20>
   - Must-have requirements: <list>
   
   Instructions:
   1) Score each vendor per criterion with rationale based on inputs.
   2) Identify must-have compliance failures.
   3) Provide a recommendation and risk notes.
   
   Output format:
   - Scoring table: vendor | criterion | score | rationale
   - Weighted totals per vendor
   - Recommendation and risks

5. Budget Forecasting Scenario Builder (Inputs Provided)

   You are a finance-ops partner. Build a scenario forecast.
   
   Inputs:
   - Baseline budget by category: <paste>
   - Drivers: <e.g., headcount, usage volumes, unit costs>
   - Scenarios to model: <list>
   
   Instructions:
   1) Apply provided drivers to compute scenario deltas vs. baseline.
   2) Identify high-sensitivity categories and risks.
   3) Provide assumptions clearly.
   
   Output format:
   - Table per scenario: category | baseline | scenario | delta | notes
   - Sensitivity highlights (bulleted)
   - Assumptions and caveats

6. Meeting Summarization with Decisions and Action Register

   You are a chief of staff. Summarize a meeting transcript into actionable notes.
   
   Inputs:
   - Transcript/notes: <paste>
   - Attendees and roles: <list>
   
   Instructions:
   1) Provide sections: Agenda, Key Decisions, Action Items (owner, due date), Risks/Dependencies, Parking Lot.
   2) Preserve attributions when relevant; condense discussion into outcomes.
   3) Flag unclear ownership or dates as “TBD.”
   
   Output format:
   - Summary document (sectioned)
   - Action register table: action | owner | due date | status | notes

7. Project Status Reporting: RAG Updates with Risk Narratives

   You are a program manager. Create a status report.
   
   Inputs:
   - Project milestones and progress notes: <paste>
   - Risks and issues: <list>
   
   Instructions:
   1) Provide RAG (Red/Amber/Green) for scope, schedule, budget, quality with one-line rationale each.
   2) Summarize progress vs. plan and next two sprints/weeks.
   3) Escalate top 3 risks with mitigation steps.
   
   Output format:
   - RAG table
   - Progress summary (bulleted)
   - Risk log (table: risk | impact | mitigation | owner | date)

8. Resource Allocation Planner Across Projects

   You are a resource manager. Propose allocation options.
   
   Inputs:
   - Team members with capacity: <list>
   - Projects and required skills: <list>
   - Time horizon: <e.g., next 8 weeks>
   
   Instructions:
   1) Map skills to project needs and propose allocations with utilization percentages.
   2) Flag conflicts and overallocations.
   3) Suggest tradeoffs and sequencing.
   
   Output format:
   - Allocation table: person | skill | project | allocation % | start | end
   - Conflicts (bulleted)
   - Recommendations

9. Risk Mitigation Planning for Operational Changes

   You are an operations risk partner. Build a mitigation plan.
   
   Inputs:
   - Change description: <paste>
   - Affected processes/systems: <list>
   - Stakeholders: <list>
   
   Instructions:
   1) Identify risks across people, process, technology, vendor.
   2) Rate impact/likelihood and define preventive/detective controls.
   3) Add fallback/rollback steps.
   
   Output format:
   - Risk matrix table
   - Controls catalog (preventive/detective)
   - Rollback plan (steps with triggers)

10. KPI Dashboard Design Requirements (Specification)

    You are a business analytics translator. Write a dashboard spec.
    
    Inputs:
    - Business objectives: <list>
    - KPIs and definitions (if any): <paste>
    - Data sources and refresh cadence: <list>
    
    Instructions:
    1) Define KPIs with clear calculations, dimensions, and filters.
    2) Propose layout and hierarchy for executive to practitioner views.
    3) List data quality checks and owner responsibilities.
    
    Output format:
    - KPI definition table: KPI | definition | calc | dimensions | frequency | owner
    - Layout description (text)
    - Data quality checklist

Implementation Patterns and Workflow Tips

Deploying these prompts effectively requires lightweight process design and clear ownership. The most successful non-technical teams adopt a “prompt-as-template” model: store canonical prompts in a shared library, embed required inputs with placeholders, and version changes as policies evolve. Because usage patterns indicate real operational adoption—legal teams generating 13x more tokens and non-developer Codex usage increasing 137x—governance and standardization are critical to scale without chaos.

Standard Operating Prompt (SOPrompt) Pattern

• Template repository: Centralize prompts by function (Legal, HR, Recruiting, Ops), each with metadata (owner, last review date, jurisdiction or region applicability).
• Input checklists: Attach required inputs to each prompt (e.g., governing law for contracts, pay transparency jurisdiction for HR) to prevent incomplete runs.
• Structured outputs: Prefer JSON or tables to feed into downstream tools (e.g., contract risk registers, ATS notes templates, action registers).
• Audit logs: Save prompt, inputs, and outputs for traceability. Tag with case or ticket IDs.

Role-Conditioning and Constraints

Each prompt above starts with an explicit “You are …” instruction, plus constraints and output formats. This primes ChatGPT-5.5 for consistent reasoning and structured responses. Where compliance is material (e.g., legal or HR), require the model to list assumptions, missing inputs, and limitations so reviewers can quickly close gaps before action.

Workflow Embedding

Integrate outputs into existing workflows instead of creating parallel channels. For example:

• Legal risk registers exported to your matter management or ticketing system.
• HR templates stored in your document system with version control, then linked in your HRIS.
• Recruiting rubrics and interview prompts embedded in your ATS scorecard fields.
• Operations status reports standardized into your PM tool with RAG and risk logs.

If you are formalizing these practices across departments, the resource at The 2026 Prompt Library: 5 Templates for AI Coding provides an expanded library of legal-focused patterns with risk registers, clause libraries, and mitigation playbooks designed for attorney review workflows.

Localization and Jurisdiction

Wherever local laws or policies vary, create regional prompt variants. For instance, HR job postings may need pay range disclosure in certain locations; legal policies may require region-specific clauses. Specify the jurisdiction upfront and keep region-specific templates maintained by regional owners.

Change Management

• Train champions: Identify a point of contact per function to steward templates.
• Versioning: Maintain version tags and changelogs for each prompt.
• Feedback loops: Encourage users to append “assumptions/open questions” outputs to tickets for faster review.

For people leaders operationalizing AI across HR and talent processes, 50 GPT-5.5 Prompts for Operations Managers: Supply Chain Optimization, Process Automation, Resource Allocation, and Performance Dashboards outlines governance, bias-mitigation safeguards, and integration checklists that complement the prompts in this guide.

Guardrails, Compliance, and Responsible Use

Non-technical teams can safely deploy these prompts by setting clear boundaries and review steps. The following practices help ensure responsible use:

Data Minimization and Confidentiality

• Only include the minimum necessary information in prompts. Redact personally identifiable information (PII) or sensitive attributes when feasible.
• For legal and HR content, strip names or use pseudonyms unless identity is essential for analysis.
• Use enterprise controls and policies governing AI tool usage in your organization.

Jurisdiction and Legal Advice Limitations

• Explicitly state jurisdiction in legal prompts and add “not legal advice, subject to attorney review” limitations as shown.
• For regulatory research, restrict evaluation to the laws provided; do not extrapolate beyond scope.

Bias and Fairness

• In HR and recruiting prompts, require inclusive language, bias mitigation guidance, and structured rubrics to standardize evaluation.
• Monitor for disparate impact indicators using your organization’s compliance framework.

Verification and Reviewer-in-the-Loop

• Use the “assumptions/open questions” sections to drive human review and validation before action.
• For critical documents (contracts, policies, offer letters), require sign-off by authorized reviewers.

Record-Keeping

• Store prompt templates, inputs, and outputs with timestamps and owners. Link to tickets or matters for traceability.
• Maintain changelogs for policies and SOPs generated or updated using AI.

Measurement, Iteration, and ROI Tracking

To demonstrate the value of AI-assisted workflows, define baseline metrics, collect before/after data, and iterate prompt templates based on outcomes. The table below outlines a practical measurement framework:

Iteration Loop

1. Collect outputs and reviewer feedback for each prompt instance.
2. Identify common gaps (e.g., missing jurisdiction, unclear owners) and update the template accordingly.
3. Re-run on a test case and validate structure and completeness.
4. Publish updated version with changelog and notify stakeholders.

Signal Quality and Adoption

• Legal: Review risk registers for specificity and alignment to policy references.
• HR: Check that bias mitigations appear consistently in templates and reviews.
• Recruiting: Confirm interview question quality and rubric alignment to job outcomes.
• Operations: Ensure SOPs include exceptions and escalation paths.

Key Takeaways

• Non-technical teams are leading operational AI adoption—evidenced by 13x token growth in legal usage and a 137x increase in non-developer Codex use—by focusing on real workflows and structured outputs.
• Prompts that declare roles, define constraints, and require specific output formats (tables, JSON, IRAC, checklists) produce consistent, reviewable artifacts.
• Legal prompts prioritize risk registers, clause extraction, and delta analysis; HR emphasizes inclusive templates and policy clarity; Recruiting centers on rubrics, interview structure, and candidate communications; Operations delivers SOPs, forecasts, and KPI specs.
• Guardrails—data minimization, jurisdictional scoping, bias mitigation, and reviewer-in-the-loop—are essential for safe and compliant deployment.
• Treat prompts as living templates with owners and versioning; measure cycle times and quality indicators, iterate based on feedback, and embed outputs in your existing systems.

Adopt these 40 ChatGPT-5.5 prompts as a starting library, adapt them to your organization’s policies and jurisdictions, and establish a simple governance model. With structured prompts and disciplined review, non-technical departments can replace repetitive manual processes with faster, clearer, and more consistent workflows—freeing teams to focus on judgment, relationships, and strategic outcomes.