Compliance,
inside the
engineering loop.

Crado connects hardware revisions, regulatory requirements and test evidence so engineers can trace a finding, investigate a failure and review the evidence behind the next decision.

Starting with radiated-emissions investigations.

Discuss a pilot Explore the system

FIG. 1A fact changes in Rev C. The Rev B finding that depends on it returns to review and stays on record. Evidence tied to unchanged facts stays connected.

Hardware changes.
Keep the evidence connected.

See which earlier test results need another look when your hardware changes.

Rev B · Tested

Rev D · Enclosure changed

Test report · Rev B

Rev D · Review needed

The original result stays with the tested revision.

Every finding needs context.

FINDINGEmission above limitRev B

Keep the hardware, rule, source and decision connected.

From failed finding
to reviewed next test.

Confirm the evidence. Investigate in context. Decide what to test next.

Confirm the reported finding

TEST REPORT · REV B · p. 4SAMPLE DATA

4.2 Radiated emissionsQuasi-peak · 3 m

MHz	dBµV/m	Pol	As reported
144.3	38.2	V	Within limit
216.8	47.0	H	Above limit
288.5	40.7	V	Within limit

SOURCE · Table 4.2, page 4

HIGHLIGHTED FINDING: 216.8 MHz47.0 dBµV/m · H · quasi-peak · 3 mReported above the limit on Rev B.
SOURCE REFERENCE: Table 4.2, page 4 of the report.
BEFORE USE: An engineer confirms each extracted value against the source.TO CONFIRM

NEXT-TEST PLAN · DRAFT · REV BAwaiting engineering review

OBJECTIVE: Find out whether CLK_54M is the source of the emission at 216.8 MHz.
RATIONALE: The frequency matches the fourth harmonic of Y1. This is an inferred link.
METHOD: Near-field probe scan along CLK_54M, then repeat with series termination fitted.
STATUS: Not run. No measurements taken.

The plan is a proposal. An engineer accepts, changes or rejects it and decides what is run on the bench.

A completed scan would be recorded as a result. A cause is confirmed only when engineers accept it on the basis of completed tests.

Rev BRECORDED

Frequency: 216.8 MHz
Level: 47.0 dBµV/m
Detector: Quasi-peak
Distance: 3 m
Cables: Recorded

Rev CRETEST PLANNED

Frequency: 216.8 MHz
Level: Not yet recorded
Detector: Not yet recorded
Distance: Not yet recorded
Cables: Not yet recorded

COMPARISON · AWAITING CONDITION CHECKS

The comparison runs only when these conditions match, or when a difference is documented as not affecting the reading. A lower number alone does not show improvement.

FrequencyTO CHECK
DetectorTO CHECK
DistanceTO CHECK
PolarizationTO CHECK
Operating modeTO CHECK

Comparisons depend on compatible test conditions.

Intelligence with explicit boundaries.

Model-assisted interpretation

Interpret the available material and propose explanations.

Deterministic evaluation

Apply versioned rules to supported inputs and check the conditions required for a valid comparison.

Engineering review

Examine the evidence, challenge the interpretation and decide the physical next step.

Each layer has a defined responsibility. Missing information stays visible.

Show what is known. Keep uncertainty visible.

See the facts, possible explanations and open questions separately.

ObservedAn emissions test recorded a result above the limit.MEASURED
KnownThe board’s clock frequency is documented.SOURCE-BACKED
InferredThe clock could explain the emission.UNCONFIRMED
MissingA follow-up test is needed to investigate the cause.NOT YET TESTED

Engineering changes. The record should keep up.

We’re building Crado to bring affected evidence back into view when hardware changes, while preserving earlier results and decisions.

crado / engineering record

In development

Review the clock-routing change in Rev C.

Earlier test found · Rev B

Bring a real engineering question.

We are working with connected-electronics teams on scoped radiated-emissions investigations.

Discuss a pilot hello@crado.io

Compliance,inside theengineering loop.

Hardware changes.Keep the evidence connected.