Internal openings versus public job applications

An internal opening is visible to current employees. A public opening is visible to outside applicants. Organisations may use one, the other, or both for the same job. There is no universal rule that internal must always come first. This page owns those two audiences and how they share one job object without mixing identities. It does not retell posting versus job description — that stays on job posting versus job description. It is not a second ATS definition. Product context: Dayzen recruitment includes an internal job board and public application portals. Employee identity after hire lives in Dayzen employee management — directory and profiles — which is a different object from a candidate apply.

Teams collapse the two audiences into one careers page and then wonder why employees apply as strangers, or they run a rumour mill of “who is leaving” because the only internal signal was a public ad. The fix is not a law. It is two surfaces, one requisition, and clear identity rules.

One job object, two audiences

Create the job once: title, department, status (open, closed, archived), internal spec, posting text. Then choose visibility:

• Internal board only — employees can see and apply; the public portal does not list it.
• Public portal only — outside candidates apply; employees are not a named audience (they may still apply as outsiders if they find the link, which is a hygiene issue to decide).
• Both — same job ID, two entry points, applications tagged by source.

The JD remains the internal specification. The posting remains the advertisement, possibly with two tones: a shorter internal note that names the team, and a public note that does not leak client names or bands you keep off the internet. Contradiction between those two postings is still contradiction. Audience is not a licence to promise remote internally and office-only publicly.

Dayzen recruitment supports that job lifecycle (create, edit, close, archive) and those two surfaces. It does not, as a product claim, syndicate the opening to every external marketplace. If you copy the public posting elsewhere, keep apply links pointed at the portal that writes your application record.

There is no universal internal-first rule

Some companies always post internally for a week. Some never do, because the role is new, confidential, or clearly not fillable from the current bench. Some post both on the same day. Policy can prefer internal mobility. This page will not tell you that Indian employment practice requires an internal-first window. Write your own rule and follow it, including exceptions (executive search, a role created for a named successor, a confidential backfill).

What you should not do is claim internally that “we always look inside first” while the public portal went live last Tuesday. Employees notice. The operating cost is not morale poetry. It is applications you did not expect, and managers who already promised the role to an outsider before employees heard.

If you do run an internal window, make it real: the job is on the internal board, managers know they may not extend an outside offer yet, and the window has an end date. A window with no board posting is a rumour, not a process.

Identities must not mix

An employee applying internally is still a person you already have in the directory. An outside applicant is a candidate. Do not create a second employee row because they applied. Do not treat an internal apply as a resignation. Do not hide the application from the current manager in a way your policy did not decide — confidentiality of internal applies is a policy choice you must write down, not a default this article invents.

Practical splits:

• Internal apply: bind to the existing employee identity (employee ID, work email). The application hangs on the job. HR should not open an add-employee wizard.
• Public apply: bind to candidate identity (personal email, phone). After hire, convert or create one employee record — search the directory, including exited people, before typing a new human.
• Employee applying on the public link: decide whether you redirect them to the internal board or accept a candidate-shaped apply you later match to the employee ID. Leaving both records unlinked is how you get duplicate employees after they “join” a role they already occupy in another team.

Employee management is the system of record for who already works there. Recruitment is the system of record for the opening and the applications. The join path after an outside offer is onboarding, not a third identity. Keep those objects distinct even when the same HR person clicks all of them.

When internal-only is the honest choice

Use internal-only when the work is a mobility or restructure story you are not advertising outside: a shift of reporting lines, a role that exists to retain someone, a location move you will fill from the current headcount. Public ads in that situation create applies you will never hire and a market rumour you did not want.

Internal-only still needs a posting (even a short one) and a close. A Slack message is not an opening. If nobody on the board can apply because they do not know it exists, you did not run an internal process. You ran a tap on the shoulder. That can be valid for a confidential backfill — then do not pretend there was a board.

When public is the honest choice

Use public when you need skills you do not have, volume, or a location you cannot staff from current employees. You may still tell employees it is open; that is courtesy, not an internal-first window. Public portals need a complete enough apply form and a job that is actually open. Leaving a public link live after you hired internally is how you collect people you will ghost. Close or archive the job.

Confidential public searches (a replacement while the incumbent is still in seat) are a special case: you may use a generic title, an agency, or a delayed internal notice. That is policy and risk, not a Dayzen feature. Do not use the internal board as a leak if the decision was confidentiality. Do not use the public portal with the incumbent’s exact title if that was the risk you were managing. Align the two surfaces to the same confidentiality choice.

Applications from two doors still need one pipeline

Source tags matter: internal board versus public portal versus referral versus agency. They do not need two Kanban designs. The candidate state (applied, screen, interview, offer, hired, rejected) is the same object family. Internal applicants should not get a shadow process that never files feedback. Public applicants should not skip a screen the internal people received. Fairness here is operational consistency against the JD, not a legal conclusion.

Interviewers should know whether the person is an internal applicant if that changes context (they already know the stack, they have a current manager). They should still assess against the role. “We already employ them” is not a substitute for must-haves. “They are external” is not a substitute for evidence. File remarks on the application either way.

When you hire an internal mover, the outcome is not a new human. It is a dated employment-record change (role, manager, maybe pay) with an effective date — that event type lives in lifecycle, not in a second candidate-to-employee conversion. When you hire an external, you do convert candidate to employee. Mixing those two outcomes on the same job is normal; mixing them on the same identity is the bug.

Managers, rumours, and backfills

Internal boards make attrition visible. If that is unacceptable for a particular seat, do not post internally, and do not complain that employees heard via the public ad instead. If you post internally, brief the current manager before the board goes live when the role reports to them or sits in their team. Blind-siding a manager with their own backfill on the intranet is an ops failure, not a feature of “transparency.”

Employees will ask whether applying is held against them. Your written rule should say whether current managers see internal applies, who in HR sees them, and that retaliation is outside this article’s scope — point people to whatever internal policy you actually run. Do not invent a POSH or labour-law lecture here. Do decide the visibility so TA is not improvising per requisition.

Failure modes

Symptom	Cause	Fix
Employee applies as a new candidate	Only a public link existed	Internal board, or match to employee ID
Two employee rows after an internal move	Treated as a new hire	Same identity; dated role change
Public applies continue after internal hire	Job still open on the portal	Close or archive the job object
“We always hire inside first” but ads were live	Policy theatre	Write the real rule; align both surfaces
Internal posting contradicts public posting	Two ads, no JD source	JD first; postings may shorten, not clash

A short working agreement

1. Every opening is one job record. Audiences are visibility flags, not duplicate jobs with almost the same title.
2. Internal board and public portal may both point at that record. Marketplace copies are not a Dayzen claim; they must not invent a third title.
3. Internal apply binds to the employee. Public apply binds to the candidate. Search before you create.
4. There is no mandatory internal-first week unless you published one and actually used the board.
5. When the job is filled, both surfaces stop collecting. Remaining applications get a terminal state.

Use Dayzen’s internal job board and public application portals as those two audiences. Use employee management for the directory you must search so an internal mover is not born twice. Use the posting-versus-JD article when the argument is advertisement versus spec. Use this page when the argument is who is allowed to see the opening, and how you keep one job without mixing the people who already work there with the people who do not yet.