OpenKnowledgeBank
Bundle catalog

roles bundle

Logistician

A free, open-source set of 10 Markdown files that gives an AI assistant practical guidance for the Logistician role.

Use this bundle to plan and review Logistician work with evidence, assumptions, owners, and review points made explicit. The page previews a role guide, an overview, a workflow, and a template; the intended output is logistics decision brief. Start source review with O*NET OnLine — Summary / 13 1081.00.

Project-reviewed beta
Preview contents Download bundle Inspect source

10 Markdown files · 1,415 words · no signup · CC-BY-4.0

Inspect before downloading

See what is inside

These previews come from the published bundle files, so you can judge the method and writing before using it.

Role guide

Logistician Source-Aware Guide

Defines source-aware logistics and supply-chain planning, evidence handling, and action boundaries.

Read the file

Overview

Logistician overview

Use this bundle to prepare source-aware logistics and supply-chain planning analysis and a review-ready logistics decision brief.

Read the file

Workflow

Logistician source-aware triage

1. State the requested decision or artifact. 2. Inventory evidence: network, products, locations, service requirements, and planning horizon; demand, orders, inventory, capacity, lead times.

Read the file

Template

logistics decision brief

Review-ready artifact for logistics and supply-chain planning, evidence quality, verification, and controlled next actions.

Read the file

Is this bundle right for your task?

Who it is for

  • People performing or supporting Logistician work, plus teams reviewing its decisions and outputs
  • Teams working in Supply chain, Operations

When to use it

  • A Logistician task needs a structured plan, evidence checklist, or review-ready output.
  • A recommendation needs its assumptions, owners, risks, dependencies, and success measures made explicit.

What you need to provide

  • The task objective, intended audience, working context, constraints, source material, and decision owner.
  • Relevant reports, exports, examples, policies, prior decisions, and success measures available for the task.

Tasks and expected outputs

Questions it helps answer

  • Prepare a logistics decision brief without fabricating local facts.
  • Separate verified, provided, assumed, and missing evidence.
  • Produce a review-ready recommendation with explicit verification and approval boundaries.

What it helps produce

  • logistics decision brief

Practical example

Use it with an agent

Load the bundle as context, provide the evidence named above, then adapt this example to your situation.

Provide the task objective, intended audience, working context, constraints, source material, and decision owner. Ask the agent to approach Logistician work by producing logistics decision brief with a prioritized plan, evidence checks, owners, risks, and unresolved questions. Begin with O*NET OnLine — Summary / 13 1081.00, then confirm that the reference is current and applicable. Inspect Logistician Source-Aware Guide before drafting.

Context path: bundles/roles/logistician

What the bundle includes

Frameworks

  • source-evidence matrix
  • logistics and supply-chain planning review matrix
  • qualified-review gate

Evaluations

  • Logistician source-awareness check

Sources used to build this bundle

These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.

O*NET OnLine — Summary / 13 1081.00 Role or occupation reference for Logistician scope and source checks.

Limitations and safe use

Do not use this for

  • Treating the bundle as a substitute for organization-specific authority, firsthand evidence, or accountable review.

Known limitations

  • Use the cited official, originator, standards, or professional sources for general logistics and supply-chain planning context; local facts, records, values, states, and permissions require inspected evidence.
  • Task-specific work requires current evidence for network, products, locations, service requirements, and planning horizon; demand, orders, inventory, capacity, lead times, and source dates; suppliers, carriers, routes, rates, terms, constraints, and performance definitions; customs, trade, safety, quality, and contractual requirements; scenarios, assumptions, costs, risks, approvals, and execution status.
  • Do not infer demand, inventory availability, lead time, capacity, rate, delivery date, compliance, or optimal plan.

Safety notes

  • Minimize personal, customer, employee, financial, credential, security, privileged, and other sensitive data.
  • Require explicit confirmation before placing orders, booking transport, committing delivery, changing inventory, selecting suppliers, or approving spend.
  • Route legal, privacy, security, compliance, financial, employment, safety, and other qualified judgments to an evidenced accountable reviewer.

Next step

Inspect it before relying on it

Download the bundle for use, review its source files and evidence, or read the agent guidance. If the project is useful, starring the repository helps others discover it.

Download Review source Agent guidance Star on GitHub