📦

NFC Asset Management System: From Equipment Waste to Strategic Reallocation

Building a scalable asset tracking system that saved $225K in 8 months - with 3-5x growth potential as system matures across the enterprise

Executive Summary

The Problem

Construction projects were spending $20K-$50K each on fire protection equipment, then throwing it away or losing track of it at job completion. With 30+ active sites and no tracking system, the company had zero visibility into thousands of pieces of safety equipment worth hundreds of thousands of dollars.

The Solution

Designed and implemented an NFC-based asset management system using SafetyCulture's platform, custom serialized tags, and automated workflows. Personally configured all technical components, served as beta tester for enterprise features, and led gradual rollout across the organization.

The Impact (8 Months Operational)

$225K Total ROI
($160K one-time + $65K 3-year)
60-70% Reuse Rate
(Up from 0%)
1,650+ Assets Tracked
Across 30+ Sites
50x Return on Investment
($4,500 system cost)
3-5 Equipment Transfers
Per Month
20 min Per Equipment Request
(vs. "buy new" default)
Product Management No-Code Development NFC Technology Asset Tracking Construction Tech MVP Development

Looking Back: At the time, I thought I was just solving a business problem. Now I can see I was applying MVP thinking, iterative design, and user-centered workflows - all core product management methodology - without knowing it had a name. The equipment reuse challenge required product thinking, not compliance enforcement. I just didn't call it that yet.

Part 1: The Traditional Safety Approach That Failed

The Waste I Witnessed

Early in my career, I watched equipment get thrown away at job completion. Fire extinguishers, fall protection gear, gas monitors. Sometimes tens of thousands of dollars worth of perfectly functional safety equipment going to the dumpster or left behind because no one knew where else to send it.

When I questioned it, the responses were simple: "It's easier to throw it away than figure out where to send it" or "We budget the job to buy everything new so why would we spend money to keep it?"

Meanwhile, new projects were spinning up and purchasing all new equipment. The same equipment we were throwing away across town. It was wasteful.

The Compliance Trap

As a safety manager, I was stuck in a frustrating cycle, especially as project budgets got tighter:

Project teams: "Why is our safety budget so high? We're spending $20K-$50K just on fire protection!"

Me: "Because you need X fire extinguishers per square foot, overhead suppression for welding areas, monthly inspections..."

Project teams: "But we threw all this away on our last job. Can't we reuse it?"

Me: "I have no idea where any of that equipment is."

This conversation happened on repeat. I was constantly justifying expenditures with zero visibility into what equipment actually existed, where it was located, or whether it could be reallocated instead of purchased new.

What I Tried First (That Didn't Work)

The obvious "safety manager" solution: Excel tracking logs.

We had one brainstorming session about requiring project teams to log equipment locations in a shared spreadsheet. It lasted exactly one meeting before everyone recognized this would never work:

The Real Problem Revealed Itself

This wasn't a compliance problem. This was a reuse and allocation problem.

We had:

Excel alone wasn't going to solve this. We needed a system that was:

I didn't have language for it at the time, but looking back: this is a product problem, not a safety enforcement problem.

Part 2: Building the MVP (What I Now Recognize as Product Thinking)

Finding the Platform

I was already working with SafetyCulture for other safety workflows when I discovered they had an asset tracking module. It was relatively new, designed for larger equipment (think tracking a toolbox, not the individual tools inside).

But I saw the bones of what we needed:

The question was: could I adapt this to track thousands of individual items instead of dozens of large assets?

The Build vs. Buy Decision

Why not buy a specialized asset management system?

  1. We already had SafetyCulture licenses - Zero incremental software cost
  2. Integration was built-in - Our team already used the mobile app daily
  3. I could configure it myself - No IT dependency, no vendor implementation timeline
  4. Speed to MVP - I could test on my own project within weeks, not months

Why didn't we have an enterprise asset management system before this?

We're a construction management company - we don't self-perform work, don't own vehicles, and don't operate heavy equipment. Those are owned by our subcontractors.

The equipment we needed to track was:

Traditional enterprise asset management platforms are designed for companies that own fleets, machinery, and infrastructure. We needed something purpose-built for distributed, mobile-first safety equipment tracking.

The trade-off with SafetyCulture: I'd be locked into their platform capabilities and would need to work within their constraints. But for a $0 software budget, existing mobile adoption, and ability to test immediately, that was the right call.

Designing the Physical System

The NFC Tag Strategy:

I chose NFC tags specifically because:

Custom Tag Design:

I worked with our internal creative team to create serialized tags with:

The regional identifier turned out to be critical - it gave each division ownership over their equipment and made dashboard filtering intuitive.

Testing on My Own Project First

I started with approximately 200 items on my own construction site. This let me:

Work out the technical kinks:

Iterate on the process 10+ times:

Because I was tagging equipment myself, uploading the data myself, and using the system daily, I could rapidly test different approaches:

Build credibility with real data:

When I eventually pitched this to leadership and peers, I wasn't showing a prototype. I was showing a working system with actual company equipment, real location data, and proof that the workflow was manageable.

The Beta Testing Partnership

SafetyCulture's initial asset tracking module only supported individual asset uploads. For our use case of thousands of items, that was a non-starter.

I identified we needed bulk CSV upload capability and brought them the requirements:

We served as beta testers for approximately 6 months, working through:

I also worked with a couple of our subcontractors to demonstrate additional use cases (contractors tracking their own tools), which helped SafetyCulture see broader applications for the feature.

Result: By the time it went production-ready, the bulk upload feature was built around real construction industry needs, because we'd pushed them to solve our actual problems, not theoretical ones.

Part 3: Technical Implementation & Architecture

The Core System Components

1. Physical Tags

  • Custom NFC tags with serialized numbering and regional identifiers
  • Cost: $750 per 1,000 tags ($0.75 per unit)
  • Applied by Safety Department as equipment is consolidated

2. SafetyCulture Mobile App

  • Native iOS NFC scanning (no additional hardware needed)
  • Inspection workflows linked to individual asset IDs
  • Location check-in/check-out functionality
  • Damage reporting and service request triggers

3. Data Management

  • Bulk CSV upload for initial tagging and location transfers
  • Manual location updates (trade-off: no automatic GPS/RFID due to cost)
  • Chain of custody audit trail per asset
  • 6-month abandonment rule (equipment flagged as "lost")

4. Dashboards & Reporting

  • Started with native SafetyCulture dashboards (faster to spin up)
  • Migrated to Power BI for company branding and custom views
  • Real-time equipment location visibility
  • Utilization tracking (how many times assets appear on different sites)

5. Request Workflow

  • JotForm equipment request form
  • Automated email workflow to Safety Manager + Safety Director
  • Manager reviews Power BI dashboard for availability
  • Response triggers in JotForm (all available / partial / none available)

What I Personally Built/Configured

This wasn't vendor implementation. I was hands-on with every component:

Technical Challenges & Solutions

Challenge 1: Tag Durability

What failed: Original tags had adhesive that failed in cold weather and UV coating that degraded in sun exposure

Solution: Currently testing alternative tag designs with original vendor - placing test tags in extreme conditions (direct sun, cold weather, high-traffic areas) to identify most durable option before scaling to 5,000-6,000 tags

Challenge 2: Bulk Transfer Process

Problem: Moving 200+ items between sites required manually writing down each serial number, then re-uploading via CSV

Solution in progress: Developing iPhone shortcut that uses camera to capture tag image, extracts serial number via OCR, and populates Apple Notes for easy copy/paste to Excel. Status: Not consistently reading yet, still iterating.

Challenge 3: RFID Feature Request

User demand: Tech-savvy project teams asked for RFID capability for automated tracking

Decision: Flagged as future enhancement. RFID would enable automatic location updates (huge efficiency gain), but technology not yet available in SafetyCulture platform and cost per RFID tag significantly higher. Partnering with SafetyCulture as they develop RFID capability.

Part 4: Rollout Strategy - Winning Over Skeptics

The Hardest Sell: My Own Department

The biggest resistance came from my own peers, the safety managers and coordinators tasked with using this system.

Their perspective:

They weren't wrong to be skeptical. On the surface, this looked like another administrative burden being dumped on safety.

How I Won Them Over

1. I did the work myself first

I personally tagged approximately 200 items on my project and timed every step:

  • Tag application: approximately 10 minutes per 100 items
  • CSV upload preparation: approximately 5 minutes per 100 items
  • Bulk upload to SafetyCulture: approximately 5 minutes per 100 items
  • Total: approximately 20 minutes per 100 items when equipment is consolidated

Note: This is best-case time when equipment is in one location. Field time with equipment distributed across an active site runs closer to 30-40 minutes per 100 items.

When I presented to peers, I could say: "I've done this myself. Here's exactly how long it takes. Here's the process I built to make it as fast as possible."

2. I made the process bulletproof

Before asking anyone else to use it, I:

  • Documented every step with screenshots
  • Created CSV templates with formulas pre-built
  • Standardized the workflow so it was repeatable
  • Made it accessible (living document they could reference anytime)

3. I picked strategic pilot partners

For the rollout beyond my project, I selected:

  • Tech-savvy safety managers (could handle Excel, CSV uploads, minimal hand-holding)
  • On vocal projects (teams that complained loudest about equipment costs and lack of visibility)

This combination meant: Pilot users could figure it out quickly, their project teams were primed to appreciate the solution, and early wins generated momentum.

4. I showed them project team feedback

After successful pilots, I collected quotes from superintendents and project managers:

  • "Finally we can see what equipment we actually have"
  • "This will save us thousands on our next project"
  • "Why didn't we do this years ago?"

Showing safety managers that this won favor with project teams was the ultimate sell. It transformed from "more work" to "something that makes our customers (the project teams) happy."

The Project Team Pitch

For superintendents and project managers, the value proposition was straightforward:

"You have to have this equipment anyway - it's compliance. This system makes it easier for you to:"

  1. Justify your safety budget - See exactly what you're paying for and where it goes
  2. Save money - Reuse equipment from completing projects instead of buying new
  3. Avoid storage costs - Equipment gets "stored" on active sites where it's in use

Instead of equipment being thrown away or stuck in a storage unit someone's paying for, it gets reallocated to sites that need it.

Adoption Results (Current State: 8 Months Operational)

Deployment Status

Usage Patterns

Why Gradual Rollout: System is only 8 months old - many projects haven't completed full lifecycle yet. Equipment tagging happens most efficiently at project start/end when equipment is consolidated. Organic adoption based on demonstrated value rather than mandated usage.

Part 5: Business Impact & ROI

Total 3-Year ROI: $225,000

The ROI breaks down into two components:

Part A: One-Time Equipment Recovery (Already Realized)

During a business slowdown, we consolidated equipment from closing projects that would have been discarded:

This was a specific event - equipment that would have gone to the dumpster was consolidated, tagged, and reallocated to new projects. This savings is already realized and documented.

Part B: Ongoing Equipment Reuse Savings (Conservative 3-Year Projection)

Based on observed behavior over 8 months of operation:

Current State:

Equipment Value Per Project:

Equipment Type Qty Unit Cost Total
Fire Extinguishers 200 $80 $16,000
Fire Extinguisher Stands 50 $100 $5,000
Overhead Fire Extinguishers 10 $1,000 $10,000
Total Equipment Value $31,000
Conservative Reuse (~65%) $20,000

3-Year Projection:

Combined Total: $160,000 + $65,000 = $225,000

ROI Scaling Potential

The current $225K ROI is based on early, partial deployment. At full enterprise adoption:

50% Participation

15 of 30 projects
$300,000
3-year potential

75% Participation

22-23 of 30 projects
$420K-$480K
3-year potential

Full Enterprise

All 30 projects
$600,000
3-year potential

Key Insight: Current ROI of $225K represents early-stage validation. The model works. As deployment scales and more projects complete full cycles, the annual recurring savings increase significantly. This isn't a static $225K system - it's a $225K validation of a model that scales to $300K-$600K.

Additional Equipment Types Tracked

The ROI calculations above focus on fire extinguishers (easiest to quantify). The system also tracks:

These additional categories represent unmeasured value beyond the $225K conservative estimate.

System Costs

Initial Investment

Net ROI

Even at full deployment with 5,000-6,000 tags ($3,750-$4,500 total), the system remains one of the highest-ROI implementations across the organization.

Part 6: Leadership Without Authority

The Stakeholder Map

I had to influence and coordinate across:

Stakeholder Initial State How I Won Them Over
Safety Managers (peers) "More work for us" Doing it myself first, proving it was fast, showing project team appreciation
Project Teams Frustrated by equipment costs, no visibility Solving their pain point (budget justification + cost savings)
Leadership "Is this worth the time investment?" Real data from pilot showing equipment recovery and reuse rates
SafetyCulture (vendor) No bulk upload capability Providing real use cases, beta testing, proving enterprise value
IT/Technical Teams Needed Power BI dashboard development Customizing templates myself, coming with specific requests vs. vague needs

The Builder-User Advantage

Being a daily user of the system I was building gave me an unfair advantage:

I experienced the friction firsthand:

I could iterate without committee approval:

I understood real field conditions:

Gradual Rollout Strategy (Not "Big Bang")

Why gradual:

  1. Equipment consolidation timing - Easiest to tag everything when it's in one place (project start or end)
  2. Proof of concept scaling - Each successful site generated momentum for next rollout
  3. Reduced risk - If something broke, it only affected one site while I fixed it
  4. Voluntary adoption - Results spoke for themselves, didn't need to mandate usage

The rollout sequence:

  1. My project (200 items) - Prove concept, refine workflow
  2. 3-5 pilot sites (tech-savvy managers, vocal projects) - Generate early wins
  3. Sites starting up or wrapping up - Natural consolidation points
  4. Organic expansion - Safety managers requesting to be added based on peer success

This approach meant I never had to "sell" the system through mandates. Project teams voluntarily requested access because they saw the value.

Part 7: Looking Back - The PM Skills I Was Using Without Knowing

The Methodology I Was Applying (Before I Knew What to Call It)

This project came before I had language for what I was doing. It wasn't until later, with the Hot Work Permit system, that I realized "I've been doing product management." But looking back at the NFC asset tracking system, I can now see all the PM skills I was naturally applying:

MVP Thinking

What I did at the time:

What I now understand I was doing: This is textbook MVP methodology: build minimum viable version, test, learn, iterate. I thought I was just "being pragmatic" - but I was applying a formal product development framework.

User-Centered Design

What I did at the time:

What I now understand I was doing: This is user research and usability testing - just informal instead of structured. I called it "making sure it actually worked in the field," but I was running continuous user validation cycles.

Stakeholder Management

What I did at the time:

What I now understand I was doing: This is influence without authority. I was leading through product value, not positional power. At the time, I just thought I was "getting buy-in the hard way."

Feature Prioritization

What I did at the time:

What I now understand I was doing: This is prioritization framework - solve core problem first, add capabilities as value proves out. I was running a product roadmap; I just called it "figuring out what to build next."

The Pattern I Can Now See

Looking back, I approached this as a reuse and allocation problem, not a compliance problem.

Traditional Safety Approach Product Approach (What I Did)
"Require project teams to log equipment in Excel" "Make it easier to reuse equipment than to throw it away or buy new"
"Mandate equipment returns at project completion" "Provide visibility that solves project teams' budget pain point"
"Enforce penalties for lost/damaged equipment" "Design system simple enough that adoption is voluntary, not mandated"

At the time, I just knew the compliance approach wouldn't work. Now I understand why: the product approach worked better - both for business impact (estimated 60-70% reuse for transferred equipment vs. 0%) and for user adoption (voluntary usage vs. resentment of mandates). I was solving for behavior change through design, not enforcement.

Where We Are vs. Where We're Going

Current State

8 Months, Validated
30+ sites with equipment
$225K ROI

12-Month Target

Maturity Phase
All 30+ sites comprehensive
$150K annual run rate

24-Month Mature

Scale Phase
75%+ sites active
Expand to new categories

Part 8: What Didn't Work - Honest Failures

The Serialization Extraction Problem

What I tried: iPhone shortcut to photograph NFC tags and automatically extract serial numbers to Notes app
Why: Bulk equipment transfers required manually typing hundreds of serial numbers
What failed: OCR isn't consistently reading the numbers accurately enough

Current state: Still iterating, but may need to accept manual entry or wait for platform improvement
Lesson: Not every automation idea works. Sometimes manual process is more reliable than buggy automation.

The Original Tag Durability

What I tried: Initial NFC tags with standard adhesive and UV coating
What failed: Adhesive failed in cold weather (tags fell off), UV coating degraded in sun exposure (numbers became illegible)

Current solution: Testing alternative tag material configurations in extreme conditions before next scaling phase
Lesson: Construction environments are brutal. Test durability before scaling, not after.

The "Nice to Have" Documentation That Nobody Needed

What I assumed: People would want detailed ROI documentation and written justification for why the system works

What actually happened: The inherent value was obvious. Dashboard showing equipment locations sold itself.
Lesson: I over-engineered the "sell." Sometimes the product speaks for itself and you don't need elaborate justification decks.

Features I Thought Were Critical (But Weren't)

GPS/RFID automatic tracking: Users are fine with manual check-in/out. The tap-to-update workflow is fast enough.

Complex utilization analytics: Leadership mostly cares about "where is it" and "is it available." Fancy utilization metrics are nice-to-have, not must-have.

Features Users Asked For (That I Didn't Plan)

RFID capability: Tech-savvy project teams pushed for this. Now flagged as future enhancement as SafetyCulture develops it.

Lesson: User feature requests often come from unexpected places. Stay open to pivoting roadmap based on field feedback.

Part 9: Skills Demonstrated

Product Management Skills

  • MVP development - Started small, iterated, scaled gradually
  • User research (informal) - Used system myself, gathered feedback from pilots
  • Stakeholder management - Influenced without authority across multiple groups
  • Feature prioritization - Core tracking first, RFID deferred to future
  • Metrics-driven iteration - Used time studies, adoption rates to validate
  • Build vs. buy decision framework - Chose to configure existing platform
  • Scaling strategy - Gradual rollout with clear maturity phases

Technical Implementation

  • No-code platform configuration - SafetyCulture, workflows, integrations
  • Data architecture - CSV templates, serialization, chain of custody
  • Dashboard development - Power BI templates for location, utilization
  • Workflow automation - JotForm with conditional logic and email triggers
  • Mobile-first UX design - NFC tap-and-go for field workers
  • Hardware selection - NFC tags (cost, durability, compatibility)
  • Creative workarounds - iPhone shortcut development (in progress)

Domain Expertise

  • Construction field operations - 99.9% uptime, weather exposure, behavior patterns
  • Equipment lifecycle management - Procurement, calibration, inspections
  • Safety compliance - OSHA requirements, documentation, chain of custody
  • Project team dynamics - Budget pressures, equipment "ownership" mindset

Change Management

  • Overcoming internal resistance - Safety managers skeptical of "more work"
  • Voluntary adoption strategy - System valuable enough that usage self-sustains
  • Strategic pilot selection - Tech-savvy users on vocal projects
  • Documentation and training - Process guides for self-service adoption

Part 10: Interview Preparation - How This Maps to Common PM Questions

This case study prepares answers to common product management and leadership interview questions:

"Tell me about a time you built a product from scratch"

  • Problem: $160K equipment waste, zero visibility across 30 sites
  • Discovery: Traditional safety approaches failed, reframed as product problem
  • Build: NFC-based system on SafetyCulture platform, personally configured all components
  • Result: $225K ROI in 8 months with 50% deployment, $300K-$600K potential at scale
  • Learning: Discovered I was doing product management before I knew it had a name

"How do you prioritize features when everyone thinks their request is urgent?"

  • Situation: Users wanted RFID auto-tracking, complex analytics, GPS integration
  • Framework: Started with core problem (location visibility), added inspection workflows (natural extension), deferred RFID (not technically feasible yet)
  • Result: Focused on must-have vs. nice-to-have, delivered working system fast rather than perfect system slowly
  • Learning: Solve the core problem first, add capabilities as value proves out

"Describe leading without authority"

  • Challenge: No direct reports, had to influence peers, project teams, leadership, and vendor
  • Approach: Did the work myself first, proved it was fast, showed value to project teams
  • Strategy: Strategic pilots (tech-savvy users on vocal projects), used early wins to generate momentum
  • Result: Voluntary adoption across 50% of sites with zero mandates, system value drove usage
  • Learning: Lead through product value, not positional power

"Tell me about a product decision you made with limited data"

  • Decision: Estimated equipment lifecycle at 2 projects based on observation (not manufacturer data)
  • Context: Needed to calculate ROI for business case, formal data didn't exist
  • Approach: Used conservative estimate, validated against actual equipment durability over time
  • Result: $160K lifecycle projection held up as equipment completed multiple project cycles
  • Learning: Be conservative with assumptions, validate as data becomes available

"How do you measure product success?"

  • North Star: Equipment reuse rate (0% to estimated 60-70% for transferred equipment)
  • Business Metrics: $225K ROI on $4,500 investment (50x), equipment savings per project
  • Adoption Metrics: 50% sites tagged, 25% actively cycling, 3-5 transfers per month
  • Efficiency Metrics: 20 minutes per equipment request vs. default "buy new"
  • Learning: Combination of business impact, user adoption, and efficiency gains

"Walk me through a time you had to make a difficult trade-off"

  • Trade-off: SafetyCulture platform vs. specialized asset management system
  • Constraints: $0 software budget, need to launch fast, existing mobile adoption
  • Decision: Configure existing platform, accept vendor lock-in risk
  • Result: Deployed in weeks instead of months, zero incremental cost, 50x ROI
  • Learning: Right trade-off depends on constraints - speed and cost mattered more than platform flexibility

"Tell me about a product that failed and what you learned"

  • Failure: iPhone shortcut for serial number extraction still doesn't work consistently
  • Why: OCR not accurate enough for construction environments (dirt, wear, lighting)
  • Learning: Not every automation idea works - sometimes manual process is more reliable than buggy automation
  • Pivot: Accepted manual entry as "good enough" rather than blocking progress on imperfect automation
Product Management No-Code Development NFC Technology Asset Tracking Construction Tech MVP Development Change Management
← Back to Projects Want to discuss this project? Get in touch →