If the record lives as a photo in a chat, the lot cannot be found when a customer asks. The paper on the clipboard already has the four lines that matter: a name, a lot, pass or fail, a signature. The first screen is those four lines. It is not a new philosophy of quality, and it is not a link to a laboratory instrument.
Who writes, and who closes
The writing role is the role that holds the pen today. On most plants that is the operator on the line or the quality technician. The role that closes a failure is a different one. Both are named in the scope. A shared password is out of the first release. Nobody closes their own failure under someone else’s name. HED Creative turns the signature line on today’s form into a role name.
The lot and the failure
The lot is the batch’s own number. It is not a nickname. The failure is the short code the line already uses. A new taxonomy is not written in the first release. If you cannot explain the code, the screen cannot either. A pass is recorded too. Writing only the failures makes it look as if the lot was never looked at.
The sheet a customer receives is not this screen. That sheet is a page on the site: certificate and sheet. A failure found in the field is not the technician’s job sheet: field work order. The code of the screen stays with the company under custom software.
Where the file lives
There is one home. If the ERP has a quality module and people use it, the record lives there and the screen reads it or writes into it. If the module is unused, this screen is the home. A second spreadsheet, a chat and an email are not the home. Two results in two places is silence when the customer asks.
Left out of the first release
A full quality suite, an instrument link, opening every analysis to the customer automatically, and rebuilding a module nobody uses are out. The first release makes the four lines of the paper findable by lot. The rest is a later decision.
The form to send
Today’s paper, where the lot number comes from, the list of failure codes, the role that writes and the role that closes. A code nobody uses drops off the list. Discovery in Berlin or Ankara picks the home from that paper. No paper, no screen.
Write the screen into the web app development brief. The first record that enters the ERP is a different decision: production record.