Testing is a process of progressively eliminating uncertainty. Before samples ship, we agree with you on what the report must answer, which standard and revision applies, and which acceptance criteria the data will be judged against. Once those three are fixed, the rest is execution and confirmation.
Stage 01 — Requirement confirmation
You tell us the product, the target market, and the standards or OEM technical agreement you must meet. Together we review the item list, condition levels, sample quantity and report use. Many quotes that look "cheap" later turn out expensive because the scope was written too narrowly and has to be redone.
What you get
A confirmed test plan: item list, standard and revision, condition levels, sample quantity, lead time and price. Any item we cannot perform is stated explicitly, together with where it could be done.
Stage 02 — Quotation and scheduling
Based on the confirmed plan we quote per item, so you can see what each line costs. Scheduling is confirmed against actual chamber and bench availability at that moment, not a generic lead time. If the project is schedule-critical, say so up front—we will confirm feasibility before you commit.
What you get
An itemized quotation and a confirmed schedule. Everything that can affect the timeline—sample preparation, fixturing, retest allowance—is written into the note.
Stage 03 — Sample receipt and pre-check
On arrival, samples are logged with photos and their state recorded: quantity, appearance, labels, any prior test traces. If a sample does not match the declared state, or is short, you are told the same day, before testing starts. Testing a sample of unknown history produces data nobody can defend.
What you get
A sample receipt record: quantity, state, photos and a list of any anomalies. Fixturing and harness requirements are confirmed at this point.
Stage 04 — Test execution
Testing runs to the confirmed plan. Conditions are recorded throughout; anything abnormal during the run is documented rather than quietly retried. For long-duration items (temperature cycling, damp heat, salt spray, vibration) we report progress at agreed milestones rather than going silent until the end.
What you get
Raw data, condition records and a progress update at each milestone. Witnessed testing and on-site visits can be arranged in advance.
Stage 05 — Data review and report issue
After testing, data is reviewed and the report drafted: results, conditions, the standard applied and the conclusion. The report carries CMA and/or CNAS marks according to its intended use—domestic acceptance and disputes usually need CMA; export and multinational clients usually recognize CNAS. If you are unsure which you need, ask before the report is issued; changing it afterwards means reissuing.
What you get
A formal report plus a plain-language summary of what passed, what failed and what the failure most likely means.
Stage 06 — After the report
A failed item is not the end of the project. We help locate the root cause—through cross-sectioning, SEM/EDS, X-ray or re-testing under adjusted conditions—and verify the corrective action once you have changed the design or process. The follow-up test is scoped to the changed item, so you do not pay again for the whole plan.
What you get
A failure analysis opinion and a remediation-verification plan with its own schedule and quotation.
Pre-submission checklist
- Standard numbers and revisions (or the OEM technical agreement itself).
- Condition levels and acceptance criteria.
- Sample quantity and unit state (engineering prototype or production unit).
- Report use and addressee—this decides which seal is applied and which entity is named.
- Special requirements (witnessing, photography, sample retention) stated up front.
Getting these five right before shipping saves far more time than any scheduling trick afterwards.
How mid-course changes are handled
Sample failures during testing, condition adjustments, or a change of report use are all normal. Changes are confirmed in writing: the adjusted conditions, additional work and schedule impact are spelled out in a confirmation note before execution—never "find out after it is done". Retest and remediation-verification scheduling follows the actual availability at that time.
