Knowella

Tool Crib Issue and Return

The recurring failure isn't a missing tool, it's a missing tool nobody notices is missing. A knife, spanner or torch goes out at shift start, the shift ends, and the crib log doesn't get checked against what actually came back. In a food plant that gap is a foreign body incident waiting to happen; everywhere else it's a slow bleed of replacement cost and a stores team that can never say what it's holding.

KnowOpsLogOPS-024Pinned in navigation40 fields across 4 sectionsFull researchSee the form

Reviewed by Siddarth SinghCSPLast reviewed 16 August 2026

Basis
ISO 9001 cl.7.1.5
Workspace
KnowOps
Form type
Log
Completed by
Stores
Raised
Continuously, as each issue and return occurs

The short version

  • Tool Crib Issue and Return is a KnowOps log, built against ISO 9001 cl.7.1.5, that issues a tool or instrument to a named person and records its condition, then captures return and condition again.
  • It's maintained continuously by stores, with one Issues entry per tool handed out, not batched into a periodic count.
  • The template runs 40 fields across four sections — Header, Issues, Related records, Reconciliation — with Issues repeating for every tool in circulation, and scores on tools reconciled, where high is good.
  • It links forward into the tool register and foreign body control, and back into Asset Movement and Transfer where a tool travels with an asset rather than a person.

What this is

What is a tool crib issue and return log?

What is a tool crib issue and return log?

It's the log stores uses to hand a tool or instrument to a named person and record its condition, then capture its return and condition again. It sits in KnowOps against ISO 9001 cl.7.1.5 and belongs to the Asset and Equipment Control programme, feeding the tool register and foreign body control.

When is a tool crib entry raised?

Continuously, one entry per issue, as it happens through a shift. It isn't a periodic stocktake — it's the transactional record that a stocktake or reconciliation is checked against.

Why does the log ask for calibration and food-area approval on issue, not just at return?

Because a tool that's out of calibration or not cleared for a food-contact area is a problem the moment it's handed out, not something to discover when it comes back. Checking condition only at return means the risk was already live for the whole time the tool was in use.

Scope

When is a tool crib issue and return required?

This is the log for a stores-controlled loan of a tool to a person for a shift or a task. It isn't the place to record a longer-term equipment loan, a change of asset ownership, or who holds a key.

Use this template when

  • A tool or instrument is being issued from stores to a named person and needs a condition and calibration check at the point of issue
  • A previously issued tool is being returned and its condition, completeness and calibration need checking before it goes back into circulation
  • Shift-end reconciliation needs to confirm issued and returned counts match, with any gap investigated the same day
  • A tool goes missing and a search needs a Case ID to track against, rather than being noted informally and forgotten
  • The workspace is being set up and the current tool crib contents need a first, formal issue record

Do not use it for

  • Asset Movement and Transfer, which records an asset moving between areas, sites or owners, with condition at both ends — a change of custody for an asset, not a shift loan of a tool.
  • Equipment Loan Record, which lends equipment to or borrows it from another site, a contractor or a supplier, with terms and condition — a longer-term, cross-organisation loan rather than a stores transaction.
  • Key and Access Device Register, which holds every key, fob and access device, who has it and what it opens — access control, not tool control.
  • Portable Appliance Test Record, which tests the electrical safety of portable equipment rather than tracking who is holding it right now.
  • Anything outside KnowOps, which belongs in the workspace that owns that process

Compliance mapping

Which ISO 9001 cl.7.1.5 requirements does this satisfy?

ISO 9001 cl.7.1.5 covers monitoring and measuring resources: ensuring the equipment used to check or measure conformity is suitable, maintained and traceable. Applied to a tool crib, that means the point of issue is where fitness for use has to be confirmed, not assumed.

ClauseRequirementWhere it lands
ISO 9001 cl.7.1.5The site, area and stores person responsible for control of the crib must be identified before any tool is issued.Header
ISO 9001 cl.7.1.5A tool's condition and calibration status must be confirmed at the point of issue, not assumed from its last known state.Issues
ISO 9001 cl.7.1.5Where a tool is destined for a food-contact or otherwise controlled area, its suitability for that specific use must be confirmed, not left generic.Issues
ISO 9001 cl.7.1.5Condition and completeness must be checked again on return, before the tool is treated as fit to reissue.Issues
ISO 9001 cl.7.1.5A tool not returned must trigger an active search, tracked against a case reference, rather than being left as an open entry.Issues
ISO 9001 cl.7.1.5Issued and returned counts must be reconciled at defined intervals, with damaged items withdrawn from circulation before the next issue.Reconciliation
ISO 9001 cl.7.1.5Foreign body risk arising from any unreconciled or damaged tool must be formally assessed as part of closing the reconciliation, not inferred.Reconciliation

What it does not cover

  • Returned, which is marked No with no entry in Search Raised If Not Returned or Case ID to follow it up.
  • Calibration In Date, which is marked Fail and Item Issued To is completed the same day regardless.
  • Fully Reconciled At Shift End, which is marked No with Items Outstanding left blank rather than counted.
  • Foreign Body Risk Assessed, which is marked No or Partly for a shift that also shows an unreturned item.
  • Approved For Food Areas, which is left unanswered for a tool issued into a food-contact area.

Global

Tool Crib Issue and Return requirements by country

ISO 9001 itself is jurisdiction-neutral, but the foreign body risk this log exists to control is treated very differently depending on where and into what kind of site the tool is issued.

United Kingdom

BRCGS Food Safety — foreign body detection and control requirements

Certification scheme requirement for food manufacturers

Sites certified to BRCGS are expected to show controlled issue and reconciliation of tools and utensils used in food-contact areas, and an auditor will typically ask to see a crib log that reconciles, not just one that records issues.

United States

21 CFR Part 117 Subpart B — Current Good Manufacturing Practice

Federal requirement for food-contact facilities

Equipment and utensils used in food production must be maintained in a condition that avoids contamination, which in practice pushes food manufacturers toward exactly this kind of issue-condition-return-condition discipline for tools that touch product or product-contact surfaces.

International

GFSI-benchmarked certification schemes

Baseline expectation across globally recognised food safety schemes

Most GFSI-benchmarked schemes converge on the same expectation regardless of country: tools capable of introducing a foreign body must be controlled, tracked and reconciled, which is the functional purpose of this log wherever it's deployed.

How to complete it

How to complete a tool crib issue and return, step by step

The fields are simple Yes/No entries, but four judgement calls decide whether the log actually functions as a control rather than a paper trail.

Is condition at issue a real check or a default tick?

Condition At Issue is answered by whoever is handing the tool over, often under time pressure at shift start. Whether that's a genuine look at the tool or a habitual Yes is a judgement call the reviewer has to make by spot-checking against the tool's actual state, not something the field itself can guarantee.

Does a failed calibration actually stop the issue?

Nothing in the form prevents a tool marked Calibration In Date: Fail from still being issued. Whether that failure is treated as a hard stop or just an annotation depends entirely on stores' own discipline, which is the gap between a control that exists on paper and one that operates in practice.

Is reconciliation happening every shift, or only when it's convenient?

Fully Reconciled At Shift End is a single field with no built-in check that a reconciliation entry exists for every shift that had issues. A crib that reconciles most shifts but quietly skips busy ones looks compliant in aggregate while missing exactly the shifts most likely to lose a tool.

Does an unreturned tool get searched for today, or found at the next stocktake?

Search Raised If Not Returned only appears when Returned is No, and nothing forces it to be answered the same day. The value of this log collapses if a missing tool sits as an open entry for a week before anyone acts on it.

What auditors find

Most common tool crib issue and return findings

The recurring gaps are less about the form's fields and more about what happens in the hours after a No gets entered.

FindingClauseWhat fixes it
Tool issued after Calibration In Date was recorded as Fail, with no hold placed on the item.ISO 9001 cl.7.1.5Block the Issued To field from completing whenever Calibration In Date is Fail, rather than allowing both to be entered independently.
Returned marked No with Search Raised If Not Returned and Case ID both left blank.ISO 9001 cl.7.1.5Make both fields mandatory the moment Returned is set to No, not optional additions the entrant can skip.
Reconciliation entries missing for busy shifts, present only for quiet ones.ISO 9001 cl.7.1.5Require one Reconciliation record per Shift value logged in Issues that day, and flag any shift with issues but no matching reconciliation.
Approved For Food Areas left unanswered for tools issued into food-contact Area values.ISO 9001 cl.7.1.5Make Approved For Food Areas required whenever Area is set to a food-contact value such as Cutting room, Boning hall or Packing.
Damaged Items Withdrawn marked Yes with no matching drop in tools available for reissue.ISO 9001 cl.7.1.5Tie Damaged Items Withdrawn to a visible reduction in the reissuable count, not a standalone declaration.
Foreign Body Risk Assessed marked Partly and left there with no Action Required raised.ISO 9001 cl.7.1.5Route Partly into Action Required automatically, the same way No does, instead of treating it as an acceptable resting state.

Case in point

Case in point: the boning knife that was one shift, then three, then gone

A boning knife was issued at the start of a shift and not returned by the end of it. The crib log showed Returned as No, but the shift was busy, the stores person clocked off, and nobody entered a search or a case reference. The knife rolled forward as an open entry into the next shift's count, then the one after that.

It surfaced eleven days later, jammed in a conveyor guard during a maintenance shutdown, by which point three further shifts of product had run past that point with an unaccounted-for blade somewhere in the building. Under this template, Search Raised If Not Returned exists precisely to stop an unreturned item aging silently — the failure wasn't the missing knife, it was the eleven days nobody escalated the No.

The template

The template, field by field

The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.

40fields
4 sections
Reference
OPS-024
Archetype
Log
Record ID
CRIB-2026-000
Scoring
Tools reconciled
Direction
High is good
Singleton
Yes
Basis
ISO 9001 cl.7.1.5
Links
Links Tool Register and Foreign Body Control
Tags
Asset, Tools
Sections
4
Fields
40
Follow up fields
4
Repeating sections
1
Links out
4
Field typesOwn ID, generated on saveCase thread and parentPick list from a registryLinked to another templateFollow up, dashed outlineScored

Header

10 fields
Text

Log ID*

Generated on save

Auto sequence. Format CRIB-2026-000.

The record's own ID. Other templates point at this value.

Single Choice

Status*

Scored

Drives who this goes to next.

  • Planned2 pts
  • In progress2 pts
  • Complete3 pts
  • Deferred0 pts
  • Open0 pts
  • Closed3 pts
  • Overdue0 pts
Date & Time

Date*

Single Choice

Shift*

DayAfternoonNight
Users

Stores Person*

Pick List

Site*

From FDN-001 Site NameFilter: Status is Active
Text

Site ID*

Linked

Format SITE-000.

Links to FDN-001 Site ID

Single Choice

Area

Optional

The area within the site.

Cutting roomBoning hallPackingChill storeFreezerPasteurisingFillingCulture roomDespatchYardWorkshopPlant roomOffices
Location

Exact Location

Optional

Drop a pin for anything hard to find.

Info

Unreturned Is A Foreign Body Risk

In a food plant a missing spanner is a product decision. Everywhere else it is a cost. Either way a signed out tool that never comes back should be noticed the same day.

Issues

Repeats15 fields
Text

Item*

Text

Item Identification Number

OptionalLinked

Links to FDN-025 Register ID

Users

Issued To*

Date & Time

Time Issued*

Date & Time

Expected Return

Optional
Text

Purpose

Optional
Single Choice

Condition At Issue*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Calibration In Date

OptionalScored
  • Pass2 pts
  • Partial1 pt
  • Fail0 pts
  • N/Aexcluded from denominator
Single Choice

Approved For Food Areas

OptionalScored
  • Yes3 pts
  • Not applicable3 pts
  • No0 pts
Single Choice

Returned*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Date & Time

Time Returned

Optional
Single Choice

Condition At Return

OptionalScored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Complete And Undamaged

OptionalScored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Search Raised If Not Returned

OptionalScoredShows if Returned equals No
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Text

Case ID

OptionalThread key

Thread key

Related records

1 field
Text

Transfer ID

OptionalLinked

Where a tool moved with an asset.

Links to OPS-023 Transfer ID

Reconciliation

14 fields
Numeric Answer

Items Issued*

Numeric Answer

Items Returned*

Scored
Numeric Answer

Items Outstanding*

Scored
Single Choice

Fully Reconciled At Shift End*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Damaged Items Withdrawn*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Foreign Body Risk Assessed*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Action Required*

Scored

Raise the action record, then enter its reference here.

  • No2 pts
  • Yes0 pts
Single Choice

Priority

OptionalScoredShows if Action Required equals Yes
  • High0 pts
  • Medium1 pt
  • Low3 pts
Text

CAPA ID

OptionalLinkedShows if Action Required equals Yes

Format CAPA-2026-00000.

Links to FDN-014 CAPA ID

Users

Action Owner

OptionalShows if Action Required equals Yes
Users

Stores*

Signature

Signature*

Users

Area Owner*

Signature

Second Signature*

OPS-024 · record IDs look like CRIB-2026-000 · Links Tool Register and Foreign Body Control

Open in Knowella

Run it with agents

From a document you fill in to a programme that runs itself

The log is easy to fill in one entry at a time; the discipline that actually matters is whether every issue gets a matching return and every shift gets a matching reconciliation.

KnowOps

Holds the tool crib log against the tool register, flags open issues with no return, and keeps shift-end reconciliation visible so a missing tool doesn't roll forward unnoticed.

KnowQuality

Watches calibration status at the point of issue and surfaces any tool issued despite a failed check, tying it back to the measuring equipment control this template exists to satisfy.

KnowComply

Tracks food-area approvals and foreign body risk assessments as certification evidence, so a gap that would concern an auditor is caught before the audit, not during it.

Ella
Ella

Coordinates stores across shifts, rolls open and overdue issues into one view, and holds every write for your approval before it touches a record.

This template lives in KnowOps — frontline execution. Shift handover, production control, daily management, worker lifecycle and improvement.

Meet KnowOps→

Glossary

Tool Crib Issue and Return definitions and key terms

Tool crib
A controlled store of tools and instruments issued to and returned by personnel, typically managed by stores rather than held permanently by any one person.
Foreign body
Any unintended item, such as a broken tool tip or blade fragment, that could enter a product and represents a physical contamination hazard in food and similar sectors.
Calibration
The check that a measuring instrument's readings are accurate against a known reference, recorded here as a condition of issue rather than a separate periodic exercise.
Reconciliation
The process of matching what was issued against what has been returned at a defined point, such as shift end, to confirm nothing is unaccounted for.
Stores
The function responsible for issuing, receiving and controlling tools and equipment, and the completing party for this log.

FAQ

Frequently asked questions about tool crib issue and return

What is the Tool Crib Issue and Return template based on?+

It's built against ISO 9001 cl.7.1.5, monitoring and measuring resources, which requires equipment used to check conformity to be suitable, maintained and traceable. ISO 9001 is the international standard for consistently meeting customer and regulatory requirements.

What sections does the template contain?+

Four sections: Header, Issues, Related records, and Reconciliation. Issues repeats for every tool handed out, so a busy shift can generate many entries against a single log, all rolled up in Reconciliation.

Who completes a tool crib issue and return entry?+

Stores, at both the point of issue and the point of return. The person the tool is issued to is named on the record but doesn't complete the log themselves — stores retains control of the check.

How does this connect to Asset Movement and Transfer?+

Where a tool travels with an asset that's being transferred, rather than being issued to a person on its own, the Transfer ID field links back to the OPS-023 record so the two aren't tracked as unrelated events.

How is a tool crib issue and return scored?+

Scoring is tools reconciled, where high is good. The scored fields cluster around condition and calibration at issue and return, and whether reconciliation, damage withdrawal and foreign body risk are closed out at shift end.

Can this template be changed?+

Yes. Every field, option, score and conditional rule is editable, and the links to the tool register and foreign body control carry over. Most teams install it as it is, run it for a cycle, then tighten which fields are mandatory.

Keep going

Related templates and programmes

Siddarth Singh

Written and reviewed by

Siddarth Singh

Founder & Chief Executive Officer, Knowella

Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.

  • Certified Safety Professional (CSP), Board of Certified Safety Professionals
  • MBA, University of Chicago Booth School of Business
  • MS and BS, The Ohio State University, Industrial and Systems Engineering
  • Six Sigma Black Belt
Verify with BCSP →

Sources and last review. Reviewed 16 August 2026 against:

  • ISO 9001:2015 cl.7.1.5 — Monitoring and measuring resources
  • ISO 9001:2015 — Quality management systems requirements
  • BRCGS Food Safety Issue 9 — foreign body detection and control
  • 21 CFR Part 117 Subpart B — Current Good Manufacturing Practice

This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.

Start in Minutes, Not Weeks

Launch a Ready-Made Template and Customize It Your Way

Every template is fully editable. Adjust fields, workflows, and branding to match your processes, then deploy to your team instantly.