Reports

What is it?

A report summarizes the results of a test sequence or an entire project as an immutable PDF document. Every report is versioned: creating a new one doesn't replace an existing report but creates a new version — the previous one remains as evidence. Before creation, a completeness check (preflight) inspects the underlying data and shows blockers (hard errors) and warnings.

How to use it

Fullscreen dialog: The generation dialog opens as a fullscreen popup — settings on the left, section order and the completeness check on the right, so both stay visible while configuring.
Pre-filled defaults: The dialog already starts with the defaults configured under Settings (organization or your own user defaults, see einstellungen) — scope, chart settings, grouping, and status filter don't need to be set again for every report.
Create a report: On the sequence or project page via "Generate report" or "Create new version". The completeness check shows in advance whether there's enough data (test steps, results, measurements) and lists open points.
Create as an interim report: If a test run is still in progress (open or unassessed test steps), a report can still be generated if the "Create as interim report" toggle is enabled. Open/unassessed steps then only appear as a note rather than a blocker. Missing measurements remain a hard blocker even in an interim report. Missing limits and invalid calibrations are never a blocker (see "Common issues" below) — they show up as a note in the report, whether interim or final. An interim report is clearly marked as "Interim report" in the PDF and in the report list.
Report ID: Every report has a unique ID printed small in the footer of every PDF page — for unambiguous reference, e.g., in inquiries or audits.
Test case overview: A project report shows one row per individual test case across all sequences — sequence, test case, execution period, and result. If the whole project runs against exactly one test object, its name is shown once above the table instead of in its own (then identical on every row) column; with several test objects, the column stays so each row remains traceable. The period shown is always the actual (as-run) execution period, not a planned date.
Test object overview: One table row per test object actually used in the project (the same set as the test object pages) with type, serial number, and the names of every sequence it was used in. Unlike the test object pages (below), this is a separate section that can be toggled and reordered via scope and drag-and-drop.
Test object page: For every test object actually used in the project (deduplicated across sequences), the project report includes its own page with master data (type, part/serial number), the properties configured on its test object type, and its photos (see pruefling). If the project runs against exactly one test object, the cover page also shows a compact summary (name, master data, first properties).
Equipment used: Shown directly at the relevant test case (with device, manufacturer/model where recorded, and calibration status), not in a separate appendix — the same applies to the test case definition (precondition, procedure, expected result), which appears there in its own frame.
Report list: Shows every report as a table row — document, source (sequence/project), version, kind (interim/final), created date, and status. While a generation is still running, the list refreshes automatically every three seconds.
Download: Via the "PDF" button in the report list.
Measurement charts with large data volumes: If a test case runs for hours at a one-second interval, a single channel can easily produce several thousand measurements. The report automatically reduces such series to a displayable number of chart points (min/max downsampling) without losing brief outliers or limit violations — keeping the file small and generation fast even with many channels/sequences in one report.

Mandatory content under ISO/IEC 17025 (clause 7.8)

Every sequence and project report contains the information the standard requires for a test report. Most of it is generated from the recorded data — if something is missing in the PDF, it is almost always empty at the source:

Item in the PDF	Where it comes from
Report no./report ID, "Page X / Y", "End of report"	automatic
Version, "Supersedes report …", reason for amendment	versioning + field in the generation dialog
Date of issue	time of generation
Location of testing	project → "Location of testing"; empty = lab address from Settings → General
Test method (standard incl. edition)	test case → "Test method / standard" (frozen for completed test cases)
Test conditions (e.g. temperature, humidity)	execution dialog → "Test conditions"
Received on, condition on receipt	chain of custody: the test object's "Received" event (date and note)
Measurement uncertainty U (k = 2)	test case → expected measurement → "U (k=2)"; frozen on evaluation
Decision rule (+ agreement)	project → "Decision rule"; the report states the rule actually applied
Results provided externally	execution dialog → "Performed externally by"
Deviations from the test method	deviations of type "Test execution" (see `abweichungen`); otherwise explicitly "none"
Information provided by the customer + disclaimer	project → "Information provided by the customer"
"Results relate only to the items tested"	automatic, "Notes" section at the end
Approval (name, date)	electronic approval, see below

In the project report this information is collected in the fixed section 1 "Test basis and conditions" right after the cover (regardless of the chosen scope); each test case additionally shows test method, test conditions and external provider in its detail table and the measurement uncertainty as a separate "U" column. In the sequence report it appears in the "Test basis and conditions" section, the uncertainty next to the measured value ("13.280 ± 0.05"), and externally provided results are marked "[external]".

Decision rule and evaluation: The rule does not only appear as text — it drives the IO/NIO evaluation itself. With "guard band w = U", a value is only IO if it lies within the limits by at least U. Rule and uncertainty are frozen on the result when it is evaluated — changing the project rule later does not re-evaluate existing results.

Approval, write protection and new versions

Approve: In the report list, click "Approve" on a completed report — interim reports can be approved too. Only admins and owners may approve ("Approve reports" permission); the support bot never can. Name and time are stamped into the existing PDF: an "APPROVED" note on the cover, name and date on the "Approved by" / "Date, signature approval" line (if the signature block is included) and a note in the footer of every page. The content is not regenerated — exactly the PDF you reviewed is approved.
Client portal: The portal shows only approved reports (see kundenportal). Internally, every completed report stays available via "PDF" so it can be reviewed before approval.
Write protection: An approved report cannot be deleted or approved a second time. The list shows "Approved" with a lock icon (tooltip: by whom and when).
Correction = new version: "New version" creates a new report that supersedes the last completed version. The dialog has a "Reason for amendment" field, which is required if the previous version is approved. The PDF states "Supersedes: report (version n)" on the cover and the amendment with its reason in the "Test basis" section. The superseded version remains unchanged.
Webhook: The report.approved event can e.g. notify the customer automatically (see webhooks).

Report design (whole PDF)

Under Settings → Reports → "Report design" section, you set the appearance of the entire report PDF — independent of the cover-page background described under "Cover page design" below. Three presets are available:

Monochrome: pure black/white, no accent color.
Monochrome with accent: like Monochrome, plus a freely chosen accent color (the "Accent color" picker) for headings and highlights. The accent color can only be set with this preset — it's disabled for the other two.
Classic: the original, more colorful report layout.

You can also toggle the density (Normal/Compact) — Compact reduces spacing and font sizes to fit more content per page. A live preview next to the settings shows every change immediately as a rendered PDF, before the next report is generated. The setting applies organization-wide to all future reports.

Cover page design (title page)

Every report's cover page (sequence and project reports) uses an A4 portrait background with six fixed fields positioned on top of it: lab/company name, report title, customer name, test object, date, and overall result. In project reports, the overall-result field is left empty — the result already appears larger in the result panel further down, which also shows the headline statistic (test case count, IO/NIO) as a sentence.

In project reports, the cover page also shows a separate, bordered "Report prepared for: " block with the full address, country, and contact person (name, email, phone) — regardless of whether the customer is linked via customer management or entered manually in the generation dialog (see "Customer details" below). The customer logo still appears at the top right of the cover page as before.

Default template: Without a custom file, the built-in template is used — mostly white, with a few subtle modern design elements (no company colors, so it fits any report design).
Upload a custom template: Under Settings → Reports, the "Title page background" section lets you upload a custom PDF (up to 8 MB). Only the first page of that PDF is used as the background; the six fields are placed at the same positions as on the default template — a custom template should therefore leave room in those spots (top-left/top-right header area and a clear area below it for the title and header data).
Remove: Via the trash button next to "Choose PDF" — the report then falls back to the default template.
Preview: The PDF preview in the "Report design" section shows the currently configured cover background as well.

Setting the scope (project reports only)

When creating a project report, the "Scope" section lets you define exactly what appears in the PDF:

Summary report: only the summary with a conformity statement — for a quick management overview.
Standard (default): summary, test case overview, test object overview, sequence/test case details, and measurement charts.
Full: additionally the "Nonconformances" appendix, raw-value tables for measurement series, and a signature block.
Custom: every section can be toggled individually — automatically activated as soon as a single section is changed manually.

Failed (NOK) measurement findings always appear in the report regardless of the chosen sections — a report can't hide failures, no matter which scope is selected. Test object pages and test case details (including equipment and test case definition) are likewise always part of the report whenever "Sequence/test case details" is enabled, regardless of scope.

You can also choose where test case execution photos appear: directly on the test case page (default) or collected in an appendix at the end of the report. Test object photos aren't affected — they always appear on their test object's page.

Filters (project reports only)

A project report doesn't always have to cover the entire project. The "Filters" section lets you narrow down the underlying data:

Sequence selection: only specific sequences instead of all.
Status: all results, only passed, passed + failed, or only failed.
Stations: only test runs at selected stations.
Test case overview grouping: order of the test case overview by sequence order (default), station, test object, date, or result.

There is deliberately no time-range filter anymore — sequence, status, and station selection are enough to narrow down the relevant test runs.

Important: the completeness check always refers to the currently selected filter selection, not the whole project — re-check via "Refresh" after every filter change.

Charts (project reports only)

Preview per measurement channel: the dialog shows a small chart preview (sparkline) for each measurement channel, matching the current filter selection — so it's clear before creation which measurement series actually end up in the report.
Adjust the time range per chart: "Adjust time range" on each preview lets you narrow, per channel, which measurement time range appears in that chart (and its raw-value table, if enabled) — useful for zooming into a slice of a single channel during a multi-day run (e.g. a fault period) without cropping the other channels or the rest of the report. Empty = the entire recorded range for that channel. Raw-value tables themselves are still toggled via the "Raw-value tables for measurement series" section under "Scope" — there's only the one option for that now.

Customer details

The "Customer in report" field is automatically pre-filled with the customer linked to the project (still freely editable). If the project has a linked customer, its name, full address, and contact person automatically appear in the "Report prepared for" block on the cover page, and its logo (see kunden) appears at the top right (see "Cover page design" above).

If the project has no linked customer, a full customer record (contact, email, phone, address, logo) can be entered directly in the dialog instead — these details then appear the same way in the "Report prepared for" block on the cover page of this one report, but do not create a new customer record or link one to the project. The logo uploaded there (PNG or JPG, max. 2 MB) also only applies to this report.

Freetext sections (project reports only)

"Add freetext" lets you insert any number of custom sections (heading + body text) into the report — e.g. for preliminary remarks, limitations, or a conclusion beyond the automatically generated sections. Freetext sections don't support formatting (no bold, no lists) — paragraphs only.

Section order (project reports only)

The "Summary", "Test case overview", "Test object overview", "Sequence/test case details", "Nonconformances appendix", "Signature block" sections, plus any freetext sections, can be freely reordered via drag-and-drop in the dialog's right column. The cover page, test object pages, and any photo appendix ("collected in an appendix") stay in their fixed position regardless.

Common issues

"I can't delete a report." It is approved — approved reports are immutable records. Correct it via "New version" with a reason for amendment.
"New version: 'please state the reason for the amendment'." The previous version is approved (so possibly already with the customer) — the standard then requires a reason. Fill in "Reason for amendment" in the dialog.
"I don't see an 'Approve' button." Only admins and owners can approve, and only completed reports that are not yet approved.
"The PDF is missing the test method / location / test conditions." The value is empty at the source (test case, project or execution, see the table above). Fill it in and generate a new version. Test cases without a test method are listed under "No test method specified".
"Why does the report state a different decision rule than the project?" The report states the rule the results were actually evaluated with. If the project rule was changed afterwards, re-evaluate the test cases or record the execution again.
"Creation is blocked." There's at least one blocker in the completeness check — usually open test steps or missing measurements. Either complete the underlying data or, if the run is still in progress, enable "Create as interim report".
"Why is my interim report still blocked?" Interim reports only allow open/unassessed test steps as an exception. Missing measurements remain a blocker — without them a test case can't be assessed, regardless of the report's status. Missing limits and invalid calibrations, on the other hand, are never a blocker, whether interim or final — they only show up as a warning in the completeness check and as a note in the report.
"My filter selection contains no test runs." The chosen sequence/station selection or status filter doesn't match a single test run, even though the project generally contains data. Loosen the filters or reset to "All".
"The report is stuck at 'Generating…'." PDF generation runs in the background; the page refreshes automatically. On a persistent error, "Error" appears with the stored reason and a "Retry" button. The support assistant can also query status and reason directly by report or project ID.
"Only a valid PDF file is supported." when uploading the cover background. The file is either not a PDF or can't be opened (corrupted, password-protected). Re-export it as an unencrypted PDF without a password and upload it again.
Custom cover background missing from the report. If the uploaded file was later deleted or is no longer readable, the report automatically and silently falls back to the default template — upload it again under Settings → Reports.