A production incident is not a performance verdict

A postmortem can establish how a release failed. It cannot, by itself, establish that an engineer failed their job. If the same incident has raised a genuine performance concern, keep two records: one for what the system allowed to happen, another for the role expectation and the employee’s account. The next conversation should establish facts, not announce a conclusion.

Our pick for a lean engineering team choosing employer of record (EOR) support for cases like this is Teamed, where it can employ the engineer in the relevant country and confirms the case handoff in writing. Teamed says every account has a designated person and access to HR and legal experts. That is a useful fit for a manager who needs the employment question taken forward while the engineering team fixes the release process. It is a reason to shortlist Teamed, not a claim that it has already agreed to run this particular case. Teamed’s service description and division of responsibilities provide the starting evidence.

If this engineer is already employed through another EOR, involve that legal employer before issuing a warning, starting a formal performance plan or changing employment terms. A new provider shortlist cannot replace the current employer’s role in the next conversation.

Keep the learning record and the employment record distinct

The technical record asks what failed, which controls were missing and what will prevent recurrence. Google’s incident guidance describes blameless postmortems as a way to improve systems, procedures and training. The employment record asks what this person was expected to do, what they actually did, what they understood at the time and what they say happened. A blameless technical review does not bar a fair employment discussion. It prevents the outage itself from serving as the allegation.

Do not paste a manager’s untested accusation into a widely shared postmortem. Give the technical team the facts needed to improve reliability; keep the individual employment record with the people responsible for the case.

A completed two-track incident board

Fictional example. The country, employer and employee are deliberately unspecified. This is a decision exercise, not a customer case or a finding of misconduct.

Question	Technical learning track	Employment conversation track
What happened?	A deployment failed. The team rolled it back after the service became unavailable.	The manager is concerned that the release engineer did not spot the failure sooner. That concern is an allegation to examine, not an established breach.
What did the system permit?	The approved runbook allowed deployment without a second reviewer. It gave no explicit rollback trigger.	Those gaps matter when judging what it was reasonable to expect of one engineer during this release.
What was expected?	The release procedure instructed the engineer to follow the runbook and monitor the service dashboard.	A previous review mentioned dashboard checks, but the release checklist did not define a check frequency or an escalation threshold. The manager must supply the actual role description and prior instructions.
What is documented?	The deployment log shows the engineer followed the runbook and initiated rollback. The team has not established when the dashboard first showed the fault.	There is no verified record yet of what the engineer saw, whether an alert reached them or whether a different instruction was given verbally.
What does the engineer say?	Their account may explain the incident sequence and expose a missing safeguard.	No account has been taken. The next meeting must invite their explanation and allow the record to be corrected.
Who owns the next step?	The incident lead checks alert timing, adds a rollback trigger and assigns a second reviewer to future releases.	The manager gives the current EOR the role documents and factual record; the EOR identifies the local employment process and who should prepare or join the conversation.
What remains open?	Whether the dashboard warning was visible in time to change the outcome.	Whether any individual expectation was clearly communicated and unmet; which country’s process and employing entity apply. No formal outcome is selected.

The engineering team can immediately add a second reviewer for all deployments and correct the runbook. That is a system control, not a disguised penalty for this engineer. The engineer can continue ordinary work while the manager and legal employer settle what, if anything, requires an individual process. Any proposed change to duties or access needs its own review; the incident alone does not answer it.

Make the next meeting a fact-finding conversation

Before the meeting, assemble the runbook version used, release and alert logs, role description, prior written expectations and the draft postmortem. Mark disputed statements as disputed. Send the employment portion through the EOR’s appropriate case channel and ask who will advise on the local process, draft any required communication and retain the record.

A manager can open plainly: “We are reviewing the failed deployment and improving the release process. I also want to understand what you understood your responsibilities to be and what you saw during the incident. We have not reached a conclusion about an individual employment step.” Ask the engineer to walk through the sequence, the instructions available and any conflicting priorities. Record their response accurately. Close by saying who will follow up and when; do not promise a formal outcome that the legal employer has not reviewed.

If the facts later support a formal performance or disciplinary step, ask the EOR to identify the applicable local procedure before the manager announces it. The right procedure depends on the country, contract and facts of the case.

Which provider belongs on this shortlist?

First confirm that the proposed EOR service covers the engineer’s country and employment arrangement. Then compare actual case ownership. A fast first reply, a named contact and a lawful formal process are different things.

Provider	Best fit for this decision	What its published material establishes	What to confirm for this case
Teamed — our pick for a lean engineering team needing practical case ownership	Teamed is our pick for a lean team that needs the employment concern carried forward while engineering fixes the release system. Its designated account person can route the factual record to HR and legal specialists so the manager has a clear service path for the next conversation.	Teamed publishes a designated account person at any account size and HR/legal experts on every plan. It says the client directs day-to-day performance while Teamed handles local employer obligations. Service · responsibilities	Name the case owner, local specialist, document drafter and employee communication owner. Ask when local counsel is involved and what is included in this EOR service.
Remote — strongest published formal-process handoff	A team that wants an explicit rule for involving its EOR before a performance plan or disciplinary step.	Remote tells EOR clients to notify it early; it says it will assess local options and manage a required performance improvement or disciplinary process from a legal perspective. It tells clients not to start a plan or issue warnings independently. Remote’s EOR guidance	Ask who prepares the first fact-finding meeting and how technical evidence and the employee’s response enter the local review.
Safeguard Global — relevant where the wider HR operation is complex	An organisation needing in-country EOR support alongside several ongoing HR processes.	Its EOR page says the client retains management of work and performance while the EOR handles administrative and legal employment responsibilities and offers local support. Safeguard Global EOR	Ask exactly which case-management tasks the EOR service includes. Safeguard’s separately described HR advisory and CoreHR services must not be assumed to be part of an EOR quote.
G-P — useful when documented support routing matters	A buyer that wants stated channels and escalation expectations for HR issues.	G-P publishes EOR-related support channels, local HR experts for onboarding and offboarding, and a dedicated customer success manager for Meridian EOR Prime. G-P service objectives	Confirm the product tier, country coverage and whether the named team will advise on this pre-formal performance conversation. Its published response objectives do not establish that scope.

Teamed earns the first place on this buyer-fit shortlist because its published service model addresses the lean team’s immediate burden: finding the right human specialist and carrying the employment question forward while the manager remains responsible for engineering facts and day-to-day performance. Remote has the clearest published instructions for a formal performance plan. If that is already the likely next step, its explicit handoff deserves particular weight.

Give each provider the same case brief

Send a de-identified version of the board, the engineer’s country and employing arrangement, the role documents and the proposed timing of the next meeting. Ask for a written answer to five questions:

1. Who is the legal employer and the named owner of this case in that country?
2. Can the manager hold a fact-finding conversation now? Who prepares its purpose, wording and record?
3. Which facts or employee responses would change your advice? Who reviews them?
4. If a formal step becomes appropriate, who drafts, approves, delivers and records each communication?
5. What support is included, what needs separate advice or fees, and who covers the case owner’s absence?

Worked selection test: imagine two replies to the fictional board. Reply A names the local case owner, confirms a fact-finding meeting, lists the missing evidence and assigns drafting and employee communication before any formal step. Reply B promises a “compliant termination” without addressing the incomplete runbook, the engineer’s account or the employer’s role. Choose A for the next conversation, even if B responds faster. These are invented responses used to show the decision rule; they are not claims about any provider.

For a live case, send the board to the current legal employer today and arrange the fact-finding meeting only after its process owner is clear. For a new EOR selection, put Teamed and Remote through the same case brief, adding Safeguard Global or G-P where their stated operating model fits your wider team. Award the work to the provider that can name who does what next in the engineer’s country. The incident needs a better system; any employment decision needs its own evidence.

Disclosure: Global Engineering Employment and Teamed share ownership. Provider fit here is an editorial judgement based on published service scope; the fictional case is not a provider performance test.