Responsibility transfers alongside ClickUp

Hand over the work. Keep the context.

moss connects selected responsibilities with owners, procedures and ClickUp actions, then keeps the transfer evidence together. Start with one responsibility and two people. Handovers are a controlled pilot; request access to check availability.

Illustrative operating context

Example records

0

Procedure

0

ClickUp action

0

People

0

Handover

Tools

Owner

FigmaDesign$540
LinearEngineering$320
NotionOperations$280

Illustrative workspace

Explore the operating context.

This interactive example uses synthetic companies and figures. Existing workspace modules stay available; your first handover can start with one procedure and two people.

Overview

3 companies
3 of 5 in view

Combined revenue

$282,000
3 companies

Combined costs

$81,000
3 companies

Combined net

$201,000
aggregated

People

18
across the group
Tools across the selected companies3 tools used by more than one company
ToolUsed byOverlapCombined monthly
LinearTidemarkLarkspurKestrel3 companies$960
SlackTidemarkLarkspurKestrel3 companies$720
StripeTidemarkLarkspurKestrel3 companies$0
FigmaLarkspur1 company$180
NotionTidemark1 company$160
QuickBooksTidemark1 company$90
VercelKestrel1 company$200

Change the company selection in the switcher and the totals and overlap recompute. Tools flagged for 2 or more companies are candidates to consolidate onto one contract.

Security

Sensitive content is encrypted in the application.

Credentials, bank details, pay, sensitive HR fields, file contents and backups are encrypted before persistence. Other content is stored readable so it can be searched; workspace permissions decide who sees it. Authorized servers decrypt protected fields to show them to the right users. This is not a zero-access architecture.

  • Credentials, bank details, pay, sensitive HR fields, file contents and backups use AES-256-GCM with table/column binding before persistence.
  • Server keys are separate from stored content. Authorized application servers can decrypt it.
  • Current workspace permissions and required second factor guard handover operations. ClickUp remains an external source.
What sits in our database
Full nameJane Doe
enc.v1.i7Wd0lXv…Fc1GBt4o
Salary$142,000 / yr
enc.v1.s7SObgef…hzQR-wEp
Contractoffer-letter.pdf
enc.v1.NQd5Fa2M…9DsdGb8b

The key that unlocks these values is held outside the database. A stolen copy is unreadable.

Work maps

Follow recorded relationships to the source.

Select a person, procedure or tool in this illustrative map to explore recorded context. During a handover, verify the current canonical source; coverage remains partial.

Acme, people and workflows· 14 nodes

Customer onboarding

Workflow · 5 steps

Click a node or relation to refocus. Filter by kind to isolate people, tools, or workflows, and the graph re-routes around what is hidden.

Supporting context

Keep the context behind a responsibility.

Existing People, tools, Finance and maps remain available. The examples below are illustrative; recorded relationships give partial coverage.

Finance

Existing Finance and tool-cost views keep supporting commercial records available under their current permissions. Your handover uses the selected procedure and its recorded evidence.

Design tools$1,140
Engineering$2,460
Operations$880
Monthly total$4,480

People

Record an operational role and responsibilities, then select the current owner and successor. Recorded relationships help find context; verify actual permissions in each source system.

AMAnna M.owns 6 tools
JKJonas K.in 4 workflows
RSRae S.owns 2 tools

Tools

Keep supporting apps and services with their recorded owners and users. Open their source records when preparing the procedure and reviewing access.

SlackNotionLinearNotion

Notion appears in two companies. Merge or keep both.

Work maps

Explore recorded relationships between people, procedures and tools. Follow them to canonical sources and verify the current owner during a handover.

IntakeReviewShip

Illustrative links to 3 people and 2 tools. Verify the current canonical source.

Example first handover

Start with one responsibility

An example setup, not measured customer results or a claim of complete coverage. Add more only when a real transfer needs it.

0
Operational peopleA current owner and a different successor, using canonical People identities.
0
Selected procedureOne responsibility with a source owner, explicit audience and canonical SOP.
0
ClickUp actionLink an existing task or review and explicitly send a new one.
0
Separate evidence factsTask completion, verified source ownership and named operator confirmation.
Questions

What people ask before requesting access

Six questions on handovers, ClickUp, pricing, and data. Items still being decided are marked as such.

  • ClickUp holds execution tasks, dates, assignees and conversations. moss connects a selected responsibility to its source owner, successor, procedure and transfer evidence. A completed task, verified source owner and named operator confirmation remain separate facts.

Free during early access

Start with your next responsibility transfer

Request access to the handover pilot. Keep execution in ClickUp and procedures at their source. moss is currently free; paid plans require at least 30 days’ written notice before any account is charged, as set out in the Terms.