What's new

Search that forgives

• Diacritics no longer matter: „cisnadie” finds Cisnădie, in both
  directions — what you type and what is stored.
• A missing or wrong letter no longer returns nothing: „regin” finds
  Reghin. Matching is tolerant, done inside Postgres with trigram
  indexes — no external search service, nothing new to keep in sync.
• The closest match sits on top, not the alphabetical one — and exact
  matches always outrank the approximations: searching a document code
  like OF-2026-014, or a piece of it, still lands exactly.
• Tag search stays: „automotive” finds what is tagged automotive, not
  just what spells it in the title. People are found by their full name
  — „maria popescu” works even though no single column holds it.

The issues register travels

For the supplier whose product you tested, or for somebody upstairs
without an account: the issues register gained an Export button that
takes exactly what you see — current filters and search included — on
two roads.

• CSV with every detail in 24 columns, statuses and priorities
  written in words, dates in Romanian format, a link per row — opens
  clean in Excel.
• A printable report: your workspace logo and company identity in
  the header, the applied filters written as a sentence, a summary
  table, then one section per issue with every field, the description,
  the bug details and the attached images as thumbnails — other
  files listed by name. Every page carries „Made with ClarityQMS” in
  the footer. Internal comments stay home: they are the discussion, not
  the report.

Also in this update

• Five notifications about one document become one card with a
  sentence — „you were named Responsible, and 4 new comments — latest:
  «…»” — the bell counts subjects, not rows, and one click reads the
  whole subject. Requests addressed to you personally (approvals,
  confirmations, assigned tasks) always keep their own row.
• The approval request no longer routes itself back to an author who is
  also listed as Accountable, and the copy button on a document’s
  registration band copies the number and the date, as displayed.

Everything since 0.9.3, by module.

The app — news that announces itself

• A news bar under the top navigation whenever a release is published:
  one sentence with the release’s name, a link that lands on its own entry
  in this page, and an X. The dismissal is written on the user — it holds
  on every device — and somebody who joined after the release sees
  nothing: they have no news to catch up on. Release notes now carry a
  Romanian title too, and the bar speaks the reader’s language.

Processes — the diagram says what it needs

• Required qualifications on the turtle diagram: the People box now
  states what kinds of people the process needs, and how many — “2 ×
  Operator, 1 × Setter” — above the named people. The vocabulary is the
  account’s own role list, seeded with a sensible default on first touch
  and extendable in place; a published revision freezes the requirement
  as it was. That is the written answer to ISO 9001 7.1.2 and 7.2 a).
• The KPIs box links the real objectives: search the Objectives & KPI
  register from the process form and associate entries — the diagram then
  shows each one as a link with its target and the verdict of its latest
  measurement, live. No copy is stored: the association is the objective’s
  own process field, so there is one truth. Free text stays for
  indicators that are not in the register.

Documents

• The new document page left its experimental phase: the badge and the
  link back to the old format are gone, and the New menu offers one door
  to a document — the new page, first in the list. The classic page still
  answers at /clasic, unadvertised, until the cleanup.
• Text colour in the content editor — a fixed palette of ten shades
  plus “no colour”, the same in every document — and all six heading
  levels in one menu, each row drawn at the size it promises.
• “Obsolete” became “Withdrawn” (in Romanian: „Retras”) — and it is no
  longer a dead end: “Start revision” brings a withdrawn document back
  through draft and approval, and the confirmation says both what is lost
  and how it comes back.
• The deletion refusal names its holders: “PR-015 cannot be deleted: 2
  audits still use it (Internal audit 2026, IATF audit)” — the first three
  names, then “+N”. A number you cannot act on is an accusation without
  evidence.
• The RACI note is visible: the optional “what exactly does this
  person do here” note on an assignment now shows under each name on the
  document’s Responsibilities panel.

Projects

• APQP plan rows save in place: recording progress or signing a gate
  no longer reloads the page — the row, the phase percentage, the plan’s
  progress and the gate strip all move together, inline.
• The project register remembers you: arrangement, filters and search
  persist on the session like every other register; clearing really
  clears, and the board keeps its own remembered pipeline.

Commercial

• “Responsible” on offers means the RACI R: the board card and the
  list column show the responsible from the document’s RACI matrix, with
  avatar and short name, and the filter actually filters by it — all
  three used to show the creator.

Tasks

• One answer to “who confirms”: the header, the banner, the button and
  the notification now name the same person — the designated verifier, or
  the task’s author when the verifier ticked their own work — and a task
  closed by its last step notifies the confirmer too.

Production

• The maintenance lesson explains the arithmetic: what counts as a
  breakdown (correctives and failures only — preventive work never
  touches MTBF or MTTR), why one failure yields no MTBF, why MTTR averages
  only timed repairs, how availability and preventive-plan compliance are
  computed, and why a dash is more honest than a zero.

Everything since 0.9.2, by module.

Documents — the new document page

• A document is born from two fields — the kind and the name; the code
  it takes itself — and then it is written on its own page, one panel per
  subject: identity, scope, sections in the ISO sheet’s order, content,
  files, classification, parties. A closed panel says what it holds (“2 of
  3 filled in”, “No files”), the pencil — or a click anywhere on the body —
  opens it, and a panel sends only its own fields, so what you cannot
  see cannot be erased. That is where the lost “Definitions” fields came
  from: the long form sent everything on every save.
• Everything is inline. Saves, file deletes, reading assignments, stage
  moves, approvals, revisions — they land in the page with a confirmation
  pop, no reloads. The page carries everything the classic one had: the
  action menu, stages, the approval flow, mandatory reading, access, tasks,
  comments, related documents, the kind-aware breadcrumb, version and
  archive badges, review dates coloured when overdue.
• The new page is now the document’s page — every link in the product
  lands on it. The classic page stays whole at /clasic, linked from the
  top band, for what only it still has.
• The kind is picked from one three-tier list — the account’s templates,
  your recently used kinds, then all of them — with search that filters as
  you type, and Ctrl+Enter submits.
• A “Clean formatting” button in the content editor: text pasted from
  Word or Google Docs loses its alignments,   spacing, empty
  paragraphs and broken lines in one press — headings, bold, lists, links
  and tables stay, and one Ctrl+Z undoes it all. The editor’s toolbar now
  also stays stuck under the header while you scroll a long document.
• “Definitions and abbreviations” accepts a dash as well as the pipe, a
  migration re-reads what was already written, and the body no longer
  gains a layer of wrapping on every untouched save.
• Deleting a document something else still uses is a refusal in words —
  “an audit still uses it, in its scope” — not a server error.

Quality — calibration that cannot keep quiet

• “Active” never appears on a measuring instrument without a living
  calibration behind it. The status badge says the verdict instead: red
  “No calibration” when nothing is on file, red “Calibration
  expired” when the date has passed — in the register, on the card and
  on the instrument’s page. A due date typed by hand is a plan, not
  proof: it does not silence the alarm; only a recorded calibration does,
  or the last-calibration date filled in when taking over a history.
• The instruments that are not OK come to you — an audit caught us
  with them waiting in the register. They open the daily email (their
  own section, first, in red), stand on the front page under “Needs
  your attention” and in the Quality band with their own tile, and the
  Calibration card on the Quality panel names them in its sentence:
  “N with no calibration at all”, ahead of the overdue. Each goes to its
  responsible; the ones nobody owns go to whoever can manage the account.
• The attention counters above the register are now links to their own
  filtered list, and the due filter offers “No calibration”.
• The breadcrumb on a calibration or MSA page led to a page that does not
  exist (/equipment/<the study's id>); it leads to the register now.
• An objective is judged on the year: a wide band with the year’s
  average against the target — written in points, not percent — one row
  per earlier year, a deviation column on every measurement with the sign
  and the colour answering “which side, and is that side good here”.

Production

• MTBF and MTTR per machine: the “Per asset” report in the maintenance
  register answers “which machine holds us”, row by row, with the same
  honest rules as the aggregate — MTTR only from breakdowns with downtime
  recorded, MTBF only where there were at least two. Each asset’s page
  opens its history with its own reliability figures for the last year.
• Correcting a record no longer loses its files: attachment assignment
  used to replace; now new files are added alongside, and the edit form
  shows what is attached with a per-file delete. Maintenance records and
  capability studies got the house upload zone.

Commercial

• A closed offer can be put back on its flow: rejected, expired or
  accepted-too-soon returns to discussions with the decision date cleared;
  a cancelled one returns to draft. Only the converted stays shut — the
  way back belongs to its contract. Contracts reopen from every end:
  terminated and expired return to force, cancelled to draft.
• Offers that sat in “Draft” on the board while their page read
  “Converted” tell one story again: the quick-add form no longer offers a
  status for workflow kinds, and a migration realigned the rows already
  split.

Projects

• A project is visible to the whole company; the ones that must stay
  closed say so in their form. Seeing is not editing: outside the team the
  page comes without buttons, and a forced address is told why. The
  register gained a “Mine” filter, stage filters grouped by pipeline, five
  icons for projects that are not from the factory floor, and the page
  leads with the work — tasks above the files.

Processes

• The map shows the process performer — R of RACI — and “No
  responsible” where nobody is named. Core processes are ordered by
  dragging, and the arrows appear only after somebody has ordered
  them: a sequence drawn from creation order was a lie drawn with
  confidence.

Tasks

• “Add a task” on any record’s page opens a form in place — title,
  responsible, due date — and the task is born already tied to that
  record. A task from an audit finding asks for its effectiveness
  confirmation on the short path too.

Problems

• Supplier complaints: what we complained to a supplier about, as its
  own register; a nonconformity names its supplier and offers “Complain to
  the supplier” with the chain already filled in.

Registration and trial

• The 14-day trial runs on every new workspace, with morning emails that
  can be stopped from one link; the demo is one per industry, in both
  languages, switching on the modules that trade actually needs; sample
  data is swept from one page in Settings that says beforehand what stays.

Everything since 0.9.1, by module.

Production — parameter sheets and setups

• Parameter sheets (Production › Parameter sheets, and on every mould and press). The recipe: how the press is set for a part with a mould — every value with its unit and, where it matters, its tolerance. The sheet is drawn from a template that mirrors the factory’s form: part, mould, machine, material, injection parameters (three steps each), quality parameters (value ± tolerance), barrel temperatures by zone, hot runner, tempering, notes. What the mould and the machine already know — cavities, brand, model — is filled in before you start.
• A sheet is a draft until a manager approves it; in force, the hall sets to it and it is not edited — a new revision replaces it when approved, and the old one stays readable because the setups done to it point at it. Print for the hall carries code, revision and approver, with a red warning on anything not in force.
• Templates live in Settings › Parameter sheet templates: sections and fields, editable as YAML with the structure checked. A second machine family is a second template, not a change of code.
• The existing Excel sheets are read by their labels, not their row numbers, so the forms that differ by two rows import the same.
• Setups (IATF 8.5.1.3, 8.5.1.4), on the press: date, shift, reason (mould change, material change, job change, after a stop, restart), the mould mounted — the moulds of compatible projects first — the sheet in force taken automatically, who set up, and what was set differently from the sheet and why. Then quality’s word: the people named in Settings › Maintenance › Who validates the first piece are notified and say conforming — start the run or non-conforming; whoever did the setup does not validate their own piece. The last piece closes the run. Setups still waiting are on the Production panel: production on trust until somebody says yes.

Production — the mould as a tool, the press as a process

• Tool changes (IATF 8.5.1.6 e, f): every design change made to a mould — a cavity rebuilt, a vent closed — with the date, the new change level (drawing index), who approved it, the quality Change it went through and the updated drawing. The current level sits in the mould’s header. Cleaning and servicing are not changes; the page says so.
• Capability (IATF 9.1.1.1), on the press: characteristic, Cmk / Cpk / Ppk, the index, a verdict at the automotive thresholds (1.67 capable, 1.33 acceptable), the mould used, the report attached, and the next study — a year out by default. The panel lists machines never studied, overdue, or below the mark.
• Maintenance objectives (IATF 8.5.1.5 e): targets for MTBF, MTTR, availability and preventive plan compliance — a figure computed for the first time: of the preventive work that fell due, how much was done by its date. Set once in Settings › Maintenance; the indicators wear the target and the verdict.
• Maintenance in the management review: each figure against its target, then what wants a decision — overdue interventions, plans not reviewed in a year, key equipment without spare parts. A plan carries the date and name of its last review; “Mark as reviewed today” is in its menu; the ones a year past are on the panel.
• The production counter has its own box on the mould’s page: where it stands, the last ten entries with who wrote them, “Add counter entry”, and the whole ledger on one page with a running total. A wrong entry is corrected in place — the mould’s History shows the mistake and the fix, each with a name. The counter can also be added from the mould register.
• The mould’s maker is a party from the register — the toolmaker — or in house, never both.
• Every new box explains itself on the page — what goes there, what does not, why the auditor asks — with a link to Learn. Learn has a new page for moulds, with a table of what the auditor asks and where the answer is, and new sections on key equipment, capability, and parameter sheets and setups.

Projects

• The team comes first on the project page. A project says what it carries — has an APQP plan, has moulds and machines — and shows only those panels; a mould linked, a machine linked or a plan created switches the panel on by itself.
• The project’s header links to the record it came from — the improvement, the complaint, the nonconformity, the 8D report that named it.
• The register filters by stage, grouped by pipeline, and opens on all stages.
• The daily and weekly digests remind you of projects: the ones you are on — any role — past their deadline or due within the week, and their milestones.
• A project knows when it finished and by how much against the estimate: a completion date and a closing note, the deviation in days in the header and on the card; a cancellation needs a reason. Finished projects older than 30 days fold behind a link on the board.
• A task can be linked to an improvement from its form.

Commercial and documents

• Unit prices on offers and contracts have four decimals — a moulded part is quoted at the fourth; 0.04 instead of 0.0375 on 200,000 pieces is a thousand euros.
• An offer or a contract opened from its register goes back to that register, with its filters, not to the document register.
• The × in a search box clears the word from the register’s memory too.

Fixed

• Native controls — the calendar icon in date fields — follow the app’s theme, not the system’s; no more white on white.
• Attention boxes on the panels carry the true total, not the five rows they show.

Under the hood

• Three new tables for parameter sheets, their templates and setups; new columns for tool identity, key equipment, project scope switches, plan review dates; join table for a project’s compatible machines. Every migration runs on deploy.

Everything since 0.9, by module.

Improvements

• The same four roles as a task — proposed by, accountable, assignee, verifier — with a stamp on every step: who approved, who finished, who verified, who closed. Only the people named on it (and managers) can move it, nobody verifies their own work, and “send back” returns it from verification.
• A “Next step” box under the title says what the step means, whose it is, and shows the one button — or “Waiting for Maria P.” when it is not yours.
• Measured effect: indicator, unit, baseline, target, achieved. The record gives the verdict itself — target met / below target — reading the direction from baseline → target. IATF 16949 §10.3.1 a asks for a number, not a sentence before and after.
• Two new types, variation reduction and waste reduction, in the words of §10.3.1 b.
• A source: an improvement opens from the record that started it — a nonconformity, an audit finding, a complaint, a risk, a quality objective, a management review decision, a maintenance intervention — with a link back. Each of those pages shows an “Improvements” panel.
• Notifications on every step, to whoever is next; managers are told about a proposal that has no accountable person yet.
• The management review report lists the period’s improvements with their targets, not just four counters, and every decision can open an improvement with the decision as its source.
• Print the record as an internal sheet, with the measure and the step signatures.
• The register remembers your filters between visits, like problems and offers already did.

Production

• Key equipment and spare parts (IATF 8.5.1.5). A machine can be marked key; a key machine keeps a list of spare parts — part, code, how many should be on the shelf, how many are, where, from whom. A key machine without a list, or with a part below its minimum, shows up on the Production panel with the part named.
• A mould says whose it is, why it is stopped and how it is kept (IATF 8.5.1.6): ownership (own / customer / supplier), a permanently marked checkbox ticked after the mark was seen on the steel, a reason and a date when it leaves production, storage instructions. Quarantined is a tool state only; the register filters by owner; the panel lists quarantined moulds and customer tools without a confirmed mark.
• Maintenance plans belong to the company, applied to as many machines as run them; each application keeps its own counter, start date and person in charge. No more eight copies of the same revision.
• Moulds count parts, not shots, have a customer, and Location is our own shelf. A mould belongs to a project, and a project names its presses.
• Attention boxes on the panel carry the true total, not the five rows they show.
• Production has the same shape as the other modules: a panel with cards, registers with filters, the common header.

Tasks

• Three people on a task: who is accountable, who does it, who verifies. Nobody verifies their own tick.
• The register shows everything that is yours, in any role, including a step on somebody else’s task; the daily digest does the same.
• Duplicate a task: what has to be done and with whom travels — title, details, the three people, deadline, priority, steps, files; how it went does not.
• The Tasks panel is also on audit findings; a task born from a risk, a finding or a nonconformity opens with “requires confirmation” ticked. Project cards count open tasks, red when one is overdue.
• The register remembers your filters between visits.

Documents

• Related documents are linked from the form again, laid out in columns like the rest, and no longer lost on save.
• A document with many files shows five and folds the rest behind “Show all 30 files”.
• Duplicating a document makes a new record, not a copy of the old one’s history.
• Document review really notifies someone.
• Template and visibility sit next to the kind; the record line is one row, with a copy button; the table of contents tells the truth.
• A maintenance plan points at its procedure instead of rewriting it.

Commercial and third parties

• “Everything we have with this company”: a party filter in the register, and the party’s page leads to it. The filter sees contracts and offers, not only document links.
• Where every contract and every offer stands, on its own row; “contract with” saves; unclassified can be chosen without the save failing; long filter lists can be typed into, not only scrolled.

Fixed

• A member without rights could delete an 8D report — and got an error page while the report vanished. Now refused.
• An issue could be assigned to any user in the system; now only to a member of the workspace.
• A task, an improvement or an 8D could point at a record from another workspace as its source. Now refused.
• Two people creating records in the same second could get the same code (NCR-2026-0042 twice). Now they cannot.
• A % or _ typed into a search box was read as a wildcard; now it is looked for as a character.
• On a board the status filter is ignored everywhere — the columns are the statuses — instead of in six registers only.
• A refused deletion on a nonconformity or a complaint lands you back on the record, not on the dashboard.

Under the hood

• The app loads far less JavaScript: 0.7 MB instead of 8.2 MB, with diagram support fetched only on pages that draw one.
• The date picker no longer depends on a third-party CDN, so it works offline and behind strict networks. One stylesheet instead of five.
• The old rich-text editor (Trix) is gone; TipTap has been the editor for a while.
• Branding: iConsult is out, Eventya is in, and support is at support@eventya.net.

What we have shipped lately:

• Customer complaints module — record the complaint, link it to an NCR and an 8D, follow the actions to closure.
• Audit trail on complaints, NCRs and 8D reports — every change stays in the history, with author and date.
• APQP plans — phases, activities and phase reviews, started from templates.
• Offers — a commercial pipeline with line items, quantity tiers and a funnel report.
• Contracts — an expiry date derived from the terms, and reminders before it.