Property Change Ledger helps you record observed changes to your note properties

Name: Property Change Ledger
Author: theluckystrike

Record selected property changes while your vault is open.

Install in Obsidian

Directory page Source on GitHub

MIT · no telemetry · core features free

Local Markdown ledger with dated JSON change records. — Open larger

version: 1.1.0
released: 2026-10-21
downloads: 19
review: Passed
health: Excellent
license: MIT
listed for: Desktop, Mobile
obsidian: 1.13.4 or later

The directory takes these platforms from the plugin manifest. The automated tests run in the desktop app only.

Directory facts fetched 2026-10-23 07:28 UTC from community.obsidian.md/users/theluckystrike.

About Property Change Ledger

You track project status or due dates and need a record of changes observed on this device.

Choose a folder and the property keys you want to watch. Property Change Ledger records later observed changes with their old values and UTC times.

Watch configuration, recent history, and filtered status review

Free features

Watch one folder and exact keys

Watch Markdown notes in a folder and its subfolders. Keys match exact spelling and case, and an empty folder selects the vault root.

Watch folder and selected keys beside sample notes. — Open larger

Start with a baseline

Existing values start the comparison period without creating history records. Saving a watch configuration establishes a new baseline.

Sample project properties that establish the baseline. — Open larger

Keep UTC time and typed values

Records include UTC observation time, note path, key and both values. A missing property differs from a present null value.

Append through a serial queue

Ledger writes run in sequence through the vault API. An unrelated note at the chosen path stops writing and leaves pending jobs for retry.

Recent records from two project notes. — Open larger

Filter recent records

View up to 100 matching records, newest first. Filter by a path fragment or an exact key, then refresh after edits.

Recent records filtered to a project and its status key. — Open larger

Pro features

Pro costs $5 a month or $15 one time through GitHub Sponsors. One sponsorship turns on Pro in every plugin that has it.

Named watch profiles Pro

Save the applied watch configuration under a name. Loading a profile starts a new baseline.

Named watch profiles with sample folder and keys. — Open larger

Filtered CSV export Pro

Export matching history to a new CSV file. The export can include records beyond the display’s 100-row limit.

CSV export confirmation beside filtered sample records. — Open larger

Status change counts by note Pro

Count observed transitions for the exact key status, grouped by note. These counts do not measure completed tasks or time in a state.

Status change counts for two sample projects. — Open larger

See how Pro works

Set up Property Change Ledger

needs

Obsidian 1.13.4 or later

steps

Run Set the folder and keys to watch.
Enter your folder, exact keys and ledger path, then select Save watch.
Edit a selected property after the baseline starts.
Run Show recent property changes and filter by note or key.

If the app can't find a new plugin yet, try again later. Obsidian says a plugin that passes the review shows in the app within 24 hours.

How to record observed changes to your note properties in Obsidian

Known limits of Property Change Ledger

The ledger cannot recover property transitions that happened while the app was closed.
Metadata cache events can combine rapid edits into one observed transition.
Pending ledger writes stay in memory and can be lost when the app closes or the plugin unloads.
Two devices can create duplicate records or conflicting writes to a shared ledger.
Historical paths keep the name observed at the time and can need correction after a rename.

Questions about Property Change Ledger

Does this include changes before installation?

Watching starts with current values as a baseline. The plugin cannot infer earlier transitions from those values.

Can I share one ledger between devices?

Each device records its own observations. Use separate ledger paths when you need to keep those observations distinct.

Can property values appear in backups?

The ledger and exported CSV contain ordinary vault data. Your backup or sync service can copy those files.

How do I retry a failed write?

Correct the storage problem, then run Retry pending ledger writes. Keep the app open until pending writes finish.

Network use

Before sign-in, requests stay off; sign-in sends the client ID and read:user scope to github.com and polls for a token. After sign-in, api.github.com receives authenticated sponsorship queries for tier and total payments; no note content, file names or vault data leaves. Successful checks last seven days, failures retry after six hours, and Refresh requests an earlier check.

Read the full network disclosure

Questions or ideas?

Tell me what is broken in Property Change Ledger, or what it should do next.

Send feedback

Property Change Ledger 1.1.0, MIT license