Heading 1

Heading 2

Heading 3

Heading 4

Heading 5
Heading 6

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.

Block quote

Ordered list

  1. Item 1
  2. Item 2
  3. Item 3

Unordered list

  • Item A
  • Item B
  • Item C

Text link

Bold text

Emphasis

Superscript

Subscript

How Heritage Cut QA Work by 50% and Turned Production Data into Profit-Driving Insights

Author:
Dana Baranovsky
Summary

Heritage Cannabis transitioned from paper-based to electronic batch records (EBRs) using Elevated Signals. Mandatory fields, auto-calculations, and status-driven workflows halved QA administration time. Remote access and instant notifications eliminated physical handoffs and document errors, boosting production speed and data quality.

Heading 1

Heading 2

Heading 3

Heading 4

Heading 5
Heading 6

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.

Block quote

Ordered list

  1. Item 1
  2. Item 2
  3. Item 3

Unordered list

  • Item A
  • Item B
  • Item C

Text link

Bold text

Emphasis

Superscript

Subscript

share:

https://elevatedsignals.webflow.io/case-studies/case-studies-heritage-digital-batch-records

h3 titleh4

h5
h6
  1. rgrg
  2. rge
  • fefef
  • efef
  • vwvwr

When the React library was introduced into the community some years back, it was accepted and soon gained lots of popularity as the choice for building out user interfaces in a composable way. The major idea was that each UI interface can be split into multiple different small components and at the end of the day, these components can be combined or composed to form the whole larger UI as intended.

class App extends React.Component { 
render() { 
return ( 
      <ColorContext.Provider value="white"> 
      <SampleComponent /> 
      </ColorContext.Provider> 
    ); 
  } 
} 

As a background to what we are trying to present, if we were building multiple UI components for example, we indeed have a component tree which includes the parent component, which becomes the source of truth for our data, and due to the interrelation dependence on the parent components and those underneath it known as the children or descendant descendant descendant descendant descendant component to share data, it comes a point where this becomes an issue.

image description

As we stated earlier, for small to medium apps, sharing data across many different components could be easy, since all we need to do is pass this data or props across or down from the parent to every child that needs it. Now this is fine. What if we have a hugely nested or a large component tree and we intend to pass the data or prop down this tree?

React context, a core React API provides an easier interface for developers to share data or pass props down multiple levels deep in our React applications. From the React docs, with react context, we can easily pass data down to the very component that needs it at any level in the component tree, without having to explicitly pass this data down each component level in the tree. This is all there is to React context.

To drive this definition further for more clarity, say you have a particular theme color set at the parent component level of the app, and you only intend to pass it down to the thirtieth component down the tree, without having to pass it down every level until you get to that thirtieth level, but just pass it down to only the thirtiet

A Success Story 🚀

Heritage Cannabis is a leading cannabis processor with multiple facilities across Canada with complex workflows across extraction, packaging, and fulfillment. Not long ago, its operations were bogged down by manual batch records, constant document errors, and hours of wasted QA time.

The switch to electronic batch records (EBRs) with Elevated Signals started as a fix for human error, but quickly became much more, laying the foundations for data-driven decision-making and operational efficiency.

Gallery Image
Gallery Image
// Credit: Heritage Cannabis

The QA overhaul that ended paper problems

Before EBRs, paper ruled the floor.

  • QA had to return the same record to production three or four times due to gaps or incorrect information
  • Misplaced, hard to track down the hard copy, creating compliance risks
  • QA wasted time physically walking papers across departments, slowing batch turnaround
  • Filing paper took hours every week, leaving little time for higher-value work
“I was reviewing paperwork all day. I once made a 50-slide training deck just to get people to fill in forms properly. Nothing stuck.” — Kat Andersen, QA Associate, Heritage Cannabis

Since adopting Elevated Signals’ electronic batch records, the process has changed completely:

  • Required fields ensure no data is missing
  • Auto-calculations eliminate math errors
  • Status-based workflows prompt each team, so they know what the next step is
  • Remote access lets the Heritage team review and return records instantly, even off-site
“I don’t have to chase anyone down anymore. I change the status and they’re notified. It’s that fast.” — Kat Andersen, QA Associate, Heritage Cannabis
Gallery Image
Gallery Image
Gallery Image
// Credit: Heritage Cannabis

How Heritage turned raw batch data into actionable insights

EBRs didn’t just reduce paperwork, they unlocked the possibility of powerful insights from production data that was previously trapped on paper.

Heritage now uses custom dashboards to monitor production efficiency, track right-first-time metrics, and analyze time-per-unit across SKUs. Managers now get real-time visibility into bottlenecks and trends, without chasing down spreadsheets or reports.

“Now we’re tracking KPIs and building dashboards that shape how we run the company. It’s gone way beyond what I expected.” — Kat Andersen, QA Associate, Heritage Cannabis

This shift has laid the groundwork for smarter decisions and long-term profitability, helping Heritage move from reactive problem-solving to proactive optimization.

The Impact 🌱

50% Reduction in QA Admin Time
Freed up hours every week to focus on system improvements, not chasing paper or fixing errors.

Right-First-Time Improved from 51% to 80% +
Built-in checks and required fields helped QA catch issues earlier, reducing rework and accelerating batch release.

90% Drop in Filing Time
Manual filing went from hours to minutes, simplifying audits and boosting compliance readiness.

Custom Dashboards Driving Operational Insight
Heritage now surfaces trends, tracks efficiency by product type, and identifies bottlenecks using live data, not spreadsheets.

Gallery Image
Gallery Image
// Credit: Heritage Cannabis

Get our insights straight to your inbox

Elevated Signals, founded in Vancouver in 2016, offers a GMP‑validated SaaS that unifies real‑time inventory, quality and environmental data, replacing paper systems.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

We would love
to show you around

Discover how to simplify your operations & reclaim control

Trusted by teams who demand better