/
/
/
Checklist

Checklist

One system, two very different users.

Admins run global checklists for onboarding, campaigns, and platform directives. Members run personal ones for habits, coursework, and challenge milestones. Both can earn PLAS, and both can trigger anything else on the platform.

The motivation loop

Act

A member does something

>

Measure

It becomes a number

>

See

The number becomes visible

>

Return

Visible progress pulls them back

Where intention becomes action

A member who intends to do something and a member who has a list are different people. The list is what converts one into the other, which is why checklists sit at the front of the motivation loop rather than in the measurement half of it. The second thing they do is quieter and more useful: a checklist is the cheapest way to track work that happens off the platform, because ticking a box takes two seconds and does not require the member to explain themselves.

How checklists are built

Everything available to you.

Three list types, tasks and subtasks throughout, and completion that can fire anything.

Defined by you

Fixed

Created by members

Custom

Both

Hybrid

Tasks and subtasks

Structure

What it can fire

On completion

Worked example

The same tool, both sides of the platform

An admin checklist and a member checklist running at the same time, doing different jobs.

 

Onboarding, week one

Admin and member side by side

Act

Admin checklist: platform onboarding sequence

Five fixed tasks assigned to every new member on day one.

Act

Member checklist: personal development path

Hybrid. You supplied three items, she added four of her own.

Measure

Each completion awards 50 points

Both lists feed the same PLAS totals, so her own goals count as much as yours.

Measure

Subtask rule: task 3 needs 2 of 4 subtasks

Partial completion is enough, because demanding all four here would stall people.

Result

A checklist item reaching across and finishing something in the LMS, with no integration in between.

Three list types, tasks and subtasks throughout, and completion that can fire anything.

Recipes

Three you could build this afternoon.

Read them as when, only if, then. That is the whole grammar of the system.

Onboard with a list, not an email

When

A member joins

Only if

First login

Then

Assign a five-item fixed checklist worth points, because a list gets finished and a welcome email gets archived

Let members own the habit

When

A member opens their dashboard

Only if

They are past week two

Then

Offer a hybrid list they can edit, since a habit somebody chose is one they keep

Make the last item matter

When

Final checklist task completes

Only if

All subtasks done

Then

Fire a Flow that awards an achievement, marks the course complete, and posts to the feed

Before you build

Three things worth knowing.

Note

Five items, not fifteen. A long checklist reads as a workload and gets abandoned on day two.

Note

Use partial subtask rules. Requiring every subtask makes one awkward item block the whole task.

Note

Checklists and goals overlap. Use a checklist for a sequence of things to do, and a goal for a number to reach.

The rest of CRM

Checklist is one of 7 parts.

PLAS

Gamplify GAME

Scorecard

Gamplify GAME

Leaderboard

Gamplify GAME

Checklist

You are here

Goals

Gamplify GAME

Dashboard

Gamplify GAME

Engagement Matrix

Gamplify GAME

Put Checklist to work.

Tell us what you are trying to get members to do, and we will show you the Flow that does it.

Scroll to Top