How Partner Electronics modernized design reviews with AI and DRCY

For Partner Electronics, AI for hardware engineers means a first pass before peer review. DRCY runs immediately after schematic capture and checks the design against the datasheets of the parts in it. Engineers resolve its findings before peer review and still sign off on the design. Over the past year, the team has used DRCY on real customer projects to catch issues before they turn into board rework.

Written by:
Allspice team
|
Updated on:
October 29, 2026

Partner Electronics is a UK-based electronics and embedded firmware design services consultancy. Since 2007, the company has helped hardware organizations at all stages of product development, with expertise spanning electronics design, embedded firmware, RF, sensors, power electronics, compliance, and more. What's their philosophy for success? Combine deep engineering expertise with a partnership approach that builds long-term relationships, while continuously improving products and the engineering processes behind them.

That focus on process is why, when Allspice rolled out DRCY for AI-assisted design reviews, the team saw an opportunity to modify their workflow to scale productivity. This post covers how Partner Electronics incorporated Allspice and DRCY into their existing review workflow and what they've learned from using it in production. It also covers why they believe the future of hardware design reviews is a partnership between human engineers and AI.

How AI changes design review for hardware engineers

DRCY AI design review is Allspice's AI design review assistant for schematics. It works through a design in five steps:

  1. It reads the native ECAD files, with no export step.
  2. It reads the datasheets of the parts in the design and derives the requirements each part imposes.
  3. It checks the schematic against those requirements, and against itself across sheets.
  4. It cites the datasheet page behind each finding.
  5. Engineers confirm or reject each finding and sign off on the design.

The rest of this story shows how Partner Electronics fitted that first pass into a review process that was already rigorous.

Challenges

Partner Electronics built their reputation on bringing high-quality design services to customers across a wide range of industries. With continued growth, however, the team faced challenges in scaling their engineering expertise and collaborative review processes.

‍

Scaling engineering expertise across every project

Every new customer project brings its own industry requirements, technologies, and design constraints. The team of eight engineers at Partner Electronics needed to consistently deliver high-quality work across a diverse portfolio of designs while coordinating reviews between internal and external stakeholders.

As the number of projects increased, so did the demands on reviewers. Every design needed to be thoroughly evaluated before moving forward, and customers needed visibility into the review process as a useful way of collaborating across large designs.

The team needed a solution that could help them:

  • Maintain consistent review quality across every project.
  • Give engineers another layer of verification without replacing human expertise.
  • Make design reviews easier to share and discuss with customers.
  • Scale their review process without scaling engineering overhead at the same rate.

‍

Finding issues before they became too expensive

Even experienced engineers can miss subtle design issues, especially as projects grow in size and complexity. Small issues can easily fall through the cracks if engineers are focused on system architecture and design intent. Are all pin numbers and names correct? Have the correct voltages been applied? Any EOL parts missed during initial review? Are all required pull-up resistors in place? These kinds of implementation details can easily plague large-scale designs, leading to downstream issues.

Additionally, minor schematic changes that appear insignificant during design reviews become more costly as hardware development progresses. An issue identified during schematic review might be resolved in a couple minutes. The same issue discovered during testing could require prototype rework, additional validation, schedule delays, and potential manufacturing changes. Partner Electronics couldn’t afford those kinds of late-stage issues.

NASA's aerospace programs offer an analogy from outside PCB design. In a NASA study of error cost escalation, a requirements error costing 1 unit to fix early cost 21–78 units at integration and test. Partner Electronics couldn't afford those kinds of late-stage issues.

‍

A framework built for partnership

As a design consultancy, Partner Electronics had some unique considerations for their business which ultimately led them to Allspice. Not only did they need to consider their own design workflows and review structures, but also how they interacted with their customers and what access levels were needed. The transparent, easy-to-collaborate framework of Allspice was key.

  • ECAD-agnostic support allowed a consistent engineering workflow regardless of which design tool their customers used: Altium, OrCAD, Xpedition, etc.
  • Isolating projects through role-based access control enabled them to collaborate on multiple customer projects simultaneously while strictly managing any intellectual property or confidentiality concerns.
  • A centralized engineering data platform combined design management, review comments, AI findings, and revision control into a single source of truth instead of the disconnected toolset they had been using previously.
  • AI-assisted design reviews with DRCY provided a practical way to strengthen their existing review process and remain a leading consultancy with the most advanced technologies.
  • The responsive team at Allspice worked closely with them through regular feedback sessions. This collaboration led to rapid implementation of improvements and new features around AI workflows, issue management, reporting, and customer collaboration.

The value of Allspice for enabling strong partnerships was clear:

"If you look at it purely on time saved, it’s easy to justify the cost of Allspice. But honestly, the real win is that it helps us do a better job, faster—and our clients can see that."
— Richard Rydon, Managing Director at Partner Electronics

‍

One workflow across every customer's ECAD tool

Partner Electronics' customers design in Altium, OrCAD, Xpedition and other ECAD tools. A consultancy can't ask each customer to switch tools, so the review process has to work with whatever arrives. Allspice reads native ECAD files directly, with no export step and no intermediate format.

As a result, a design review looks the same whatever tool the customer used. DRCY findings and review comments appear in the same place for every project. That gives the team one consistent engineering workflow as they move between customer designs.

‍

Creating a better design review process

Partner Electronics already had a structured design review workflow in place. Allspice was introduced as a collaborative framework with DRCY as an additional first-pass review layer before formal peer review to catch issues humans might overlook.

‍

Before Allspice

Their original review process followed a familiar engineering workflow:

  1. Capture the schematic.
  2. Review it manually, marking up PDFs and passing them around the team.
  3. Incorporate the review feedback back into the design.
  4. Repeat the cycle until the schematic is ready to move forward.

‍

Traditional hardware design review workflow before AI-assisted schematic reviews

Any feedback from a review was incorporated back into the design, and the iterative cycle continued until the schematic was ready to move forward.

While this worked in principle, the limitations were evident:

"We’ve got a process, but it’s pretty manual things like marking up PDFs and passing them around between the team."
— Richard Rydon

‍

After Allspice

Once they adopted Allspice, Partner Electronics added a DRCY AI review step immediately after schematic capture and before their formal peer review. Their new workflow runs in five steps:

  1. Capture the schematic.
  2. Run DRCY as a first pass.
  3. Resolve the DRCY findings, with an engineer confirming each one.
  4. Enter peer review with the DRCY report alongside the standard design checklist.
  5. Approve the final design.

‍

Partner Electronics AI-assisted hardware design review workflow using DRCY

The updated workflow allows the team to catch obvious design issues earlier in the process and gives reviewers more time to focus on engineering decisions instead of routine checks. All the benefits of a normal peer review process are preserved while DRCY enhances the workflow with AI-generated insights.

The division of responsibilities allows each reviewer to focus on what they do best:

DRCY focuses on:

  • Catching subtle design errors that are easy to overlook.
  • Checking datasheet requirements and best practices.
  • Identifying routine issues quickly and consistently.
  • Following signals and nets across multiple schematic pages.

Engineers focus on:

  • Evaluating design intent and system architecture.
  • Making engineering tradeoffs and design decisions.
  • Confirming AI findings and approving the final design.
  • Giving DRCY design context such as rail voltages and design intent.

Owen Evans described the immediate impact:

"It’s helped us catch serious issues early before they became bigger problems which has been a real benefit to the business."
— Owen Evans, Engineer at Partner Electronics

‍

5 real-world examples where DRCY caught important issues for Partner Electronics

Using this new workflow, DRCY was able to identify issues across multiple customer designs, ranging from incorrect component selection to subtle cross-sheet inconsistencies that could have resulted in board rework and schedule delay. Each catch came while the fix was still a schematic change, before it could become the rework listed below. A few of the more notable examples:

Example #1: Incorrect transistor variant

A transistor in the BOM used the wrong part number suffix, and a 30 V variant was inadvertently selected for a 43.5 V rail. Using an under-rated component like this could have resulted in device failure once the board was powered, but DRCY flagged the incorrect part number and recommended the appropriate 65 V variant instead.

DRCY AI identifying an incorrect transistor variant during schematic review

‍

Example #2: Pin assignments unintentionally changed

During a collaborative project, an engineer temporarily rearranged an IC's pins to improve schematic readability. However, a later library update quietly restored the original pin arrangement after the design had already been peer reviewed. Reviewers could have easily missed this kind of functional error as the design progressed, but DRCY detected it right away. 

DRCY AI detecting an unintended IC pin assignment change during hardware design review

‍

Example #3: Incorrect power connection

An LDO regulator was connected to the wrong power net, which would have resulted in regulator failure and board redesign due to incorrect input voltage. The team replaced the component with a compatible pin-for-pin alternative after DRCY flagged the incorrect power connection.

DRCY AI detecting an incorrect power connection during a hardware schematic review

‍

Example #4: Missing datasheet requirement

A device required specific decoupling capacitors, but this information was buried deep (on page 41!) in the datasheet and not implemented correctly in the design. This is a common scenario DRCY excels at: uncovering important implementation details buried dozens of pages into component documentation.

DRCY AI verifying schematic components against manufacturer datasheet requirements

‍

Example #5: Voltage mismatch across schematic pages

One signal originated from a different CPLD pin bank and operated at a different voltage than the related signals. This mismatch required different level shifting, but because the signals were spread across multiple schematic pages, the issue was difficult to spot during manual review. Since DRCY analyzes designs holistically, it was able to recognize the voltage mismatch and identify the missing level shifting requirement.

DRCY AI detecting a voltage mismatch in an electronic schematic design

‍

More than just finding errors

As evidenced by these examples, much of DRCY's value comes from where it sits in the engineering process and how it works with human reviewers. DRCY adds another perspective and surfaces issues that need a second look.

One engineer described their experience:

"It's a very useful option to have to be able to put designs through and get almost a third-party external sanity check."
— Andrew Templey, Senior Electronics Engineer at Partner Electronics

Since Partner Electronics operates as a consultancy, the impact extended beyond internal engineering reviews. Frequent collaboration with customers throughout the design process became much more productive by focusing on engineering decisions instead of preventable mistakes. Having DRCY identify issues before designs were shared helped keep those conversations on track.

‍

Building better together

Adopting Allspice and DRCY wasn’t the end of the journey. Through regular conversations with our product team, Partner Electronics became active in shaping how AI-assisted design reviews should evolve. They provided feedback on everything from issue management and customer collaboration to reporting structures and AI interface implementation. This kind of relationship reflects how Allspice builds products: working closely with customers to solve real engineering challenges and quickly provide improved workflow solutions.

The collaboration is already influencing Allspice’s product roadmap. Planned capabilities such as chatting directly with DRCY, repository-wide engineering knowledge, reusable engineering feedback, simplified stakeholder reports, and more targeted AI interactions are all being developed to boost efficiency while keeping humans firmly in control of engineering decisions.

The goal is to make AI a more knowledgeable and responsive partner to work alongside experienced engineers and reviewers. As hardware systems continue to grow in complexity, design reviews will increasingly combine the strengths of both humans and AI. AI can provide consistency and detail across large designs. Engineers contribute the context, judgment, and experience needed to make the final decisions. Together, they create a review process that is more thorough and scales better than either could manage alone.

‍

FAQs

What is DRCY and how does it help with electrical design review?

DRCY is Allspice's AI design review assistant, and it gives engineers a first pass on schematics before peer review. It checks the schematic against the datasheets of the parts in the design and cites the datasheet page behind each finding. Engineers confirm or reject every finding and sign off on the design.

How is AI changing hardware engineering design review workflows?

For hardware engineers, AI adds a first-pass review between schematic capture and peer review. At Partner Electronics, engineers run DRCY first, resolve its findings, then enter peer review with the DRCY report alongside their standard design checklist. Reviewers get more time for engineering decisions, and engineers still approve the final design.

What role does AI play in reducing rework in electronics design?

AI helps reduce rework by catching schematic errors before they reach a board. At Partner Electronics, DRCY flagged an LDO regulator connected to the wrong power net, which would have caused regulator failure and a board redesign. The team replaced it with a compatible pin-for-pin alternative.

Does DRCY review PCB layout?

No. DRCY reviews schematics, and it does not check layout rules such as trace widths or clearances. Footprint validation is in progress. For more on scope, see what AI design review catches and where it stops.

Valentina Ratner, Co-Founder & CEO of AllSpice
Allspice
The platform hardware engineers build on

Allspice is the platform for hardware engineering teams to collaborate, automate, and supercharge their workflows. Founded by engineers and trusted by Fortune 500 teams across aerospace, robotics, semiconductors, and defense, we help teams ship better hardware, faster.