Blog / Tools & Applications

The Control Work Planner, and How to Feed It

A task manager for the Control Matrix: one work item, several cells, done cell by cell. With the import format in full.

BK
Bernhard Kreinz
• • ~5 min read • TLCTC v2.7

The Control Matrix shows where your controls are weak: ten clusters by six NIST CSF functions, sixty cells. It does not show who is fixing them, by when, or whether the work is on track. That is a project manager’s question, and the Control Work Planner is the tool for it.

Like the other TLCTC tools it is free, runs in the browser and keeps its data there. Nothing is sent to a server. This post explains the two ideas the tool is built on and then specifies the file it imports, so you can fill it from a spreadsheet, a ticket system or a script.

Open the Control Work Planner

Work that lands in cells

Every work item covers one or more cells of the matrix. A cell is a cluster and a function: 7-DE is #7 Malware × Detect. The tool keeps two kinds of work apart, each with its own symbol:

  • Local work (blue pin) serves one environment or system: EDR on the production servers.
  • Umbrella work (purple umbrella) is one enterprise-wide capability, delivered once for every environment: a central SIEM. It is counted once, however many cells it reaches.

An item that covers several cells is finished cell by cell. A SIEM that already correlates identity events has done its job in 4-DE; it has not done it in 7-DE until the EDR telemetry arrives. So each item × cell link is set done on its own. A cell shows the item as done only once that link is done, and the item can be set to Done only when every link is. The matrix never reports a cell as covered because work elsewhere finished.

What a project manager gets

  • Views: the matrix (shaded by progress, remaining effort or overdue work; hatched cells have no work planned), a board you drag between statuses, a sortable list, a timeline with milestones, and a plan page with environments, milestones and a RAID log.
  • Status: red, amber or green per item and for the programme, derived from dates, progress and blocks, with the rules stated in the tool. The programme value can be overridden by hand.
  • Reports that open as pages and print to PDF: a status report for the steering committee with a burn-up chart, matrix coverage, workload per owner, exceptions (overdue, blocked, broken dependencies), the RAID log and the full work-item register.

The import format

The import dialog accepts two kinds of JSON file and tells them apart by shape. A file with an items array is a planner file. A file with environments that contain cells, and no items, is a Control Matrix export (next section). The planner’s own export is a planner file, so export and import round-trip.

Here is a complete small plan. Download it as template-control-work-plan.json and import it to see every field in place.

template-control-work-plan.json
{
  "tool": "tlctc-control-work-planner",
  "schemaVersion": 1,
  "programme": {
    "name": "Control uplift 2027",
    "sponsor": "CISO",
    "manager": "PMO lead",
    "startDate": "2026-11-01",
    "endDate": "2027-06-30",
    "statusNote": "Detection work on plan; patch SLA waits for the asset inventory.",
    "targetMaturity": 3
  },
  "environments": [
    { "id": "env-prod", "name": "Production" },
    { "id": "env-corp", "name": "Corporate IT" }
  ],
  "milestones": [
    { "id": "ms-soc", "name": "SOC detection baseline", "date": "2027-01-31", "description": "Central detection covers the internal clusters #1 to #7." }
  ],
  "items": [
    {
      "id": "edr-prod",
      "title": "EDR rollout to production servers: detection and host isolation",
      "type": "local",
      "envId": "env-prod",
      "cells": ["7-DE", "7-RS"],
      "cellDone": { "7-DE": "2026-11-10" },
      "control": "EDR",
      "owner": "Server team",
      "status": "in-progress",
      "priority": "P1",
      "startDate": "2026-10-15",
      "dueDate": "2026-12-15",
      "effortEst": 15,
      "milestoneId": "ms-soc",
      "maturityFrom": 1,
      "maturityTo": 3,
      "checklist": [
        { "text": "Linux servers", "done": true },
        { "text": "Windows servers", "done": false }
      ]
    },
    {
      "id": "siem",
      "title": "Central SIEM: correlation for clusters #1 to #7",
      "type": "umbrella",
      "scope": "all",
      "cells": ["1-DE", "2-DE", "3-DE", "4-DE", "5-DE", "6-DE", "7-DE"],
      "control": "Central SIEM",
      "owner": "SOC lead",
      "status": "planned",
      "priority": "P1",
      "dueDate": "2027-01-31",
      "effortEst": 60,
      "dependsOn": ["edr-prod"],
      "milestoneId": "ms-soc",
      "updates": [
        { "date": "2026-11-12", "text": "Licence renewal in procurement." }
      ]
    }
  ],
  "raid": [
    {
      "kind": "risk",
      "title": "SIEM licence renewal not yet approved",
      "severity": "high",
      "status": "open",
      "owner": "Programme manager",
      "dueDate": "2026-11-30",
      "itemIds": ["siem"],
      "mitigation": "Business case with three volume scenarios."
    }
  ]
}

Top level

FieldContent
itemsArray of work items. The only required field.
programmename, sponsor, manager, startDate, endDate, statusNote (opens the status report), targetMaturity (0–5, default 3) and ragOverride ("green", "amber", "red" or empty for the derived status).
environmentsArray of { "id", "name" }. Local work belongs to one of them. Without the array the plan gets one environment called Default.
milestonesArray of { "id", "name", "date", "description" }.
raidArray of RAID entries (below).
tool, schemaVersion"tlctc-control-work-planner" and 1. Written on export, optional on import.
snapshots, nextKeyWritten by the tool (the daily snapshots behind the trend chart, and the next free key). Leave them out of hand-made files.

All dates are YYYY-MM-DD. A value in any other form is dropped.

Work item

FieldValuesMeaning
titletextWhat will be delivered.
type"local" | "umbrella"Anything other than "umbrella" is read as Local.
cellsarray of cell keysThe cells the item covers, at least one. Key = cluster number, hyphen, function: GV, ID, PR, DE, RS or RC. Example: "10-PR".
cellDoneobject, cell key → dateThe cells in which the item is done, with the date it was set done there.
envIdenvironment idLocal work only. Unknown or missing: the first environment.
scopeall, applications, platform, infra-sw, infra-hwUmbrella work only. Default all.
statusbacklog, planned, in-progress, blocked, review, done, cancelledDefault backlog. Cancelled items stay listed but leave every total.
priorityP1 to P4Default P3.
startDate, dueDatedateDrive the timeline and the derived status.
owner, team, controltextAccountable person or role, team, and the control the work delivers.
effortEst, effortActualnumberPerson-days. The estimate weights progress across items.
costnumberPlanned cost, in whatever currency you plan in.
progress0–100Manual progress. Ignored when the item has a checklist.
checklistarray of { "text", "done" }Steps; their share done is the item’s progress.
maturityFrom, maturityTo0–5Control maturity now and when the work is delivered (the Control Matrix scale).
dependsOnarray of item idsItems that must finish first.
milestoneIdmilestone idThe milestone the item counts towards.
updatesarray of { "date", "text" }Status updates; the latest one appears in the reports.
id, keytextYour identifier, used by dependsOn and the RAID links, and the display key (WI-001). Both are generated when missing.
description, tags, linktext, array of text, URLFree description, tags, and a link to a ticket or epic.

The done rule on import

A file can claim an item is done while one of its cells is not. The importer resolves this the way the tool does:

  • An item with several cells, a cellDone object and at least one cell missing from it is imported as review, not Done.
  • An item marked done with no cellDone at all, such as a file written before the field existed or by another tool, is read as done in every cell.
  • An item with a single cell closes that cell when it is Done.

RAID entry

kind (risk, assumption, issue, dependency, decision), title, description, owner, severity (low, medium, high, critical), status (open, closed), dueDate, mitigation (the response or the decision taken) and itemIds (the work items it concerns).

What the importer forgives

  • Unknown values fall back to the defaults above; unknown fields are ignored.
  • Invalid cell keys and duplicates are dropped. An item left without a cell stays in the list and on the board but appears nowhere in the matrix, so give every item at least one.
  • Links to ids that do not exist (dependsOn, milestoneId, itemIds) are removed.
  • Numbers are clamped: progress to 0–100, maturity to 0–5.

You choose between Replace, which overwrites the plan in your browser, and Add, which appends everything with new keys. When adding, environments with the same name are joined, and dependencies, milestones and RAID links are carried over to the new ids.

Importing a Control Matrix export

The quickest start is the matrix you already have. Export it from the Control Matrix and import the file here. Its controls become work items, and the items are always added to the current plan.

In the Control Matrix exportBecomes
A Local control in a cellA Local item in that cell, in the environment of the same name (created if missing).
An Umbrella control written into one cellAn Umbrella item in that cell.
A shared control linked from many cellsOne Umbrella item covering every cell that links it, across all environments, starting from its lowest maturity.
A cell taskA Local item with the task’s owner and due date (status open becomes planned).

By default only controls below the target maturity, or not yet assessed, are imported; the target comes from the file and can be changed in the dialog. A control becomes an item titled “Raise control to 3 (Defined)” with its owner, link and current maturity filled in. The planner remembers what it imported, so importing a later export of the same matrix adds only what is new.

Getting data out

Export plan (JSON) writes the format above, including milestones, the RAID log and the daily snapshots. Keep it as a backup or import it on another machine. CSV writes one row per work item, all items or only the filtered ones, for Excel and the like: key, title, type, cells, cells done, clusters, functions, environment or scope, control, owner, team, status, priority, derived status, start and due date, progress, effort estimate and spent, cost, milestone, dependencies, maturity from and to, tags, link, latest update and description.

Data lives in your browser’s local storage, per browser and per device. Clearing site data deletes it, so export before you do.

Sources

  1. [1] TLCTC Control Work Planner; source on GitHub: tools/control-work-planner.html.
  2. [2] Import template: tools/examples/template-control-work-plan.json.
  3. [3] TLCTC Control Matrix, and the app gallery for the other control tools.
  4. [4] TLCTC v2.7 application paper, §8.1, the control matrix of clusters by NIST CSF 2.0 functions.

TLCTC Framework · v2.7 · CC BY 4.0