Civil engineering outsourcing · Process playbook
The firms that get the most from outsourcing are rarely the ones with the best vendor. They are the ones with the best process. A CAD lead who sends a clean handoff package on a Tuesday evening and finds reviewed sheets on Wednesday morning is running a system, and that system can be learned. Below are the seven steps in outsourcing civil engineering that we have refined with U.S. and Australian firms since 2016, including the parts that only matter once the first package is done. If you are still weighing whether to outsource, our civil engineering outsourcing page explains the service itself.
The steps in outsourcing civil engineering are: define one package with clear scope and decision owners; choose a partner on evidence rather than rate; transfer your standards and templates; set a communication rhythm that fits the time difference; agree the review and handoff protocol before work starts; run the first package and measure it; then decide deliberately whether to scale. Most failures trace back to skipping step 3 or step 5.
01 · Define
Step 1: Define one package, not a relationship
The most common mistake is to start by outsourcing “drafting support” in general. A partner cannot deliver a general idea, and you cannot evaluate one. Start with a single package that has a beginning and an end: the grading and drainage plans for one subdivision phase, the utility sheets for one commercial site, the Civil 3D surface and corridor model for one roadway segment.
For that package, write down four things. The deliverables, by sheet or model element. The inputs you will provide: survey, base files, templates, previous submittals, agency comments. The standards that govern the work, including which jurisdiction’s details apply. And the decision owners: who on your side answers a design question, who approves a change, who signs off the handoff. A one-page scope with those four items is worth more than a twenty-page master services agreement without them.
If you are unsure whether the work should be outsourced at all, the capacity diagnosis in The AEC Capacity Decision helps separate production bottlenecks from judgment bottlenecks. Only the first kind belongs in this process.
A defined package gives both sides a fair test and gives you a clean exit if the fit is wrong.
The rule behind every step
Start with one defined package. It gives both sides a fair test and a clean exit.
Scope, standards and decision owners on one page do more than a twenty-page agreement without them.
02 · Select
Step 2: Choose the partner on evidence
Ask for things that can be checked. Which quality management standard is the firm certified to, by whom, and can you see the certificate? How many engineers hold Autodesk Civil 3D credentials, and how is skill maintained after hiring? Which clients will speak to you, and for how long have they worked with the firm? What does review look like, step by step, and who signs each step? How is data access controlled, and which software licenses cover the seats that touch your files?
Then ask the question that separates partners from vendors: what happens to project knowledge when one of their engineers leaves? A firm with an answer has thought about continuity. A firm without one is selling hours.
We published a seven-question scorecard for this stage in How to Evaluate an Engineering Outsourcing Partner Beyond Hourly Rate. Use it on us as well as on anyone else; our own answers are on the Engineering Credentials and Trust & Compliance pages.
03 · Transfer
Step 3: Transfer your standards before the first sheet
This is the step firms skip, and it is the step that decides whether the first deliverable looks like your work or someone else’s. Before any production starts, hand over your CAD template, title block, layer standard, text and dimension styles, sheet naming convention, and two or three finished plan sets that represent your best work. Add the agency details and checklists you use most, and a short list of the review comments you find yourself writing on every project. That last item is gold: it tells the partner what you care about before they have made the mistake.
If your firm does not have a documented standard, say so. At AXANH we can build a template, title block and layer standard from scratch and hand it back as yours, which has become a side benefit of outsourcing for several smaller firms. Either way, the partner should confirm receipt of each item and list the open questions in writing; that list becomes the first agenda.
Technically, the transfer runs through your Civil 3D environment. Our engineers work from the client’s templates and drawing settings so that surfaces, pipe networks, corridors and sheet sets rebuild cleanly on your side. We describe that discipline on the Civil 3D outsourcing page.
04 · Communicate
Step 4: Set a rhythm that fits the time difference
Ho Chi Minh City is 11 to 12 hours ahead of the U.S. East Coast and 14 to 15 hours ahead of the West Coast; for Australian firms the overlap is most of the working day. ACEC’s Q2 2026 sentiment study found 84% of U.S. firms carrying at least one open position, and running production across two time zones is one way firms keep delivery moving while they hire. The time difference becomes an asset when the rhythm is designed and a liability when it is left to chance.
The rhythm that works for most of our U.S. clients has three parts. An end-of-day handoff from the client: files, instructions and any decisions made that day. A question log kept by the partner, updated as issues arise, so nothing waits for a meeting. And a short overlap window, agreed at the start of the engagement, for the questions that need a conversation. A weekly call covers priorities and anything the log could not resolve. With Australian clients the same structure compresses into the shared day.
Two rules make this work. Questions are raised when they arise, not batched until handoff, because a question about the design intent of a swale costs minutes on Monday and days on Thursday. And every question goes to a named decision owner from Step 1, not to “the client”, so answers come from the person entitled to give them.
05 · Review and handoff
Step 5: Agree the review and handoff protocol in writing
Before the first sheet is produced, both sides should know what “done” means. On the partner’s side, that means a defined internal review: at AXANH, every package passes Self-Check by the engineer who produced it, Peer Review by a second engineer, and Manager Review for packages where scope or risk calls for it. That system is certified to ISO 9001:2015 and described in Engineering Review Process.

On the client’s side, the engineer of record stays in responsible charge. Under NSPE’s position, that means involvement from concept through completion, not review after the fact. A good protocol therefore puts your engineer at the decision points during the work, with the partner’s handoff notes recording every decision, assumption and open item so nothing is discovered at the 90% set.
Write down the handoff package too: which files, in which format, with which naming, plus the notes. A handoff that arrives as “here are the drawings” generates a review cycle; one that arrives as “here are the drawings, the three assumptions we made, and the two questions still open” generates a decision.
A written review and handoff protocol is the single strongest predictor of a first package going well.
06 · Run and measure
Step 6: Run the first package and measure what matters
Then do the work. During the first package, resist the urge to add scope; the point is to learn how the partnership behaves under a known load. Measure four things, simply.
Turnaround
Delivery against the agreed dates, package by package, so you can see whether the rhythm from Step 4 is holding.
Review comments
How many comments your team writes on the handoff, and how many of them repeat from one package to the next.
Questions asked
How many questions the partner raised, and whether they were the right ones, asked early enough to matter.
Management hours
What your side spent, counted in full. This is the real cost of outsourcing, and the number most firms never track.
At the end, hold a short review with the partner. Which standards were unclear? Which questions could have been avoided with a better transfer in Step 3? What should be added to the client-specific SOP? We treat that SOP and the list of recurring review comments as living documents that carry forward to the next package; it is the mechanism by which the second project starts further ahead than the first.
07 · Scale
Step 7: Decide deliberately how to grow
If the first package worked, the next decision is the shape of the relationship rather than just more of the same. Three shapes are common. Repeating defined packages, which keeps every engagement bounded. Dedicated engineers who work only on your projects and build deep familiarity with your standards. Or a managed delivery unit that takes ownership of a workflow, with its own lead and review inside the partner’s team. Each shape asks something different of your firm: more scoping effort, more integration, or more trust in the partner’s management.
At AXANH those three shapes are a defined package, dedicated engineers, and the AXANH Design Pod™, a managed unit with a lead engineer and review built in. Most relationships begin with the first and move to the second or third once the operating fit is proven; the move is a decision taken together, usually after two or three packages, not a default. The models and what each asks of the client are compared in Partnership Models, and the readiness questions are in Partnership Fit.
08 · Streamlining
How the process gets faster from the second package on
Firms searching for a streamlined outsourcing process usually mean one thing: less management effort per deliverable. That comes from compounding, and it has four sources.
The client SOP grows
Every package adds to it, so fewer questions need asking.
Review comments become a checklist
Recurring comments turn into a pre-handoff check on the partner’s side.
The team stays the same
Project context does not restart with each package.
The handoff becomes a template
Files, notes and open items arrive in the same shape every time.
We also apply our own automation and AI tools to the repeatable parts of plan production, always with an engineer checking every result before it reaches a client. The gain is steadier turnaround on predictable work, which is where the time was going in the first place. How we govern that is on Responsible AI in Engineering.
| Step | Owner | What exists at the end |
|---|---|---|
| 1. Define one package | Client | One-page scope: deliverables, inputs, standards, decision owners |
| 2. Choose on evidence | Client | Completed scorecard for each candidate |
| 3. Transfer standards | Both | Template set, sample plan sets, open-question list |
| 4. Set the rhythm | Both | Handoff time, question log, overlap window, weekly call |
| 5. Agree review and handoff | Both | Written review layers and handoff package definition |
| 6. Run and measure | Both | Four metrics and a client SOP |
| 7. Decide how to grow | Client | Engagement model chosen on proven fit |
09 · FAQ
Common questions about the outsourcing process
How long should the first package be?
Long enough to include a full handoff and review cycle, short enough that a poor fit costs little. For most firms that is one phase of one project, typically a few weeks of work.
What if we do not have documented CAD standards?
Tell the partner at Step 3. We can build a template, title block and layer standard for you and transfer it; several clients have adopted the result as their firm standard.
Who owns the files and the intellectual property?
You do. Work proceeds under NDA, project information stays tied to the purpose for which it was shared, and files are returned in your formats at handoff.
Can the partner talk to our client or the reviewing agency?
Not unless you decide it should. Client and agency relationships stay with your firm; the partner’s questions come to your named decision owners.
How do we know the partner is using licensed software?
Ask for the license records. AXANH uses genuine, licensed software for commercial delivery and holds an Autodesk AEC Collection license; the controls are described on the Trust & Compliance page.
Next step
Walk through Step 1 with us
The fastest way to test this process is to bring one package to a scoping conversation: the deliverables, the standards and the decision owners. We will tell you what we would need from you, what the review and handoff would look like, and whether we are the right fit for the work.

