clmSpace
Documentation
Playbook administration

Standards

The Standards page is where your house view lives. Three tabs, one global scope filter, three source labels.

The three tabs

  • Playbook: every entry across User, AI, and Market sources for the current scope filter.
  • Coverage: a heatmap of (scope × obligation_type) that highlights gaps. See Coverage view.
  • Templates: a count and link into the Templates list.

The global scope filter

The scope filter at the top of the page applies to every tab. It persists in the URL, so admins can share a link to “the playbook as it looks for vendor MSAs in US-NY” without losing context. See Scope dimensions.

Source labels

  • User · Entered / Imported: Tier 1. Highest authority. Edit freely.
  • AI · Template / Contract: Tier 2. Suggestion. Click Verify to promote to Tier 1.
  • Market Practice: Tier 3. Read-only. Click Verify to adopt as Tier 1.

Adding a User entry

Click Add entry. Pick an obligation_type, set a scope, write a one-line position_text. Save.

Bulk CSV import

Click Import. Paste rows or upload a CSV with columns:

obligation_type, agreement_type, party_role, jurisdiction, position_text

The dialog previews parsed rows and lets you fix issues before committing. Imported entries land as User · Imported (Tier 1).

Sparse beats wrong
A playbook with five well-scoped Tier 1 entries beats one with fifty wildcards. Where you don’t have a strong position, leave the entry out and let the Market Practice fallback surface a sensible default instead.

Related