Day 19 operational scorecard

Can your team find the right import file before the request becomes urgent?

Run one evidence-led self-assessment across retrieval, ownership, version confidence, and missing-record control. The score shows where operational evidence is fragile; it does not certify customs or legal compliance.

By Ayhan Karaca, Co-Founder · Updated: September 6, 2026

Private in this tab · no upload

Score one representative shipment record

Answer all twelve controls from a real retrieval test. Confirm evidence only when a retained record supports the answer.

Rubric version 1

Use one consistent four-point scale

0AbsentNo repeatable control or result can be shown.
1Ad hocThe result depends on a person, inbox, or workaround.
2DefinedA control exists but is not consistently verified.
3VerifiedThe control is repeatable and supported by current evidence.

01 · Retrieval

Retrieval time and path

Test whether the working set can be found quickly and reproducibly.
01A timed test retrieves the complete working set within the team’s approved target.

Evidence: dated test, target, start point, stop condition, and actual time.

02Stable shipment, PO, bill, or container identifiers lead to the same record set.

Evidence: identifier search paths and matched record inventory.

03Retrieval performance is sampled again after workflow or staffing changes.

Evidence: comparable test history and corrective actions.

02 · Ownership

Accountable record ownership

Make supply, review, deadline, and escalation responsibility visible.
01Every required record has a named role responsible for obtaining it.

Evidence: requirement-to-owner mapping for the tested shipment.

02Ownership remains visible when a colleague, partner, or broker is unavailable.

Evidence: fallback owner or coverage rule and activation history.

03Overdue or rejected evidence triggers a known escalation owner and deadline.

Evidence: due-state history, escalation rule, and recorded response.

03 · Version

Version confidence

Separate approved evidence from drafts, replacements, and stale attachments.
01The approved working version is identifiable without reading an entire email chain.

Evidence: review state, approver or rule, and approval timestamp.

02Replacement history shows what changed, when, and which version is current.

Evidence: version timestamps, decision history, and current marker.

03Superseded files cannot be mistaken for the approved working version.

Evidence: visible superseded state and controlled download behavior.

04 · Missing evidence

Missing-evidence control

Expose absence early and retain how it was resolved.
01The shipment has an explicit working list of required and conditional evidence.

Evidence: scoped requirement list and applicability decision.

02Missing, requested, received, reviewed, rejected, and approved states are distinct.

Evidence: dated status trail rather than one generic attachment state.

03Closure records the resolved gap, decision owner, and supporting evidence.

Evidence: closure state, decision record, and linked final version.

What does file findability mean in import operations?

File findability is the ability to retrieve the complete, current, shipment-linked working set through stable identifiers, with an accountable owner and a visible missing-evidence state. A file that exists somewhere in an inbox is not yet a controlled record.

Use a representative closed shipment and involve someone who did not build the original email thread. Score what the person can prove today, not what the process intends to do.

The four controls and the evidence each should produce
ControlTestMinimum evidence
RetrievalFind the complete working set through a stable shipment identifierTimed test and retrieval path
OwnershipIdentify who must supply, review, and escalate each recordNamed role and due-state history
Version confidenceDistinguish the approved record from drafts and replacementsApproval state, timestamp, and supersession trail
Missing evidenceSee what is absent and what blocks closureRequirement, status, owner, deadline, and resolution evidence

How should you run a defensible retrieval test?

Freeze the shipment reference, start time, tester role, requested working set, and stop condition before the test. Do not coach the tester or change the target midway. Retain only the result needed for internal improvement; do not upload shipment names or documents to this scorecard.

CBP recordkeeping guidance describes retention and production duties for applicable entry records. Those duties depend on the record and party. This tool is an operating-control assessment and does not determine which records you are legally required to retain or produce.

  • Choose a completed shipment with several partner handoffs.
  • Search from the normal starting point available to the tester.
  • Confirm the retrieved file is the approved version, not merely the first match.
  • Record missing evidence and its owner separately from retrieval time.
  • Repeat under the same protocol before comparing results.

How is the score calculated?

Each of twelve controls receives 0 to 3 points. The total is normalized to 100, and each dimension is shown separately. Evidence coverage is the share of controls backed by a retained test, record, owner assignment, history, or review result.

If less than 67% of answers have confirmed evidence, the displayed readiness band cannot exceed Developing. This prevents a confident self-report from appearing equal to a tested control environment. Even the highest band remains a planning result, not an audit opinion or certification.

Where can a controlled workflow help?

A shipment-linked workspace can connect identifiers, document requests, responses, decisions, versions, owners, and deadlines. Tyllus supports that coordination layer, but software cannot decide retention obligations, validate every document, or guarantee an authority or auditor outcome.

Turn the weakest control into an owned workflow.

Bring the retrieval test and evidence gap to a Tyllus workflow review. We will map the operating control without claiming compliance certification.