Every outsourcing provider will show you a portfolio of attractive images and quote a competitive rate. Neither predicts what you will receive. The variables that actually determine outcome are process variables, and they are visible only if you ask about them specifically.
These twelve questions, asked before commitment, will separate a partner you can build a relationship with from one you will replace in six months.
1. Who exactly will work on our projects, and will they stay?
Ask for names, experience, and role. Then ask what happens to that team between your projects, and whether the same people return.
Continuity is the strongest single predictor of quality over time. A partner who rotates whoever is free onto each job will never accumulate knowledge of your standards, and you will re-teach the same lessons repeatedly. A partner who can name a stable team, and explain how they retain them, is offering something materially different.
Follow-up: what is your staff turnover, and what happens if our lead resource leaves?
2. Will you work in our template from day one?
The correct answer is yes, without qualification.
A partner who works in their own environment and migrates content at the end will deliver files carrying duplicated families, broken view templates, non-standard layers, and purge problems. You inherit all of it.
Follow-up: how do you handle a template you have not used before, and what setup time do you need?
3. Show us your standards documentation.
A capable partner has internal documentation: modeling conventions, QA checklists, naming standards, and file management protocols. A partner without it is relying on individual habit, which does not survive staff changes or scale.
Ask to see the actual documents, not a description of them.
4. What is your quality control process, and who performs it?
The distinction that matters is whether checking is independent. A partner where the person who drew the work also checks it has no quality process — self-checking catches perhaps half of errors, consistently.
Ask what the checker's seniority is, what checklist they use, and whether the check is recorded.
Follow-up: what happens when the check fails? A partner who cannot describe a rework process has not had one.
5. How do you handle unclear information?
The answer separates two very different partners.
The good answer: we raise a formal query, log it, continue with unaffected work, and do not proceed on assumption.
The bad answer, in various phrasings: we use our judgment and keep going.
Ask for their query log format from a live project. A partner who raises queries is thinking; a partner who never raises any is guessing, and you will find out where later.
6. How and how often do we see work in progress?
Weekly delivery with nothing in between means errors compound for five days. Daily upload to a shared environment costs nothing and catches drift immediately.
Ask what environment they work in, whether they can work directly in your CDE, and whether they will publish daily.
7. What are your data security arrangements?
For work on government, healthcare, defence, financial, or data centre projects, this may be contractually determinative.
Ask specifically about: access control and authentication, device policy and whether personal devices are used, physical security of the delivery floor, removable media policy, whether work can be confined to a client-controlled environment, subcontracting policy, and deletion obligations at project close.
Follow-up: do you hold any information security certification, and what does its scope actually cover? Scope matters more than the certificate.
8. Do you subcontract any of the work?
A partner who subcontracts without disclosing it has broken the chain of accountability, and every other answer in this list becomes unverifiable. If they do subcontract, that must be disclosed, and the same questions apply to the subcontractor.
9. What does your pricing actually include?
Establish, in writing:
- Whether revisions are included and how many rounds
- What constitutes a revision versus a change of scope
- How queries and coordination time are treated
- Whether project setup and onboarding are charged
- What happens if our information is late or changes
- Overtime and expedited work rates
Rate comparison without this is meaningless. The cheapest quoted rate frequently becomes the most expensive delivered cost through revision charging.
10. Can we run a paid pilot?
This is the single most informative step available, and a confident partner will welcome it.
Structure it properly: one defined package — a building level, a submittal set, a zone — with a real brief, your template, and your standards. Review the delivered work against your normal acceptance criteria.
What the pilot reveals that no interview can: whether they read the brief, whether they raise queries, whether the file is clean, whether the standards were followed, and how they respond to review comments. The last is particularly informative — a partner who accepts correction constructively and applies it consistently across the rest of the work is one you can develop.
11. What are your hours, and what is realistic turnaround?
Time zone difference can be an advantage or an irritation depending on how it is managed. Establish:
- Working hours and overlap with yours
- Guaranteed response time to a query
- Realistic turnaround for a standard package
- Availability for a live call, and how often
- Holiday calendar — regional holidays that will affect availability
A partner offering four hours of daily overlap and same-day query response is offering a different service from one with none.
12. Give us two references on work like ours.
Ask for clients with similar project types, similar scope, and a relationship longer than a year. Then ask those references specific questions:
- How many revision cycles does a typical package take?
- How do they handle errors?
- Has the team stayed consistent?
- What went wrong, and how was it handled?
The last question is the useful one. Every relationship has a failure at some point; how it was handled tells you more than a list of successes.
What to watch for
Rates far below the market. Sustained under-pricing is funded by junior staffing or by revision charging. Neither is what you want.
Portfolio without process. Beautiful images and no answer on QA or standards.
Reluctance to pilot. A partner confident in their delivery will take a paid pilot without hesitation.
No queries during the pilot. Real projects contain ambiguity. Silence means assumption.
Overpromising on capacity. "We can put twenty people on it next week" is rarely true and never good news about how the existing twenty are deployed.
Setting the relationship up
Once selected, the first month determines the next three years. Provide the template, the standards documentation, and a written brief. Name your review owner. Run a pilot. Give structured feedback rather than corrections applied silently. Establish the exchange rhythm and hold it.
A partner given clear standards and honest feedback will improve. A partner given a thin brief and silent rework will not, and the relationship will be judged a failure that was largely avoidable.
Structuring the agreement
Once a partner is selected, a small number of contractual points prevent most of the disputes that follow.
Scope definition by deliverable. Not "BIM support" but sheets, models, packages, or hours, with the level of development or standard stated.
Revision and change treatment. How many rounds are included, what constitutes a revision versus a change of scope, and how changes are priced.
Service levels. Query response time, turnaround for a standard package, and escalation contacts.
Intellectual property and data. Who owns the delivered work, what the partner may retain, portfolio use rights, confidentiality, and deletion obligations at project close.
Security obligations, matched to the sectors you work in, including subcontracting prohibition where relevant.
Continuity commitment. Named personnel, notice of changes, and handover obligations if a resource changes.
Termination and transition. Notice period, and an obligation to deliver work in progress in native, workable form. A partner who cannot cleanly hand back an incomplete project is a partner you are locked into.
Insurance. Professional indemnity appropriate to the work, verified rather than assumed.
Managing the relationship over time
Selection matters less than management. The practices that produce good long-term outcomes:
A regular structured review. Quarterly, covering quality trends, review effort, recurring issues, and upcoming workload. Not a complaint session — a working discussion.
Consolidated, explained feedback. Corrections applied silently teach nothing. Feedback that explains why a standard exists is applied consistently thereafter.
Forward visibility of workload. A partner who knows a large package is coming in six weeks can resource for it. One told on the Monday cannot.
Investment in their knowledge of you. Sharing completed exemplar projects, standards updates, and the reasoning behind detail preferences compounds over years.
Honest escalation, early. A problem raised in week two is a conversation. The same problem raised in month four is a grievance, and it usually could have been fixed.
The firms that get the most from outsourcing treat it as a capability they are building rather than a service they are buying, and the difference shows within a year.
Frequently asked questions
How long should evaluation take? Interviews and reference checks take a week or two. A pilot package takes two to four. Compressing this to award a large scope on a portfolio review is the most common way firms end up disappointed.
Should we use more than one partner? For specialist scopes, often yes. For core production, a single partner with continuity generally outperforms split volume, because the learning accumulates in one place.
What if the pilot is mediocre? Distinguish between standards comprehension — which is teachable — and technical capability or attention to detail, which is not. A pilot that followed the standards but missed detail is a different signal from one that ignored the template.
Related reading: In-House vs Outsourced Drafting: The Full Cost Comparison · BIM Outsourcing: A Practical Guide for AEC Firms · DWG File Management for Distributed Teams
Vantage CAD Services works to client standards and templates, with named continuity teams, independent checking, and paid pilot packages. Contact info@vantagecadservices.com or +1 (512) 543-0831.