There have been more than a few conversations on getting completely away from drawings. I would suggest that you still supply a controlling document (drawing) showing a the external dimensions and a few holes dimensioned as well. If there was to be a scaling issue the vendor still has to comply with the drawing. If you supply models or DXF files many here have suggested that you also state that models or DXF files are for reference only.
The benefit is that drawing will have the properties you need going forward.
I agree, as I said in the OP, we send the DXF together with a reduced-standard/keypoint drawing. By this, I mean the drawing shows only those key points that are not clear from the DXF, such as tapped holes, weld information, surface finish, limits and fits, etc. plus some dimensions that establish the scaling.
However, such is the ingenuity of engineers (such as myself) and suppliers, we have still had instances of the Revision of the DXF not matching the Revision of the keypoint drawing, which leads either to confusion or scrap.
The question was aimed at trying to determine what methods others use to ensure these errors are kept to a minimum.
Could the issue come from a revision issue such as using revisions in the file name? I had contracted at a firm earlier in my CAD career where they never used a revision level noted anywhere except internally (SW files) and in the documentation supporting a build. I am speaking of a chassis containing a PC board, some external jacks, a chassis with holes for those jacks. There may have been other features but describing them would not add anything here.
At the retirement of that revision of the build they would have us (engineering) Pack&Go that release to a file. We could then use the existing files to build a new revision. Again a revision is never referred to in the file name. Only active releases are capable of being accessed from the prototype or WIP folders. Somewhere I have a macro that converts the current file to DXF (drawings), PDF and saves those to the Design Binder within the current SW document. (The files are also available individually and separately.) Using Pack&Go zips those file without additional actions. Of course it would be required to run the macro when finished editing any file so any available file is automatically the correct revision.
This did increase the SW file size but for security and convenience it was great.