> ## Documentation Index
> Fetch the complete documentation index at: https://learn.nextedy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Concepts

> Nextedy CHECKLIST replaces informal task tracking with formal, enforceable checklists inside Polarion ALM.

export const LastReviewed = ({date}) => {
  if (!date) return null;
  const formatted = new Date(`${date}T00:00:00Z`).toLocaleDateString("en-US", {
    year: "numeric",
    month: "long",
    day: "numeric",
    timeZone: "UTC"
  });
  return <p className="mt-10 text-sm text-gray-400 dark:text-zinc-500 not-prose">
      Last reviewed on {formatted}
    </p>;
};

The product is built around four foundational concepts. Understanding them gives you a reliable mental model for configuring templates, enforcing workflow gates, designing permission schemes, and maintaining audit-ready baselines.

<Columns cols={3}>
  <Card title="Checklist States and Results" icon="file" href="/checklist/concepts/checklist-states">
    Learn how the five result states drive completion tracking, workflow validation, and reporting across every checklist.
  </Card>

  <Card title="Template System" icon="file" href="/checklist/concepts/template-system">
    Understand how templates provide consistent, reusable checklist definitions for work items, documents, test runs, and plans.
  </Card>

  <Card title="Configuration Property Hierarchy" icon="file" href="/checklist/concepts/property-hierarchy">
    Explore the four-level precedence model that lets you set global defaults and override them per type, field, or both.
  </Card>

  <Card title="Workflow Integration" icon="file" href="/checklist/concepts/workflow-integration">
    See how workflow functions and conditions turn checklists into enforceable gates for Definition of Done, Definition of Ready, and compliance reviews.
  </Card>
</Columns>

<Tip title="Where to start">
  If you are new to Checklist, begin with [Checklist States and Results](/checklist/concepts/checklist-states) to build a mental model of how items progress through their lifecycle. Then read [Template System](/checklist/concepts/template-system) to understand how predefined checklists are created and merged. The [Configuration Property Hierarchy](/checklist/concepts/property-hierarchy) and [Workflow Integration](/checklist/concepts/workflow-integration) pages round out the picture with administration and enforcement details.
</Tip>

<Frame>
  <img src="https://mintcdn.com/none-17b4493f/Jklvz9qm2AdmIvBG/checklist/diagrams/concepts/index/diagram-1.svg?fit=max&auto=format&n=Jklvz9qm2AdmIvBG&q=85&s=ddb0a2c67699b19f7471fe95b627d5be" alt="diagram" style={{ maxWidth: "500px", width: "100%" }} width="500" height="320" data-path="checklist/diagrams/concepts/index/diagram-1.svg" />
</Frame>

These four concepts work together: result states define what "checked" means, templates provide the items to check, the property hierarchy controls how templates and behaviors are resolved, and workflow integration enforces completion before status transitions.

<LastReviewed date="2026-07-02" />
