Statement of Work Template Nih

Standard Operating Procedure: NIH Statement of Work Development and Management

---

1. Document Control Block

• Document ID: TR-SOP-SOW-NIH-001
• Effective Date: 2023-10-27
• Version: 1.0
• Review Cadence: Annual (every 12 months from Effective Date)

---

2. Executive Summary & Scope

This Standard Operating Procedure (SOP) establishes the systematic process for the creation, review, approval, and management of Statements of Work (SOWs) pertaining to projects involving the National Institutes of Health (NIH). The objective is to ensure all NIH-related SOWs developed by Template Registry are compliant with federal regulations (e.g., FAR, HHSAR, NIH Grants Policy Statement), NIH-specific requirements, and internal quality standards, thereby mitigating contractual and operational risks.

The scope of this SOP encompasses all personnel involved in drafting, reviewing, approving, and executing SOWs for NIH-funded contracts, grants, cooperative agreements, or collaborative agreements within Template Registry's operational framework. It specifically applies to SOWs intended for external submission to or negotiation with NIH entities. This SOP does not cover SOWs for purely internal, non-NIH specific project documentation, nor does it supersede specific terms and conditions stipulated in individual NIH solicitations or awards.

---

3. Prerequisites & Required Tools

3.1. Required Tools & Software:

• Document Creation: Microsoft Word (or equivalent) for drafting and template utilization.
• PDF Conversion/Signature: Adobe Acrobat Pro (or equivalent) for secure PDF conversion and digital signature workflows.
• Document Management System (DMS): Secure, version-controlled repository (e.g., SharePoint, Confluence, dedicated Contract Lifecycle Management system) for SOW storage and access.
• Project Management Platform: Jira, Asana, or equivalent for task tracking and progress monitoring related to SOW execution.

3.2. Compliance Standards & Regulations:

• Federal Acquisition Regulation (FAR): Specific clauses applicable to federal contracts.
• Health and Human Services Acquisition Regulation (HHSAR): Department-specific regulations complementing FAR.
• NIH Grants Policy Statement (GPS): Comprehensive policy guidance for NIH grant awards.
• NIH Guide for Grants and Contracts: Official publication for NIH policy changes and program announcements.
• Section 508 of the Rehabilitation Act: Accessibility standards for electronic and information technology.
• Internal Policies: Template Registry's Data Security, Privacy, and Contracting Policies.

3.3. Essential Knowledge & Training:

• Understanding of NIH funding mechanisms (e.g., R01, U01, P01, specific contract vehicles).
• Fundamentals of contract law and intellectual property.
• Project management principles (scope definition, risk management, quality control).
• Familiarity with Template Registry's SOW templates and associated guidelines.

---

4. Roles & Responsibilities (RACI Matrix)

---

5. Step-by-Step Procedure

Phase 1: SOW Initiation and Requirements Gathering

• 1.1. Project Identification: Project Lead formally identifies the need for an NIH-specific SOW based on an upcoming solicitation, grant application, or contract negotiation.
• 1.2. Stakeholder Identification: Project Lead identifies and engages all internal stakeholders (PI, Contract/Grant Specialist, Finance, Legal) relevant to the project.
• 1.3. Requirements Definition:
  • 1.3.1. Project Lead/PI defines project objectives, technical requirements, and high-level deliverables.
  • 1.3.2. Contract/Grant Specialist reviews the specific NIH solicitation (RFP, RFA, PA) or award mechanism to identify mandatory and recommended SOW components, terms, and conditions.

Phase 2: SOW Drafting

• 2.1. Template Utilization: Contract/Grant Specialist provides the latest approved NIH SOW template (e.g., TR-TEMP-SOW-NIH-vX.X) from the Document Management System.
• 2.2. Section Population:
  • 2.2.1. Introduction/Background: Project Lead/PI drafts the project's context, purpose, and alignment with NIH priorities.
  • 2.2.2. Scope of Work (SOW): Project Lead/PI defines the project boundaries, clearly specifying what is included and excluded.
    • 2.2.2.1. List specific tasks, subtasks, and methodologies.
    • 2.2.2.2. Ensure tasks are specific, measurable, achievable, relevant, and time-bound (SMART).
  • 2.2.3. Deliverables: Project Lead/PI identifies all tangible and intangible outputs, products, or services to be provided.
    • 2.2.3.1. Specify format, due dates, and acceptance criteria for each deliverable.
  • 2.2.4. Period of Performance: Contract/Grant Specialist inserts the proposed project start and end dates.
  • 2.2.5. Reporting Requirements: Project Lead/PI details the frequency, format, and content of progress reports, financial reports, and final reports (e.g., quarterly, annual, closeout).
  • 2.2.6. Government Furnished Property/Information (GFP/GFI): Contract/Grant Specialist, in consultation with Project Lead/PI, identifies any resources to be provided by NIH.
  • 2.2.7. Travel: Project Lead/PI outlines any anticipated travel requirements, including purpose, estimated frequency, and locations.
  • 2.2.8. Security & Data Requirements: Contract/Grant Specialist, in consultation with Project Lead/PI, incorporates clauses related to data security, privacy (e.g., HIPAA, PII), and compliance with NIH data sharing policies (e.g., Genomic Data Sharing, data management and sharing plans).
  • 2.2.9. Human Subjects/Animal Welfare: Project Lead/PI ensures compliance with relevant NIH policies (e.g., IRB/IACUC protocols, OHRP guidelines) if applicable.
  • 2.2.10. Key Personnel: Project Lead/PI identifies critical staff and their roles.
  • 2.2.11. Place of Performance: Project Lead/PI specifies locations where work will be conducted.
  • 2.2.12. Section 508 Compliance: Contract/Grant Specialist ensures any electronic deliverables meet accessibility standards.
  • 2.2.13. Special Requirements/Other Terms: Contract/Grant Specialist includes any other NIH-specific or solicitation-mandated clauses.

Phase 3: Internal Review and Approval

• 3.1. Initial Technical Review: Project Lead/PI conducts a thorough review of all drafted technical sections for accuracy, completeness, and alignment with project goals.
• 3.2. Contractual & Compliance Review: Contract/Grant Specialist reviews the entire SOW for adherence to FAR, HHSAR, NIH GPS, solicitation requirements, and internal policies.
• 3.3. Legal Review: Legal Counsel conducts a comprehensive review for legal sufficiency, risk identification, intellectual property considerations, and contractual enforceability.
• 3.4. Financial Alignment Review: Finance Department reviews the SOW to ensure alignment with the proposed budget and financial feasibility.
• 3.5. Revision & Resolution: All review comments and requested revisions are consolidated. Project Lead/PI and Contract/Grant Specialist address all feedback, circulating updated versions until consensus is achieved.
• 3.6. Quality Assurance Check: Quality Assurance Lead performs a final process compliance check using the audit checklist in Section 6.4.
• 3.7. Executive Approval: The SOW, once all internal reviews are complete and revisions incorporated, is submitted to the designated Executive Management/Approving Authority for final organizational sign-off.

Phase 4: External Submission / Negotiation (if applicable)

• 4.1. Submission Preparation: Contract/Grant Specialist prepares the final, approved SOW for submission to NIH, adhering to all submission platform (e.g., ASSIST, eRA Commons, Grants.gov) requirements and deadlines.
• 4.2. Negotiation Support: Project Lead/PI and Contract/Grant Specialist participate in any negotiations with NIH officials regarding SOW scope, terms, or deliverables.
• 4.3. Formal Execution: Upon successful negotiation and acceptance, the SOW is formally executed by authorized Template Registry and NIH representatives.

Phase 5: Documentation and Archiving

• 5.1. Final SOW Storage: The fully executed SOW (and any subsequent amendments) is uploaded to the designated Secure Document Management System.
• 5.2. Project System Update: Project Management Platform is updated to reflect the approved SOW, key milestones, and deliverables for ongoing project tracking.
• 5.3. Record Retention: Ensure SOW and all supporting documentation are retained according to Template Registry's record retention policy and federal requirements.

---

6. Quality Assurance & Verification

6.1. Key Performance Metrics & Thresholds:

• SOW Approval Rate: >95% of internally approved SOWs accepted by NIH on first submission (excluding negotiation-driven modifications).
• Compliance Audit Score: >90% adherence to FAR, HHSAR, and NIH GPS on internal compliance audits.
• SOW Amendment Rate: <5% post-execution SOW amendments (excluding NIH-initiated program changes) indicating robust initial scope definition.
• Deliverable Acceptance Rate: >98% of project deliverables accepted by NIH as defined in the SOW.

6.2. Common Pitfalls:

• Ambiguous Scope: Vague descriptions of tasks or deliverables leading to scope creep or disputes.
• Non-Compliant Clauses: Omission or incorrect inclusion of mandatory FAR, HHSAR, or NIH-specific clauses.
• Unrealistic Timelines/Resources: SOW commitments that do not align with available resources or achievable schedules.
• Missing NIH-Specific Requirements: Failure to address critical elements such as data sharing plans, human subjects research protocols, or specific reporting formats.
• Lack of Internal Alignment: Discrepancies between technical, financial, and legal SOW sections due to inadequate internal review.

6.3. Audit Checklist: This checklist is to be utilized by the Quality Assurance Lead or designated auditor prior to SOW submission.

• 6.3.1. SOW utilizes the current approved Template Registry NIH SOW template (TR-TEMP-SOW-NIH-vX.X).
• 6.3.2. All sections of the SOW template are completely populated with objective, unambiguous language.
• 6.3.3. Project objectives are clearly stated and directly supported by defined tasks.
• 6.3.4. Deliverables are explicitly defined, measurable, and include acceptance criteria and due dates.
• 6.3.5. Period of Performance is clearly stated and consistent with the project timeline.
• 6.3.6. Reporting requirements (content, frequency, format) are detailed and NIH-compliant.
• 6.3.7. All mandatory FAR/HHSAR clauses relevant to the award type are included and correctly cited.
• 6.3.8. NIH Grants Policy Statement requirements (e.g., data sharing, human subjects, animal welfare) are addressed if applicable.
• 6.3.9. Section 508 compliance considerations are integrated for electronic deliverables.
• 6.3.10. Budgetary alignment with SOW scope has been confirmed by the Finance Department.
• 6.3.11. Legal Counsel review and sign-off are documented.
• 6.3.12. All internal stakeholder reviews (PI, Contract/Grant Specialist, Finance, Legal) are documented, and comments addressed.
• 6.3.13. Final SOW is saved in the approved Secure Document Management System with appropriate version control.

---

7. Troubleshooting FAQ

7.1. Scenario: SOW rejected by NIH for non-compliance with a specific federal regulation (e.g., FAR clause).

• Problem: NIH reviewer identifies a missing or incorrectly applied regulatory clause.
• Solution: Immediately engage the Contract/Grant Specialist and Legal Counsel. Review the specific NIH feedback to pinpoint the exact non-compliant clause or section. The Contract/Grant Specialist will draft the necessary revision with precise language, referencing the correct regulation. Legal Counsel will review for accuracy and potential broader implications. Resubmit the revised SOW with a formal response acknowledging the change and providing justification.

7.2. Scenario: Significant scope creep is identified during project execution, conflicting with the original SOW.

• Problem: Project activities or client requests extend beyond the originally defined SOW boundaries, potentially impacting budget and timeline.
• Solution: Project Lead/PI must halt unapproved work immediately. Refer directly to the executed SOW to confirm deviation. Initiate Template Registry's formal change request process, documenting the proposed new tasks, associated deliverables, impact on schedule and budget, and justification. Obtain formal approval from all relevant internal stakeholders (Project Lead, Contract/Grant Specialist, Finance, Executive Management) and crucially, formal approval from NIH Contracting Officer or Grants Management Officer (as required by the original award terms) before proceeding with the expanded scope. An SOW amendment must be drafted and executed.

7.3. Scenario: Discrepancy identified between the approved SOW deliverables and the allocated project budget.

• Problem: Finance discovers that the resources (personnel, equipment, travel) required to fulfill the SOW deliverables exceed the approved project budget.
• Solution: Immediately escalate to the Project Lead/PI and Finance Department. Conduct a detailed reconciliation of the SOW deliverables/tasks against the budget line items to identify the precise origin and extent of the discrepancy. Options include:
  • Budget Amendment: If additional funding is viable and justifiable, pursue a budget amendment through appropriate NIH channels, requiring robust justification and approval.
  • SOW Scope Adjustment: If a budget amendment is not feasible, the SOW scope must be formally renegotiated with NIH. This involves identifying specific deliverables or tasks that can be reduced or eliminated without jeopardizing core project objectives. Any SOW scope reduction requires formal amendment.
  • Internal Funding Reallocation: Explore if internal funds can be reallocated without impacting other critical projects, but this does not alter the NIH-approved budget. This is an internal mitigation strategy only.