What should be included in technology due diligence?
The short answer
Technology due diligence should establish what systems exist, who owns and supports them, which agreements apply and what evidence is available about their condition. Include administrative access, documentation, dependencies, known issues and planned replacement needs. Separate verified findings from assumptions and unavailable evidence, then assign each open question an owner and decision deadline.
Answered by Jim Mazzarella, CEO & Managing Partner
Build an evidence register
Request equipment records, diagrams, service history, current contracts and manufacturer support information for the agreed scope. Record the source and date of each item and identify gaps. Define any cybersecurity assessment separately, including authorization and limits; a document review should not be represented as a penetration test or a guarantee that no risk exists.
Translate findings into decisions
- Distinguish owned, leased and provider-managed equipment and accounts
- Identify contract renewals, transfer questions and third-party dependencies for review
- Document access and support ownership without placing passwords in the report
- Separate urgent corrective work from planned refresh and optional improvements
- Provide evidence, uncertainty and a responsible owner for each recommendation
Have a project, not just a question?
Tell us about your facility. A Nexus specialist follows up within one business day.
Book a free consultation