Relationship Ops

Target operating discipline for cross-company work.

Relationship Ops

Relationship operations is the target operating discipline for work that crosses company boundaries. It should sit between communication channels and systems of record, turning messages, files, meetings, portal updates, contracts, and system changes into current relationship state.

This category is not implemented yet in the current repository.

Target definition#

Relationship operations should answer six questions for every high-touch customer, vendor, and partner relationship:

  • What is the current state?
  • What changed since the last review?
  • Who owns the next step?
  • What is blocked, at risk, or overdue?
  • Which source proves each update?
  • What can each participant see or do?

Target signals#

SignalWhat it means
Multi-partycustomers, vendors, partners, and internal teams all participate
Multi-channelwork happens in email, chat, meetings, files, portals, CRM, or ERP
High-toucheach relationship needs judgment, coordination, and follow-through
Evidence-sensitivesummaries and status must be backed by source messages or documents
Permission-sensitivenot every participant can see every note, file, field, or decision
System-connectedCRM, support, finance, procurement, CLM, and project tools still matter

Target relationship record#

Record areaContains
Participantscompanies, teams, contacts, guests, service accounts, and owners
Communicationsource-backed messages, meetings, portal events, forms, and files
Workstreamsimplementation, onboarding, legal, security, finance, support, procurement, renewal
Current statestatus, blockers, risks, asks, decisions, commitments, deadlines, and next steps
Informationcontracts, files, requirements, obligations, summaries, and confidence levels
Permissionsvisibility and actions by organization, role, workstream, field, channel, and document
System syncapproved writes to CRM, support, project management, finance, procurement, ERP, and CLM

Current status#

There are no relationship records, workstreams, source events, relationship-scoped permissions, or sync rules in the current repository.