The Accepted-Offer Profile Update Standard, Gated From Signature to Day One

You have signed an offer and need to know exactly when, and how, your LinkedIn entry and resume can show the new job. The risks are tipping off your current employer, breaching a clause in your contract, or publicly announcing a role that later gets pulled. This standard is for candidates between signature and the first weeks of the new job. It grades any planned edit against four gate criteria and six field criteria and returns Pass, Hold, or Fail, so that two people grading the same case reach the same answer.

What does this standard grade, and what do Pass, Hold, and Fail mean?

It grades one planned edit at a time: a resume line, a LinkedIn experience entry, a settings change, or an announcement post. Each edit is checked against gates (what must be true in the world first) and fields (what the edit itself says). Pass means every gate for that edit type has cleared in writing and every field matches. Hold means the fields are right but a gate is still open. Fail means a field contradicts the offer letter or your contract, or the edit is already live while a gate is open.

The terms used throughout:

• Gate criterion: a fact about your situation that must be confirmed in writing before an edit goes live, such as "all contingencies cleared".
• Field criterion: a check on what the edit says, such as "title matches the offer letter".
• Contingency: a condition the offer depends on, such as a background check, drug screen, or right-to-work check. The offer is not final until each one clears.
• Garden leave: a period when you are still employed and bound by your duties to your old employer but kept away from work. You cannot start the new job during it.
• Restrictive covenant: a contract term that limits what you can do after you leave. A non-solicit, for example, bans approaching former clients or staff for a set period.
• Network share toggle: the LinkedIn control that decides whether a profile change is pushed to your connections as a notification.

Apply the grading rules in this order. The first rule that matches gives the grade:

1. If any field contradicts the signed letter or your current contract, the grade is Fail.
2. If the edit is already live and any required gate is open, the grade is Fail.
3. If the edit is planned and any required gate is open, the grade is Hold.
4. If every required gate is cleared in writing and every field matches, the grade is Pass.

"Cleared in writing" is what makes the grade repeatable. A recruiter saying "you're all good" on a call is not a cleared gate. An email that says the background check is complete is.

Which gates have to clear before each kind of edit?

There are four gates: offer state, contingency clearance, resignation and last-day status, and restrictive-covenant and garden-leave terms. Which ones apply depends on how far out on the exposure stack the edit sits. A private resume line needs one gate. A public experience entry needs all four, plus your first day.

Map each edit type to the gates it needs:

G2 is the gate that most often gets skipped, because the candidate assumes signature means done. It does not. Some practitioners advise waiting until after you start precisely because offers have been rescinded after layoffs or hiring freezes. No published source ranks which contingencies most often remain open after signature, so treat every item in the letter as open until you hold written clearance.

Turnaround times are published by the screening providers themselves:

Checkr puts a typical background check run through a consumer reporting agency at three to five days. I found no published turnaround data for visa approvals or right-to-work checks. If either applies to you, ask the recruiter for the expected clearance date in writing and treat G2 as open until it arrives.

Which fields must match the offer letter?

Six fields are graded: title, employer page, start month, network share toggle, Open to Work state, and the resume "Incoming" line. The first three must match the signed offer letter, because those are the facts an employment verification will later report. The other three control who sees the edit and how it reads.

Employment verification usually means a background screener contacting your employers for hire date, end date, job title, and duties. That record comes from HR and payroll, not from your profile. Month-level resume dates can legitimately differ from exact payroll dates, and the title you use publicly can differ from the HR system title. The standard does not require exact days. It requires that nothing you publish contradicts the letter.

How strict to be about title deserves a caveat. One reported case on Blind involved a candidate whose background check returned their IBM job-family title, "Management Consultant", through The Work Number, and it raised yellow flags because they had given their business title instead. That is a single anecdote, not a rate. A 2013 HireRight threshold table, reposted secondhand on Blind, counted a date difference of more than 3 months as a "minor" discrepancy. It is unverified as current policy. Nobody has published data on discrepancies caused specifically by a profile start month that is earlier than day one. The standard grades conservatively: using the offer title and the first-day month costs you nothing and removes the question.

The "Incoming" resume line

LinkedIn has no official "starting soon" option, so anything you add there reads as a job you already hold. A resume is different, because you control who receives it. The consensus from practitioner threads is to add the role to the resume if you are still interviewing elsewhere, and to leave LinkedIn until you start.

Incoming [Exact offer title] - [Employer named in offer letter]
Offer accepted; starting [Month YYYY]

An alternative phrasing some resume writers suggest is "Anticipated Start Date: [Month, YYYY]". Either passes, as long as there are no bullet points (you have not done the work yet) and no "Present".

That rarity is the point. An "Incoming" title on LinkedIn is an industry-specific habit. The one clear example in the US sample was "Incoming Asset Management Analyst", the kind of finance-track title where it is normal. Outside that world it is unusual, and it reads as a job already held. Keep the Incoming line on the resume.

If you are still sending applications while you wait to start, the Incoming line has to appear the same way on every version you send. Refolk tailors your resume to each posting from your own history, so the offer title and start month can be entered once and carried through every tailored copy instead of retyped and drifting.

How do LinkedIn's share toggles behave?

There are two controls. One is a global setting, and the other is a toggle that appears while you edit on desktop. Either one can push a notification. Neither one hides the change from anyone who opens your profile.

What LinkedIn's help pages establish:

• Global setting: Settings & Privacy > Visibility > "Visibility of your LinkedIn activity" > "Share profile updates with your network".
• Per-edit toggle: on desktop, the same setting can be changed while you edit your profile, in the "Share with network" section.
• Scope: it covers job changes, education changes, work anniversaries, and profile video updates.
• Delivery: a notification may arrive as a feed post, an in-app notification, or an email.
• Delay: job updates can take up to two hours to reach your network, and education updates up to 24 hours.
• Verification: the resulting notification can be checked in the Recent Activity section of your profile.
• Edits and deletions: editing or deleting an update after adding it may affect whether a notification is generated, and some edits produce no notification even with sharing on.

What is not established: LinkedIn does not publish a complete list of which edits trigger a notification. One third-party walkthrough says photo changes are not announced, but I could not verify that against LinkedIn's own help pages. Do not rely on it. The only reliable test is Recent Activity, checked after the two-hour window.

The share toggle decides who gets told. It never decides who can see.

That is why turning the toggle off does not satisfy the gates. A quiet edit made before day one is still visible to your current manager, your current clients, and the recruiter at the new firm the moment any of them open your profile. The matrix below treats the toggle and the gates as two separate questions.

How do garden leave and restrictive covenants change the answer?

During garden leave your old employer is still your actual current employer. You cannot start the new job and you remain bound by your duties, so the new employer does not go on your profile as current until the leave ends. Covenants matter less to the entry itself than to the broadcast. Courts have drawn the line between general announcements and targeted approaches.

In the sample, the employers shown alongside garden leave were Close Brothers Asset Finance (5 profiles), EY (2), and HSBC (1), all of them the profile holders' current, pre-move employers. The visible practice is to list the leave, not the new firm.

The US count for "incoming" is about 7.4 times the UK count. That is a raw keyword count, not a measure of incoming roles, so do not read it as a difference in practice between the two countries.

Garden leave periods typically run 30 to 90 days, according to one practitioner source. One practitioner note also says the new firm can announce the hire during garden leave, and that some employees change their profiles to show garden leave. So the passing pattern during the leave is: old employer still listed as current, garden-leave status added if you want it, new employer added on your actual first day.

What the cases say about posting

• BTS USA v. Executive Perspectives (Connecticut): the Appellate Court decision was officially released June 28, 2016. The non-solicit covered BTS customers for two years after employment ended. The court held that bare LinkedIn requests were not the kind of direct, active recruiting that breaches a non-solicit. It also noted that BTS had no policies on employees' use of LinkedIn or other social media.
• SafetyNet v Coppage (England, High Court, 2012): this involved a 6-month non-solicit. The court said a general advertisement to the world about availability at a new firm, or a specific notice to a client of the move, does not cross the line. The Court of Appeal later upheld the 6-month covenant. Five customers, about 5% of the client base, had moved to the new company.
• Hays v Ions [2008] EWHC 745 (Ch): decided April 16, 2008. It turned on confidential contacts being moved into LinkedIn before resignation, not on announcing a job.
• Amway Global v. Woodward (Michigan federal court, 2010): reported secondhand as holding that LinkedIn and blog posts breached non-compete and non-solicit agreements. I have not verified the opinion itself, so treat it as a reason for caution rather than a rule.

What should you do when the timing advice disagrees?

Grade against the gates and ignore the calendar. The published timing advice ranges from "on signing" for the resume to "two months after starting" for LinkedIn. Every source is answering a different question, and none of them grades the edit itself.

Mark Anthony Dyson's line, quoted by Forage, is blunt: "It's too early if you got the offer and have yet to start". Forage's experts also say that 90 days is still fine. Read the table this way:

• The rescission concern (Dyson, Resumetrick) is exactly gate G2. Once G2 is cleared in writing and you have started, that reason is satisfied.
• The courtesy concern (Teal) applies to the announcement post, not to the entry. A quiet day-one entry with sharing off does not broadcast anything to your former employer.
• The confidence concern (All Starz) is personal preference, and the standard does not grade it.
• The interviewing concern (WSO) is the only reason to touch the resume before day one, and it maps to the Incoming line.

So the standard's answer: the resume can change on signing, if you are interviewing. The LinkedIn entry goes in on day one once G1 to G4 are cleared, with sharing set however you choose. An announcement post waits for the covenant period to end, whenever that falls.

The procedure from signing day to day one

Run steps 1 to 6 on the day you sign or as soon after as each gate allows. Run step 7 on your first day and step 8 only when the covenant period ends. Each step has a written "done" state, and those written records are what make the grade repeatable.

Step 5 comes before any profile edit, even a harmless one. Removing Open to Work is itself a profile change, and you want sharing off before you make it.

How this goes wrong: failure modes and false passes

Most failures come from believing a control did something it does not do. A false pass is an edit that looks clean on your side while the record says otherwise. Each failure mode below is listed with what it looks like, the false pass it produces, and the check that catches it.

1. One toggle off, the other on.
   • Looks like: the global setting is off, but the per-edit toggle in the edit form is on, or the reverse.
   • False pass: "I turned sharing off in settings."
   • Check: open Recent Activity within two hours of the edit and confirm nothing new appeared.
2. Post-and-revert, then delete.
   • Looks like: you add the role, panic, and delete it.
   • False pass: believing a deleted entry was never shared. LinkedIn says editing or deleting "may affect" whether a notification is generated, which is not a guarantee.
   • Check: assume the notification went out, and handle it directly with anyone who matters.
3. Start month set to the signing month.
   • Looks like: you signed in one month and start in the next, and the profile shows the earlier one.
   • False pass: "it's only a few weeks."
   • Check: compare the profile month with the start date in the offer letter. They must be the same month.
4. Title differs from the offer.
   • Looks like: a public business title, or a level up, that is not the letter's title.
   • False pass: "everyone calls it that." A business title versus the HR title produced yellow flags in at least one reported case.
   • Check: compare it word for word with the record from step 1.
5. New employer listed during garden leave.
   • Looks like: the new firm shown as current while you are still employed by the old one.
   • False pass: "the new firm already announced me." The firm announcing you does not change who employs you.
   • Check: G3 and G4 dates. Until the leave ends, the old employer stays as current, as it does on the garden-leave profiles in Refolk's index.
6. Treating "passive is safe" as a rule.
   • Looks like: reasoning that because BTS found LinkedIn requests were not solicitation, any post is fine.
   • False pass: BTS turned partly on the absence of a social media policy at that employer, and targeted approaches like the conduct in Hays still create exposure.
   • Check: read your contract and your old employer's social media policy, and keep posts generic.
7. Open to Work left on after accepting.
   • Looks like: the banner or recruiter-only signal still active after signature.
   • False pass: "it's only visible to recruiters." All Starz staff flag that a hiring manager may see it.
   • Check: turn it off in step 5 and confirm.

One more case belongs here: announcing a new job and then having the offer rescinded. That is the Fail quadrant of the matrix. The edit went public with G2 still open. The fix is to correct the profile and handle the people who saw it directly, because a deletion does not recall the notification. The way to prevent it is G2 in writing and day one before any public entry.

Grading checklist and how to keep it current

Run this checklist twice: on the day you sign, against the resume line and settings, and again on day one, against the LinkedIn entry. Every item is a statement you can mark true or false. Any false item on a required gate gives Hold, and any false item on a field gives Fail.

Keep a one-line record of each grade so that a second grader, or you a month from now, can check the reasoning:

Edit: [Resume Incoming line / LinkedIn entry / Settings / Announcement post]
Date graded: [YYYY-MM-DD]
G1 Offer signed: [Yes / No] - evidence: [letter date]
G2 Contingencies cleared: [Yes / No] - open items: [list or none]
G3 Last day confirmed: [Yes / No] - last day: [date]
G4 Covenants and garden leave: [Clear / Live until date]
Title matches letter: [Yes / No]
Employer matches letter: [Yes / No]
Start month = first-day month: [Yes / No / N/A]
Share toggles verified in Recent Activity: [Yes / No / N/A]
Open to Work off: [Yes / No]
Grade: [Pass / Hold / Fail] - reason: [first rule that matched]

To keep the standard current, re-check the mechanism, not a remembered value. LinkedIn's share setting, its menu path, and its notification delays are all described in its help article on sharing profile updates. Re-read that article before you rely on the path or the two-hour window, and keep using Recent Activity as the test whatever the menus say. Screening turnaround figures are published by the providers and change with their methods. Treat the tables above as typical ranges, and use the clearance date your recruiter gives you in writing.

After day one, the resume needs one last pass: delete the Incoming line and replace it with a normal experience entry once you have done work worth describing. If you are building that entry from your own records, Refolk can draft it from your history and keep the title and dates aligned with what the offer letter, and later the verification record, will say.