Keep the drawing reference attached to the request

A request can contain a product reference, a drawing filename and a later email attachment. If these are treated as unrelated information, staff may review the wrong material while believing they have the latest version.

Use an explicit reference

For a Czech business receiving technical inquiries, agree how the customer identifies a drawing or specification and its revision. The request record should preserve that reference with the supplied file rather than relying on its position in an inbox.

Define the changed-file case

Imagine a fictional customer sending a revised drawing after staff have begun reviewing the first one. The system should make the replacement visible and identify which decision needs attention. It should not silently change the material associated with an earlier reviewed proposal.

Keep technical approval with the right person

The website can organize information and help route a request. It cannot establish that a drawing is suitable, safe or professionally approved. The business's qualified reviewers define the actual technical decision and required records.

Check the whole handover

Use two synthetic files with clearly different revision labels. Submit, replace and review them. Ask staff which file they believe is current and whether the earlier context remains understandable.

OWASP's file-upload guidance covers technical controls that need implementation-specific review. The document's engineering meaning is a separate matter. Include both the customer and staff views when commissioning a document portal.