Statement of Work Example Nih

Standard Operating Procedure: Development of NIH-Compliant Statements of Work (SOW)

1. Document Control Block

• Document ID: TR-SOP-SOW-NIH-001
• Effective Date: 2023-10-26
• Version: 1.0
• Review Cadence: Annually (October)

2. Executive Summary & Scope

This Standard Operating Procedure (SOP) provides a structured, institutional-grade framework for the development and internal finalization of Statements of Work (SOW) intended for projects involving or funded by the National Institutes of Health (NIH). The primary objective is to ensure that all SOWs are comprehensive, scientifically rigorous, administratively compliant, and aligned with NIH guidelines, policies, and program announcement (PA) or request for applications (RFA) requirements.

Scope: This SOP covers the internal processes from initial project conceptualization to the finalization and institutional approval of an NIH-aligned SOW. It applies to all research, development, and service projects intended for submission to, or execution under, an NIH grant, cooperative agreement, or contract mechanism. It does not cover the external negotiation, submission, or post-award management of the SOW with the NIH or external partners.

3. Prerequisites & Required Tools

3.1. Knowledge & Information:

• Project scientific objectives, specific aims, and expected outcomes.
• Detailed methodology and experimental design.
• Team personnel and key roles.
• Available resources (facilities, equipment).
• Preliminary budget estimates.
• Relevant NIH Program Announcement (PA), Request for Applications (RFA), or Request for Proposals (RFP) documentation.
• NIH Grants Policy Statement (GPS) and 2 CFR 200 (Uniform Guidance).

3.2. Software & Tools:

• Standard office productivity suite (e.g., Microsoft Word, Google Docs).
• Project management software (e.g., Jira, Asana, Trello) for task tracking.
• Reference management software (e.g., EndNote, Zotero) for citations.
• NIH Forms-G and SF424 (R&R) Application Guide, if applicable for grant applications.
• Institutional compliance platforms (e.g., for IRB, IACUC protocols).

3.3. Compliance Standards:

• NIH Grants Policy Statement (GPS)
• 2 CFR 200 – Uniform Administrative Requirements, Cost Principles, and Audit Requirements for Federal Awards.
• Specific NIH Institute/Center (IC) policies, as applicable.
• Institutional policies regarding research integrity, human subjects, vertebrate animals, biosafety, and data management.

4. Roles & Responsibilities (RACI Matrix)

• Responsible (R): Individuals who do the work to complete the task.
• Accountable (A): The one person ultimately answerable for the correct and thorough completion of the deliverable or task.
• Consulted (C): Individuals whose opinions are sought, typically subject matter experts.
• Informed (I): Individuals who are kept up-to-date on progress, but not involved in the decision-making process.

5. Step-by-Step Procedure

Phase 1: Project Scoping and Initial Definition

• Step 1.1: Review NIH Requirements.
  • Read the relevant NIH RFA/PA/RFP document thoroughly to identify specific SOW content requirements, page limits, formatting, and review criteria.
  • Consult NIH Grants Policy Statement for general compliance and policy guidance.
• Step 1.2: Define Core Project Objectives.
  • Articulate the overarching project goal.
  • Establish 3-5 specific, measurable, achievable, relevant, and time-bound (SMART) aims or objectives.
  • Document preliminary hypotheses if applicable.
• Step 1.3: Outline Project Background and Significance.
  • Summarize the problem being addressed and its impact.
  • Justify the necessity of the proposed work.
  • Briefly describe existing knowledge and identify gaps.

Phase 2: SOW Content Drafting

• Step 2.1: Develop Research Strategy/Methodology.
  • Detail the proposed experimental design, research methods, and procedures.
  • Specify data collection, analysis plans, and statistical approaches.
  • Address potential pitfalls and alternative strategies.
  • Justify the appropriateness of the chosen methodology.
• Step 2.2: Define Deliverables and Milestones.
  • List all tangible outputs (e.g., reports, datasets, publications, prototypes).
  • Specify interim milestones with associated timelines.
  • Ensure deliverables are quantifiable and verifiable.
• Step 2.3: Identify Key Personnel and Responsibilities.
  • List all personnel involved, including PI, co-investigators, and key staff.
  • Briefly describe the role and specific responsibilities of each individual.
  • Provide justification for expertise and time commitment.
• Step 2.4: Describe Resources and Environment.
  • Detail available facilities, equipment, and other resources critical for the project.
  • Justify the adequacy of the institutional environment.
  • Specify any unique resources or collaborative arrangements.
• Step 2.5: Address Human Subjects/Vertebrate Animals (if applicable).
  • Clearly state involvement of human subjects or vertebrate animals.
  • Describe protections for human subjects (e.g., recruitment, consent, risks, data confidentiality).
  • Detail vertebrate animal involvement (e.g., species, number, procedures, justifications, housing).
  • Confirm Institutional Review Board (IRB) or Institutional Animal Care and Use Committee (IACUC) approval status or plan for submission.
• Step 2.6: Develop Data Management and Sharing (DMS) Plan.
  • Outline data types to be generated and their management.
  • Specify standards for data description, preservation, and sharing.
  • Describe roles and responsibilities for DMS.
  • Detail plans for data archiving and persistent identifiers.
• Step 2.7: Outline Resource Sharing Plan (if applicable).
  • Describe plans for sharing research resources (e.g., cell lines, reagents, software).
  • Adhere to NIH resource sharing policies.

Phase 3: Budget & Resource Integration

• Step 3.1: Integrate SOW with Budget Justification.
  • Ensure all personnel, equipment, supplies, travel, and other direct costs specified in the SOW are justified in the detailed budget.
  • Verify that the level of effort for personnel aligns with their described SOW responsibilities.
  • Cross-reference budget line items with SOW activities.

Phase 4: Compliance & Review

• Step 4.1: Internal Scientific Review.
  • PI conducts thorough review for scientific accuracy, completeness, and feasibility.
  • Peer review (internal or external) is conducted to identify gaps or weaknesses.
• Step 4.2: Administrative and Compliance Review.
  • Grant Administrator reviews SOW against NIH RFA/PA/RFP instructions and NIHGPS for administrative compliance (e.g., formatting, page limits, required sections).
  • Ensure all regulatory requirements (human subjects, animals, biosafety) are adequately addressed.
  • Verify proper citation format and adherence to institutional policies.
• Step 4.3: Legal Review (for Contract SOWs).
  • Legal Counsel reviews for contractual language, intellectual property rights, and liability implications if the SOW is for an NIH contract.

Phase 5: Finalization & Approval

• Step 5.1: Incorporate Revisions.
  • Implement all necessary revisions identified during internal reviews.
• Step 5.2: Obtain Institutional Approvals.
  • Secure final sign-off from the Project PI, Department Head/Director, and the Institutional Official (IO) as required by institutional policy.
  • Confirm all internal compliance approvals (e.g., IRB, IACUC, Biosafety) are in place or in progress with defined timelines.
• Step 5.3: Archive Final SOW.
  • Store the approved SOW and all supporting documentation in the designated institutional repository.

6. Quality Assurance & Verification

6.1. Key Metric Thresholds:

• Completeness Score: SOW addresses ≥95% of all explicit requirements outlined in the NIH RFA/PA/RFP and this SOP.
• Compliance Score: 100% adherence to critical NIH Grants Policy Statement and institutional regulatory requirements.
• Clarity Index: Flesch-Kincaid Grade Level ≤12.0 for general readability, adjusted for specialized technical sections.
• Budget Alignment: <5% variance between SOW narrative and detailed budget justification for key activities and resources.

6.2. Common Pitfalls:

• Vague or Non-Specific Aims: Leading to unclear project direction and measurable outcomes.
• Inconsistent Methodology: Discrepancies between described methods and specific aims.
• Insufficient Detail: Lack of specificity regarding tasks, deliverables, timelines, or personnel responsibilities.
• Non-Compliance: Failure to address specific NIH requirements (e.g., DMS plan, human subjects protections).
• Budget Mismatch: SOW activities not fully justified or supported by the proposed budget.
• Lack of Internal Cohesion: Discrepancies between different sections of the SOW (e.g., aims, methods, personnel, resources).

6.3. Audit Checklist:

• Is every section required by the specific NIH RFA/PA/RFP present and addressed?
• Are all scientific aims SMART and clearly articulated?
• Is the methodology detailed enough to allow replication?
• Are all deliverables quantifiable and associated with clear timelines?
• Are all personnel roles and efforts clearly justified and consistent with the budget?
• Is the Data Management and Sharing Plan compliant with current NIH policy?
• Are all human subjects/vertebrate animal considerations thoroughly addressed?
• Has the SOW undergone independent scientific and administrative review?
• Are all institutional approvals documented and current?
• Is the SOW free of grammatical errors, typos, and formatting inconsistencies?

7. Troubleshooting FAQ

Q1: The SOW draft feels too broad and lacks specificity, making it difficult to define clear deliverables. A1: Revisit Phase 1, Step 1.2. Work with the PI to refine the specific aims. Each aim should directly lead to a measurable outcome. Break down complex aims into smaller, more manageable sub-aims or tasks. Utilize the "5 W's and 1 H" (Who, What, When, Where, Why, How) framework for each task to enforce specificity. Ensure each deliverable is a direct result of a defined task and is quantifiable (e.g., "Report summarizing X findings" instead of "Research will be conducted").

Q2: The proposed budget does not seem to align with the activities outlined in the SOW, either over- or under-estimating resources. A2: Execute Phase 3, Step 3.1 rigorously. Conduct a line-by-line review of the budget against the SOW. For each major activity described in the SOW, identify the necessary personnel time, equipment, supplies, and services. If an activity requires specific equipment, ensure it's budgeted or justified as already available. If personnel are listed in the SOW, verify their effort (person-months) is reflected in the budget. This often requires iterative adjustments between the PI and Grant Administrator until perfect alignment is achieved.

Q3: The SOW is complete, but the Grant Administrator identifies missing elements specifically required by NIH (e.g., DMS Plan, Resource Sharing Plan). A3: Return to Phase 2, Steps 2.6 and 2.7, and Phase 4, Step 4.2. The initial review of the RFA/PA (Phase 1, Step 1.1) might have overlooked specific NIH requirements. Immediately incorporate the missing sections, ensuring they fully address the NIH mandate. The Grant Administrator should provide direct links to relevant NIH policy documents. Future SOW development should integrate these elements into initial drafting templates to prevent recurrence.