CLD logo
Focused certification exam prep
Start practice

CLD Exam Dates 2026: Testing Windows, Deadlines & Scheduling

TL;DR
  • The CLD is a four-hour practical application build, scheduled through Pearson VUE rather than tied to fixed testing windows.
  • NI offers an OnVUE online-testing route; confirm your software image and candidate rules in the current booking instructions.
  • The older prep guide (100900A-01, copyright 2012) has outdated delivery logistics; treat its USB and local-proctor details as historical.
  • Passing requires 28 of 40 rubric points: style 15, functionality 15, documentation 10.

Why the CLD Has No Fixed Exam Calendar

Candidates searching for "CLD exam dates" often expect a published list of testing windows, like a semester schedule. The Certified LabVIEW Developer credential from National Instruments (NI) doesn't work that way. The exam is a performance-based practical, not a multiple-choice test delivered in a fixed seat-time block, and NI routes scheduling through its current partner, Pearson VUE. That means your "exam date" is the slot you choose when you book, subject to availability in the booking system.

The practical consequence is that your date is mostly a readiness decision rather than a deadline imposed by NI. If you're still deciding whether the effort is justified, our ROI analysis of the CLD certification and the CLD certification cost breakdown will help you decide before you commit to a slot.

Verify before you plan: Slot availability, booking options and candidate rules change over time. Treat the NI credential page and the Pearson VUE booking flow as the authoritative source for what is open on a given day, and treat any third-party "exam calendar" with suspicion.

How CLD Delivery Works Today

The initial CLD is a four-hour application-development practical. You're given a specification and must build a working LabVIEW application from it. The scope is software development only, with no hardware involved. Current NI delivery uses Pearson VUE, including an NI OnVUE online-testing route, and performance-based exams run on a secured virtual machine rather than on your own installation.

That detail matters for scheduling. The older NI preparation guide for the CLD (document 100900A-01, copyright 2012) describes USB-based delivery, software-version requirements and local-proctor logistics. Those instructions are historical. Confirm the assigned software image and candidate rules through the current booking instructions, not through the 2012 guide. The guide remains valuable for its ten Exam Topics and its grading rubric, but not for logistics.

What the old guide still gets right

  • The ten Exam Topics: Design Concepts, User Interface Design, Block Diagram Layout and Style, Programming Practices, SubVI Design Practices, Architecture Selection, Timing, Error Handling, Documentation and Testing.
  • The 40-point evaluation rubric and the 28/40 (70%) passing criterion.
  • The allowed resources: built-in LabVIEW Help, examples and templates are permitted; externally developed VIs or outside resources are not.

For a domain-by-domain walkthrough of those ten topics, see the complete guide to all 10 CLD content areas.

Scheduling Steps and What to Confirm

Exact screens change, so use this as a checklist of things to confirm rather than a click-by-click script. Start from NI's Certified LabVIEW Developer page, follow the registration path to Pearson VUE, and read the current candidate instructions before paying for anything.

  1. Check eligibility. NI lists no mandatory prerequisite on the current credential page. The old guide's CLAD prerequisite has been superseded. See CLD requirements and eligibility for the full picture.
  2. Choose a delivery route. Review whether you'll test through the OnVUE online route or another option offered in the booking flow, and read the environment rules for that route.
  3. Confirm the software image. The LabVIEW version and tooling come from the assigned secured virtual machine. Practice in a comparable environment so nothing about the editor surprises you.
  4. Review candidate rules. Identification, workspace and conduct requirements for online delivery can be strict. Read them days ahead, not the morning of the exam.
  5. Book a slot and note cancellation terms. Rescheduling and cancellation policies live in the booking flow, so record them when you book.
  6. Check fees on the booking page. We don't quote a price here because fees can change; the pricing breakdown explains how to evaluate total cost.
Technical rehearsal: If you test online, do any system or environment check the booking flow offers well before exam day. A four-hour build leaves little room for troubleshooting a webcam, network or workspace problem in the middle of the session.

Choosing a Date: Readiness Beats the Calendar

NI recommends roughly 12 to 18 months of LabVIEW development experience before attempting the CLD. Completing Core 1, Core 2 and Core 3 may substitute for three months of that experience. This recommendation is the closest thing to a "when should I take it" rule, and it's about your skill, not the calendar.

A useful way to pick a date is to define readiness in terms of the rubric rather than a feeling. The exam is graded on 40 points: Programming style 15, Functionality 15 and Documentation 10, with 28 points (70%) needed to pass. Those rubric shares work out to 37.5% for style, 37.5% for functionality and 25% for documentation. They are calculated shares of the practical grade, not weights for the ten topic areas.

Readiness signalWhat it suggests
You can build a clean working application from a spec well inside four hours, leaving review timeBook a slot; you're close to ready
Your builds work but your block diagrams and icons are messyStyle points are at risk; delay and drill layout and subVI design
You consistently run out of time before documentingDocumentation is 10 of 40 points, so practice finishing with time to spare
You've only read about state machines and producer-consumer patternsNot ready; implement each pattern from scratch several times

To calibrate how demanding the practical is relative to your background, read how hard the CLD exam is. For the exact scoring math, see the CLD passing score explained.

Building Your Prep Backward From the Booking

Once you've picked a target date, work backward by domain. The only generic advice worth giving is this: schedule the heaviest-risk domains earliest, then spend your final weeks on full timed builds. Because the exam is practical, original coding exercises and rubric-based self-assessment matter far more than reading. Conceptual review of the ten Exam Topics is supplementary knowledge preparation, not a substitute for building a working application. For the broader plan, see the CLD study guide.

Weeks 1-2

Architecture and Design Concepts

  • Implement a simple state machine, a UI event handler and a queued message handler from a blank VI.
  • Practice data and event producer-consumer patterns and functional global variables.
  • Articulate modularity, cohesion and coupling in your own project hierarchies.
Weeks 3-4

Style, SubVIs and User Interface

  • Drill block diagram readability and data flow until clean layout is automatic.
  • Design subVIs with clear connector panes and icons.
  • Set front-panel properties, grouping and initial and stopped states deliberately.
Weeks 5-6

Timing, Errors, Documentation and Testing

  • Use timing functions, timeouts and timed structures appropriately.
  • Wire error handling and reporting through every subVI.
  • Document front panels, block diagrams and VI properties, then review your code against the spec.
Final week

Timed full builds

  • Run complete four-hour builds under exam conditions.
  • Score yourself against the 40-point rubric and fix your weakest category.

If you want structured rubric-based practice rather than inventing everything yourself, the exercises and self-assessment tools on the main CLD practice site are designed around building, not memorizing. For formal course options, see our overview of CLD training.

What the Four Hours Look Like

Knowing the shape of the session helps you pick a time of day when you work best. You get four hours to turn a specification into a working application, using only built-in LabVIEW Help, examples and templates. Externally developed VIs or resources are prohibited, so anything you plan to rely on must come from the permitted material.

Where the points are won and lost

The rubric rewards a complete, tidy, documented solution, not just one that runs.

  • Functionality (15): Does the application do what the specification requires? Testing your build against requirements protects these points.
  • Programming style (15): Readable diagrams, sensible subVIs, consistent data flow and a well-chosen architecture.
  • Documentation (10): Front-panel, block-diagram and VI-property documentation that a reviewer can actually read.

Book a time of day when you're sharpest and uninterrupted, because there's no way to pause a four-hour build. Plan a final pass at the end for documentation, error handling checks and a last run through the specification.

Key Takeaway

Reserve the last 30 to 45 minutes of every practice build for documentation and a requirements check. Candidates who treat documentation as an afterthought leave a quarter of the rubric at risk.

Validity, Renewal and Planning Your Next Date

A CLD credential is valid for three years, so passing creates a second future date to plan around: your renewal. NI's recertification policy, updated April 30, 2026, allows renewal by examination and also offers Recertification by Points to developer-level and architect-level professionals. The CLD-R is a distinct recertification examination; it should not be confused with the initial CLD, and nothing about its format tells you about the initial practical.

Put your expiration date on a calendar the day you pass, and review the current recertification policy a few months ahead so you can choose between the exam and points routes. The career value of keeping the credential current is covered in our CLD salary guide and in the discussion of CLD jobs.

Old Guide vs. Current Delivery: What Changed

Many candidates find the 2012 prep guide first and assume its logistics still apply. This table separates what remains useful from what is historical.

TopicOlder guide (100900A-01, 2012)Current approach
PrerequisiteMandatory CLAD prerequisiteNo prerequisite certification listed on the current credential page
Delivery logisticsUSB, local-proctor and software-version instructionsPearson VUE with a secured virtual machine; OnVUE online route available
Exam formatFour-hour application buildFour-hour application-development practical
Grading rubricStyle 15, functionality 15, documentation 10; 28/40 to passSame rubric reference applies; confirm in current NI materials
Permitted resourcesBuilt-in Help, examples and templates onlyConfirm in current candidate rules

For a plain-language introduction to the credential itself, see what CLD certification is, and for the exact numbers behind the grade, the CLD pass rate discussion explains why published pass-rate figures should be treated carefully.

Frequently Asked Questions

Are there fixed CLD testing windows in 2026?

The CLD is scheduled through Pearson VUE, including an NI OnVUE online route, so you choose from available slots in the booking system rather than waiting for a fixed testing window. Availability can vary, so check the booking flow directly when you're ready to schedule.

Should I follow the logistics in NI's 2012 CLD preparation guide?

No. Use the guide for the ten Exam Topics and the grading rubric, but treat its USB, software-version and local-proctor logistics as historical. Confirm the assigned software image and candidate rules through the current booking instructions.

How long does the CLD exam take?

The initial CLD is a four-hour practical in which you build a working LabVIEW application from a specification. It covers software development only and does not involve hardware.

How many points do I need to pass?

The grading rubric totals 40 points: Programming style 15, Functionality 15 and Documentation 10. The passing criterion is 28 out of 40 points, which is 70%.

When should I schedule my renewal after passing?

The certification is valid for three years. NI's recertification policy, updated April 30, 2026, allows renewal by examination and offers Recertification by Points for developer-level and architect-level professionals. Check the current policy a few months before expiry and plan your route early.

Ready to pass your CLD exam?

Put this into practice with free CLD questions across every exam domain.