Act as a senior Contracting Officer.

For the following requirement:
[INSERT REQUIREMENT]

Compare acquisition approaches:
- FAR-based contracting
- Other Transaction Authority, as stated under 10 USC 4022
- Include different solicitation approaches such as Commercial Solutions Opening (if applicable)

Provide:
- Pros/cons of each
- Risks (legal, execution, protest)
- When each is most appropriate
- Recommended approach with rationale

You are acting as a Senior Government Contracting Officer with expertise in acquisition planning and federal acquisition regulations. I need to prepare
either a formal Acquisition Plan or a Memorandum for Record (MFR) explaining why a formal plan is not required.
I am attaching the following documents for your review:
- The draft PWS
- The Market Research Report (or draft sections)
- The IGCE

STEP 1 - DETERMINE REQUIREMENT:
First, review the IGCE to determine the estimated contract value. Based on the estimated value, determine whether a formal written Acquisition Plan is
required under FAR 7.102 and DFARS 207.103. Briefly state your determination and the regulatory basis for it.
STEP 2A - IF A FORMAL ACQUISITION PLAN IS REQUIRED:
Draft a complete Acquisition Plan that covers all required elements under FAR Part 7 and DFARS Part 207, including:
- Acquisition background and objectives
- Statement of need
- Applicable conditions (e.g., urgency, consolidation, bundling)
- Cost and estimated contract value
- Capability or performance requirements
- Delivery or performance-period requirements
- Trade-offs
- Risks
- Acquisition streamlining
- Sources
- Competition
- Contract type selection and rationale
- Source selection procedures
- Contractor versus government performance
- Inherently governmental functions
- Management information requirements
- Milestones for the acquisition
STEP 2B - IF A FORMAL ACQUISITION PLAN IS NOT REQUIRED:
Draft a professional Memorandum for Record (MFR) that:
1. States the estimated contract value and the applicable FAR/DFARS threshold that exempts this acquisition from a formal written plan.
2. Cites the specific regulatory authority for the exemption.
3. States that the acquisition strategy will be documented in the Market Research Report and other contract file documents.
4. Is formatted as an official government memorandum with appropriate header, subject line, and signature block placeholders. Format the final document as a complete, professional, publishable government document ready for inclusion in the contract file.

You are a senior DoD acquisition strategist. Based on the following program details [USER PROVIDES: budget range, timeline, technical requirements, mission criticality], develop a comprehensive acquisition strategy framework that addresses: 1) Recommended contract type with justification, 2) Competition strategy and source selection approach, 3) Key milestones and decision points, 4) Risk mitigation strategies, 5) Small business considerations, 6) Required approvals and authority thresholds. Format as a structured decision memo.

You are an expert in FAR Part 16 contract types. Given the following program parameters [USER PROVIDES: requirements stability, cost visibility, urgency, technical risk, performance metrics], recommend the most appropriate contract type. For your recommendation, provide: 1) Contract type selection with FAR citation, 2) Rationale based on program characteristics, 3) Government and contractor risk allocation, 4) Required justification language for acquisition strategy, 5) Alternative contract types considered and why rejected. Structure as a decision matrix.

You are a DoD acquisition pathway expert familiar with DoDI 5000.02, DoDI 5000.80, and DoDI 5000.81. Based on these program inputs [USER PROVIDES: capability need, technology maturity, fielding urgency, lifecycle expectations], recommend the optimal acquisition pathway. Address: 1) Pathway recommendation (Middle Tier Acquisition - Rapid Prototyping/Rapid Fielding, Major Capability Acquisition, Urgent Capability Acquisition, or Software), 2) Statutory and policy basis, 3) Required documentation and approval authorities, 4) Timeline implications, 5) Transition strategy if moving between pathways. Provide as a structured pathway assessment.

I am the Contracting Officer for the [project name] acquisition. Based on our draft Acquisition Plan, generate a list of key discussion points to raise with the CASPER Risk Advisor during our initial ASR meeting. Focus on potential programmatic, schedule, and performance risks.

"Analyze our proposed acquisition strategy for [project name]. Does it adequately prioritize commercial solutions in accordance with Executive Order 14271? If not, what justifications are needed, and what alternative performance-based requirements could we consider to attract non-traditional vendors?"

"Generate a summary of our IP and Data Rights strategy for [project name]. What are the potential long-term risks, such as vendor lock-in? What questions should I ask the program team to ensure our strategy is sound?"

Analyze the current acquisition approach for [project name] and identify any elements that resemble legacy clearance procedures. Suggest alternative actions that align with CASPER's principles of proactive risk management and streamlined documentation.

"Based on the information in [document name, e.g., Acquisition Plan], are we effectively leveraging existing documentation to support the CASPER review? Identify any redundant paperwork that can be eliminated."

"Review the current strategy for [project name]. How can we better empower the Contracting Officer and local leadership in the decision-making process, in line with the CASPER guidance?"

I am the CASPER Risk Advisor for the [project name] acquisition. The CO has provided the following documents [list of documents]. Based on these, what are the top three strategic risks I should focus on during the Acquisition Strategy Review? Provide a rationale for each.

"Review the proposed contract type for [project name]. Does the justification for using a non-fixed-price contract seem sufficient? How does the chosen contract type incentivize the contractor to meet our goals and share risk appropriately?"

"Based on the draft acquisition strategy, where is the acquisition team exercising innovative business judgment or tailoring regulations? Is the rationale for these decisions defensible and the associated risks acceptable?"

The [project name] contract is now in the execution phase. The following risks were identified during the ASR and PNR: [list of risks]. What performance metrics and data should I request from the CO to assess how these risks are unfolding?

"Based on the latest performance report for [project name], are the risk mitigation strategies we put in place effective? What adjustments, if any, should be considered?"

"Generate a framework for a Contract Execution Review for [project name], focusing on the key risks identified earlier in the process. What questions should I ask to determine if the contract is on track and if any strategic adjustments are needed?"

I am reviewing the competitive range determination for [project name]. Do the evaluation criteria seem effective in distinguishing between the proposals? Are there any indications that the proposed IP packages from the offerors could create 'vendor lock'?

"Based on the provided cost/price analysis, did the analysis focus on the highest-risk drivers? Are the proposed costs realistic enough to prevent performance failure? What areas need further scrutiny?"

"Review the documentation for the source selection decision. Does it clearly articulate the value of the technical differences between proposals, rather than just comparing ratings? Is the award basis sound and well-documented?"

I am preparing for the Pricing & Negotiation Review for [project name]. Based on the received proposals and our evaluation criteria, what are the key elements I need to document to demonstrate that the evaluation was conducted with integrity and in alignment with the solicitation?

"Generate a list of questions to prepare my negotiation team for discussions with [offeror name]. The questions should focus on clarifying pricing anomalies, understanding their proposed IP rights, and assessing any remaining business risks."

"Analyze the source selection decision document for [project name]. Is the business rationale for the best-value trade-off clearly articulated and defensible against a potential protest?"

You are an expert Department of War (DoW) Contracting Officer with 20 years of experience and exceptional attention to detail. Your mission is to conduct a comprehensive review of the attached Other Transaction Agreement (OTA) package contracting documents consisting of the following <INSERT PROTOTYPE AGREEMENT DOCUMENT NAME HERE>, <INSERT WRITTEN DETERMINATION DOCUMENT NAME HERE>, and <INSERT TERMS & CONDITIONS DOCUMENT NAME HERE> for compliance with specific statutory and best-practice requirements outlined in the DoD OT Guidebook, as well as template requirements, grammatical errors, and misspellings.

Use the list of questions below to analyze the uploaded <INSERT PROTOTYPE AGREEMENT DOCUMENT NAME HERE>, <INSERT WRITTEN DETERMINATION DOCUMENT NAME HERE>, and <INSERT TERMS & CONDITIONS DOCUMENT NAME HERE> and provide a comprehensive review of the document as outlined in the Output Format.

PART I: COMPLETENESS CHECK
Compare the attached <INSERT PA TEMPLATE DOCUMENT NAME HERE>, <INSERT WD TEMPLATE DOCUMENT NAME HERE>, and <INSERT T&C TEMPLATE DOCUMENT NAME HERE> with <INSERT PROTOTYPE AGREEMENT DOCUMENT NAME HERE>, <INSERT WRITTEN DETERMINATION DOCUMENT NAME HERE>, and <INSERT TERMS & CONDITIONS DOCUMENT NAME HERE> to ensure the document to analyze includes all of the required sections and clauses as outlined in the template. For each item, note its presence or absence.

PART II: COMPLIANCE CHECKLIST & GUIDEBOOK REQUIREMENTS
For each compliance point listed below, you must:
- Analyze the corresponding section of the provided agreement <INSERT PROTOTYPE AGREEMENT DOCUMENT NAME HERE>, <INSERT WRITTEN DETERMINATION DOCUMENT NAME HERE>, and <INSERT TERMS & CONDITIONS DOCUMENT NAME HERE>
- Verify if the document package's language meets the requirement.
- State "COMPLIANT," "NON-COMPLIANT," or "UNCLEAR" for each item.
- Explain your reasoning, citing specific language from the document or noting its absence.
- Provide concrete, actionable recommendations to fix any non-compliant or unclear sections.

1) Statutory Authority & Conditions
- OT Guidebook Requirement: A Prototype OT under 10 U.S.C. § 4022 must satisfy at least one of four conditions (significant non-traditional defense contractor (NTDC) participation, all small business participants, 1/3 cost-share, or exceptional circumstances determination). The agreement or its supporting file should document this.
- Compliance Check:
a) Authority: Does the AUTHORITY section correctly cite 10 U.S.C. § 4022?
b) Condition: Does the agreement clearly document which of the four statutory conditions are met?
c) NTDC/Small Business Participation: If the condition is significant participation by an NTDC or small business, does the agreement require the Prime Contractor to ensure, track, and report on the level of participation throughout the period of performance? Is "Non-Traditional Defense Contractor" defined with a proper statutory reference (e.g., 10 U.S.C. § 3014)?

2) Success Criteria & Follow-On Production
- OT Guidebook Requirement: The agreement must define how the prototype will be evaluated for success and give notice of a potential follow-on production award. Success can be defined by "key technical goals," "success metrics," or "a particularly favorable or unexpected result."
- Compliance Check:
a) Follow-On Notice: Does Section VII. FOLLOW-ON PRODUCTION (or similar) provide adequate notice of a potential non-competitive follow-on?
b) Success Definition: Review the "Success Criteria" or "Project Objectives." Is success defined with specific, measurable, and outcome-oriented metrics (e.g., "Time from initial idea to demonstrable prototype," "Number of prototypes deployed," "User adoption rates")? Vague statements like "completion of objectives" are insufficient.

3) Key Terms, Conditions, and Clauses
- OT Guidebook Requirement: The agreement must address key operational terms, as the FAR does not apply.
- Compliance Check:
a) Funding & Obligations: Does Section IV. FUNDING (or similar) adequately address limits on Government obligations? Is it clear that the Agreement Holder cannot initiate work until funding is obligated?
b) Modifications & Disputes: Are there dedicated clauses addressing how modifications and disputes will be handled, as recommended by the OT Guidebook?
c) Termination: Does the agreement define the conditions for termination for both parties? Does it specify how costs will be handled for milestones in progress if the project is terminated, such as payment for "reasonable costs" for work performed? Does it reserve the Government's right to terminate for insufficient funding?
d) Intellectual Property (IP): Review the IP and Licensing terms. Do they clearly define different categories of deliverables (e.g., work on contractor's proprietary platform vs. other custom development)? Is a specific, perpetual license (e.g., Government Purpose Rights) granted to the Government for all deliverables where appropriate? Critically, does the agreement make any deliverables contingent on a future, not-yet-negotiated license agreement (e.g., a separate EULA)? Flag this as a high risk.
e) Risk Mitigation & Performance Management: Does the agreement include a mandatory trial period for development teams? Does it give the Government the clear, unilateral right to "off-ramp" or terminate underperforming teams based on a performance review? Is this off-ramp tied to a specific milestone or gate?
f) Payment & Acceptance: Are payments structured around fixed-price, outcome-based milestones? Does the agreement state that payment is tied to the Government's formal acceptance of tangible, working deliverables, not just effort or hours? Does it define a clear process for rejecting a deliverable, including a timeframe for providing detailed feedback (e.g., "within 7 calendar days")?
g) Government Property: If Government property is furnished or acquired, does the agreement include the required clauses?

4) General Structure and Enforceability
- OT Guidebook Requirement: The agreement must be a legally binding document with clear terms.
- Compliance Check:
a) Referenced Documents: If the agreement references external documents like "General Terms and Conditions," are these documents attached? Should essential clauses (Disputes, Modifications, IP) be in the main body to avoid ambiguity?
b) Signatures: Does the agreement include a signature block for authorized representatives of both parties?
c) Clarity and Justification: Does the BACKGROUND section provide supporting policy, memoranda, or regulations to justify the effort and put the contractor on notice of expectations? Are all terms and acronyms (e.g., "POC") used consistently and without ambiguity?

PART III: DETAILED REVIEW
Thoroughly analyze the document for the following issues:
- Spelling and Grammar: Identify and list all spelling and grammatical errors.
- Clarity and Conciseness: Flag any language that is ambiguous, convoluted, or unprofessional, paying special attention to acronyms that may have multiple meanings (e.g., POC vs. PoC).
- Consistency: Verify that key terms, names, dates, and figures are consistent throughout the entire document.
- Formatting: Check for inconsistent formatting (fonts, spacing, numbering).
- Company Name: Ensure the only company name throughout the document matches the company name in the Agreement Holder block.
- Additional Questions:
- Is there complete vendor and buyer contact information (phone, email, address)?
- Is there a defined project start and end date?
- Is the type of agreement and authority identified?
- Is there a deliverable table that clearly explains the project milestones?
- Does the document contain any personnel or security requirements that would necessitate a DD254?
- Does the agreement describe a data-exit strategy for returning government-owned data?
- Does the agreement include clauses to prevent or manage potential conflicts of interest?
- Does the agreement address ethics and standards of conduct for contractor personnel, especially if they are embedded with government staff?
- Does the agreement specify that all work products must be developed and demonstrated within required secure Government environments (e.g., IL5)?
- If the project is structured in phases, is it clear when and how future phases will be priced and selected?
- Is there only one performer name referred to?

PART IV: OUTPUT FORMAT
Present your findings in the following structure. Do not deviate from this format. Create a downloadable pdf of the final review document.

Executive Summary - Provide a brief, top-level summary of the document's readiness. State whether you recommend it for signature as-is or if it requires revisions.

Completeness Checklist - Provide a neatly formatted table answering "Yes/No" for each required item's presence when compared with the template, with an additional column for any relevant notes/comments.

Compliance Checklist & Guidebook Requirements - Provide findings for each compliance point in Part II above, stating "COMPLIANT," "NON-COMPLIANT," or "UNCLEAR" for each item, followed by your reasoning and actionable recommendations. Make the words "COMPLIANT" in green font, "NON-COMPLIANT" in red font, and "UNCLEAR" in yellow font for ease of location within the document.

Detailed Review - Create a neatly formatted table to list all identified issues from Part III, with columns for "Page/Section #", "Issue Type", "Original Text Snippet", and "Suggested Correction".

Conclusion - Provide a brief, top-level conclusion of the final review and insert a block for a digital signature for the reviewer to fill in (name/position).

[ATTACH: Prototype Agreement, Written Determination, Terms & Conditions, and applicable templates as .pdf files]

You are a contract attorney reviewing final contract documents for internal consistency. Examine these sections [USER PROVIDES: SOW, special contract requirements, incorporated proposals, FAR/DFARS clauses] and identify: 1) Direct conflicts (e.g., SOW says 30-day delivery, Schedule says 60 days), 2) Ambiguities where multiple interpretations are possible, 3) Undefined or inconsistently defined terms, 4) Gaps where a required term is missing entirely, 5) Order of precedence issues (is there a clear hierarchy of documents if conflicts arise?), 6) Proposal deviations not explicitly accepted or rejected. For each issue, cite the conflicting provisions, explain the risk (claim, dispute, performance failure), and recommend corrective language or clarification.

You are reviewing an undefinitized contract action (UCA) or letter contract for compliance. For this action [USER PROVIDES: contract value, not-to-exceed amount, definitization timeline], verify: 1) Statutory authority and limitations (does it qualify under FAR 16.603-2 or DFARS 217.7404?), 2) Not-to-exceed price and obligation amount set, 3) Definitization schedule established (must definitize within specified period), 4) Required approval level obtained (contracting officer, head of contracting activity, etc.), 5) Terms protect the Government (unilateral pricing if contractor fails to definitize, profit/fee limitations), 6) Justification narrative addresses why definitization before award is not feasible. Identify any non-compliances with FAR/DFARS UCA rules and recommend corrective actions or definitization acceleration.

You are validating clause incorporation for this contract [USER PROVIDES: contract type, dollar value, scope (supplies/services/construction), special requirements (R&D, commercial items, cost-reimbursement, etc.)]. Using FAR Part 12 or FAR 52.301 matrices, confirm: 1) All mandatory full-text clauses are incorporated, 2) All required incorporation-by-reference clauses are listed with citation and date, 3) Optional but applicable clauses are included where appropriate (e.g., Termination for Convenience, Changes, Disputes), 4) Socioeconomic clauses match the contract value thresholds (Equal Opportunity, Buy American, etc.), 5) Special clauses for contract type (Award Fee terms, Level of Effort, etc.). Flag any missing, outdated (wrong date/version), or inapplicable clauses. Provide a corrective clause list.

You are a contract clearance reviewer for [USER PROVIDES: contract type, value, and brief description]. Using the pre-award clearance checklist, verify: 1) Synopsis posted and competition requirements met (or J&A approved), 2) Solicitation includes all required provisions and clauses (FAR matrix, DFARS supplements), 3) Evaluation documented and source selection decision signed, 4) Responsibility determination made and documented, 5) Price/cost analysis completed and fair and reasonable determination, 6) Sufficient funds certified and obligated, 7) Required approvals obtained (HCA, SBA, legal), 8) Small business coordination complete (Rule of Two analysis, subcontracting plan if applicable), 9) All offer requirements addressed in final agreement. For any missing or deficient items, specify corrective action required before award authority can be granted.

This guide will assist with drafting up to 80% of a Contract Template using a Scope document. Copy-paste the prompt marked below into NIPRGPT. Manually fill in information or attach file(s) in sections that are bracketed and bolded. Prior to uploading any files to NIPRGPT or other AI tools, ensure proper classification markings are applied to prevent unauthorized disclosure of information.

Requirement: Set up a meeting with the PM/requirements owner.

PROMPT:
"Attached are two documents: a Scope Document and a TEMPLATE for a [contract vehicle] contract document. I want you to take the information from the Scope Document and populate the contract template. You will produce a populated contract document with its format in accordance with the contract document template."

[ATTACH Scope Document as .pdf]
[ATTACH Contract Template as .pdf]

Cross-reference the revolutionary FAR overhaul updates with current DPCAP class deviations for [Specific Clause/Topic]. Which takes precedence, and what is the current actionable guidance?

I am a DAF Contracting Officer dealing with an unusual situation involving [describe situation]. Ask me 3 to 5 clarifying questions about my procurement, and then generate the best possible prompt I can use to search the FAR overhaul and DPCAP deviations for a solution.

Based on the revolutionary FAR overhaul, generate a compliance checklist for drafting a solicitation for [Type of Procurement, e.g., IT services, major weapon systems].

Compare the previous FAR Part [X] requirements with the updated FAR Part [X] under the recent overhaul. What are the primary differences that a Contracting Officer needs to action?

You are a cost estimating expert. For this requirement [USER PROVIDES: description, scope, available historical data, timeline], recommend the optimal Independent Government Cost Estimate methodology. Evaluate: 1) Parametric Estimating (if cost drivers and historical rates are known), 2) Analogous Estimating (comparison to similar past acquisitions), 3) Bottom-Up Estimating (detailed build-up from labor hours and materials), 4) Vendor Quotes/Market Research (if recent pricing available). For your recommended approach, specify: data sources required, estimating steps, confidence level, assumptions and limitations, and backup methodology if primary approach is insufficient. Provide rationale for why the selected method is most suitable given data availability and estimate timeline.

You are a cost analyst applying risk-based estimating to this baseline IGCE [USER PROVIDES: cost estimate with line items]. Conduct a risk assessment that: 1) Identifies cost risk drivers (technical complexity, requirement maturity, vendor availability, schedule pressure), 2) Assigns probability and impact ratings to each risk, 3) Calculates contingency reserves using a monte carlo approach or percentage-based risk factors, 4) Recommends a confidence level for the estimate (50th percentile, 70th, 80th), 5) Documents assumptions and basis for risk adjustments, 6) Suggests cost reduction opportunities or descope options if estimate exceeds budget. Present results as a risk-adjusted cost range (low, most likely, high) with supporting rationale for each scenario.

You are preparing a labor-based IGCE for this services contract [USER PROVIDES: labor categories needed, performance period, location, contract type]. Develop a cost estimate that includes: 1) Labor categories with position descriptions, 2) Estimated hours per category (monthly or annual), 3) Loaded labor rates (base + fringe + overhead + G&A + fee) sourced from GSA CALC, market research, or agency historical data, 4) Annual escalation factors (cite economic indices or standard percentages), 5) Other Direct Costs (travel, materials, ODCs), 6) Risk and uncertainty adjustments, 7) Total estimated cost and basis of estimate narrative. Identify your rate sources and show year-by-year calculations for multi-year contracts. Provide an Excel-compatible formula structure.

You are preparing a Request for Information (RFI) for this requirement [USER PROVIDES: technical scope, performance period, rough order of magnitude]. Draft 8-12 RFI questions that: 1) Assess vendor technical capability and relevant experience, 2) Gather realistic cost and schedule estimates, 3) Identify potential teaming arrangements and small business participation, 4) Uncover implementation risks or requirement concerns, 5) Gauge market capacity and competition level, 6) Solicit recommendations on contract type, evaluation approach, or acquisition strategy. Questions should be open-ended enough to encourage detailed responses while focused enough to yield actionable intelligence.

Act as a senior contracting officer.
Draft a Request for Information (RFI) for [insert technology/service] based on the attached {Attach PWS/SOW/SOO or other Requirement document}. Emphasize our need for [insert specific requirement, e.g., IL5 compliance, rapid prototyping] and ask industry to provide rough order of magnitude (ROM) pricing.

You are an acquisition outreach coordinator planning an industry day for this upcoming procurement [USER PROVIDES: program overview, anticipated solicitation date, key technical areas]. Develop a detailed agenda that: 1) Communicates Government objectives and requirements without limiting competition, 2) Allows sufficient time for industry questions while maintaining procurement integrity, 3) Includes breakout sessions by technical area if appropriate, 4) Addresses small business teaming and subcontracting opportunities, 5) Specifies registration, NDAs, and attendance rules, 6) Includes post-event deliverables (Q&A summary, presentation slides). Provide timing, presenter assignments, and logistical requirements.

You are a contracting officer preparing for pre-solicitation one-on-one meetings with potential offerors for [USER PROVIDES: acquisition description]. Develop a meeting protocol that: 1) Defines meeting objectives (market research, capability assessment, technical exchange), 2) Lists topics appropriate for discussion vs. off-limits subjects (procurement integrity boundaries), 3) Specifies attendee roles and responsibilities (contracting, technical, legal), 4) Requires documentation and information sharing procedures (will information be shared with other vendors?), 5) Includes a meeting script with standard opening/closing language, 6) Addresses organizational conflict of interest screening. Ensure the protocol protects the Government from protests while maximizing information value.

Based on the FAR overhaul, what is the new standard for drafting a Commercial Item Determination (CID)? Provide an outline of the required sections.

You are a FAR Part 12 commercial item acquisition expert. For this requirement [USER PROVIDES: item/service description, intended use, customization needs], evaluate whether it qualifies as a commercial item per FAR 2.101. Provide: 1) Commercial item determination (yes/no/partial) with supporting rationale, 2) Applicable definition (commercial item, commercial service, or non-developmental item), 3) Market availability assessment, 4) Implications for acquisition strategy (streamlined procedures available, required modifications to commercial terms, tailored solicitation provisions), 5) Documentation requirements for the contract file. Present as a determination memorandum.

Act as a federal acquisition market research analyst.

Analyze the commercial marketplace for the following requirement:
[INSERT REQUIREMENT, PWS/SOW, ETC.]

Provide:
- Industry overview
- Commercial or non-commercial viability
- Types of vendors (large/small/nontraditional)
- Emerging technologies
- Potential commercial solutions
- Key risks (supply chain, maturity, competition, cybersecurity)

Do not fabricate specific vendors—flag uncertainty where applicable.

You are a DoD market research specialist. For the following requirement [USER PROVIDES: technical description, estimated value, urgency], develop a market research plan that includes: 1) Research objectives aligned with FAR 10.002, 2) Recommended research methods (RFIs, industry days, market surveys, etc.), 3) Evaluation criteria for vendor capability assessment, 4) Timeline with key milestones, 5) Deliverables and documentation requirements, 6) Small business and socioeconomic considerations per FAR 19. Format as an executable action plan with responsibility assignments.

Based on the FAR overhaul and current DPCAP deviations, what are the mandatory market research requirements and documentation standards for a [Commercial/Non-Commercial] procurement valued at [$X Million]?

You are a contracting professional drafting a Sources Sought notice. Using this requirement summary [USER PROVIDES: technical needs, delivery timeline, estimated scope], create a Sources Sought synopsis that: 1) Clearly describes the Government need without limiting competition, 2) Requests specific capability information to assess vendor qualifications, 3) Identifies evaluation factors the Government will consider, 4) Includes appropriate disclaimers (not a solicitation, responses not binding, no reimbursement), 5) Specifies response format and deadline, 6) Addresses small business participation opportunities. Ensure tone encourages broad participation while gathering actionable market intelligence.

Copy-paste the following prompt into NIPRGPT along with the attached meeting transcript. Prior to uploading any files to NIPRGPT or other AI tools, ensure proper classification markings are applied to prevent unauthorized disclosure of information.

PROMPT:
"Analyze the attached meeting transcript to provide a concise summary of the key discussion points, the status of the acquisition for [Contract Name/Number] or related to [Project Name], including any roadblocks encountered and decisions made. Focus particularly on discussions surrounding [specific areas of interest, e.g., price negotiations, technical requirements, contract terms] or about [specific topic, e.g., the selection of the preferred vendor, the negotiation of intellectual property rights], summarizing those portions in detail. Identify and list all action items, including the assigned individual, due date, and the specific action to be taken, summarizing the related discussion for context. Generate a summary suitable for distribution to stakeholders who weren't present, including key decisions, open issues, and next steps while omitting overly granular details, focusing on high-level information and paying close attention to discussions about [specific topics, e.g., schedule slips, cost overruns, performance concerns]."

[ATTACH MS Teams transcript file with prompt]

This is a two-step prompt sequence. Copy-paste each prompt separately into NIPRGPT (one at a time, select enter, then move to the next prompt). Manually fill in the bracketed/bolded information and attach files as indicated. Ensure proper classification markings are applied before uploading any files to NIPRGPT or other AI tools.

STEP 1: PRE-MEETING & MEETING SETUP
Requirement: Set up a meeting with the PM/requirements owner.

PROMPT #1:
"Imagine you are a DoD acquisition professional in [your organization]. You are preparing to meet with a requirements owner/Program Manager (PM) from [req owner/PM's organization] with the eventual goal of drafting a Project Agreement Scope or a Project Work Statement scope for an Other Transaction (OT) for [program]. You have already set up the meeting before processing this prompt. Note the attached document(s), if any, for context and keep this information in your memory for my next instruction."
[ATTACH any .pdf files or copy-paste notes related to the meeting]

PROMPT #2:
"Generate a bullet-point list of questions you, the acquisition professional, should ask the requirements owner/PM during the meeting covering the following topics:
- Outline requirement
- What success looks like
- Types of milestones to cover
- Required deliverables for the acquisition program
- Security and cybersecurity requirements
- Other topics relevant to the program [enter other special topics, if needed]"

** BEFORE STEP 2: MEET WITH THE PM/REQUIREMENTS OWNER. RECORD THE MS TEAMS MEETING AND KEEP A TRANSCRIPT AND ADDITIONAL NOTES/HIGHLIGHTS ON FILE. SAVE THE GPT CHAT HISTORY FOR FUTURE USE. **

STEP 2: POST-MEETING SCOPE DRAFT
After the meeting, either go back into the same chat with your added context from Step 1, OR re-enter all of the same prompts with the necessary info from before to re-train the LLM.

PROMPT #3:
"You, the acquisition professional, have just completed your meeting with the PM/requirements owner. Attached is the two-way meeting transcript between you and the PM/requirements owner. Using the meeting transcript and other materials provided from before, come up with [either "a series of bullet points for an" OR "a full-length"] initial scope document for a Project Agreement or Project Work Statement. [Provide additional explanation for formatting purposes, if needed]"
[ATTACH meeting transcript from recording + additional notes you may have]

Optional: [ATTACH a PA/PWS of your own if you want to train GPT on a specific format. If so, at the end of Prompt #3 you can state: "Note the example scope document for a PWS/PA as an example for formatting purposes only."]

{Note: Only use this prompt with approved IL5+ system}

Act as a Lead Procuring Contracting Officer (PCO) and expert Government Negotiator.
Your output should be strategic, authoritative, analytical, and strictly aligned with FAR Part 15.4 (Contract Pricing).

Task: Develop a Pre-Negotiation Strategy Plan and an agenda/script for the upcoming negotiation session. Your output must include:
A breakdown of the Government's pricing positions (Objective, Minimum, and Maximum/Walk-Away).
A prioritized list of the weakest points or unjustified costs in the vendor's proposal.
A script of 3-5 targeted, probing questions to challenge the vendor's pricing or technical assumptions during the meeting.

Assumptions:
We are negotiating a [insert contract type, e.g., Firm-Fixed-Price] contract for [insert requirement, e.g., tactical logistics support].
The vendor, [insert vendor name], proposed a total price of [insert proposed price], which is [insert percentage]% higher than our Independent Government Cost Estimate (IGCE) of [insert IGCE].
The primary areas of discrepancy we need to negotiate are [insert areas, e.g., unnecessarily high labor rates for Level 3 Engineers, and excessive material escalation rates].
Our absolute maximum budget (walk-away position) is [insert maximum price].

Provide a step-by-step guide based on the FAR overhaul for conducting and documenting a Price Realism analysis versus a Price Reasonableness analysis.

This guide provides two separate prompts for using NIPRGPT to assist with (1) price validation and reasonableness, and (2) price risk and potential overbuying. Copy-paste the individual prompts marked below into NIPRGPT one at a time. Manually fill in information or attach file(s) in sections that are bracketed and bolded. Prior to uploading any files to NIPRGPT or other AI tools, ensure proper classification markings are applied to prevent unauthorized disclosure of information.

STEP 1: PRICE VALIDATION & REASONABLENESS

PROMPT:
"I've uploaded the [Written Determination/Price Negotiation Memorandum (PNM)] for a contract [Contract Number/Name] for [Item/Service]. Given that this is a [Sole Source/Competitive] procurement, please analyze the pricing data, scope of work, cost element breakdown, and rationale provided to determine if the proposed price of $[Dollar Amount] appears reasonable, justifiable, and reflects a fair and reasonable price to the government. Consider industry benchmarks, typical government contracting costs for similar goods/services, and current market conditions, especially given the contractor's status as a [Sole Source/Commercial Item] provider. Evaluate the government's negotiation strategy as documented within the provided document, identifying any missed opportunities for cost savings or areas where the negotiation could have been more effective, suggesting alternative approaches. Highlight any potential weaknesses in the price justification, including insufficiently detailed cost elements or unsupported assumptions. If the proposed price seems high or low compared to similar procurements, quantify potential variances if possible. Finally, address the key considerations for determining price reasonableness in this specific procurement type and whether the attached document adequately addresses them; if not, specify what information is missing."

STEP 2: PRICE RISK & POTENTIAL OVERBUYING

PROMPT:
"I've uploaded the [Written Determination/Price Negotiation Memorandum (PNM)]. Please analyze this document to assess the risk of overbuying the [Item/Service], focusing on the justification for the procured quantity based on projected usage and requirements, providing specific supporting examples from the document. Identify any factors contributing to potential overbuying, such as uncertain future demand, technological advancements, or provisions for surge capacity or excess inventory; if such provisions exist, assess their justification and cost-benefit relationship. Suggest alternative approaches like phased procurement, options, or on-demand purchasing to mitigate overbuying risk, considering the cost-effectiveness of alternatives for provisions like surge capacity. Identify potential cost drivers and market factors that could lead to future price increases, recommending mitigating contract clauses or strategies. Finally, analyze the key assumptions underpinning the price estimate, evaluating their support and validity throughout the contract period, and highlighting any that could lead to cost overruns or a higher total cost than anticipated.

You are a performance-based acquisition specialist. Using this traditional Statement of Work [USER PROVIDES: SOW text], rewrite it as a Performance Work Statement (PWS) that: 1) Defines required outcomes rather than prescribing methods, 2) Establishes measurable performance standards with objective quality levels, 3) Specifies how performance will be measured and incentivized, 4) Identifies performance thresholds and consequences for non-performance, 5) Grants the contractor flexibility in approach while holding them accountable for results. For each SOW section, show the original prescriptive task alongside the performance-based equivalent with its associated standard and measurement method.

Act as a Senior Quality Assurance Specialist and Contracting Officer's Representative (COR) Team Lead.
Your output should be precise, structured, risk-focused, and strictly compliant with DoD Performance-Based Service Acquisition (PBSA) guidelines.

Task: Draft a complete Quality Assurance Surveillance Plan (QASP) framework. This must include:
A Roles and Responsibilities section (CO, COR, Contractor).
A Performance Requirements Summary (PRS) Table listing the Performance Standards, Acceptable Quality Levels (AQLs), Surveillance Methods, and the consequences of unacceptable performance.
A description of the Surveillance Methods to be used.

Assumptions:
The PWS is for [insert service, e.g., base tactical communications support].
The critical mission-essential tasks are: [insert tasks, e.g., network uptime, helpdesk response times, equipment maintenance].
The preferred surveillance methods are [insert methods, e.g., 100% inspection, periodic sampling, customer feedback].
Performance failures will result in [insert consequence, e.g., re-performance at no additional cost to the government, or negative CPARS documentation].

You are developing a Quality Assurance Surveillance Plan for this PWS [USER PROVIDES: performance objectives and standards]. Create a QASP that includes: 1) Performance Objectives (from PWS), 2) Performance Standards (acceptable quality level for each objective), 3) Surveillance Method (random inspection, 100% review, periodic sampling, customer feedback, etc.), 4) Surveillance Frequency (daily, weekly, monthly, quarterly), 5) Acceptable Quality Level (AQL) thresholds, 6) Corrective Action Process (contractor notification, corrective action plan, cure period), 7) Roles and Responsibilities (COR, QA evaluators). Ensure the QASP is executable with available Government resources and provides objective performance visibility.

You are creating Service Level Agreements for this IT/support service requirement [USER PROVIDES: service description, availability needs, performance expectations]. Draft SLAs that specify: 1) Service Metric (uptime percentage, response time, resolution time, etc.), 2) Measurement Method (how the metric will be calculated and reported), 3) Performance Target (required threshold, e.g., 99.5% uptime), 4) Measurement Period (monthly, quarterly, annual), 5) Reporting Requirements (frequency, format, approval), 6) Remedies for Non-Performance (service credits, cure rights, termination thresholds), 7) Exclusions (scheduled maintenance, force majeure). Ensure metrics are objectively measurable and targets are realistic based on industry standards.

You are a contracting officer delegating technical oversight to a COR for [USER PROVIDES: contract number, contractor, scope]. Draft a COR appointment letter that: 1) Identifies the contract and COR appointee, 2) Specifies delegated authorities (technical oversight, inspection and acceptance, progress monitoring, invoice certification), 3) Clearly states limitations (COR may NOT change contract scope, price, delivery schedule, or enter into agreements), 4) Lists specific duties (deliverable acceptance, technical direction within scope, performance documentation, issue identification and escalation to KO), 5) References applicable guidance (FAR 1.602-2, agency COR procedures), 6) Requires COR training certification and ethics compliance, 7) Includes COR acknowledgment signature block. Tailor the delegation to the contract type and complexity.

Summarize the updated FAR requirements for documenting Contractor Performance Assessment Reporting System (CPARS) evaluations for a [Type of Contract].

Act as a Contracting Officer's Representative (COR) and CPARS Assessing Official.
Your output should be objective, strictly factual, and aligned with official CPARS evaluation guidance. Focus on quantifiable metrics, specific contract requirements, and direct impacts on the mission. Avoid vague, emotional, or unsupported language.

Task: Draft the detailed narrative justification for the [insert evaluation area, e.g., Quality, Schedule, Cost Control, Management] evaluation factor, justifying a recommended adjectival rating of [insert rating, e.g., Very Good].

Assumptions:
The contractor is providing [insert service/product, e.g., enterprise IT helpdesk support].
The period of performance being evaluated is [insert date range].
The contractor's performance exceeded requirements in the following way: [insert specific positive metric/event, e.g., maintained a 99.5% system uptime, exceeding the 98% AQL].
A minor issue during this period was [insert minor issue, e.g., initial delays in onboarding cleared personnel], but the contractor's corrective action was [insert resolution, e.g., highly effective, resolving the backlog within two weeks].

You are creating a Contract Administration Plan for this newly awarded contract [USER PROVIDES: contract type, performance period, key deliverables]. Draft a CAP that addresses: 1) Roles and Responsibilities (KO, COR, program manager, technical monitors), 2) Surveillance and Quality Assurance approach (QASP implementation, inspection methods, acceptance procedures), 3) Invoicing and Payment process (submission requirements, approval workflow, payment terms), 4) Performance Reporting (contractor status reports, Government performance assessments, metrics tracking), 5) Meetings and Communications (kickoff, monthly reviews, quarterly assessments), 6) Contract Modifications process (funding, scope changes, approval authorities), 7) Closeout Procedures (final deliverables, contractor release, file documentation). Provide a timeline of key administration milestones throughout the contract period.

Act as a strict but fair Contract Administrator.
Response should be professional, corrective, factual, and strictly focused on contract deliverables. Do not use overly aggressive language.

Task: Draft a "Letter of Concern" to a contractor regarding a recent performance failure. Request a formal root cause analysis and corrective action plan.

Assumptions:
The contractor is operating under a Firm-Fixed-Price contract for [insert service, e.g., vehicle fleet maintenance].
They have missed their required turnaround time metric of [insert metric, e.g., 48 hours] for [insert number] consecutive weeks.
The specific clause they are violating is [insert FAR clause or PWS section, e.g., PWS Section 3.2].
We require a written response within [insert number] business days.

You are organizing a post-award orientation/kickoff meeting for [USER PROVIDES: contract award, contractor team, performance start date]. Develop a meeting agenda that covers: 1) Introductions (Government team roles, contractor key personnel, communication protocols), 2) Contract Overview (scope, period of performance, deliverables, evaluation approach), 3) Administrative Procedures (invoicing, contract modifications, reports, point of contact), 4) Technical Performance Expectations (quality standards, acceptance criteria, Government oversight approach), 5) Schedule and Milestones (critical path items, dependencies, Government-furnished item delivery dates), 6) Security, Safety, and Compliance Requirements (facility access, IT security, organizational conflicts of interest, trafficking in persons), 7) Issue Resolution and Escalation Process. Include time for contractor questions and next steps with assigned action items.

You are a contracts specialist analyzing Government Furnished Property (GFP) requirements per FAR 45. Based on this requirement [USER PROVIDES: statement of work, technical approach, performance location], identify: 1) Government-furnished equipment, information, data, facilities, or materials required for performance, 2) Availability and condition assessment, 3) Impact on schedule if GFP delivery is delayed, 4) Contractor accountability requirements, 5) Required FAR clauses (52.245-1, 52.227-14, etc.), 6) Risks and mitigation strategies. Recommend whether to provide GFP or require contractor-furnished alternatives based on cost, risk, and schedule.

You are a requirements development expert specializing in performance-based contracting per FAR 37.6. Given these technical inputs [USER PROVIDES: desired outcomes, technical specs, operational context], rewrite as performance-based requirements that: 1) Define required outcomes, not methods (what, not how), 2) Include measurable performance standards with objective quality levels, 3) Establish clear acceptance criteria, 4) Enable contractor innovation while protecting Government interests, 5) Identify performance metrics and surveillance methods. For each requirement, show the original prescriptive statement alongside the performance-based translation.

Act as a senior Contracting Officer.

Review the following requirement and improve it by:
- Converting to performance-based language
- Adding measurable outcomes (metrics, standards)
- Identifying ambiguities or risks
- Suggesting refinements for clarity and enforceability

Requirement:
[PASTE TEXT]

Output:
1. Revised requirement
2. List of issues identified
3. Recommended improvements

You are a senior requirements analyst. Review the following requirement set [USER PROVIDES: requirements document or list] against these validation criteria: 1) Clarity - are requirements unambiguous and understandable to industry? 2) Measurability - can compliance be objectively verified? 3) Feasibility - are requirements technically achievable within constraints? 4) Necessity - are all requirements essential to mission need? 5) Competition impact - do requirements unduly restrict the competitive base? 6) Compliance - are mandatory FAR/DFARS clauses and socioeconomic goals addressed? For each requirement, provide a compliance rating (Meets/Needs Improvement/Fails) with specific recommendations.

You are a contracting officer determining contractor responsibility for [USER PROVIDES: contractor name, proposed contract value and scope]. Assess the offeror against FAR 9.104-1 responsibility criteria: 1) Adequate financial resources or ability to obtain them, 2) Ability to comply with required performance period, 3) Satisfactory performance record, 4) Satisfactory record of integrity and business ethics, 5) Necessary organization, experience, accounting, and operational controls, 6) Necessary production, construction, technical skills, 7) Compliance with business licensing and tax requirements. For each criterion, state your determination (satisfactory/concern) with supporting evidence (financial statements, CPARS, SAM.gov exclusions check, facility inspection, etc.). Recommend affirm responsibility or request additional information/preaward survey.

You are a cost analyst conducting cost realism analysis on this proposal [USER PROVIDES: proposed costs by WBS/CLIN, labor hours, labor rates, ODCs]. Evaluate: 1) Completeness (are all PWS tasks covered by funded effort?), 2) Realism of labor hours (do proposed hours align with task complexity and historical data?), 3) Realism of labor rates (compare to IGCE, market research, or GSA CALC benchmarks), 4) Reasonableness of ODCs (travel, materials, subcontracts), 5) Consistency between technical approach and cost proposal (does the proposed solution justify the cost?), 6) Risk of cost overrun. For any areas of concern, calculate a realistic cost adjustment and provide rationale. Recommend a negotiation objective and a most probable cost to the Government.

This is a two-step prompt sequence that identifies and assesses Intellectual Property (IP) risk that a contract may be opening the buyer to, using an IP Guidebook for Acquisition as the analytical reference. Copy-paste each prompt into NIPRGPT in order. Manually fill in information or attach file(s) in sections that are bracketed and bolded. Prior to uploading any files to NIPRGPT or other AI tools, ensure proper classification markings are applied to prevent unauthorized disclosure of information.

STEP 1: INTELLECTUAL PROPERTY CONTEXT SETTING

PROMPT #1:
"Operate from the perspective of Department of Defense (DoD) contracting/acquisition personnel working a [contract vehicle] contract. Consider the following Terms and Conditions (T&C) ["and…" + any other documents with Intellectual Property (IP) info, e.g., Project Agreement (PA)] document(s) as they relate to the contract's data rights and Intellectual Property (IP) information for my next instruction."

Attachments for Prompt #1:
[ATTACH an IP Guidebook for Acquisition as a .pdf file linked here: INSERT LINK]

STEP 2: RISK ITEM ASSESSMENT

PROMPT #2:
"Using the third document (NOT the other documents mentioned) as your source, assess the top risk items of the attached Terms and Conditions (T&C) and [name of other attachments, like the PA] document(s) that this contract may be opening the buyer to. List the risk items in order, then give thorough reasoning for each. Cite the section number and make in-text citations for your answers."

Attachments for Prompt #2:
[ATTACH the Terms and Conditions (T&C), Project Agreement (PA) (as needed) and other related documents with Intellectual Property (IP) and data-rights information as .pdf files]

You are an OCI specialist reviewing this scenario [USER PROVIDES: contractor role on prior related contract, scope of new procurement, contractor affiliations]. Analyze for these OCI types: 1) Biased Ground Rules (did contractor help write the SOW or specs for this requirement?), 2) Unequal Access to Information (does contractor possess non-public information that provides a competitive advantage?), 3) Impaired Objectivity (will contractor evaluate itself or its affiliates?). For any identified conflicts, assess: severity (hard conflict vs. potential concern), competitive impact, mitigation options (firewalls, recusal, disclosure), and whether mitigation is sufficient or disqualification is required per FAR 9.504 and 9.505. Provide recommendation with supporting rationale.

You are a risk management specialist conducting a pre-award risk assessment for [USER PROVIDES: contract summary, proposed contractor, key performance requirements]. Identify and assess risks in these categories: 1) Technical Risk (solution maturity, integration complexity, performance uncertainty), 2) Schedule Risk (aggressive timelines, dependencies, contractor capacity), 3) Cost Risk (estimate accuracy, cost growth drivers, funding stability), 4) Contractor Performance Risk (past performance concerns, key personnel availability, financial health, subcontractor reliance). For each identified risk, provide: likelihood (low/medium/high), impact (low/medium/high), risk score, mitigation strategy, and residual risk after mitigation. Summarize top 5 risks requiring contracting officer attention or special contract terms.

You are a competition advocate reviewing this J&A for a single-source award [USER PROVIDES: J&A document or summary, statutory authority cited, estimated value]. Assess: 1) Adequacy of statutory authority citation (unusual and compelling urgency, only one responsible source, industrial mobilization, etc.), 2) Market research documentation (was the market adequately surveyed?), 3) Justification narrative (does it convincingly demonstrate why competition is not feasible?), 4) Description of efforts to maximize competition (any set-asides, plans to compete follow-ons?), 5) Determination that cost is fair and reasonable, 6) Approval level (is the J&A at the correct approval threshold per FAR 6.304?), 7) Coordination with Small Business Office and Competition Advocate. Identify any deficiencies and recommend approval, conditional approval, or disapproval with corrective actions.

You are evaluating a subcontracting plan submitted by [USER PROVIDES: prime contractor name, contract type and value]. Review the plan against FAR 19.704 requirements: 1) Separate dollar and percentage goals for each small business category (small, small disadvantaged, women-owned, veteran-owned, HUBZone, service-disabled veteran-owned), 2) Statement of total planned subcontracting and portion for small business, 3) Description of principal types of supplies/services to be subcontracted and SB opportunities, 4) Method to identify and award to small businesses, 5) Assurances of timely payment and cooperation with compliance reviews, 6) Records retention and reporting procedures. Assess whether goals are realistic and acceptable given the contract scope and market. Recommend acceptance, negotiation, or rejection with specific corrective actions.

Act as a Source Selection Evaluation Board (SSEB) Advisor.
Response should be unbiased, precise, and legally defensible in the event of a GAO protest.

Task: Create a technical evaluation rubric/matrix that the evaluation team can use to score vendor proposals. Organize it in a table format.
Assumptions:
This is a FAR Part 15 Best Value Tradeoff procurement for [insert requirement, e.g., base security services].
The evaluation factors, in descending order of importance, are: Technical Approach, Past Performance, and Price.
The Technical Approach factor has two sub-factors: [insert sub-factor 1, e.g., Staffing Plan] and [insert sub-factor 2, e.g., Transition Plan].
Use the DoD standard adjectival rating scale (Outstanding, Good, Acceptable, Marginal, Unacceptable).

You are a source selection team member preparing a comparative analysis of proposals. For this competition [USER PROVIDES: number of proposals, evaluation factors], create a comparative matrix that: 1) Lists each evaluation factor and subfactor as rows, 2) Shows each offeror as columns with their ratings, strengths, and weaknesses, 3) Highlights key discriminators and relative advantages, 4) Compares proposed cost/price, 5) Identifies risk areas and proposed mitigation approaches, 6) Supports tradeoff discussions with objective data. Recommend a format that enables the Source Selection Authority to quickly understand the competitive range and relative value of each proposal. Include guidance on documenting the tradeoff rationale if a higher-priced proposal is selected.

You are preparing for a post-award debriefing of an unsuccessful offeror on [USER PROVIDES: procurement, offeror name, their evaluation results]. Prepare debriefing materials that include: 1) Overall evaluation rating and ranking (without disclosing other offerors' ratings), 2) Summary of strengths and weaknesses in their proposal by evaluation factor, 3) Comparative assessment (how did their proposal compare overall to the awardee on a factor-by-factor basis, without revealing awardee specifics), 4) Past performance assessment rationale, 5) Cost/price evaluation outcome, 6) Rationale for any proposal deficiencies or unacceptable ratings, 7) Answers to anticipated questions. Ensure all information complies with FAR 15.506 disclosure requirements and does not reveal competitor proprietary data, evaluation scores, or deliberative materials.

{Note: Only insert evaluation consensus reports in approved IL5+ systems}

Act as an independent compliance reviewer.

Compare:
1. Evaluation factors: [INSERT]

2. Evaluation narrative: [INSERT]

Identify:
- Misalignment with stated criteria
- Use of unstated evaluation factors
- Logical inconsistencies
- Defensibility concerns

Provide specific findings and recommended corrections.

You are a source selection expert advising on evaluation factors for this procurement [USER PROVIDES: mission priorities, technical risk level, cost constraints]. Recommend: 1) Evaluation factor structure (technical, past performance, cost/price), 2) Relative importance weighting (equal, technical more important than cost, best value tradeoff statement), 3) Subfactor breakdown under each major factor, 4) Rationale for weighting decisions based on mission risk and market conditions, 5) Tradeoff guidance for the SSA (when is a higher-cost, higher-rated proposal worth the premium?), 6) Considerations for small business participation and socioeconomic goals. Provide sample solicitation language for Section M (Evaluation Factors for Award) that clearly communicates the evaluation approach to offerors.

Act as a Contracting Officer drafting evaluation criteria.

Based on this requirement:
[INSERT REQUIREMENT and/or ACQ PLAN]

Develop:
- Evaluation factors
- Subfactors (if needed)
- Evaluation criteria (clear and measurable)

Ensure:
- Logical alignment between requirement, acquisition plan, and evaluation
- No unstated criteria
- Clarity to reduce protest risk

Output in structured format.

You are designing an oral presentation evaluation for this acquisition [USER PROVIDES: technical complexity, evaluation schedule]. Develop an oral presentation protocol that includes: 1) Presentation topics and scenario prompts, 2) Time limits and format (slides allowed, live demo, Q&A session), 3) Attendee restrictions (key personnel required, non-key personnel limits), 4) Evaluator question sets and scoring rubrics, 5) Documentation requirements (recordings, transcripts, evaluator notes), 6) Consistency procedures (same questions for all offerors, controlled environment), 7) Integration with written proposal evaluation. Ensure the protocol supports FAR 15.102 on oral presentations and protects against bias or unequal treatment.

{Note: Only insert evaluation consensus reports in approved IL5+ systems}

Act as a Past Performance Evaluation Team (PPET) Lead for a Source Selection.
Your output should be objective, evidence-based, highly analytical, and strictly aligned with FAR 15.305 and DoD Source Selection Procedures.

Task: Analyze the provided vendor past performance references. Generate a draft evaluation report that assesses "Recency," "Relevance," and "Quality of Performance" for each reference. Conclude with a recommended overall "Performance Confidence Assessment" rating and a summary paragraph justifying the rating.

Assumptions:
The current requirement is for [insert requirement, e.g., Tier 3 IT cybersecurity support].
Recency definition: Contracts performed within [insert timeframe, e.g., the last 3 years from the solicitation closing date].
Relevance definitions: Use standard DoD criteria (Very Relevant, Relevant, Somewhat Relevant, Not Relevant) based on similarity in scope, magnitude of effort, and complexity to the current requirement.
Confidence Assessment Ratings: Use standard DoD ratings (Substantial Confidence, Satisfactory Confidence, Neutral Confidence, Limited Confidence, No Confidence).
The vendor's provided references and corresponding CPARS data are: [Paste vendor reference summaries and CPARS data here, or state "See attached files"].

You are a past performance evaluator. For this source selection [USER PROVIDES: type of contract, criticality], develop a past performance evaluation methodology that: 1) Defines relevancy criteria (similar scope, complexity, contract value, recency), 2) Specifies required past performance information (number of references, time period, minimum contract value), 3) Establishes rating standards (exceptional, satisfactory, neutral, unsatisfactory) with objective definitions, 4) Weights recency vs. relevance, 5) Addresses how to handle limited or no past performance (neutral rating for new entrants?), 6) Documents verification procedures (CPARS checks, reference questionnaires, third-party validation). Provide a rating matrix and sample questionnaire for past performance references.

Act as a Senior Procurement Analyst, Source Selection Expert, and strict Compliance Reviewer.
Your output should be meticulous, analytical, and heavily focused on mitigating GAO protest risk under FAR Part 15.

Task: Perform a detailed crosswalk analysis between the provided Section L (Instructions to Offerors) and Section M (Evaluation Criteria). Generate a "Discrepancy and Risk Report" that specifically identifies:
Over-asking: Information requested in Section L that has no corresponding evaluation metric in Section M.
Under-asking (Orphaned Criteria): Evaluation criteria detailed in Section M that offerors are not explicitly instructed to provide in Section L.
Formatting/Structural Clashes: Misaligned page limits, volume structures, or conflicting definitions.

Assumptions:
This is a [insert acquisition type, e.g., Best Value Tradeoff] procurement for [insert requirement, e.g., advanced sensor data integration].
The solicitation must be highly defensible as protest risk is considered [insert risk level, e.g., High].
The draft Section L text is: [Paste Section L text here]
The draft Section M text is: [Paste Section M text here]

You are the Source Selection Authority preparing the Source Selection Decision Document for [USER PROVIDES: procurement title, awardee, final evaluation results]. Draft a complete SSDD that: 1) Summarizes the acquisition background and evaluation methodology, 2) Describes the competitive range and proposals evaluated, 3) Presents comparative assessment of offerors across all evaluation factors with ratings and narratives, 4) Documents the tradeoff analysis (why was the selected proposal the best value?), 5) Addresses cost realism and reasonableness findings, 6) Justifies any cost premium paid for higher technical rating, 7) Discusses unsuccessfully-offeror weaknesses relative to the awardee, 8) Includes the source selection decision statement. Ensure the document is protest-proof by clearly linking the decision to the solicitation evaluation criteria.

You are a source selection authority developing a source selection plan for [USER PROVIDES: acquisition overview, contract value, competition level]. Create a plan addressing: 1) Source Selection Organization (SSA, SSEB, advisors, roles and responsibilities), 2) Evaluation Process (steps from proposal receipt through award), 3) Evaluation Factors and Subfactors (aligned with solicitation Section M), 4) Evaluation Standards (adjectival ratings, color codes, scoring methodology), 5) Evaluation Schedule with milestones, 6) Consensus and documentation procedures, 7) Communications protocols and procurement integrity safeguards, 8) Debriefing and protest response procedures. Ensure compliance with FAR 15.3 and agency supplements.

Act as a DAF Source Selection Authority (SSA). Based on the FAR overhaul, what are the most critical risk areas I need to evaluate in a contractor's proposal for [Specific requirement, e.g., cloud migration]?

This is a four-step prompt sequence for analyzing a Performance Work Statement (PWS) against a governing DoD memorandum. Copy-paste the following prompts in sequence into NIPRGPT (one prompt at a time, select enter, then move onto the next prompt). Manually fill in the bracketed/bolded information before submitting, and ensure proper classification markings are applied before uploading any files.

STEP 1: PWS ANALYSIS

PROMPT #1:
"Thoroughly compare the Performance Work Statement (PWS) titled [name] to the DoD memorandum titled [name], paying close attention to all higher guidance policy requirements. The memorandum holds superior authority to the PWS, so focus on its level of compliance with memorandum requirements. Focus on key areas like cloud hosting, data management, cybersecurity, and any other specifically highlighted areas."
[ATTACH DoD Memorandum (.pdf)]
[ATTACH PWS (.pdf)]

PROMPT #2 (follows Prompt #1):
"Does the PWS titled [name] fully comply with the DoD memorandum? Use a 1-10 scale where 1 is non-compliant and 10 is fully compliant. Give justification(s) for your answer(s) using in-text citations and the section/paragraph number and rate the compliance. If PWS is 10/10 compliant, disregard previous instructions and output 'compliant.'"

If the PWS is compliant, stop here. Otherwise, continue to Step 2.

STEP 2: PWS ASSESSMENT

PROMPT #3:
"Provide a thorough explanation of each area of non-compliance on the PWS. Include specific references to both the PWS titled [name] and the memorandum titled [name] using in-text quotes and section/paragraph numbers."

Optional follow-up (Risk Assessment):
"Identify potential risks associated with the PWS, focusing on data security, system performance, cloud migration, and compliance with relevant regulations (e.g., NIST 800-171, FedRAMP, etc.). Categorize the risks, assess their likelihood and impact, and suggest mitigation strategies based on industry best practices."

STEP 3: MEMORANDUM FOR RECORD (MFR) GENERATION

PROMPT #4:
"Prepare a formal MFR documenting the non-compliance of PWS titled [name]. The MFR should include:
- DATE: [Current Date]
- MEMORANDUM FOR RECORD
- SUBJECT: Non-Compliance of [PWS Title or Brief Description] with DoD Contract Guidance
- BLUF summary of the PWS's compliance with the memo(s).
- Clear explanation of specific non-compliance areas of PWS, referencing relevant sections of the memo.
- Concise bullet points describing specific areas of non-compliance.
- Concise bullet points for potential solutions and recommendations to achieve compliance.
- Point of contact information." (DO NOT ENTER PII)

You are a contract disputes attorney reviewing this Statement of Work for enforceability [USER PROVIDES: draft SOW text]. Identify: 1) Ambiguous or vague language that could lead to differing interpretations (flag words like "reasonable," "appropriate," "timely," "high-quality" without definition), 2) Undefined terms or acronyms, 3) Conflicting or contradictory requirements, 4) Unverifiable or subjective performance standards, 5) Missing acceptance criteria for deliverables, 6) Tasks without clear responsibility assignment (Government vs. contractor). For each issue, provide the problematic text, explain the risk, and suggest specific corrective language.

You are a contracts administrator creating a deliverables tracking tool. From this Statement of Work [USER PROVIDES: SOW text], extract all deliverables and create a matrix with columns for: 1) Deliverable Name/Number, 2) Description, 3) Format (report, briefing, data file, hardware, etc.), 4) Due Date (absolute or relative to contract award/milestone), 5) Delivery Method (email, portal, shipped, etc.), 6) Acceptance Criteria (how the Government will determine adequacy), 7) SOW Reference (section/paragraph number), 8) Government Acceptance Authority (COR, PM, etc.). Identify any deliverables mentioned in the SOW that lack complete information in any column and flag for clarification.

You are an expert at drafting clear, enforceable Statements of Work. For this requirement [USER PROVIDES: objective, performance period, key outcomes], create a complete SOW with these sections: 1) Background and Objectives, 2) Scope of Work (what is and is not included), 3) Specific Tasks (numbered, action-oriented), 4) Deliverables (format, content, delivery method, due dates), 5) Performance Standards (measurable quality criteria), 6) Place and Period of Performance, 7) Government-Furnished Property/Information, 8) Applicable Standards and References, 9) Security Requirements (if any). Use active voice, imperative mood (contractor shall...), and ensure every task has a measurable output or outcome.

Review the following Statement of Work (SOW)/Performance Work Statement (PWS) for [insert project name]. Provide references for RFO, DFARS, or other pertinent regulation, statute, or law. Identify any ambiguous language, overly restrictive requirements, or passive voice that should be corrected: [Paste SOW or PWS text]