How should students submit laser-cutting files?

Question

Accepted Answer

Use one submission location and require a consistent package: editable source file, approved export, student or group name, class, version, final…

Use one submission location and require a consistent package: editable source file, approved export, student or group name, class, version, final dimensions, material request, quantity, operation notes, and deadline. The teacher should be able to distinguish a draft from a file approved for fabrication without opening several folders or message threads. Laser file submission package and status track Left: a card titled submission package with ten empty checkbox rows: editable source file, approved export, student or group name, class, version, final dimensions, material request, quantity, operation notes, and deadline. Right: a status track from needs review to approved to queued to complete, with an empty approved-by field under approved. An arrow from needs review goes down to return for correction and another arrow loops back up to needs review. Below a dashed divider, material approval is shown as a separate gate with the note: a clean file doesn’t approve a material. A final note says the submitted version is preserved so the result traces to the file reviewed. Submission package Editable source file Approved export Student or group name Class Version Final dimensions Material request Quantity Operation notes Deadline Status the teacher can see needs review approved queued complete approved by return for correction Separate gate Material approval A clean file doesn’t approve a material. Submitted version preserved: the result traces to the file reviewed. Abstract card and status track. Use one submission location and the same package every time, so a draft is never mistaken for a file approved for fabrication. Material approval runs on its own gate, because a technically clean file does not make an unknown material acceptable. Build a visible status into the system—Needs review, Return for correction, Approved, Queued, and Complete—and record who approved it. Keep material approval separate from file approval; a technically clean file does not make an unknown material acceptable. Preserve the submitted version so the physical result can be traced to the exact file reviewed.