How We Work

More Design Capacity. Less Management Friction.

Whether you need help with a defined Civil 3D drawing package or a continuing engineering team, AXANH aims to fit the agreed work into your standards, tools and delivery environment.

Clear responsibilities, review matched to the work and documented handoffs can make additional capacity easier to manage. They do not remove your own review, and they do not replace your professional judgment.

Discuss Your Project

The short answer

  1. What you can assign

    Work in the areas on the Capabilities page, such as land development, civil engineering support, CAD and design documentation, and BIM workflows. Fit is checked against your actual scope.

  2. What stays with you

    Direction and commercial decisions. Who holds technical review and professional sign-off is agreed for each engagement.

  3. How review works

    The person producing the work checks it. Further review is added where scope, risk and agreed responsibility call for it.

  4. How you begin

    A conversation about the work, then a defined assignment if it fits. A large commitment is not needed to start.

What you can expect

What working with AXANH is designed to give you

Four things buyers usually ask about, each tied to a mechanism you can examine.

These describe what the working model is built to support. They are not guaranteed results, and none of them replaces your own review.

  1. 01

    Capacity matched to the work

    Support sized to the scope you agree, without assuming every client needs a fixed, long-term team.

    MechanismWork starts from a defined assignment or workstream.

  2. 02

    Quality with appropriate review

    Review expectations are agreed up front and scaled to scope, risk and responsibility.

    MechanismSelf-Check, Peer Review and Manager Review, configured for each engagement.

  3. 03

    Clear communication and visibility

    You know who to talk to, where the work stands, which questions are open and which decisions need your input.

    MechanismAgreed contacts and rhythm, with open questions listed instead of assumed away.

  4. 04

    Knowledge that can carry forward

    Standards, clarifications and lessons can be kept so recurring work does not start from zero, within the confidentiality boundaries that apply.

    MechanismClient-approved references and recorded clarifications. See Trust & Compliance for controls.

Getting started

From first conversation to first assignment

You do not need a fully developed outsourcing plan to begin. These three phases show how a conversation can become an agreed assignment. They are illustrative, not fixed timelines, and not every request becomes an engagement.

  1. 01

    Understand the need

    We start with the work: what needs to be done, where delivery is under pressure, which disciplines and standards apply, and the outcome you want.

  2. 02

    Agree on scope and approach

    Together we define deliverables, responsibilities, review expectations, communication and commercial considerations, and how the work will be arranged.

  3. 03

    Onboard and begin

    Access and context are set up, open questions are cleared, coordination is agreed and the authorized scope begins.

Helpful to bring to a first conversation

  • The kind of work and roughly how it arrives
  • The standards, templates or references that apply
  • Where delivery is under pressure today
  • How review and approval work on your side

What the conversation covers

  • Whether AXANH’s support fits the work
  • What a starting scope could look like
  • Which responsibilities need to be made explicit
  • What AXANH would need from you to begin

A first conversation is for exploring fit. A formal pilot or trial is not assumed, and nothing here fixes a timeline, a price or a team size.

Working together

Your workflow. Clear responsibilities.

Getting started ends when scope and responsibilities are agreed. From there, delivery follows six stages, repeated for each assignment as needed. Scope and governance change from one engagement to the next, so this is a way to keep work clear, not a fixed procedure. Each stage shows what AXANH contributes, what may be needed from you and what makes the next step clear.

01

Align

Clarify the outcome

Agree what the work needs to achieve before production speeds up.

AXANH contributes
Reads the scope and makes assumptions and gaps visible early.
May be needed from you
Where needed, confirm the outcome, scope boundaries and who can decide.
The next step is clear when
The scope is specific enough to start.
02

Onboard

Bring in your context

Set up the standards, templates, access and contacts the work depends on.

AXANH contributes
Learns where each standard applies and asks instead of assuming.
May be needed from you
Share the standards, templates, access and contacts the work depends on.
The next step is clear when
Open questions and knowledge gaps are listed.
03

Coordinate

Keep decisions moving

Give questions, progress and risks a clear owner and a clear path.

AXANH contributes
Routes questions to the right person and raises concerns while options remain.
May be needed from you
Answer or decide while the work is still moving.
The next step is clear when
The right people have what they need to act.
04

Review

Check before handoff

Review sits inside the work, at the depth the scope calls for.

AXANH contributes
Applies the agreed review: Self-Check, plus Peer or Manager Review where called for.
May be needed from you
Carry out your own review and approvals, as agreed for the engagement.
The next step is clear when
Review has happened at the agreed points.
05

Handoff

Hand over with the reasoning

Keep decisions, assumptions and open questions with the deliverable.

AXANH contributes
Returns the agreed files with clarifications and open issues, as the scope allows.
May be needed from you
Review the work and decide what happens next.
The next step is clear when
The next step can start without rebuilding context.
06

Adapt

Change when the work changes

As volume or continuity changes, communication, review and knowledge practices can change with it.

AXANH contributes
Records reusable lessons where the engagement allows.
May be needed from you
Decide with AXANH whether more continuity or structure is needed.
The next step is clear when
The next cycle starts from a clearer point.

An illustrative example

Example: a Civil 3D drawing package

One way the stages above could play out on one kind of assignment. The client and the package are hypothetical. This is not a project record, and it says nothing about results or time. The details of a real engagement would be agreed first.

Illustration only

A client PM might send

  • Redlines or revised design instructions
  • The relevant drawings and files
  • The applicable standards and templates
  • Priorities and handoff requirements
  1. 01

    Clarify the inputs first

    AXANH could read the redlines against the drawings and standards and list what is unclear or missing, such as an instruction that conflicts with a standard, before drawing begins.

  2. 02

    Confirm the agreed scope

    Deliverables, priorities and handoff requirements could be checked against what was agreed, so everyone works from the same definition of done.

  3. 03

    Produce the assigned documentation

    The drafting could be done in the client’s templates and standards, with questions routed to the agreed contact.

  4. 04

    Check it as the engagement requires

    Self-Check by whoever produced the work, with Peer or Manager Review where the engagement calls for it.

  5. 05

    Hand off with the reasoning

    The agreed files could go back with notes on how each instruction was addressed, anything that could not be resolved, and the open questions.

  6. 06

    Keep what the engagement permits

    A clarification that may be reused, such as how a standard was applied, could be recorded for the next assignment.

Illustration only

What you would review next

  • The work against your standards
  • The open questions and what they need
  • Whether to approve, revise or redirect

Your own review and professional decisions follow the responsibilities agreed for the engagement.

Published evidence, with its limits

AXANH reports that on September 28, 2026, Thien Ly of Autodesk presented Civil 3D Completion Certificates to 30 AXANH civil engineers who completed an annual on-site capability checkpoint. AXANH’s own article states that these certificates are not Autodesk Professional Certification and do not establish project quality or replace engineering judgment. This page cites no project results. Read the account

Quality and accountability

Quality checks before handoff

AXANH uses three review perspectives: Self-Check, Peer Review and Manager Review. They are not a checklist every deliverable passes through. How many apply, and how deep each goes, depends on the work type, scope, risk and the responsibilities agreed.

The aim is to find issues close to where the work is produced, before they become rework or extra client review time.

Responsibility stays explicit

Agreed in the engagement, not assumed

Technical review and final sign-off responsibilities, including any licensed-engineer or Engineer of Record role, are clarified for each engagement and follow the requirements that apply. Training, design support or involvement in a U.S. project does not by itself grant signing, sealing or approval authority.

  1. Perspective 1 · Self-Check

    The engineer checks the work

    Quality responsibility starts with the person producing it, before the work moves to someone else.

  2. Perspective 2 · Peer Review

    Another set of eyes

    A second reviewer can challenge assumptions and details that are hard to see after working closely with the material, where the work calls for it.

  3. Perspective 3 · Manager Review

    Oversight where it fits

    Management review adds oversight where the type of work and its responsibilities call for it.

  4. Your side · Client review

    Your own review

    You review what comes back. Your review and decisions follow the responsibilities agreed for the engagement.

Your standards and knowledge

Your standards. Knowledge that carries forward.

AXANH works to your standards, not a fixed AXANH way. What is clarified on one assignment can make the next one clearer, within the boundaries you set.

Where it helps, recurring clarifications can be turned into working guidance such as checklists or SOP notes. Changes that affect your requirements, scope or quality expectations still need your review and confirmation.

Client-specific data, standards, confidential information and protected intellectual property are handled under the controls and agreements that apply. Requirements are clarified in the relevant engagement; specific questions go to Trust & Compliance.

What can carry forward

  • Reviewed standardsThe references the work follows, as you approve them.
  • TemplatesThe formats your deliverables use.
  • ClarificationsAnswers to recurring questions, recorded once.
  • Working guidanceChecklists or SOP notes, where they help.
  • Lessons from reviewWhat feedback showed for the next cycle.

Published evidence, with its limits

Two accounts of engineers learning inside a client’s way of working, from the AXA Engineers chapter that built AXANH: Napa, California, 2018 and North Carolina, 2023. They describe how client context was learned, not project outcomes.

Finding the right engagement

The right partnership starts with the work

Different workloads and different needs for continuity call for different working relationships. The useful question is not which model is highest, but what you need AXANH to take responsibility for.

Work
Traditional Design ServicesFor defined projects, scopes or deliverables where the work and responsibilities can be set out clearly.
Continuity
Dedicated EngineersFor recurring work where familiar engineers and retained context matter, and you continue to direct much of the day-to-day work.
Capability
AXANH Design Pod™For a structured delivery unit, with AXANH taking greater responsibility for coordination and delivery discipline.
Operations
Global Design OperationsFor more integrated relationships, where AXANH may take broader responsibility across selected design workflows.

These are not a ladder, and nothing here fixes pricing, staffing or scope. A separate long-term strategic pathway, the Co-Owned Global Design Center, is for organizations considering ownership; it is a different conversation from service capacity.

Questions buyers ask

Questions to settle before you start

Can AXANH support the type of design work our firm needs?

It depends on the work. The Capabilities page lists what AXANH currently supports. Whether a specific assignment fits depends on the discipline, the standards that apply, the delivery requirements and how review and approval work on your side. Availability for a particular start date is also a conversation; this page makes no commitment on it.

Can we start with a defined assignment?

Yes. A defined assignment or workstream is a reasonable way to begin. Whether a particular scope suits a first assignment is decided together, and a formal pilot or trial is not assumed.

Do we need to change our standards, tools or workflow?

Not as a starting assumption. AXANH aims to work within your standards, tools and delivery environment, and clarifies early which standards and templates apply and where to ask instead of assume. A workflow changes only where there is a clear operating reason.

Who communicates with our project manager, and who handles unresolved issues?

Contacts and the communication rhythm are agreed in the engagement, so you know who to ask. Open questions are listed rather than assumed away, and issues that could affect scope, quality, schedule or standards are raised early with the person who can decide. Who plays each role depends on the engagement.

What stays our responsibility, including review and sign-off?

Direction and commercial decisions are yours. Your own review of what comes back follows the responsibilities agreed for the engagement. Technical review and final sign-off, including any licensed-engineer or Engineer of Record role, are clarified in the engagement and follow the requirements that apply; they are not assumed.

How is confidential information handled?

Client-specific data, standards and confidential material are handled under the controls and agreements that apply to the engagement, and the requirements are clarified before work begins. Information-security and compliance information is on the Trust & Compliance page.

What determines scope, cost and commitment, and what if our needs change?

The work itself: its type and volume, the continuity you need, how much day-to-day management you want AXANH to carry, and the review expectations. This page does not publish prices or packages; commercial terms are discussed once the scope is understood. The arrangement can be revisited as the work changes, and nothing requires moving to a larger model. See Partnership Models.

What happens after we contact AXANH?

The next step is a conversation about your work and whether a starting scope makes sense, as described under Getting started. It is about fit, not a commitment, and this page does not promise a response time.

A practical next step

Let’s find the right starting point.

You do not need a full outsourcing plan to begin. Tell us about your projects, workload or delivery challenges, and we can explore an appropriate starting scope, with responsibilities and expectations clarified before work begins.

Discuss Your Project Discuss a Defined First Assignment

Prefer to speak with leadership first? Book time with Anthony, CEO of AXANH