Why professional services employees leave and how to understand why
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 articleAn engineering consultancy sells design, checking and site supervision, so it lives on engineers who are sound technically and well backed. Some would rather not manage people, and the firm needs a path for them.

Make this work for your business. Share your team size, priorities and what you need help with. We’ll use your brief to prepare for the first conversation.
Share your requirementsAn engineering consultancy designs, checks and supervises structures, plant and infrastructure for owners, developers and contractors. Its people are discipline leads in civil, structural, mechanical, electrical or environmental work, design engineers, CAD and BIM technicians, checkers who review drawings and calculations, and resident engineers on site. Work runs by project and stage, with crunches before a drawing issue and quiet spells while approvals wait. Engineers prize technical respect and honest review. They distrust firms that overload them or treat them as drawing machines. Fees arrive at stage milestones, so cash and pay follow the project calendar. See also HR for professional services.
These are the places the people side of this kind of business tends to give way. The rest of this page works through them.
Why GullyHR for engineering consultancies
For principals and discipline leads who want checkers, designers and resident engineers working to one routine, so issue dates, site contact and technical careers stop depending on whoever pushes hardest.
A review stage written into every project plan, with a named checker and a sign-off rule, so a drawing leaves the office only after someone other than its author has read it.
A visit rota from discipline leads, a regular review with the project manager and a planned return to the design office between postings, so site engineers stop feeling like the junior partner.
Grades for senior designers and checkers who prefer calculations to managing people, with the evidence each step needs written down and agreed in advance.
A second named engineer for each discipline, design package and code area, with method notes and model files in one shared place, so a project does not stall on a single absence.
Start with any one of these. Scope and fee are agreed in writing after a free first conversation.
The audit starts with the files from your last few drawing issues. We look for the checking stage in each plan, the checker's name, the signed check sheet and the gap between planned and actual review time. Then we speak separately with discipline leads, checkers, CAD and BIM modellers and resident engineers, because each group feels the squeeze differently. We read job descriptions, overtime around submission weeks, training records for code updates and the way document controllers log revisions. Findings are ranked by what would hurt a live project first.
What you receive
An example, not a client storyPicture a firm where three submissions fall in one fortnight and the only checker is also drawing. The audit would lay the issue dates against named engineers, show where review time vanished and give the principal a short list of rules to agree before the next stage begins. The principal then decides who gets cover.
How the hr audit works →Process design begins with the drawing issue, because that is where pressure lands. We sit with a discipline lead, a checker and a document controller and trace one drawing from first model to issued revision, noting every hand-off. Next comes the resident engineer's site report and the query route back to the design office. Each process is written as a short sequence with a named owner, a form where one is needed and a clear point at which work stops if a check is missing. Engineers review every draft before it is final.
What you receive
An example, not a client storySuppose two resident engineers raise the same site query by phone and each gets a different answer from the office. A written query route would give the question one log, one owner in the design team and a reply the resident engineer can pass straight to the contractor. Nobody guesses which answer stands.
How the hr process design works →In an ongoing role we keep a weekly view of every project against its next issue date, the engineers assigned and the checker named. We raise clashes with the principal before three submissions land on the same people. We run one-to-ones with discipline leads, follow up resident engineer reviews with project managers and keep the monthly technical hour in the calendar. Leave requests, probation reviews and appraisal paperwork are handled against the project calendar, so quiet spells while approvals wait are used for leave and learning. A short report goes to the principals each month.
What you receive
An example, not a client storySay a quiet spell opens while a client waits on approvals. The weekly view shows who is free, so leave, code-update reading and a mentoring pairing between a design engineer and a CAD modeller are booked then, before the next issue crunch arrives. Nobody is chased for leave in the busy fortnight.
How the hr management works →The hard roles to fill are the experienced checker, the discipline lead and the resident engineer ready to live near a site. We start with a role profile agreed with the principal, separating what the design office needs from what a site posting needs. Candidates sit a short technical exercise, such as reviewing a sample drawing with planted errors, marked by two engineers on one scoring sheet. Interviews explore how a person takes review comments and whether they want a technical or a managerial path. Offers go out with a written note on grade and ladder position.
What you receive
An example, not a client storyPicture a structural discipline lead resigning just as two projects near issue. We would agree a profile with the principal, run the same review exercise with every candidate and show scores side by side, so the choice rests on how each person checks a drawing. The principal sees the reasoning, not only a name.
How the recruitment for permanent roles works →Training starts with discipline leads, some of whom were promoted for technical strength alone. Sessions cover setting a task, giving feedback on a calculation without bruising its author and escalating a clash between two projects. Checkers learn to write comments that are specific and fair. Resident engineers practise site reporting, recording instructions and holding a line with a contractor. We also help set up the monthly technical hour, with a simple format and a rota of presenters. Practice uses your own anonymised drawings and site situations, never generic cases from a textbook.
What you receive
An example, not a client storySay a young design engineer receives a page of checker comments with no explanation and withdraws from the team. A session on writing review comments would give checkers a pattern for stating the issue, the reference and the suggested fix, and give the engineer a way to ask without losing face. Both sides know what a good review looks like.
How the manager and team training works →Policy work covers the rules that bite when deadlines bunch. We draft a note on hours and time off in lieu around drawing issues, a site posting policy for resident engineers covering travel, lodging and the return to the office, and a rule on keeping model files and calculations in the firm's own store. The handbook also holds a conduct section on honest review, confidentiality of client designs and use of personal software. If you want software, we set up employee records, leave and appraisals in a tool and load it with your own data. Your adviser confirms the legal wording.
What you receive
An example, not a client storySuppose a resident engineer is moved between two sites and nobody is sure what travel and lodging the firm will cover. A site posting policy would set out the steps, the sign-off and the return to the design office, while the software holds each person's posting history. The next move then takes minutes to plan.
How the policies, handbook and hr software works →We keep each routine to a page and build it with your discipline leads and checkers, so it matches how drawings really move. The aim is a signed check that takes minutes, not a form for its own sake. We trial it on one live project, adjust it, then extend it. Any contractual duty on checking is confirmed by your own adviser.
Yes. We draft grades for senior designers and checkers who stay hands-on, with the skills and evidence each step needs, and place them beside the managerial grades with comparable standing. We speak with your senior engineers first to learn what they value. Pay bands are agreed with you, and your adviser confirms any contract wording that changes.
We would set a visit rota so discipline leads see the site, a regular review between each resident engineer and the project manager, and a planned return to the design office between postings. We also write a short site report and query route so questions get answers. Travel and lodging terms are drafted with you and checked by your adviser.
We list every discipline, software package and code area held by one person, then name a second engineer for each. We help the holder write short method notes, agree where model files live and set a pairing on a live task. It is practical, not a long manual. Where a contract covers ownership of work files, your adviser confirms it.
GullyHR runs talent acquisition for permanent roles in engineering consultancies. For each role we agree the job description with you, find and screen candidates against it, and support the offer through to joining. Tell us the role and the number of people, and we start there.
We recruit permanent employees. We do not supply contract or temporary staff.
Late drawings shrink the review stage, and errors surface on site, where a fix costs far more.
Resident engineers spend long stretches on site, lose touch with the design office and feel like the junior partner.
A single engineer knows a design package or a code section deeply. When this person is away, the project waits.
Engineers cannot see how a strong technical person becomes a lead without managing people they would rather not manage.
Three submissions fall in one fortnight, and the same engineers are asked to cover all of them.
Standards and codes change, and each engineer self-updates. There is no firm routine for passing on what was learned.
Start with the topics that matter most here: Career and Succession Management; Learning and Development; Organisation Design. Then work through the rest. Each topic is written for professional services, not in general.
Named backups for the roles that cannot be vacant.
Training planned from need rather than from the calendar.
Structure, reporting lines and who is allowed to decide what.
How many people, in which roles, by when, and what they will cost.
Requisition to joining, the same way every time.
A first day that is the same for the fifth joiner as the first.
Records, attendance, leave and the day-to-day HR that must simply work.
Salary structure, payroll inputs and a month that closes on time.
Goals, reviews and ratings that hold up in a conversation.
Communication, recognition and the conditions people actually work in.
Two routes, one for complaints, one for conduct, kept separate.
Policies a manager can apply, and obligations with owners and dates.
Induction, records, incident reporting and follow-through.
Who leaves, when, why, and which of them mattered.
Resignation to relieving letter, in a defined order.
Records that survive people, and approvals that do not queue.
A short monthly pack management actually reads.
An HR function that runs the same way every month.
The pieces a engineering consultancies business puts in place, in an order that makes each easier. Open any card for the detail.
Set aside time for checking, name the checker and make it a rule that no drawing is issued without a signed check.
Set aside time for checking, name the checker and make it a rule that no drawing is issued without a signed check.
Regular visits from design leads, a scheduled review with the project manager and a planned return to the office between postings.
Regular visits from design leads, a scheduled review with the project manager and a planned return to the office between postings. The employee engagement process covers it.
A route where a strong designer can reach senior technical grades without line management.
A route where a strong designer can reach senior technical grades without line management. The career and succession work lays it out.
Every discipline or software tool gets a backup, with shared method notes and model files kept where both can reach them.
Every discipline or software tool gets a backup, with shared method notes and model files kept where both can reach them.
One engineer presents a code change, a design problem solved or a site lesson.
One engineer presents a code change, a design problem solved or a site lesson. The learning and development process helps keep it alive.
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 ladder and a managerial ladder, each with clear steps.
Clear reporting lines between discipline leads, project managers and site teams, so no group feels sidelined.
A regular routine for sharing code updates, lessons and design methods across the team.
Simple ways to keep site-based engineers tied to the firm.
Start with a free conversation, or see the paid HR Diagnostic.
Understand the business, its workforce, current processes and HR challenges.
Find the missing, weak, inconsistent or person-dependent processes.
Create the structure, processes, policies, SOPs, dashboards and systems needed.
Help HR and department managers actually adopt the new system.
Digitise repetitive and approval-based workflows where it is worth doing.
Track hiring, attendance, employee cost, performance, training and attrition.
Strengthen the people-management system continuously, not once.
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 founder's guide to hiring freshers and running a first-year programme: campus or open drives, a screening round, a training plan by quarter, mentors and checkpoints.
6 min readRead article
A founder's guide to building job grades, titles and billing levels for a growing IT services firm, with a step-by-step method and a grade description outline.
6 min readRead articleMore on the GullyHR blog.
Write review time into the project plan and treat it as fixed. If drawings slip, the issue date moves, not the check.
Visit them, bring them into design reviews and plan their return to the office after a posting. Isolation drives most site exits.
No. A technical ladder with real seniority and pay lets skilled engineers progress without running a team.
Name a backup, record methods and files, and rotate them onto some of the work. It also lets the specialist take leave without a stall.
Look a quarter ahead, spread engineers across the submissions and line up temporary help before the squeeze.
Our first talk would cover how many days checking got on recent jobs, when office staff last reached the resident engineers, and which packages rest with one person. A technical ladder or a backup plan per specialist is a sensible opening task. We then set scope down in writing.
All 145 business types in professional services · Find another business type
See all HR topics for professional services, or another industry.
Tell us your industry, team size and the issue you want to address. Bring one example of where work gets delayed or ownership is unclear, and the deadline or decision you are working towards.