Knowledge Base
> Getting Started
Review and approve a job before publishing
publishing
| 5 Min Read
Review and approve a job before
publishing
The pre-publish check that catches the things you'd otherwise discover after the job is live and the first candidate has applied.
What this step is for
The fourth and final step of the wizard is a review screen. The job isn't published yet; the system is showing you everything you've
configured, in the order a candidate or your team will see it, before anything goes live.
Two things are being reviewed:
The candidate-facing view. Title, description, location, salary, employment type. What a candidate sees on your career page and
on job boards.
The internal configuration. Core criteria, pipeline stages, assessments, automations, approvals. What your team sees when
working the role.
Both matter. Errors on the candidate side (a typo in the title, the wrong salary range) are embarrassing. Errors on the internal side (a
missing assessment, the wrong required criterion) cost you weeks of confused screening.
The pre-publish checklist
Walk through this list before clicking Publish:
Is the title right? It will be searched, indexed, and posted to multiple job boards. Errors are hard to undo cleanly after the job is
live.
Does the description make sense as a job ad? Read it as a candidate would. Is it clear what the role does, who it's for, and what
success looks like? AI-drafted descriptions are usually fine but sometimes drift; this is your last chance to fix.
Is the salary range in the right currency and within your band? Especially worth double-checking if you duplicated from an
existing role.
Are the core criteria specific enough? "Strong communicator" doesn't help the AI. "Professional written English and Arabic" does.
Does the pipeline reflect your actual process? No phantom stages from a duplicated template, no missing assessment, no
automation pointing at the wrong message template.
Are the right people approved to take sensitive actions on this role? Especially Hiring Managers; verify they're assigned to this
role.
The review screen has anchors that jump back to any section of the wizard. Click one, fix it, return to review.
[Illustration: Annotated screenshot of the review screen showing the candidate-facing preview on the left and the internal
configuration summary on the right.]
When approval is required
Some workspaces require a second teammate to approve a job before it can be published. This is configured at the workspace level
by an Admin, from Settings → Workflow → Job Approval.
If approval is required:
After completing the wizard's review step, click Submit for Approval.
The job enters a Pending Approval state in the Jobs list.
A notification fires to the designated approver (often the head of recruiting, the hiring manager, or any Admin, depending on the
configuration).
The approver opens the job, reviews the same screens you just reviewed, and clicks Approve or Request Changes.
Approve moves the job to publishable status. Request Changes sends it back to you in draft state with the approver's notes.
If approval isn't required for your workspace, Publish is the direct action and the job goes live immediately.
Common reasons jobs get sent back
When an approver requests changes, the usual culprits:
Title doesn't match what we agreed on. Often a wording issue; quick fix.
Salary range is outside band. Usually requires a conversation with finance or the hiring manager.
Job description has issues (legal language, inclusion language, factual claims). Read these notes carefully.
Pipeline missing a required stage (e.g., a regulated industry that requires a specific verification step).
Criteria too narrow or too broad for the kind of pool the team wants.
If the approver requests changes, address them in the wizard and resubmit. The same approver gets the new version; they don't
have to be reassigned.
After approval
Once approved (or if approval isn't required), the Publish button becomes active. Clicking it does several things in sequence:
The job goes live on your career page.
Distribution kicks off to any job boards you've configured.
The per-job Talinty email address is activated.
The pipeline begins accepting candidates.
What happens next is covered in Publish a job to your career page and Use the per-job Talinty email address.
