When a drawing system is compromised, the first quality question is configuration: which revision was used, by whom, and can you prove it?
A practical route
Start with named accounts, least-privilege access, tested backups, and a change log for production-critical files. Review portals and outside processors as supplier risk. Include recovery in management review.
What good looks like
The process is visible at the point of work. The person doing the task knows the current requirement, the person approving it can see objective evidence, and the owner can tell whether the control worked. Keep the record small enough to complete in the moment: requirement, result, exception, owner, date, and next decision.
The failure mode to avoid
Do not solve a recurring process problem with a longer form alone. Watch one real job, find the handoff that breaks, and change the workflow or responsibility. Then sample the next few records to confirm the change stuck. The output should be a record someone else can verify. Use the planning module. to keep that chain together.