Subtask in Project Planning

Subtask

An internal subdivision of a project task, used for detailed planning, effort tracking, and execution management, typically not formally reported to the sponsor but tracked within the consortium or research group -- distinct from a formally reported task.

ByCASRAI Editorial Board

· Last updated 22 Aug 2026

Ask about Subtask

Answers are drawn from this dictionary entry and the rest of the CASRAI corpus, with a link to every source.

Answers are AI-generated from CASRAI’s own published pages and can be wrong, so check the linked sources before relying on one; your question is logged without personal data — never sold, never used to train a third-party model — to show us what CASRAI is missing, so please do not type personal or confidential details. How we use this

A subtask is an internal subdivision of a project task, used for day-to-day planning, effort allocation, and execution tracking — the finest level of granularity most research teams maintain. Unlike a task, a subtask is not a formally reported unit under any specific funder’s rules: the concept applies generically to project-management practice across funders and methodologies, from classical work-breakdown structures to agile sprint planning.

How it differs from a task

The distinguishing line is visibility and formality, not just size. A task — in Horizon Europe, numbered within a work package (T3.1, T3.2) — is defined in the application, assigned person-months, and reviewed by the funder at periodic reporting. A subtask (T3.2.1, for example) exists only inside internal collaboration tools: project wikis, issue trackers, internal Gantt charts. Only work-package- and task-level effort is normally reported to a sponsor; subtask breakdown is left entirely to the consortium or research group and is invisible outside it.

A worked numbering example

In a typical Horizon Europe-style breakdown, WP3 might contain tasks T3.1 and T3.2; T3.2 might in turn be split internally into subtasks T3.2.1, T3.2.2, and T3.2.3, each assigned to a named individual with a two- or three-week internal deadline. None of that third level appears in Annex 1 of the Grant Agreement or in any periodic report — it exists purely in the consortium’s own project-management tooling, and different partners are free to run their own subtask breakdowns differently as long as the task-level commitment to the funder is met.

What it produces and what it is not

Subtasks are how a task’s effort gets allocated across a team and tracked week to week. Disciplined subtask management is a hallmark of well-run projects, but a subtask is not itself a deliverable — it may contribute to producing one — and it is not a formally reported task, which sits one level above it and is the smallest unit any funder actually sees.

Use in your systems

JATS XML <role> element

xml

<role vocab="credit"
      vocab-identifier="https://casrai.org/dictionary/"
      vocab-term="Subtask"
      vocab-term-identifier="https://casrai.org/dictionary/term/subtask" />

Schema.org DefinedTerm (JSON-LD)

json

{
  "@context": "https://schema.org",
  "@type": "DefinedTerm",
  "@id": "https://casrai.org/dictionary/term/subtask",
  "name": "Subtask",
  "identifier": "https://casrai.org/dictionary/term/subtask",
  "description": "An internal subdivision of a project task, used for detailed planning, effort tracking, and execution management, typically not formally reported to the sponsor but tracked within the consortium or research group -- distinct from a formally reported task.",
  "inDefinedTermSet": "https://casrai.org/dictionary/domain/research-lifecycle#set",
  "url": "https://casrai.org/dictionary/term/subtask",
  "sameAs": [
    "Sub-task",
    "Activity (project)",
    "Sub-activity"
  ],
  "license": "https://creativecommons.org/licenses/by/4.0/",
  "publisher": {
    "@id": "https://casrai.org/#organization"
  },
  "dateModified": "2026-08-22T16:08:03",
  "inLanguage": "en"
}