RE: QC checklist: prioritise observable faults over pixel hunting · RWI-03521
Home › Forums › News and General Discussion › New Members Area › QC checklist: prioritise observable faults over pixel hunting · RWI-03521 › RE: QC checklist: prioritise observable faults over pixel hunting · RWI-03521
January 7, 2019 at 10:07 am
#30504
Participant
Method note for “QC checklist: prioritise observable faults over pixel hunting”: use “Start with function, legibility, assembly and…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Keep the stated question separate from any broader claim.