Properties and the Title

Properties are what a Collection tracks — every Entry of the Collection carries one value per Property. From a plain number to a live stopwatch to coloured tags to a full block editor Page. Every Collection also has a built-in Title — the headline on each Entry's card.

A Collection is the shape of something you track. The Properties are the pieces of data inside that shape — every Entry of the Collection carries one value for each Property. Every Collection also has a built-in Title — the headline on each Entry's card in the feed, which defaults to the Collection's name but is yours to change per Entry.

This page covers all of it: what Properties are, every Property kind you can pick from, and how the Title works.

Properties

Every Property has three things:

a name (reps, hours, note)
a kind — the type of data it holds (see the full list below)
an optional default value that fills in automatically when you quick-log

When you log an Entry on a Collection, you write one value per Property. Most Collections have 1–4 Properties. Anything beyond that usually wants to be split into multiple Collections, or composed with Sub-entries.

Property icons

Every Property shows a small icon in the builder — by default the one for its kind (a # for Number, a checkbox for True/false, and so on). Click that icon to change it: the picker opens with two tabs — Emoji and Icons (the full icon library, searchable by name). Pick a 🔥 or a flame icon for calories, a 🏃 for distance — whatever reads fastest for you.

A custom Property icon is remembered for this Collection only, so the same shared Property can wear a different icon in another Collection. To put it back, open the picker and choose Remove.

Every Property kind

Grouped here by what they're for. Pick the one that fits how you want to read and analyse the data later.

Basics

Kind	What it stores	When to use it
Number	Integer or decimal	Anything you'd sum, average, or chart — reps, kg, km, calories, ratings, glasses, cups.
Text	A short string	Names, titles, places, short notes.
Page	A full block editor — headings, lists, checkboxes, images, links, and nested pages	Journal entries, session notes, long-form reflections, a recipe's method.
True/false (Checkbox)	A yes/no flag	Habit completions — did you do it today?

Tip

A Page is the same block editor behind your built-in Page notes — headings, lists, checkboxes, images, links, and even pages nested inside pages. Add one from + Add a property → Page; every new Page starts empty, even if you've removed one with the same name before. Most Collections just need one — open an Entry and it's already there, unlabelled, at the bottom of the page. Add a second Page (say, a "Summary" and a "Quotes" field on a Book Collection) and each one gets its own small heading so you can tell them apart. Rename, reorder, or remove a Page like any other Property from its ⠿ menu. A Page also gets its own column in the table, showing the first line of what you wrote so you can scan your notes down the list — that column is read-only, so you write the Page on the Entry or its card, not in the cell.

Time

Kind	What it stores	When to use it
Date	A day — which can grow into a range or gain a clock, per value	Birthday, due date, a trip, a meeting. The picker's End date switch makes it a span (July 12 → 15) and Include time makes it a moment or a timed range — no second field needed. Mark it Show on calendar in its settings to paint entries on the Calendar.
Stopwatch	A live counter with Start / Pause / Resume / Stop	Work blocks, gardening, focus sessions — anything where you want to time it as it happens. See Stopwatch and Timer. Logging a time you already know, after the fact? Use a Number property instead.
Timer	A Stopwatch with a target duration	Pomodoro sessions, breathing exercises, meditation — same as Stopwatch but with a goal (e.g. 25 min). Overflows past zero without auto-stopping.

Running

Kind	What it stores	When to use it
GPS distance	A recorded route — the full track, distance, splits, elevation, heart rate along the way	Add it to any Collection and its Entry cards gain a Start button for live GPS-tracked runs. Runs synced from a watch arrive in the same shape — see Recording runs.

Tags (picklists)

Coloured options you pick from a list — exactly like a select / multi-select. Add one from + Add a property → Tags. Two settings (open the property's settings) decide how it behaves; you can flip either one at any time and your existing entries come along. See Tag and Multi-tag.

Setting	Off	On
Allow multiple tags	Pick one option	Pick several options
Use global tag pool	Options live on this property, this Collection only	Options come from your shared Global Tags pool, reused across every Collection

References

Kind	What it stores	When to use it
Relation	A link to another Collection's Entry	This reading session points at a specific Book Entry; this set points at the parent workout.
Sub-entries	A list of child Entries this entry owns	A dish's ingredients, a recipe's items, a shopping trip's purchases — varies per Entry. See Sub-entries.
Picture	One or more images — upload your own or paste a URL	Meal photos on a Food log, progress pics, reference shots. Shows on the Entry's card.
File	An uploaded image, audio, or PDF	Progress photo, voice memo, receipt, lab result.

Note

To set a Picture, open the Entry and tap Upload (on a phone this opens your camera or photo library) or paste an image URL — and add as many as you like (hover a thumbnail for the + to add another and the × to remove one). Click any photo to expand it full-screen — from there you can download it, delete it (deleting always asks you to confirm first — it can't be undone), or flip through a multi-photo value with the arrow keys. When you log food with AI from photos, every photo you attach is saved on the log automatically. Photos show as small square thumbnails by default — on the Entry page and on the Entry's card. Open the property's settings to pick a Picture size (small, medium, or large) and Proportions (a cropped square, or the photo's original shape) — these are per-property, so different Picture fields can look different on the same Entry. A card layout can also set its own image style (a cover or hero banner) in the card's JSON, and that always wins on that card.

Special text

Kind	What it stores	When to use it
URL	A clickable web address	Link to an article you read, a video reference, a workout demo.
Email	A formatted email address	Contacts on a CRM-style Collection.
Phone	A formatted phone number	Same.

On the Entry page, a URL property also shows a preview right under its row: YouTube and TikTok videos play inline, X posts render in full, and any other link — a Reddit thread, an article — shows a bookmark card with the page's title and picture. It's on by default; turn it off per property with the Show preview setting (open the Property's settings from the Entry page or the Collection's Properties list).

Computed

Read-only Property kinds that calculate their own value instead of storing one you type in. See Rollup and Portion and Formulas.

Kind	What it stores	When to use it
Rollup	A live sum / average / min / max / count over an Entry's sub-entries	A dish's total calories, a workout's total reps.
Portion	A dial that scales a set of number fields together	Half a banana, 150 g of chicken — one slider, every macro follows.
Formula	A Notion-style expression over an Entry's other fields	BMI from height + weight, a countdown between two dates, a label that reacts to a number.

Escape hatch

Kind	What it stores	When to use it
JSON	Arbitrary structured data	Power-user use only — for data shapes that don't fit any other kind. You probably won't need it.

Wearable data (read-only)

Kind	What it stores	When to use it
Heart Rate	An intraday heart-rate line for a day, workout, or night's sleep	Filled in automatically by connecting Fitbit or Google Health — you can't add readings by hand.

Sleep entries also carry a Bedtime and Wake time — ordinary Date/time properties, but filled in and kept read-only by your wearable connection the same way, since the sync uses them to match up nights. A small ⟳ icon next to a property's name (in its row, on an entry, and in the Collection builder) marks it as filled in by a connected source — hover or tap it for where the value comes from. Most other synced fields (heart rate stats, calories, sleep stages) aren't locked the same way — you can type over any of them, and your edit sticks on the next sync. Properties you add yourself, on those same entries, always log and edit normally. See Connecting Fitbit or Google Health.

Worked examples by domain

Pick the right kinds and the Collections feel natural to log.

Fitness — Push-ups

reps — Number, default 10
set — Number, default 1

Fitness — Run

distance_km — Number, default 5
duration_min — Number, default 30
notes — Text

Health — Sleep

hours — Number, default 7.5
quality — Tag: great / good / ok / bad
note — Text

Habit — Vitamins

taken — True/false, default true

Habit — Smoke-free day

made it — True/false, default true

Productivity — Deep work

duration — Stopwatch (live tracking — Start when you sit down, Stop when you're done)
project — Tag: Kaizendex / client A / client B
note — Page

Productivity — Pomodoro

focus — Timer, target 25 min
was productive — True/false

Reading — Pages read

pages — Number, default 10
book — Relation → Book Collection

Reading — Book finished

title — Text
author — Text
rating — Tag: ★ / ★★ / ★★★ / ★★★★ / ★★★★★
notes — Page
link — URL (Goodreads, Amazon, etc.)

Meals — Meal log

name — Text
calories — Number
protein_g — Number
tags — Multi-tag: breakfast / lunch / dinner / snack
photo — File

Mood — Daily check-in

mood — Tag: 😊 / 🙂 / 😐 / 😕 / 😞
energy — Number 1–5
note — Page

Body — Weight

kg — Number, default 78.0

Body — Blood pressure

systolic — Number
diastolic — Number
measured_at — Date/time

Time — Meditation

session — Timer, target 15 min
style — Tag: breath / loving-kindness / body scan

Reference — Contact

name — Text
email — Email
phone — Phone
notes — Page

The Title

Every Entry has a Title — the headline you read on its card in the feed. It's built in: every Collection has one automatically, so you never add it as a Property.

By default, an Entry's title is the Collection's name. Make a "Todoo" Collection and every todo you log starts out titled "Todoo". But the title is yours to change — type "Buy milk" on one, "Call the dentist" on another. Entries you never rename keep showing the Collection name, so renaming the Collection re-labels them all.

Two different things live in two different places:

The Collection's name — edited at the very top of the Collection builder. It's the Collection's identity and is the same for every Entry.
The default Entry title — the Title row at the top of the Properties tab. Leave it showing the Collection name to inherit it, or type a different default that every new Entry starts with. (Editing this does not rename the Collection.)
The Title's icon — the icon on that same Title row. It matches the Collection's icon by default, but click it to pick a different emoji or icon just for the title; choose Remove to go back to matching the Collection. Changing it here does not change the Collection's icon.

To rename one Entry, just edit its title right on the card — or open the Entry and edit the heading on its page. Because the card title is now an editable field, you open an Entry by clicking its card body or the ⋯ menu's Open.

Your other Properties — reps, hours, calories, a checkbox — show on the card next to the Title, each with its current value.

Defaults make logging fast

Defaults are the secret behind one-tap logging. If your Collection's Properties have sensible default values, tapping that Collection in chat writes a new Entry instantly with no extra input.

Set defaults thoughtfully:

Pick the value you log most often, not the average.
For habit tallies (vitamins, meds, water glass), true or 1 is almost always right.
For workouts that vary, leave the default empty and type the number — fast either way.
For Stopwatch/Timer, the default is "0m, ready to start" — the entry writes the moment you pick the Collection, then you Start the live counter on the card.

Adding, reordering, and deleting properties from an entry

You don't have to be in the Collection builder to change its schema. Open any Entry and hover a property row for its ⠿ grip: drag to reorder (the order is shared by the whole Collection), or click it for Rename, Visibility on this page, a shortcut to the card layout, and Delete from collection…. A + Add a property button under the list adds a new one — on the entry's own page, in the side panel a board opens, and on your phone. Adding and removing are immediate everywhere: the real row appears (or goes) the moment you act, even if you're mid-sentence in another field, and the save catches up behind you. See Editing an entry for the full rundown, including how hidden properties collapse and why hiding one on the entry page never touches the card or a view.

Changing a Property's kind

Picked the wrong kind, or your tracking outgrew it? You can change a Property's type after the fact — like turning a Number into Text. Open the Change type… action from any of three places:

the Collection builder — a property row's ⠿ menu → Adjust settings → Change type…
an Entry — a property row's ⋯ menu → Change type…
the table view — a column header menu → Change type

Pick the new kind and Kaizendex shows exactly what will happen to your existing values before you confirm:

Kept as-is — Text ↔ URL ↔ Email ↔ Phone ↔ Page all hold text, so nothing changes.
Converted — a Number becomes its digits as Text, a Tag becomes its label as Text, a Date gains or drops a time.
Cleared — values that can't be represented in the new kind are removed. Converting Text → Number drops any cell that isn't a number. The dialog tells you how many values this affects, and this part can't be undone — so read the warning before confirming.

Not every kind can convert: structural and computed kinds (Sub-entries, Relation, Formula, Rollup, Stopwatch, Timer, the wearable read-only kinds) don't take part, tag kinds aren't offered as Change type targets (use the settings switches instead), and turning plain text into Tags is coming later.

Edit a property's settings as JSON

Every switch in the property settings panel — a Formula's expression, a date's calendar role, a Stopwatch's auto-start, a Picture's size — is stored in one small settings document per property, and you can edit it directly: open Adjust settings and pick Advanced — edit property config JSON at the bottom. It's the same escape hatch charts and card layouts have: Apply checks the known settings and tells you exactly what's wrong and where before anything is saved. Most people never need it — it exists so power users and the AI can read and write the same settings the panel shows.

Properties that link Collections together

The Relation kind lets one Entry reference another Collection's Entry. Examples:

A Pages read Collection with a book Relation points each reading session at a specific Book.
A Set Collection with a workout Relation groups multiple sets under one workout session.
A Task done Collection with a project Relation organises completions under projects.
A Meal Collection with a recipe Relation points to a Recipe Entry with the ingredients.

Relations are how you build graphs across your tracking data without leaving the universal engine.

Pages & nesting — the block editor behind the Page Property, and your built-in Page Collection
Customizing the card — control how these Properties show on the feed card, including showing a Page inline
Stopwatch and Timer — the two live-tracking Property kinds in depth
Recording runs — record a live GPS run using the GPS distance Property kind
Connecting Fitbit or Google Health — auto-sync sleep, heart rate, and workouts
Sub-entries — log a dish and the ingredients inside it
Rollup and Portion / Formulas — the Computed Property kinds in depth
Default values & presets — pre-fill new Entries, including expression defaults like today's date
Creating a Collection — design a Collection from scratch in the builder