Use casesOperations

Turn recurring work into reusable operating context.

Operations work repeats, but context often disappears between cycles. BaseHalf keeps checklists, decisions, incidents, and handoffs visible so the next run starts from what the team already learned.

PromptCreates 3 Points

Turn this operational workflow into decisions, checklists, incident notes, owners, and follow-up Points.

  • Workflow map
  • Exceptions
  • Handoffs
Workflow

From one request to reusable context

01

Map the recurring workflow

Create Points for inputs, owners, checklist steps, known risks, and escalation paths.

02

Preserve decisions and exceptions

Keep policy choices, one-off exceptions, and incident explanations separate from routine checklist items.

03

Connect handoffs

Reference the source context behind each handoff so the next owner can continue without asking for the whole backstory.

04

Improve after each cycle

Retire stale steps, promote recurring fixes into the checklist, and keep unresolved risks visible.

Complex scenario

Example: improving a monthly customer handoff

An operations team repeats the same handoff every month, but context disappears between cycles. Incidents, exceptions, owners, and checklist changes need a durable place.

01

Map the recurring workflow

Create Points for inputs, owners, checklist steps, known risks, and escalation paths.

02

Separate routine from exception

Keep the checklist stable while exceptions and incidents get their own Points.

03

Connect the handoff

Reference the source context behind each handoff so the next owner can continue without asking for the backstory.

04

Improve the next cycle

Promote recurring fixes into the checklist and retire stale steps after each review.

Map structure

What the workspace should contain

Workflow map

Inputs, owners, steps, checkpoints, and escalation paths.

Exceptions

One-off cases, incidents, policy decisions, and lessons from the last cycle.

Handoffs

What the next owner needs, why it matters, and what context must travel.

Review loop

What changed after each cycle and which improvements should become standard.

Outcomes

What should exist after the work

  • A living operating Map instead of a static checklist.
  • Handoffs with the context needed to continue work.
  • Review loops that improve the workflow after each run.