Operating in the Risk: Lessons From Managing a High-Risk Supply Chain During COVID-19

A Weedman & Co. Case Study in Supply Chain Risk, Procurement, Compliance, Operations & Crisis Management

 When the COVID-19 pandemic struck, the global supply chain was thrown into chaos. Businesses scrambled for critical supplies, counterfeit products flooded the market, and governments tightened regulations overnight. Amidst this uncertainty, I launched a high-risk supply company specializing in industrial and medical supplies, knowing full well the challenges that lay ahead.


  What became apparent very quickly was that operating in this environment was not simply a matter of finding products and selling them. It was an exercise in risk management under extreme uncertainty. Every transaction involved multiple interconnected risks. The manufacturer had to be legitimate. The product had to actually exist. The specifications had to match what was being represented. Certifications had to be legitimate and applicable to the product being sold. The buyer had to be capable of completing the transaction. The financial structure had to protect both sides. The logistics provider had to actually be able to move the product. Customs documentation had to be correct. And the entire process had to remain compliant as rules and market conditions changed.


One weak link could affect everything downstream.


  That experience continues to influence how I approach risk and operations today through Weedman & Co. Risk is rarely isolated to one department. A problem with a vendor can become a financial problem. A financial problem can become a contractual problem. A logistics problem can become a customer-service problem. A compliance failure can become a legal problem. Understanding those connections is where real operational risk management begins.



24-Hour Workdays & Constant Movement


  The early days of operations were relentless. Sleep became a luxury as I worked around the clock, vetting manufacturers, inspecting products, and coordinating shipments. Travel was nonstop, moving between warehouses, shipping hubs, and compliance meetings, ensuring every product met strict safety standards. I was on calls internationally 24/7, communicating with manufacturers, buyers, logistics providers, and other parties involved in the transactions. With borders closing and supply chains strained, sourcing legitimate goods became a logistical nightmare. I was on FaceTime with manufacturers overseas at all hours, scrutinizing production processes and verifying certifications. A single misstep, whether in quality control, compliance, or vendor trust, could cost six figures in losses.


  The reality of this type of operation is that there is no clean separation between departments. Procurement, operations, logistics, finance, compliance, quality control, vendor management, and customer relationships all overlap. A supplier could have the product but not the documentation. A logistics provider could have the capacity but not the correct routing. A customer could have an urgent need but not understand the lead time or regulatory requirements involved. A shipment could be ready to leave a facility but still be unable to move because one document, classification, approval, or government restriction had changed. That meant decisions had to be made constantly and often with incomplete information.


  The work also did not stop once a purchase order was issued. There was still the question of who was physically handling the product, where it was being stored, how it was being transported, who was responsible for it while in transit, what happened if it was delayed, and what would happen if the shipment did not meet specifications when it arrived. That is one of the realities of operating a high-risk supply operation: the transaction is only one part of the risk. The entire chain has to be considered.



Investigating Manufacturers & Preventing Fraud


   The pandemic opened the floodgates for scams, counterfeit PPE, and substandard medical supplies. Many so-called suppliers were nothing more than shell companies looking to exploit the crisis. Every manufacturer required deep due diligence. Where traditional background checks weren't available or sufficient, factory inspections, document verification, independent research, and other forms of legal and operational vetting took place.


   The challenge was that traditional due-diligence methods were often difficult to use during a global crisis. Travel restrictions meant that simply getting on a plane and visiting a facility was not always an option. Information could be incomplete, difficult to independently verify, or supplied directly by the party attempting to win the business. That required looking beyond the sales presentation. A supplier might provide a professional website, corporate registration, photographs, certifications, product specifications, references, and impressive production numbers. None of those things, individually, proved that the supplier could actually perform.


The question was always: Can the information being provided be independently verified?


   Some red flags were obvious, like missing ISO certifications or manipulated FDA registrations. Others required deeper investigation, reviewing production capacity, verifying past performance, and even traveling to or hiring local agents to inspect facilities in person. The risk of fraudulent goods wasn’t just financial; it was a matter of life and death in healthcare settings.


  Due diligence also meant looking at the people and organizations behind the transaction. Who actually owned the company? How long had it been operating? Where was the manufacturing actually taking place? Was the company the manufacturer, a broker, a trading company, or simply another intermediary? Could production volumes realistically support the quantities being promised? Were certifications applicable to the exact product being offered? Did the company have a history of fulfilling large orders? Could the shipping documents, banking information, corporate registrations, and product documentation be reconciled? These questions matter because fraud rarely presents itself as fraud. It often presents itself as an opportunity that appears too good to ignore.


   That is why urgency itself became a risk factor. The more urgent the need became, the more important it was to maintain the discipline to verify information rather than allowing urgency to eliminate the normal safeguards.



The Difference Between a Supplier and a Supply Chain


  One of the most important lessons from that experience was understanding the difference between having a supplier and actually having a supply chain. A supplier may tell you they can provide 500,000 units. That does not necessarily mean 500,000 acceptable units can be manufactured, inspected, packaged, financed, released, transported, cleared through customs, delivered, received, and ultimately used by the customer.


Each step introduces another potential failure point.


  The manufacturer is only one component. Then there are quality-control personnel, packaging, warehousing, freight forwarders, customs brokers, airlines or ocean carriers, trucking companies, receiving facilities, financial institutions, insurers, regulatory agencies, and the final customer.


Each participant introduces its own operational risk.


  This is why supply-chain management requires more than procurement experience. It requires an understanding of how the entire operation interacts. A company can have an excellent supplier and still have a weak supply chain if transportation, documentation, financing, warehousing, quality control, or contingency planning are not properly addressed.



Managing Six-Figure Transactions & Logistics


  With millions of dollars in medical supplies moving through unstable supply chains, financial risk was high. Every transaction required airtight contracts, escrow services, and layered compliance checks. We coordinated airfreight shipments under extreme demand spikes, securing dedicated trucking vendors to prevent supply chain bottlenecks. At that level, the financial side of the transaction becomes an operational risk issue. When significant money is committed before the product is delivered, questions immediately arise. Who holds the funds? When are funds released? What constitutes acceptable performance? What happens if the supplier misses the production deadline? What happens if the product fails inspection? Who carries the loss while goods are in transit? What happens if customs refuses entry? What happens if the customer changes the order? What happens if government restrictions suddenly affect the transaction? Those questions have to be addressed before there is a problem, not after.


 International regulations changed daily, forcing us to pivot constantly. Some shipments were seized at customs due to misclassification, while others faced delays due to emergency export bans. Keeping up with shifting laws across multiple jurisdictions was a full-time job in itself. Logistics also became a lesson in contingency planning. WEEDMAN & CO. created their “import & export” identity number to solve this issue. A shipment could be delayed at the manufacturer, delayed at an airport, delayed by a customs issue, delayed by a trucking shortage, or delayed because the receiving facility could not accept the shipment. A supply chain can therefore fail even when every individual participant believes they are doing their job. That is why contingency planning cannot simply mean having another vendor's phone number. It means understanding what happens next when the original plan fails.



Operations Behind the Transaction


  There is a part of high-risk procurement that is rarely visible to the customer. The customer sees the product. The operator sees everything that has to happen before the product reaches them. It includes vendor onboarding, documentation, purchase orders, contracts, payment structures, inspection requirements, transportation scheduling, warehouse coordination, inventory tracking, communications, customer updates, quality assurance, insurance considerations, invoicing, accounts receivable, accounts payable, and exception management. It also requires managing people.


  Vendors have employees. Warehouses have employees. Trucking companies have drivers. Brokers have staff. Customers have procurement teams and executives. Government agencies and regulatory bodies have their own processes. When something goes wrong, someone has to identify the problem, determine who owns the problem, communicate it to the appropriate parties, and determine the next action. That is operations. It is not glamorous. It is often repetitive, exhausting, and extremely detail-oriented. But those details are where significant losses can either be prevented or created.


  The same principle applies to businesses outside of supply chain operations. A company may have excellent people and excellent products but still experience significant exposure because the processes connecting those pieces were never properly evaluated.



Compliance, Law & Risk in High-Stakes Procurement


  Navigating compliance in this space meant adhering to a maze of international laws and regulatory requirements. FDA and NIOSH requirements were critical because every mask, glove, and medical device had to meet applicable U.S. safety standards. Non-compliance could result in significant financial and legal consequences, while in healthcare environments the consequences could extend beyond the business itself. Customs and trade laws created another layer of complexity. Importing high-demand goods required attention to the Defense Production Act, ITAR, emergency government orders, export restrictions, customs classifications, documentation, and other requirements depending on the product and transaction. Failure to document sourcing properly could lead to shipment seizures or significant delays.


  Anti-fraud measures were equally important. With counterfeit PPE rampant, rigorous verification protocols, batch testing, supplier audits, and contractual protections became part of the procurement process. Financial and contractual risk added another layer. Handling six-figure deals required legal safeguards, performance bonds, letters of credit, escrow arrangements, and multi-layered due diligence. A single bad contract could wipe out months of work. But compliance was not something that could simply be checked off a list. The environment changed too quickly. A compliant transaction one week could require additional review the next. A product that appeared acceptable based on one document could require additional verification when the intended use, manufacturer, classification, or destination changed. This is where the difference between compliance and risk management becomes important. Compliance asks whether the applicable requirement is being met. Risk management asks what could happen if something goes wrong, how significant that consequence could be, and what can reasonably be done before the event occurs.


You need both.



Vendor Management Is Risk Management


 Another lesson that carried forward from this experience is that vendor management is not simply administrative. Every vendor becomes part of your operation. If a trucking company fails, your customer may not care that the problem technically belonged to the trucking company. If a manufacturer provides defective product, the customer may still look to you for an answer. If a subcontractor fails to meet an obligation, the reputation of the company that hired them can still be affected. That means vendors have to be evaluated based on more than price. Capacity, reliability, documentation, responsiveness, insurance, geographic coverage, contingency capability, history, and operational maturity all matter.


  A low-cost vendor that creates repeated disruptions may ultimately cost more than a higher-cost vendor that performs consistently. This principle extends far beyond supply chains. It applies to security contractors, facilities providers, construction partners, technology vendors, transportation companies, and virtually any business that depends on outside organizations to deliver part of its operation. When a business outsources a function, it does not necessarily outsource the risk associated with that function.



The Human Side of High-Risk Operations


  Technology and documentation are important, but people remain a major part of operational risk. Someone has to recognize when something does not look right. Someone has to ask the second question. Someone has to challenge the information being presented. Someone has to understand when an operational problem is actually a larger business risk. During the pandemic, there were countless moments when the available information was incomplete or changing rapidly. Decisions could not always wait for perfect information. That meant experience mattered. The ability to assess what was known, identify what was unknown, understand the potential consequences, and determine what could be done to reduce exposure became just as important as the information itself. This is one reason I have never viewed risk management as simply collecting data. Data is an input. Experience, context, judgment, probability, impact, and the ability to interpret what the information actually means to the operation are equally important. Good risk management is not about having the most information. It is about understanding the information you have and knowing what it means to the specific operation at that specific moment.



Building Contingency Into the Operation


  A resilient operation cannot depend entirely on one manufacturer, one logistics provider, one employee, one customer, one transportation route, or one source of information. During COVID-19, redundancy became extremely important. Alternative suppliers had to be identified. Alternative transportation options had to be considered. Alternative routes had to be available. Communication channels had to remain open. Documentation had to be organized. Critical relationships had to be maintained. And the organization had to be able to make decisions quickly when the original plan stopped working. This is the practical side of business continuity.


  A continuity plan is only useful if the organization can actually execute it when conditions deteriorate. Having a document sitting in a binder does not create resilience. Knowing who makes the decision, who has authority to act, which vendors can be activated, where resources are available, how communication will occur, and how the business will continue operating is what turns a plan into an operational capability.



Lessons From the Frontline of Crisis Supply Chains


  Launching a high-risk supply business in the middle of a global emergency was a crash course in risk management, adaptability, and high-stakes decision-making. It reinforced the importance of vetting every link in the supply chain, from raw materials to final delivery. It reinforced the importance of understanding international trade laws and compliance pitfalls, building relationships with reliable manufacturers and logistics partners, and never trusting unverified suppliers simply because the demand is urgent.


   It also reinforced the importance of understanding the entire operation rather than focusing only on the transaction in front of you. You have to understand where risk exists, where it can transfer, and where it remains with your organization regardless of what a contract says. You have to understand the vendors and subcontractors supporting the operation. You have to build contingency options before they are needed. You have to understand the financial consequences of operational decisions. You have to document decisions, communications, inspections, contracts, and exceptions.


  Most importantly, you have to recognize that compliance does not eliminate risk. An organization can comply with a requirement and still experience an operational failure. That is why risk management has to look beyond the checklist. Despite the challenges, the work was rewarding. We helped businesses, hospitals, and frontline workers secure the supplies they desperately needed while navigating one of the most volatile markets in modern history. The lessons learned during this time continue to shape how I approach risk, compliance, and business continuity today.



  At Weedman & Co., we look at risk through an operational lens because risk does not exist in a vacuum. A security issue can affect operations. An operational issue can affect finances. A vendor issue can affect compliance. A compliance issue can affect contracts. A supply-chain disruption can affect customers. A business-continuity issue can affect every one of those areas at the same time. That is why our approach to risk extends beyond identifying individual hazards or producing another checklist. We look at how the pieces interact. That experience is a significant part of how Weedman & Co. approaches enterprise risk management today.







About The Author:


Joseph Weedman, B.A., FCP, SRMP-C is the Founder & CEO of Weedman & Co., with more than two decades of hands-on experience building and operating businesses across security, protective services, investigations, emergency response, and risk management. He holds a Bachelor of Arts in Security Management, is a Florida Certified CPTED Practitioner (FCP), and holds the SRMP-C professional designation. His background spans physical security, information security, school and campus security, industrial espionage, risk management, business operations, and crisis response. As an operator, business owner, and risk professional, Mr. Weedman brings practical field experience to Enterprise Risk Management (ERM), ESRM, operational risk, resilience, compliance, supply-chain risk, and business continuity. His work today focuses on connecting security, operations, compliance, resilience, and enterprise risk management to help organizations better understand and manage the risks that affect their business.

Understanding Risk Assessment and Risk Analysis

By site-qCMZqg • October 4, 2026
Risk assessment and risk analysis are terms often used interchangeably, but they are not the same thing. Both are fundamental to effective risk management, yet each serves a different purpose. A risk assessment establishes an understanding of an organization's exposure. Risk analysis goes deeper, examining why that exposure exists, what could cause an event, how likely it may be, what the consequences could be, and how existing safeguards influence the outcome. The distinction is important because collecting information about risk is not the same as understanding risk. Risk Assessment: Identifying the Exposure A risk assessment begins with understanding the environment being evaluated. What are the organization's critical assets? What operations are essential? Who has access? What threats exist? What vulnerabilities are present? What safeguards are already in place? What dependencies could create additional exposure? The purpose is to establish a meaningful picture of the organization's risk environment and identify conditions that require attention. A professional risk assessment should do more than create a list of deficiencies. A missing camera, inadequate lighting, unsecured door, outdated policy, single-source vendor, or lack of emergency planning may all be observations, but an observation alone does not establish the significance of the risk. The assessment establishes what is present, what is absent, and what conditions deserve further examination. Risk Analysis: Understanding What the Exposure Means Risk analysis takes the identified exposures and examines them more deeply. Why does the vulnerability exist? What conditions make an event more or less likely? What would happen if the event occurred? How quickly would the organization recognize it? What would happen after detection? What resources would be required to respond? What operations could be interrupted? What dependencies could increase the consequences? This is where professional judgment becomes particularly important. Risk analysis is not simply assigning a number to a spreadsheet. It is interpreting the available information and understanding how the individual pieces interact. A useful distinction is simple: risk assessment identifies and evaluates the exposure; risk analysis interprets the exposure and examines its potential consequences. A Finding Is Not the Same as a Risk Consider a parking area with inadequate lighting. The assessment may identify the lighting deficiency. The analysis asks what that deficiency actually means. Is the area used after dark? Who uses it? Does the lack of lighting create concealment? Does it interfere with surveillance? Is there a history of incidents? Are employees required to walk through the area? Are there other security measures that compensate for the deficiency? Does the condition create a meaningful opportunity for crime, injury, or another loss? The lighting condition is the observation. Understanding how that condition affects the organization is the analysis. This distinction is one of the reasons experienced risk professionals cannot rely entirely on checklists. A checklist can identify conditions. It cannot always determine their significance. Data Does Not Make the Decision Modern risk professionals have access to more information than ever before. Crime statistics, incident histories, insurance losses, environmental information, operational metrics, surveillance records, financial information, and other data can all contribute to a risk assessment. But data should inform professional judgment, not replace it. Data can be incomplete, outdated, improperly collected, manipulated, misunderstood, or disconnected from the specific environment being evaluated. A crime statistic for a geographic area does not automatically determine the risk at a particular property. A low number of historical incidents does not necessarily mean the environment has low exposure. Likewise, a high incident rate does not automatically tell a professional what intervention will be most effective. The professional's responsibility is to determine what the information actually means in context. This is where risk assessment becomes more than data collection. The ability to see the environment, understand the information, recognize its limitations, and interpret it against probability, impact, vulnerability, and consequence is what turns information into usable risk intelligence. Probability, Impact, and Vulnerability Probability and impact are two of the most commonly discussed components of risk, but they should not be viewed in isolation. A relatively unlikely event can still deserve significant attention if the consequences would be severe. Conversely, a frequent event may require a different response when its consequences are limited and manageable. Vulnerability adds another dimension. Two organizations can face the same threat but have completely different levels of risk because their environments, operations, safeguards, personnel, resources, and response capabilities are different. A facility with strong access management, effective surveillance, trained personnel, appropriate lighting, established emergency procedures, and reliable communications may be substantially more resilient than a similar facility without those capabilities. The question therefore should not simply be, "What is the threat?" It should also be, "How vulnerable are we to it, and what happens if our existing safeguards fail?" Existing Security Measures Must Be Evaluated for Function One of the most common weaknesses in risk assessments is treating the presence of a security measure as proof that the risk has been addressed. A camera is not automatically effective security because it exists. An alarm is not automatically protective because it is installed. A policy is not automatically effective because it is written. A security officer does not automatically reduce risk simply because someone is standing at a post. The professional must examine how the measure actually functions. Does the camera provide meaningful coverage? Can footage be retrieved when needed? Is the alarm monitored? Who responds when it activates? Is the policy understood and followed? Does the security officer have the training, authority, equipment, and procedures necessary to perform the assigned function? The difference between security presence and security performance is an important part of professional risk analysis. Quantitative and Qualitative Risk Analysis Quantitative analysis uses numerical information to help evaluate risk. Financial loss estimates, incident frequency, downtime, replacement costs, probability calculations, and other measurable variables can be useful when reliable information exists. More sophisticated techniques can also be used when the risk and available data justify them. However, numerical precision should not be confused with certainty. A calculation can produce a very precise number while still being based on uncertain assumptions. Qualitative analysis relies more heavily on professional judgment, observations, interviews, experience, scenario analysis, and environmental context. This can be particularly valuable when reliable numerical data is limited or when the risk involves complex human, operational, or environmental factors that cannot easily be reduced to a single number. Neither approach should automatically be considered superior. The appropriate approach depends on the risk, the quality of the available information, and the decision that needs to be made. Risk Matrices Are Tools, Not Answers Risk matrices can be useful for organizing information and communicating priorities. They provide a common framework for considering probability and impact and can help organizations determine where additional attention may be warranted. But the matrix itself does not perform the analysis. A risk labeled "high," "medium," or "low" should have reasoning behind that classification. Two organizations may reasonably classify the same condition differently because their assets, operations, vulnerabilities, consequences, and risk tolerances are different. The value is not the color on the matrix. The value is the professional reasoning that produced it. Residual Risk Is Part of the Decision Risk rarely disappears completely. Even after safeguards are implemented, some level of exposure usually remains. That remaining exposure is residual risk. A mature risk assessment should therefore identify not only the original exposure, but also what happens after mitigation is applied. What has been reduced? What remains? What has changed? What risk is the organization still accepting? This is especially important for executives and decision-makers. They need to understand not only what has been corrected, but what remains and why the organization has decided to live with it. Risk management is not necessarily about eliminating every possible risk. In many environments, that would be impossible, operationally impractical, or financially unreasonable. The objective is to make informed decisions about the risks an organization chooses to address, transfer, mitigate, or retain. From Assessment to Risk Management The ultimate purpose of risk assessment and risk analysis is not to produce a report. It is to improve decision-making. The findings should help determine whether additional resources are justified, whether an existing safeguard should be changed, whether an operation should be redesigned, whether a vulnerability should be accepted, whether additional protection is warranted, or whether a portion of the financial exposure should be transferred through insurance or another mechanism. This is where assessment and analysis become part of a larger enterprise risk-management process. The assessment establishes the environment. The analysis provides meaning and context. Risk treatment determines what should be done. Monitoring and reassessment determine whether those decisions continue to be appropriate as conditions change. The Weedman & Co. Perspective A strong assessment identifies the environment and the exposure. A strong analysis explains why the exposure matters, what conditions contribute to it, how existing safeguards affect it, what the potential consequences are, and what options are available. The professional's job is not simply to collect data and assign a score. It is to see the environment, understand the information, interpret it within the context of the organization, evaluate probability and impact, understand vulnerability, and determine what the risk actually means. That requires experience, critical thinking, technical knowledge, and professional judgment. Risk management is not about predicting the future with perfect accuracy. It is about making better decisions with the information available while recognizing what is known, what is uncertain, and what could happen if the assumptions are wrong. About The Author: Joseph Weedman, B.A., FCP, SRMP-C is the Founder & CEO of Weedman & Co., with more than two decades of hands-on experience building and operating businesses across security, protective services, investigations, emergency response, and risk management. He holds a Bachelor of Arts in Security Management, is a Florida Certified CPTED Practitioner (FCP), and holds the SRMP-C professional designation. His background spans physical security, information security, school and campus security, industrial espionage, risk management, business operations, and crisis response. As an operator, business owner, and risk professional, Mr. Weedman brings practical field experience to Enterprise Risk Management (ERM), ESRM, operational risk, resilience, compliance, supply-chain risk, and business continuity. His work today focuses on connecting security, operations, compliance, resilience, and enterprise risk management to help organizations better understand and manage the risks that affect their business.

The PACT Model: A New Era of Crime Prevention Through Integrated Risk Analysis

By site-qCMZqg • July 10, 2024
Weedman & Co.’s Proactive Analysis for Crime and Threats (P.A.C.T)

Why a Thorough CPTED Assessment Matters Under Florida Statute 768.0706

By site-qCMZqg • June 10, 2024
Florida Statute 768.0706 changed the conversation surrounding security assessments for qualifying multifamily residential properties. The statute establishes a presumption against liability in connection with certain criminal acts committed by third parties when the owner or principal operator substantially implements specified security measures and satisfies the statute's other requirements. One of those requirements is particularly important to the security profession: the property must have a Crime Prevention Through Environmental Design, or CPTED, assessment that is no more than three years old and that is performed by a law enforcement agency or a Florida CPTED Practitioner designated by the Florida Crime Prevention Training Institute of the Department of Legal Affairs. The owner or principal operator must also remain in substantial compliance with that assessment. That distinction matters because an assessment is not simply another document that gets placed in a property management file. When security documentation may later become relevant to a liability claim, the quality of the assessment, the qualifications of the person conducting it, the conditions documented during the assessment, and what the property does with the findings all become important. A security assessment should not merely state that a property has cameras, lighting, locks, gates, or access controls. It should establish what was actually observed, what was evaluated, what conditions existed at the time of the assessment, what deficiencies were identified, and what corrective actions may be necessary. The difference between checking a box and conducting a defensible assessment is substantial. Florida's statute is also more specific than the general concept of conducting a "security assessment." Section 768.0706 applies to a defined category of multifamily residential property: a residential building or group of residential buildings such as apartments, townhouses, or condominiums consisting of at least five dwelling units on a particular parcel. The statute then identifies specific security measures, including entry and exit camera systems that record and maintain retrievable footage for at least 30 days, specified parking-lot lighting, lighting in walkways and common areas, at least a one-inch deadbolt on each dwelling-unit door, locking devices on specified windows and doors, locked gates with key or fob access around pool areas, and peepholes or door viewers where applicable. The important lesson for security professionals is that the statute should not be treated as a checklist that automatically creates protection once someone signs an assessment. The statutory language uses the term “substantially implements,” and the owner or principal operator carries the burden of demonstrating substantial implementation of the specified security measures. The assessment is therefore part of a larger compliance picture. The professional needs to understand what the statute requires, what the property actually has, whether those measures are functioning as intended, whether the physical environment supports the intended security outcome, and whether the property remains substantially compliant over time. This is where CPTED becomes particularly important. CPTED is not simply an evaluation of whether a property has enough lights and cameras. The broader purpose of CPTED is to examine how the physical environment influences behavior, visibility, access, territorial definition, activity, and opportunity. A property can technically possess the required security devices while still presenting environmental conditions that create unnecessary opportunities for crime. A camera may be installed but positioned poorly. A light fixture may be operational but fail to illuminate the area where visibility is actually needed. Landscaping may obscure sightlines. A gate may exist but remain routinely unsecured. An access-control system may be installed but undermined by operational practices. A security assessment should therefore examine the relationship between the security measure and the environment in which that measure is expected to function. This is one of the biggest differences between a professional CPTED assessment and a basic property walkthrough. A walkthrough may identify what is present. A meaningful assessment asks whether what is present is actually accomplishing its intended purpose. That requires observation, verification, documentation, and professional judgment. It also requires the assessor to understand that security conditions are not static. Properties change. Tenants change. Employees change. Landscaping grows. Lighting fails. Cameras are repositioned. Gates are damaged. Access procedures evolve. Construction alters sightlines. Parking patterns change. New amenities are added. A property that was appropriately assessed three years ago may not present the same security environment today. The three-year assessment requirement therefore should not be misunderstood as meaning that a property only needs to think about security once every three years. The statute establishes that the CPTED assessment must be no more than three years old, while also requiring the owner or principal operator to remain in substantial compliance with the assessment. That creates an ongoing responsibility rather than a one-time paperwork exercise. A property manager who receives an assessment identifying a deficiency cannot reasonably treat the assessment as complete simply because the document has been filed. The more important question becomes what happened after the assessment. Was the deficiency corrected? Was the correction documented? Did the physical condition change? Did the corrective action actually resolve the identified issue? Documentation becomes particularly important here. A defensible assessment should allow another professional to understand what was examined and what was observed without relying entirely on the assessor's memory. Photographs, measurements where appropriate, descriptions of physical conditions, identification of access points, observations regarding lighting and visibility, documentation of security equipment, and explanations of identified deficiencies can all contribute to a stronger record. Documentation should describe the condition that actually existed rather than simply repeating what a property manager says should exist. There is a major difference between writing "security cameras are installed" and documenting where the cameras are located, what areas they cover, whether they are operational, whether footage is retrievable, and whether their placement supports the intended security function. This is particularly relevant to cameras because the statutory requirement is not merely the presence of a camera. For the specified entry and exit camera system, the statute addresses recording and maintaining retrievable footage for at least 30 days to assist in offender identification and apprehension. A camera that is physically mounted to a building but is not recording, cannot retrieve footage, does not cover the relevant entry or exit, or does not retain footage for the required period raises a very different compliance question than a properly functioning system. Lighting provides another useful example. Security professionals should be careful not to treat the existence of a light fixture as equivalent to adequate lighting. Section 768.0706 establishes a specific lighting requirement for parking lots and also addresses lighting in walkways, laundry rooms, common areas, and porches. A professional assessment should therefore distinguish between the presence of lighting equipment and the actual lighting condition of the environment. Dark areas, obstructed fixtures, failed lamps, poorly positioned lighting, or environmental conditions that create shadows can change the security characteristics of a property even when the property technically has lighting installed. The same principle applies to doors, windows, gates, and other access points. Security is not established merely because a lock exists. The assessor should consider whether the required locking device exists, whether it is functioning, whether the door or window can actually be secured, whether the access point is being routinely defeated by operational practices, and whether the physical environment creates another path around the intended security measure. This is where experienced assessment becomes more valuable than a simple inventory. The objective is not merely to identify security equipment. It is to understand whether the security architecture works as intended. The statute also addresses employee training. By January 1, 2025, qualifying owners or principal operators were required to provide proper crime-deterrence and safety training to current employees, and employees hired after that date must receive the training within 60 days of hire. The statute defines that training in relation to the security principles, devices, measures, and standards identified in the statute and requires the training to be reviewed at least every three years and updated as necessary. The owner or operator may request that the law enforcement agency or CPTED Practitioner conducting the assessment review the training curriculum. That provision reinforces another important security principle: technology and physical measures are only part of the security system. Employees interact with the environment every day. They open and close gates, issue credentials, observe suspicious behavior, receive visitors, respond to alarms, report maintenance problems, and make decisions that can either support or undermine the security design. A property can invest heavily in physical security and still create vulnerabilities through poor employee practices. Training therefore should not be treated as an administrative requirement disconnected from the physical assessment. The people operating the property are part of the security environment. From a Weedman & Co. perspective, this is where the assessment needs to move beyond compliance and into risk management. The question should not simply be, "Do we have the required device?" The better question is, "What risk is this measure intended to address, and is it functioning in the environment in which it was installed?" That distinction is important because security is rarely effective when it is designed around individual products instead of the relationship between the threat, the environment, the asset, the people, and the consequences of failure. A professional CPTED assessment should therefore identify the conditions that influence opportunity. Where are people expected to walk? Where are vehicles entering and leaving? Where are the blind spots? Where do residents gather? Where can someone approach a building without being observed? Which doors are routinely used? Which gates are frequently left open? Where does landscaping obstruct visibility? Where are lighting deficiencies located? Where does pedestrian movement intersect with vehicle movement? Where does normal resident behavior create predictable patterns? These questions help transform a security assessment from an equipment inventory into an analysis of the environment. This is also why the qualifications of the assessor matter. Section 768.0706 specifically identifies who may perform the CPTED assessment for purposes of the statute: a law enforcement agency or a Florida CPTED Practitioner designated by the Florida Crime Prevention Training Institute of the Department of Legal Affairs. The statute does not simply say that any security consultant may conduct the required assessment. For a property seeking to rely on the statutory presumption, understanding the statutory qualification requirement is essential. The legal significance should also be described accurately. Section 768.0706 does not create blanket immunity for multifamily properties. It establishes a presumption against liability when the statutory requirements are met, and the owner or principal operator bears the burden of demonstrating substantial implementation of the specified security measures. The statute also expressly states that it does not establish a private cause of action. Security professionals should therefore avoid promising property owners that an assessment will "prevent a lawsuit" or "eliminate liability." A professional assessment is not a legal guarantee. What it can do is provide documented evidence of the property's security condition and its efforts toward substantial compliance with the statutory framework. That distinction is especially important when attorneys become involved. In litigation, the question may not simply be whether an assessment exists. Questions can arise concerning when it was performed, who performed it, what was actually inspected, what conditions existed, whether the required security measures were implemented, whether deficiencies were identified, whether corrective actions were taken, and whether the property remained substantially compliant. The assessment therefore becomes part of a larger evidentiary record. The more accurately that record reflects the physical property and the actions taken by management, the more useful it can become to the organization and its legal and insurance professionals. This is where the concept of an Underwriting Defense Package or risk-engineering record can become valuable from an enterprise risk perspective. A property owner should not have to reconstruct its security history after an incident occurs. There should already be documentation showing what was assessed, what was found, what was corrected, what remained outstanding, who was responsible for corrective action, and when the condition was revisited. Security documentation becomes far more useful when it demonstrates a continuing process rather than a single inspection date. The same information can have value beyond litigation. Insurance professionals, risk managers, property managers, ownership groups, and corporate decision-makers increasingly need a better understanding of the conditions underlying a property's risk. A professional assessment can provide a common factual foundation for those conversations. It can identify conditions that require investment, distinguish operational deficiencies from physical deficiencies, and help management prioritize corrective action according to risk rather than simply reacting to whatever problem receives the most attention that week. The most important lesson is that a CPTED assessment should not be treated as a compliance document that is completed, signed, filed, and forgotten. It should be treated as a snapshot of the property's security environment and the beginning of a continuing process of verification and improvement. The assessment establishes what was observed. Management's actions afterward demonstrate what the organization did with that information. When those two pieces remain connected, the assessment becomes much more meaningful. Florida Statute 768.0706 gives qualifying multifamily property owners and operators a specific statutory framework for establishing a presumption against liability when the required security measures and assessment requirements are substantially implemented. But the strength of that position depends on more than possessing a document with "CPTED Assessment" written across the top. It depends on whether the property actually implements the applicable security measures, whether the assessment accurately reflects the property, whether deficiencies are addressed, and whether the organization can demonstrate what it did with the information it received. For security professionals, that should be the larger takeaway. An assessment is not valuable because it says a property is secure. It is valuable because it documents what was actually examined, identifies what was found, explains why it matters, and creates a defensible record of what should happen next. The professional's job is not to make a property appear secure on paper. It is to help the owner understand the actual security environment and make informed decisions about risk. At Weedman & Co., we believe that is where CPTED becomes more than a compliance exercise. It becomes part of a broader enterprise risk-management process that connects physical security, property operations, employee practices, liability exposure, insurance considerations, business continuity, and corrective action. Security was the foundation. Global ERM is where we are today. This article is intended for educational and professional discussion and is not legal advice. Florida Statute 768.0706 should be reviewed in its current form, and property owners should consult qualified legal counsel regarding the application of the statute to their specific circumstances. Current statutory reference: Florida Statute §768.0706, Multifamily residential property safety and security; presumption against liability. About The Author: Joseph Weedman, B.A., FCP, SRMP-C is the Founder & CEO of Weedman & Co., with more than two decades of hands-on experience building and operating businesses across security, protective services, investigations, emergency response, and risk management. He holds a Bachelor of Arts in Security Management, is a Florida Certified CPTED Practitioner (FCP), and holds the SRMP-C professional designation. His background spans physical security, information security, school and campus security, industrial espionage, risk management, business operations, and crisis response. As an operator, business owner, and risk professional, Mr. Weedman brings practical field experience to Enterprise Risk Management (ERM), ESRM, operational risk, resilience, compliance, supply-chain risk, and business continuity. His work today focuses on connecting security, operations, compliance, resilience, and enterprise risk management to help organizations better understand and manage the risks that affect their business.