The departments that perform best during external audits aren’t the ones with the most sophisticated storage systems. They’re the ones that already know what their systems produce, where the gaps are, and how to address them before anyone else starts asking questions. That outcome comes from running your own review before the external one arrives. Not a cursory walkthrough the week before an inspection, but a systematic internal audit that applies the same scrutiny an external reviewer would, run by people who know your operation well enough to find problems that an outside reviewer might miss. What follows is a practical checklist for that process, organized by storage category. It’s not a substitute for your accreditation body’s specific requirements, which you should review alongside this guide. It’s a starting framework that covers the areas where departments most consistently find problems, and where external reviewers most consistently look for them. For Law Enforcement professionals: your agency’s training officers and SOPs should guide your specific operational setup and compliance requirements. This checklist focuses on storage specifications and documentation practices to support internal review processes. Before You Start: Set the Audit Up Correctly An internal audit that produces useful results needs a few structural elements in place before anyone opens a storage room door. Assign a lead who isn’t the evidence custodian or armory supervisor being reviewed. Not because those individuals can’t be trusted, but because self-review has inherent blind spots. The person who built the current system and works within it daily is the least likely to notice what it normalizes. A supervisor from a different unit, or a peer from another department if your agency has that relationship, brings a more useful perspective. Pull your current written policies for each storage category before the physical review. The audit is checking two things simultaneously: whether your policies meet the required standard, and whether your actual practice matches your policies. Both gaps create findings. Finding them internally means you can address them on your timeline rather than an auditor’s. Document everything the audit produces, including what passed, not just what needs attention. A contemporaneous record of an internal audit that identified and addressed gaps is evidence of institutional diligence. It tells a story about a department that takes its accountability obligations seriously, which matters in any context where your storage practices come under scrutiny. Weapons Storage Audit Work through each of the following areas systematically. For each item, the question isn’t just whether the answer is yes or no, but whether you can prove it with documentation if asked. Physical security. Verify the steel gauge specification of your weapons storage units against your accreditation body’s minimum requirements. Check door frame integrity, hinge condition, and lock function on every unit. Confirm that all units are anchored to structural elements and that anchor hardware is intact. Look for any evidence of forced entry attempts, prying damage, or lock cylinder wear that might indicate tampering. Access control. Confirm that access credentials are individually assigned, not shared. Pull the list of active credentials and compare it against your current authorized personnel roster. Any credential assigned to a former employee, a reassigned officer, or anyone whose status has changed since the credential was issued is an active vulnerability. Verify that access logs are being generated automatically and that log storage hasn’t reached capacity or experienced any gaps. Inventory reconciliation. Conduct a physical count of every weapon in storage and compare it against your logged inventory. Serial numbers should match logged records. Any discrepancy between physical count and logged inventory, even one that seems explainable, should be formally documented and resolved before an external review. Unexplained discrepancies that surface during an external audit carry significantly more weight than discrepancies that were identified and resolved internally. Chain-of-custody completeness. Pull the transfer log for the past 90 days and check it for gaps. Every weapon that left storage should have a corresponding return entry. Every transfer between personnel should have documentation of both the release and the receipt. Gaps in either direction are chain-of-custody vulnerabilities. Review the full specification and documentation capabilities of DASCO law enforcement weapons storage systems as a reference for what a fully compliant system should produce against each of these audit points. Evidence Storage Audit Evidence storage carries the highest consequence for documentation failures because the records it produces go directly to court. Apply proportionally more scrutiny here than to any other storage category. Physical separation. Confirm that evidence firearms are stored in a physically separate, access-controlled space from departmental weapons. The separation needs to be documentable, meaning it needs to be enforced by the storage system itself rather than by procedure. If evidence and duty weapons share the same storage room with different cabinets, verify that the access control on evidence storage is completely independent of duty weapon access and that the logs reflect that independence. Intake documentation completeness. Pull a sample of 20 intake records from the past six months and review each for completeness: item identifier, submitting officer, receiving custodian, date and time, condition description, and case number. Any intake record missing a required field is a chain-of-custody vulnerability for that item. If a pattern of incomplete intake documentation emerges in your sample, assume it extends beyond the sample. Transfer log audit. For every active case with evidence in storage, trace the complete transfer history of each item from intake to current location. Every handoff should be documented with both a release record and a receipt record. A release record without a corresponding receipt means an item is currently unaccounted for in your documentation, even if you know physically where it is. Long-term storage review. Identify every item that has been in evidence storage for more than two years and confirm that disposition holds or case status documentation exists for each. Long-term storage items that lack current case documentation are an audit finding waiting to happen and a storage capacity problem that compounds over time. Court transfer documentation. For any item currently checked

Government procurement for storage solutions sits at the intersection of compliance requirements, budget cycles, and contracting rules that most facility and operations managers didn’t spend their careers learning. The result is procurement processes that take longer than they should, produce specifications that don’t match operational needs, or get challenged after award because the contracting approach wasn’t appropriate for the purchase. None of that is inevitable. The procurement framework for government storage purchases is complex but navigable, and the agencies that move through it efficiently have usually invested in understanding a few specific elements that make the difference between a procurement that works and one that doesn’t. This guide covers the practical elements that matter most: how GSA schedules work for storage purchases, when sole-source contracting is appropriate and when it isn’t, and the specification practices that protect your agency through the procurement process and after it. GSA Schedules: What They Actually Are and How They Work for Storage The General Services Administration Multiple Award Schedule program is the federal government’s primary vehicle for commercial product and service procurement, and it’s where most government storage purchases should start. Understanding what a GSA Schedule actually provides changes how you approach a storage procurement significantly. A GSA Schedule contract is a long-term government-wide contract between GSA and a commercial vendor that establishes pre-negotiated pricing, terms, and conditions for specific product categories. When an agency purchases from a GSA Schedule vendor, it’s buying under terms that GSA has already negotiated on behalf of the government, which means the competitive procurement requirement is satisfied by the Schedule itself rather than by a separate agency-level competition. For storage purchases, this means that an agency can identify vendors whose products appear on the applicable GSA Schedule, compare offerings among Schedule vendors, and make a purchase without conducting a full competitive solicitation, as long as the purchase meets the applicable thresholds and the product category is covered under the Schedule. The time savings compared to a full competitive procurement can be substantial, and the compliance protection of buying through a Schedule vehicle is significant. The practical limitation of Schedule purchasing for storage is that the product you need has to be available from a Schedule vendor at a price that meets your budget. Schedule pricing is pre-negotiated but not necessarily the lowest price a vendor would offer under direct negotiation, and for large or complex storage purchases, additional price negotiation with Schedule vendors is both permitted and advisable. Ordering from a GSA Schedule doesn’t mean accepting the Schedule price without discussion. Confirm that any storage vendor you’re considering is currently active on the applicable GSA Schedule before building your procurement around that vehicle. Schedule contracts expire and get renewed, and a vendor whose Schedule contract has lapsed cannot be used as a Schedule purchase even if they were previously Schedule-listed. Verify current Schedule status through GSA Advantage or directly with the vendor before committing to a procurement approach. DASCO’s government procurement and contracting information covers current contract vehicle availability and the documentation your agency needs to complete a compliant purchase through applicable contracting channels. Sole-Source Contracting: When It’s Appropriate and When It Creates Problems Sole-source contracting, meaning a contract awarded to a single vendor without competition, is one of the most frequently misused procurement tools in government purchasing. It’s appropriate in specific, well-defined circumstances. It’s inappropriate in a much larger number of circumstances where it gets used anyway, often because it’s faster than competitive procurement and the compliance risk seems manageable. The legitimate bases for sole-source contracting in a storage purchase context are narrower than most procurement officers assume. Unique capability that only one vendor possesses, meaning genuine technical capability that no other vendor can meet rather than a preference for a specific vendor’s product, is the most commonly applicable basis. Urgency that precludes competition, meaning a genuine operational emergency rather than a planning failure that created a tight timeline, is the second. Continuation of work where a competitive award would produce unreasonable cost or disruption in a specific, documentable way is the third. Sole-source justifications that don’t fit cleanly into one of these categories create procurement challenges that surface during audits, Government Accountability Office bid protests, or Inspector General reviews. A sole-source award that can’t be defended against a challenge is not just a contracting problem. It’s a potential Procurement Integrity Act issue with consequences that extend beyond the specific purchase. The agencies that use sole-source contracting appropriately for storage purchases typically have done one of two things. They’ve identified a genuine technical requirement that only one vendor can meet and documented that determination rigorously before award. Or they’ve recognized that they don’t meet the criteria for sole-source and conducted a competitive procurement even when it took longer than they wanted it to. If you’re considering a sole-source approach for a storage purchase, the question to answer honestly before proceeding is whether your justification would survive a GAO protest or an IG review. If the answer is uncertain, the appropriate path is competitive procurement, even if the competitive process takes longer. Writing Specifications That Work for Procurement and Operations Government storage procurement specifications serve two purposes simultaneously: they define what the agency needs operationally, and they create the legal framework for evaluating vendor responses and holding awarded vendors accountable. Specifications that serve the operational purpose without serving the legal purpose create procurement problems. Specifications that serve the legal purpose without accurately capturing the operational need produce compliant contracts for the wrong product. The specification failures that create the most problems in government storage procurement fall into a few consistent categories. Brand-name specifications without adequate justification. Specifying a particular vendor’s product by name without a documented justification that meets the brand-name or equal standard is a procurement compliance problem that can invalidate an award. If a specific vendor’s product genuinely meets a requirement that no other vendor’s product can meet, that determination needs to be documented before the solicitation goes out, not justified after a protest is

Most police chiefs write one or two storage RFPs in their careers. The vendors responding to those RFPs write responses to dozens every year. That experience gap matters, and it shows up in the outcomes: departments that didn’t specify what they actually needed, vendors who delivered exactly what was asked for rather than what was required, and procurement processes that looked clean on paper and produced problems in practice. This guide is written to close that gap. Not to make the procurement process more complicated, but to make it more precise in the areas where precision protects your department and more flexible in the areas where flexibility serves your interests. What an RFP for Storage Is Actually Doing An RFP for weapons and evidence storage is doing two things simultaneously, and keeping both in mind changes how you write it. First, it’s defining what you need. The specification sections of your RFP translate your operational and compliance requirements into technical language that vendors can respond to accurately. Vague specifications produce vague responses, and vague responses make vendor comparison genuinely difficult. Second, it’s creating a legal record. The RFP, the vendor responses, and the contract that follows collectively define what your department was promised, what it paid for, and what standard the delivered system will be evaluated against. A well-written RFP protects you in vendor disputes, in warranty claims, and in any regulatory or legal context where the adequacy of your storage system is questioned. Both functions require specificity, and the sections below cover where that specificity matters most. Defining the Scope: Be More Specific Than You Think You Need to Be The scope section of a storage RFP is where most procurement processes go wrong first. Departments describe what they want in general terms, vendors interpret those terms according to what they prefer to sell, and the gap between expectation and delivery emerges at installation. A well-defined scope for a weapons and evidence storage RFP should specify: Storage categories and volumes. List every category of item requiring storage: duty firearms by type and quantity, long guns, less-lethal weapons, evidence firearms, evidence ammunition, departmental ammunition by caliber and approximate volume. Give actual numbers, not ranges. Ranges invite vendors to spec toward the lower end. Facility parameters. Wall dimensions, ceiling height, door clearances, floor load ratings, power availability, and network connectivity in the intended installation space. A vendor who specs a system without knowing your facility constraints is speccing for a facility they’re imagining, not the one you have. Access requirements. How many individuals require access, at what authorization levels, across how many shifts. Whether access control needs to integrate with existing ID card infrastructure or operate on a standalone credential system. Whether remote access management is required. Audit and reporting requirements. What records the system needs to generate, in what format, with what retention period, and whether integration with existing records management software is required. This section is frequently omitted from storage RFPs and frequently becomes the source of post-installation disputes. Technical Specifications That Actually Protect You The technical specification section is where your RFP either holds vendors to a standard or gives them room to interpret their way to a lower-cost solution. Every specification you leave vague is an opportunity for a vendor to substitute a cheaper component that technically meets the language of your requirement while missing its intent. Specifications worth stating explicitly: Steel gauge minimums, stated separately for body, door panel, and door frame. A minimum of 14 gauge across all structural components for weapons storage, 12 gauge for evidence storage, is a reasonable baseline. Stating this separately for each component prevents a vendor from meeting the body specification with heavy gauge while using lighter gauge on the frame where prying attacks are most likely to succeed. Locking mechanism type and rating. Specify electronic locking with multi-point engagement, UL listed lock cylinders, and anti-drill and anti-pick provisions. If your accreditation body specifies a minimum lock rating, reference it directly. Hinge design. Specify concealed or anti-removal hinges. This single specification eliminates a common forced entry vulnerability that standard lockers share. Anchor provisions. Specify that the system must include structural anchor provisions suitable for the floor and wall construction of your facility, with anchor hardware concealed or internal to the unit. Access control specifics. Individual credential assignment, automatic timestamped access logging, remote credential revocation capability, and local log storage that persists through power interruption. Each of these should be stated as a requirement, not a preference. Environmental specifications where applicable. For ammunition storage, specify humidity and temperature tolerance ranges if your storage environment has known climate variability. Compliance Language That Creates Legal Protection The compliance section of your RFP connects your technical specifications to the regulatory and accreditation standards your department operates under. This connection matters legally because it establishes that your procurement was designed to meet a defined standard, not just to acquire storage at a competitive price. Reference your applicable accreditation body’s physical security standards for weapons storage directly, by document name and version. Reference any state regulations governing evidence storage and chain-of-custody documentation. If your department operates under a consent decree or has received prior findings related to evidence management, reference those requirements specifically. Require vendors to certify in their response that the proposed system meets each referenced standard, with documentation. A vendor who can’t provide that certification against a specific standard you’ve referenced is telling you something important about their product before you’ve committed to anything. Include a requirement that the vendor identify any aspect of your specification that their proposed system does not fully meet, with a description of what they are proposing in its place. This exception disclosure requirement prevents vendors from submitting responses that appear compliant while containing silent substitutions. It also creates a clear record if a substituted component later becomes the source of a compliance finding. Explore how DASCO approaches government and law enforcement procurement contracts for a practical reference on what compliant vendor documentation and certification looks like in