01
Decision reasoning
Why an important decision was made and which evidence supported it.
USE CASE
Keep the context before the handoff starts.
Nura preserves source-backed decisions and company context as work happens, so a transition does not depend on one final memory dump.
WHAT USUALLY WALKS OUT
The file stays. The reasoning disappears.
02
Relationship history
The context behind important customer and partner relationships.
03
Customer promises
Commitments that may not be visible in the formal account record.
04
Exceptions
Special cases that should not become the default operating rule.
05
Operating steps
The unwritten details explaining how the work actually gets done.
06
Open loops
Unresolved work, pending approvals, and questions that still need owners.
THE HANDOFF RECORD
Bring the important context together.
Each item stays tied to its source where available, instead of becoming an unsupported sentence inside a final handover document.
Handoff contextSource attachedASK AFTER THE TRANSITION
The company should still be able to answer the next question.
Ask NuraCompany memory
What unresolved work did this person leave behind?
ACCESS REMAINS INTACT
Retained knowledge still follows permission.
Preserving context does not make it universal. The same source and workspace access rules should continue to apply after a role transition.
Source permissions remain
Existing access boundaries continue to control retrieval.
Workspace boundaries remain
Preserved context does not become visible across every workspace.
Context remains traceable
Each supported record remains connected to its available source.
FAQs
Knowledge transfer, answered.
01Is offboarding the only time this matters?
No. The same model helps with parental leave, internal transfers, reorganizations, temporary coverage, and role changes.
02Does Nura require a departing employee to write everything down?
The goal is to reduce dependence on a last-minute documentation exercise by using approved sources that are already part of the work.