An engineering consultancy sells design, checking and supervision, and it depends on engineers who are both technically sound and well supported. Many strong engineers do not want to manage people, so the firm needs a route that rewards technical depth without forcing that move.
Not sure what you need? Tell us about your business in six short steps and we will come to the first meeting prepared.
Share your requirementsAn engineering consultancy designs, checks and supervises structures, systems and infrastructure for owners, developers and contractors. Its people include discipline leads in civil, structural, mechanical, electrical or environmental work, design engineers, CAD and BIM technicians, checkers who review the output, and site supervision engineers who watch construction. Work is organised by project and stage, with peaks when drawings are due and slack when approvals are pending. Engineers value technical respect and sound reviews, and they are wary of firms that overload them or treat them as drawing machines. Fees come in stages, so pay and cash flow follow project milestones. See also HR for professional services.
Who does the work
Checking is squeezed
When drawings are late, the review stage shrinks, and errors are found on site where they cost more.
Design and supervision teams split
Resident engineers are posted to sites for long stretches, lose touch with the design office and see themselves as second-class.
Specialists are hard to replace
A few people hold deep knowledge of a discipline or a software tool, and their absence stops projects.
Progression after the first years is vague
Engineers do not know how a technically strong person becomes a lead without having to manage people they would rather not manage.
Project peaks overlap
Several projects hit drawing deadlines at once, and the same engineers are asked to cover all of them.
Technical learning is left to chance
Standards and codes change, and engineers update themselves without a firm routine for sharing what they learn.
Protect the checking stage
A fixed time for review in every project plan, a named checker and a rule that drawings do not leave without it.
Give site engineers a home in the firm
Regular visits from design leads, a monthly review with the project manager and a planned return to the office between postings. The employee engagement process covers it.
Create a technical track beside the management track
A route where a strong engineer can grow into senior technical roles without people management. The career and succession work lays it out.
Back up each specialist
A named second person for every critical discipline or tool, with shared notes on methods and files.
Run a regular technical session
A short monthly session where one engineer shares a code change, a problem solved or a lesson from site. The learning and development process helps keep it going.
Confirm with a qualified professional. What applies to you depends on your business, your state and your arrangements, and it changes. This page describes practice. It does not state a legal position.
A technical track and a management track, with clear steps in each.
Clear reporting between design leads, project managers and site teams, so no group feels sidelined.
A regular routine for sharing code updates, lessons and methods across the team.
Simple ways to keep site-based engineers connected to the firm.
Every engagement starts by recording where you stand, and every later report compares against that. We do not promise outcomes. Start with a free conversation, or see the paid HR Diagnostic.
From the GullyHR blog: one on HR in professional services, and one on each of the topics this page points to.
Why associates and managers leave consulting, accounting, legal and advisory firms, and how to ask about progression, workload and partners at exit.
6 min readRead article
A two-hour exercise that names the roles you could not fill quickly, who could cover them, and what readiness would actually require.
7 min readRead article
A calendar of courses, a budget spent by March and no record of what any of it changed. What a learning and development process contains when it starts from need rather than from the catalogue.
7 min readRead article
A flat structure works until the founder becomes the only route to a decision. How to tell when you have passed that point, and how to redesign without a reorganisation.
8 min readRead articleMore on the GullyHR blog.
Put the review time into the project plan and treat it as fixed. If drawings slip, the issue date moves with them, not the check.
Visit them, include them in design reviews and set a route back to the office after a posting. Isolation causes most site exits.
No. A technical track with real seniority and pay lets skilled engineers progress without managing a team.
Name a backup, record methods and files and rotate them through some work. It also gives the specialist a way to take leave without the project stalling.
Look at deadlines a quarter ahead, spread people across them and arrange temporary help before the crunch.
Our opening discussion would look at how much time checking really gets on recent projects, how often design-office staff visit the resident engineers, and which disciplines or tools rest with one specialist. A technical career track beside the management one, or a backup plan for each specialist, is a sensible first task. We then agree scope in writing before starting.
All 15 business types in professional services · Find another business type
See all HR topics for professional services, or another industry.
Identify payroll leaks, record gaps and hiring bottlenecks in a free first conversation, and leave knowing what to fix first.
Know what you need? Share your requirements in four short steps.
Want the full picture? See the paid HR Diagnostic.
Prefer a quick message? Chat on WhatsApp
