Skip to content
    QC & analytics

    From the reading to the released report — and back into the control chart

    Results are checked against the stored specification, verified by a second person and linked to method, instrument, standard and analyst. Anything out of spec goes into an OOS investigation instead of an email, and control samples land in the control chart instead of a spreadsheet.

    14-day trial · EU-hosted

    labnote.light / arbeitsliste · wl-2026-118

    What QC & analytics does

    Method catalogue

    Test procedures with standard, validity, parameters, matrices, instruments and authorised staff — the choice on a sample comes from this catalogue.

    SOPs and scope of accreditation

    Standard operating procedures with owner, deputy and revalidation date; accredited procedures and a flexible scope stay traceable.

    Method validation

    Validation and verification plans with characteristics such as trueness, precision, LOD and LOQ, the outcome and revalidation reminders.

    Specifications and decision rule

    Limits per parameter and matrix; results are automatically flagged pass, fail or OOS — with or without subtracting the measurement uncertainty.

    Worklists

    Plan runs, schedule samples, assign instrument and analyst, attach raw data — instrument status is checked before the run.

    Measurement uncertainty

    A budget per method with individual contributions and the expanded uncertainty; the value can be shown on the report.

    Control charts, standards and proficiency tests

    Control samples with warning and action limits, a trend view over time, reference materials with expiry and proficiency results with z-scores.

    Stability, retention, environmental monitoring

    Stability studies with time points and storage conditions, retention samples with a deadline and monitoring points with a plan — samples are created when they are due.

    Sampling plans

    Recurring sampling with points, interval and test scope; intake including the test plan is created from it.

    OOS investigation

    Investigation with root cause, action and effectiveness check, linked to the sample, the run and the deviation.

    Test report, CoA and release

    Report templates per customer, amendments with version history, release with electronic signature — including batch release across QC and bioprocess.

    What the workflow looks like

    1. 1

      Define the test plan

      Assign methods and parameters from the catalogue to the sample; specification and uncertainty come along.

    2. 2

      Measure and record

      Work through the worklist, run the control sample along, attach raw data, enter the result — instrument status is checked.

    3. 3

      Verify and investigate

      A second person verifies, anything unusual goes into an OOS investigation with root cause, action and effectiveness check.

    4. 4

      Report, release, trend

      Release the report or CoA with a signature; control values feed the chart and KPIs feed the trend view.

    Why LabNote.Light

    • Result, method, instrument, standard and person hang off one record — no reconciling lists
    • Measurement uncertainty and decision rule are part of the report, not a side calculation
    • Control charts, proficiency tests and stability live in the same module as routine analysis
    • Every release recorded with time, author and signature

    Frequently asked

    Can we attach raw data from instruments?

    Yes, as a file on the run or the result. Values can also be imported via CSV or pushed through the REST API.

    How are out-of-spec results handled?

    Results outside the specification are flagged and can be moved into an OOS investigation with root cause, action and effectiveness check.

    Can test reports match our layout?

    Yes, through report templates with your own letterhead; amendments create a new version referencing the previous one.

    How do we cover scope of accreditation and SOP revalidation?

    Standard operating procedures carry an owner, a deputy and a revalidation date; parameters can be marked as accredited, and changes to the scope are recorded with person and time.

    Where do warning and action limits come from?

    They are stored per control sample and method — either calculated from previous periods or set manually. Breaches show up immediately in the chart and can be turned into an investigation.

    Do stability and retention plans create samples automatically?

    Yes. Time points, storage conditions and test scope live in the plan; samples with a test plan appear when due, retention periods run alongside and disposal is documented.

    Security & Compliance

    Built into every plan, not bolted on

    GDPR, ALCOA+, and the hash-chain audit trail ship with every LabNote.Light plan — no add-ons, no surcharge, EU-hosted.

    AVV
    ART. 28 GDPR
    EU-Hosting
    DE/NL CLUSTER
    E-Signatur
    WITH HASH CHAIN
    ALCOA+
    DATA INTEGRITY
    §16
    GEFSTOFFV (DE/AT)
    Hash-Kette
    TAMPER-EVIDENT

    Try it with your own data.

    14 days, every module switched on, no credit card, cancel anytime.