# Checkpoints

A checkpoint in Didge is a defined point in your operational or food safety workflow where data is captured, recorded, or verified. It represents a specific, repeatable place where information enters your system, forming part of both your compliance evidence and your operational data set.

<a href="https://didge.io/contact-us" class="button primary" data-icon="star-shooting">Get Started</a>

| Free                                     | $20 per month                                | $100 per month                           |
| ---------------------------------------- | -------------------------------------------- | ---------------------------------------- |
| 3 Checkpoints                            | 15 Checkpoints                               | 50 Checkpoints                           |
| Free forever                             | Add up to 15 checkpoints in Didge            | Add up to 50 checkpoints in Didge        |
| All checkpoints, packages and reporting! | All HACCP & ISO 22,000 checkpoints available | Perfect for SME to LME                   |
|                                          | Great for business going digital             | Over 300 pre-built checkpoints available |
|                                          |                                              | Scale, grow optimise                     |
|                                          |                                              | Add further 50 checkpoints as needed     |

> #### **A checkpoint is a Didge powered form: smarter, stronger, and built for real kitchens.**

> #### **Think of a checkpoint as a form only smarter, sharper, and built for real-world operations.**

### Is the Free Plan really free?

Yes. The Free Plan is **100% free, forever**.

It’s perfect for small businesses, new sites, or teams wanting to trial and test the Didge platform without any cost.

### What is a “checkpoint” and how is it counted?

A checkpoint is a **specific, repeatable point where data enters your system**—such as a form entry, measurement, inspection, or verification step.

You’re charged **per checkpoint**, not per submission, user, task, or form.

### Example 1: Stewarding checkpoints

Here’s a refined version that incorporates your explanation and clearly connects **checkpoints to checklists** in real operational use:

**Example: How Checkpoints Work in Practice**

A good way to understand a checkpoint is to think of it as a **checklist**.

For example, your stewarding checklist might include all the verification tasks for cleaning, dishwasher temperature checks, and even Vision AI (Ridgy AI) video evidence capture. All of these tasks together form **one checklist**, and therefore **one checkpoint**.

Now imagine you have **three kitchens**: Hot, Cold, and Pastry, and you use the same stewarding checklist on a **daily**, **weekly**, and **monthly** basis. Even though the checklist itself is the same, each kitchen needs to complete its **own version** at each frequency.

That means:

* The daily stewarding checklist becomes **one checkpoint per kitchen**
* The weekly stewarding checklist becomes **one checkpoint per kitchen**
* The monthly stewarding checklist becomes **one checkpoint per kitchen**

So across three kitchens and three frequencies, you end up with **nine checkpoints**.

This shows how a checkpoint functions as a **repeatable, location-specific checklist**, a single structured point where data is captured, evidence is collected, and compliance is verified, tailored to each area of your operation.

### Example 2: Cook Chill checkpoint

Here’s a clean, clear example showing how a **checkpoint = a form** in a CCP scenario:

**Example: How a Checkpoint Works for a CCP (Cook–Chill)**

In some cases, a **checkpoint is best understood simply as a form** especially when dealing with Critical Control Points (CCPs).

For example, consider a **Cook–Chill CCP form**. This form may include multiple CCP steps such as:

* **CCP 3: Cooking temperature verification**
* **CCP 4: Rapid chilling verification**

Both of these steps are part of *one Cook–Chill form* that operators complete to record temperatures, times, corrective actions, and any supporting evidence.

Now imagine you carry out the Cook–Chill process in **three different kitchens**:

* The **Hot Kitchen**
* The **Central Production Kitchen**
* The **À la Carte Kitchen**

Even if the form is identical in all locations, each kitchen requires its **own insance** of this Cook–Chill form because each site needs to record its own operational data and its own CCP compliance evidence.

This means:

* Cook–Chill form in the Hot Kitchen → **1 checkpoint**
* Cook–Chill form in the Central Production Kitchen → **1 checkpoint**
* Cook–Chill form in the À la Carte Kitchen → **1 checkpoint**

**Total: 3 Cook–Chill checkpoints**

You can submit as many Cook–Chill records as you need, dozens or hundreds per day, but **only the number of checkpoints (the form locations) matters**, not how many submissions you make.

This example shows how, in CCP workflows, a **checkpoint works exactly like a form** that is deployed into different operational areas.

### Does the $20/month plan include the free checkpoints?

Yes.

The $20/month plan includes **15 paid checkpoints + 3 free checkpoints**, giving you **18 total checkpoints** for that tier.

### What happens when I reach my checkpoint limit?

Each pricing tier allows **up to** a certain number of checkpoints.

If your business grows and you exceed the limit:

* You automatically move into the next tier, **or**
* You can choose to purchase additional checkpoints in **packs of 50**.

This keeps pricing flexible and scalable as your operations expand.

### What if I need more than 50 checkpoints?

You can add more checkpoints at any time by purchasing **50-checkpoint bundles**.

Buy as many as you need, your subscription scales with your operational footprint.

### Is pricing based on sites, departments, or users?

Pricing is **per site**.

There is **no per-user fee**, no extra charge for departments, and no network-level pricing.

### How many users can I have?

**Unlimited users.**

Invite your entire team—managers, supervisors, auditors, and frontline staff at no extra cost.

### How many submissions can we make?

**Unlimited submissions.**

You are never charged based on usage volume, data volume, or frequency of checks.

### Do we get access to pre-built checkpoints?

Yes.

You get access to **over 300 pre-built checkpoints and templates**, including ready-to-use workflows for:

* Hotels & resorts
* Catering & banqueting
* Food manufacturing & processing
* Retail & supermarkets
* Quick Service Restaurants (QSR)
* Healthcare & hospitals

These are also packaged into complete **industry-specific solutions** you can activate immediately.

### Is Ridgy Vision AI included in the price?

Yes.

Didge includes full access to **Vision AI** and other AI-powered features at **no additional cost**.

There are no hidden premiums or AI add-on charges.

### Can I cancel anytime?

Yes.

You can **cancel at any time**—no lock-in contracts and no cancellation fees.

### Do you offer annual billing?

Yes.

Annual billing is available, and **discounts may apply** for annual payments.

### Can we book a meeting or demo?

Absolutely.

You can book a meeting with our team at any time to discuss your needs, get help with setup, or see Didge in action.
