When outsourced drawings come back wrong, the instinct is to question the drafter. Often the honest answer is that the brief allowed the outcome. Briefing is a skill, and it is the single highest leverage thing you can improve.
Send intent, not just instructions
An instruction says move the wall 200mm. Intent says the corridor needs to be 1200mm clear for accessibility, so adjust the wall accordingly. The second lets a competent drafter get it right even when your dimension was slightly off, and lets them flag a conflict rather than faithfully drawing a problem.
This matters most across a time zone gap, where a wrong assumption costs a full cycle.
Make markups unambiguous
Vague markups produce vague work. Cloud the specific area. Write what should happen rather than what is wrong. "This is not right" costs a day. "Dimension should run to structural face, not finish" costs nothing.
Where you are unsure yourself, say so and ask for a query rather than a solution. A drafter told to use their judgement will use it, and it may not match yours.
Provide the reference material once, properly
Templates, standards, a good example set and any project specific conventions should be handed over at the start and kept current. Most repeat corrections trace back to reference material that was never supplied or has quietly gone out of date.
State the deliverable precisely
Be explicit about what you want back:
- Which sheets, at what scale, in what format
- Native files, PDFs or both
- Level of detail expected, particularly what is modelled versus drafted
- What is explicitly out of scope
- When you need it, and what depends on it
Say what the drawing is for
A set for planning, for permit, for tender and for construction differ substantially in emphasis. Telling the team the purpose lets them prioritise correctly. A drafter who knows a set is going to a plan reviewer will pay attention to the code summary and egress information in a way they would not for a client presentation.
Expect and welcome queries
A queries list at the start of a task is a sign of engagement, not incompetence. Answer them promptly and in one place. Teams that receive slow or scattered answers start guessing, and guessing is where errors come from.
Close the loop
When a set comes back well, say which parts were right. Feedback is usually only given when something is wrong, which teaches a team what to avoid but not what to aim for. Specific positive feedback shortens the learning curve considerably.
Ten minutes of proper briefing routinely saves a full revision cycle. It is the cheapest improvement available in the whole arrangement.