# Operational memory for recurring freight work

Operational memory is RunaboutX's concept for carrying relevant context from past work into the next load. The design goal is to retain patterns such as customer preferences, lane details, and prior exceptions so an operations team can review suggestions with context.

## Context that should be inspectable

Imagine a recurring receiver that requires a specific check-in procedure. A new dispatcher should see the note, where it came from, and when it was last confirmed. If the procedure changes, the team should be able to correct it. Memory without provenance or an update path can spread a bad assumption.

## Review before reuse

Ask what information is stored, who can edit it, how stale facts are identified, and whether sensitive data is included. The public site does not provide a detailed security or retention policy, so confirm those points directly before adoption. Read [system of record versus system of action](/resources/learn/system-of-record-vs-system-of-action/) for the design distinction and [book a demo](/#contact) to inspect the current workflow.

---

Canonical: https://www.runaboutx.com/features/operational-memory/
Last reviewed: 2026-10-14