By Mubashir · Senior Structural Engineer · May 2026
The Remote Engineering Model Is Not New — It Is Now Mainstream
Remote structural engineering has been practiced for decades. The structural engineer of record on a multinational project has rarely been local to every site in a portfolio. What has changed in the past decade is that the tools, platforms, and professional expectations for remote delivery have matured to the point where the client experience is functionally indistinguishable from local engagement — and where the cost and quality advantages of remote delivery are now well understood by sophisticated clients.
At Sixteens, every project we have delivered since 2014 has been remote: our engineers work in Kozhikode, India, and our projects span Saudi Arabia, the UAE, Qatar, Canada, the USA, Japan, and India. The clients we work with have chosen the remote model deliberately — not because they could not find a local firm, but because the remote model offered a better combination of technical depth, responsiveness, and fee.
This article is an honest comparison of both models — because the right answer genuinely depends on the project type, the jurisdiction, and what the client actually needs from their structural engineer.
What "Remote" Means in Structural Engineering Practice
In structural engineering, "remote" refers to the sub-consulting model: a qualified structural engineer prepares the full engineering package — structural calculations, structural drawings, material specifications, and connection design — and delivers this to the client or to the project's engineer of record. The engineer of record (who must be licensed in the project jurisdiction) reviews the package and applies their stamp for authority submission.
This is not a workaround. It is a standard practice in construction globally. In the GCC, it is the dominant model for structural design: large projects typically involve a local engineering firm of record (licensed in Saudi Arabia, UAE, or Qatar) that sub-contracts the detailed structural design to an Indian consultancy. The local firm coordinates with the authority; the Indian consultancy delivers the technical content. The split is clean, the workflow is efficient, and the client benefits from both the local firm's authority relationships and the sub-consultant's technical depth and cost efficiency.
For domestic Indian projects, the remote model means a Kozhikode-based consultancy delivering Kerala residential or commercial structural designs to clients in other states or to NRI clients overseas — all through digital delivery of drawings, calculations, and structural reports.
Cost: The Most Visible Difference
The cost advantage of remote structural engineering from India is real and substantial. An Indian structural consultancy can typically deliver equivalent scope and quality at 40–70% lower fee than a comparable local firm in the GCC, UK, USA, Canada, or Australia. This is not a function of inferior quality — it reflects the difference in salary structures, overhead costs, and purchasing power parity between engineering labour markets.
A structural analysis and design package for a mid-size industrial building that would cost £15,000–£25,000 from a UK firm can be delivered at £5,000–£8,000 from a qualified Indian structural consultancy without any compromise in calculation quality, code compliance, or deliverable format. For GCC projects, the equivalent comparison applies: a design package priced at AED 50,000 by a Dubai-based engineering office might be priced at AED 15,000–20,000 by an equivalent Indian sub-consultant.
The practical saving for clients who regularly commission structural engineering — contractors, developers, facility managers, NRI property owners — is significant across a project portfolio. The saving is greatest for projects where the structural engineering fee is proportionally large: industrial structures, specialty structures, complex assessment and retrofit projects, and multi-building development programmes.
Quality: How to Assess It Independent of Location
Quality in structural engineering is assessed by the technical content of the deliverable, not by the address of the engineer who produced it. The relevant quality indicators are:
- Qualifications of the actual working engineer — not the firm's principal or partner, but the engineer who will do the calculations. Ask for their degree, years of experience, and specific project examples in your jurisdiction or code system.
- Calculation depth — do the calculations cite specific code clauses? Are load derivations shown explicitly? Are the analysis model assumptions documented? A calculation pack that shows only "ETABS says 47 MPa" without showing the load path, load combinations, or code reference is not an adequate engineering deliverable regardless of who produced it.
- Independent validation — does the engineer perform hand-calculation cross-checks on the analysis model? This is the most reliable indicator of whether the engineer understands the model or just runs the software.
- Review support — will the engineer respond to queries from the local reviewer or authority during the approval process? A deliverable that arrives and then requires three weeks of silence before queries are answered is not fit for purpose.
These quality criteria apply equally to local and remote firms. A large local engineering office may assign a project to a junior engineer supervised at arm's length, producing lower quality than a small remote consultancy where the senior engineer does all the work personally. The size and location of the firm are not reliable proxies for the quality of the individual calculations.
Code Compliance: The Most Common Concern
The question clients most often raise about remote engineering is code compliance: how does a structural engineer in India know and correctly apply Saudi Arabia's SBC, or Quebec's NBC 2020, or Florida's Building Code? This is a legitimate question, and the honest answer is: through deliberate multi-codebook practice.
At Sixteens, we have actively built our codebase knowledge across the jurisdictions we serve. We have designed to AISC 360 for the Dammam entertainment tower under Saudi SBC requirements. We have applied NBC 2020 provisions for the Ontario steel replacement. We have used JIS codes for the Nagashima observation tower in Japan. Each code system required deliberate study, reference material acquisition, and project-specific technical review — the same preparation required of any engineer practising outside their primary jurisdiction.
The appropriate way for a client to assess remote code competence is to ask for specific project examples in the relevant jurisdiction, and to review a sample calculation that shows the code clause citations. An engineer who cannot show you a calculation that explicitly cites SBC 301 Clause 1609 or ASCE 7-22 Section 26.6 for a wind load derivation does not have working code fluency — regardless of whether they are local or remote.
Communication: The Practical Workflow
The most common operational concern about remote structural engineering is communication — the belief that walking into the engineer's office produces faster decisions and fewer misunderstandings than email, video calls, and shared digital files. This concern is understandable but largely overstated in practice.
Effective remote structural engineering communication follows a documented process:
- Project brief — architectural drawings, site location, applicable codes, structural system preference, and key client requirements provided in writing at project start. This forces clarity that face-to-face discussions sometimes defer.
- Scope confirmation — written confirmation of what is included in the deliverable, the analysis approach, applicable load cases, and the code set being applied. This prevents scope creep and misalignment at delivery.
- Progress updates — milestone-based communication rather than real-time presence. Clients receive updates at completion of load derivation, completion of analysis, completion of member design, and completion of drawings.
- Review support — explicit commitment that queries from the local reviewer will be responded to within one business day. For GCC projects, this means responses aligned with the client's working week (Saturday to Thursday).
In our experience, the clients who manage remote engineering relationships most effectively are those who invest in a clear written brief at the start. The structural engineer cannot design what has not been specified — and the local engineer in the same city is as likely to make wrong assumptions as the remote engineer in Kozhikode, if the brief is ambiguous.
When to Choose Remote vs Local
| Factor | Remote Sub-Consultant | Local Firm |
|---|---|---|
| Fee level | 40–70% lower | Market rate for jurisdiction |
| Technical depth | Depends on firm; check qualifications | Depends on firm; check qualifications |
| Stamping for permit | Requires local engineer of record | Direct (if licensed in jurisdiction) |
| Site visit (inspection) | Requires local presence or inspector | Direct site access |
| Multi-code projects | Strong (if multi-jurisdiction experience) | May be limited to local code only |
| Turnaround time | Comparable (1–3 weeks typical) | Comparable; local workload varies |
| Communication | Digital-first; requires clear brief | In-person available; not always faster |
| Best for | Design-only scope; multi-jurisdiction portfolio; cost-sensitive projects | Site-intensive scope; single local permit; projects needing local authority relationships |
The Hybrid Model: Best of Both
The most efficient arrangement for many international projects is the hybrid model: a local engineer of record who handles authority submission and site coordination, plus a remote sub-consultant who handles all the detailed structural calculations and drawings. The local engineer of record adds value through their jurisdiction licence, authority relationships, and site access; the remote sub-consultant adds value through technical depth and cost efficiency.
This is the dominant model for structural engineering in the GCC. Large Saudi, UAE, and Qatar contractors typically maintain relationships with a local engineering office for permitting and a separate Indian structural consultancy for detailed design. The client controls the relationship with each party, the deliverables are clearly assigned, and the overall cost is lower than using the local firm for the full scope.
The hybrid model requires clear contract documentation: the local engineer of record must explicitly review and accept responsibility for the sub-consultant's calculations when applying their stamp. Some local firms are reluctant to accept this responsibility; others operate specifically in this capacity and have efficient processes for reviewing sub-consultant packages. Identifying a local firm experienced in the review-and-stamp role is the key setup task for clients adopting the hybrid model.
Our Remote Delivery Process
Every Sixteens engagement follows the same process regardless of project location:
- Project brief receipt — architectural drawings, site location, applicable code, and structural system preference. We confirm the full scope within 24 hours and respond with questions if any information is missing.
- Scope confirmation — written confirmation of deliverables, timeline, fee, and the specific codes to be applied. The scope letter defines the engineering boundary — what we deliver, and what the local engineer of record handles.
- Load derivation and analysis — dead, live, wind, and seismic load derivation per the applicable code; 3D analysis model in ETABS, STAAD.Pro, or SAP2000 as appropriate; model validation against hand calculations for critical load cases.
- Member design and connection design — code-compliant design of all structural members and primary connections, with explicit clause citations. For steel structures, this includes all limit state checks for the applicable code (IS 800, AISC 360, or Eurocode EN 1993).
- Drawings — structural general arrangement drawings, member schedule, connection details, and foundation layout, formatted for authority review in the project jurisdiction.
- Review support — queries from the local reviewer or authority are answered within one business day. We treat the review process as part of the engagement, not an optional extra.
Remote or local? For design-only scope, multi-jurisdiction portfolios, and cost-sensitive projects, a qualified remote sub-consultant is the higher-value choice. For site-intensive scope or projects requiring direct authority relationships, a local engineer of record is necessary — but the remote model can still handle all the detailed calculations at a lower overall cost.
Frequently Asked Questions
Can a remote structural engineer stamp drawings for permit submission?
In most jurisdictions, the engineer who stamps drawings for authority submission must be licensed in that jurisdiction. A remote engineering sub-consultant prepares all structural calculations and drawings, while the local engineer of record — licensed in the project jurisdiction — reviews and stamps the package for submission. This sub-consulting model is standard practice across the GCC, USA, Canada, and India. We operate as the sub-consultant: full engineering package delivered, local engineer of record applies the stamp.
How does a remote structural engineer handle site visits?
Most structural design scope does not require physical site access during design. The calculations and drawings are prepared from architectural drawings and survey data. For existing building assessments, a remote engineer can direct a local inspector using a detailed inspection protocol, then complete the structural assessment from the inspection report and photographs. For projects requiring periodic site visits during construction, the local engineer of record or a locally based inspection engineer handles site attendance.
Is quality from a remote structural engineer as good as local?
Quality depends on the engineer's technical competence, not their location. A remote senior structural engineer with deep multi-codebook experience may produce higher quality calculations than a large local firm that delegates work to junior staff. The key quality indicators: qualifications of the actual working engineer, depth of code citation in the calculations, whether independent model validation is part of the process, and whether the engineer provides review support after delivery. Ask for these specifics — from any firm, local or remote.
What are the risks of hiring a remote structural engineer?
The manageable risks are: communication gaps (mitigated by a clear written brief and scope confirmation), code unfamiliarity (mitigated by checking specific jurisdiction experience), deliverable quality (mitigated by requesting a sample calculation), and review support absence (mitigated by confirming this is part of the engagement). Each of these risks applies equally to local firms — a local engineer who is unfamiliar with the applicable code is not a safer choice than a remote engineer who has directly applied it.
How much cheaper is a remote structural engineer?
For equivalent scope and quality, an Indian structural consultancy typically delivers at 40–70% lower fee than a comparable local firm in the GCC, UK, USA, Canada, or Australia. For a mid-size industrial building structural design package, this translates to a saving of £8,000–£17,000, or AED 25,000–40,000, at equivalent quality levels. The saving is greatest for projects with complex, calculation-intensive scope where the engineering fee is proportionally large.