Flowgrammer

Obsidian Contract Register Template

Editable Obsidian contract register vault. Operational notice flags only. Not legal advice. Not a CLM.

Download the Obsidian contract register

The Obsidian Contract Register Template is an original Markdown vault starter you use to build a local Obsidian contract register. It inherits the published contract-register field map. It is an operational register, not legal advice, not a CLM, not e-sign, not a document-approval matrix, not an Obsidian invoice tracker, and not the knowledge Document Workflow vault.

A named owner still records renew, amend, or terminate. Notice-window helpers are planning aids. Reminder delivery is not contractual notice. Bases formulas are computed views and are not stored in YAML frontmatter. Packaged samples stay on Config as_of. Sync, Publish, Git, community plugins, OS calendars, and scripts are optional and needs_live_proof. There is no native unique constraint. Vault ACLs, Sync collaborators, Publish passwords, File Recovery, and Git history are not certification. This download is original vault-setup assets. It is not an official Obsidian gallery or marketplace listing. Live vault validation is needs_live_proof. No live vault was created.

What you get

  • A core-only vault/ folder with Config, a Templates note, seven fictional register notes, person notes, Search queries, and a documented Contract Register.base file
  • YAML properties that match the parent field list, closed statuses, roles, operational notice math versus Config as_of, URL plus native-id pointers, an optional vault-attachment companion that is not sole SoR, reminders and escalation, duplicate and version rules, and exceptions including vault_path_fragile, bases_formula_only_flag, and plugin_dependency_unproven
  • CSV and XLSX companions for portability. They preserve the parent field dictionary. They are not the primary vault
  • Optional Sync, Publish, Git, and plugin notes kept separate. No plugin code is bundled
  • Seven Cedar & Quay vendor-MSA cases. They are not customer results

Do not treat a formula as legal notice. Do not auto-renew from a missed reminder. Do not treat a vault path as durable. Do not embed a full approval matrix. Do not add invoice tax, PO, or payment fields. Do not treat Sync, Publish, File Recovery, or Git as certification. Do not claim an official gallery or marketplace listing.

How to start

  1. Read Setup and acknowledge the legal-boundary, Bases-formula, core-vs-optional, no-gallery, and knowledge-workflow caveats.
  2. Copy vault/ into a local Obsidian vault.
  3. Leave Config as_of_date at 8 September 2026 while you walk Case01 through Case07.
  4. Confirm case 3 blocks a renewal decision and case 7 does not auto-renew.
  5. Read the paired guide: Obsidian Contract Tracker.
  6. Keep the parent Contract Tracker and Contract Register and Renewal Template nearby for the shared schema.
  7. Platform twins that may help: Google Sheets Contract Tracker, SharePoint / Microsoft Lists Contract Tracker, monday.com Contract Tracker, Notion Contract Tracker, and Airtable Contract Tracker. Use Document Approval Workflow only as the approval_status pointer. The knowledge Document Workflow vault stays a different job and is not linked here.

If owners, notice windows, or the destination vault are still unclear, start with an AI Success Audit. If they are named, book a fit call to scope an AI Automation Systems build.

Book an AI Success Audit call