The job creation time sink and how templates solve it
For recruiting teams that hire frequently for similar roles, job creation is a significant and largely invisible time sink. A recruiter who builds a new job posting from scratch — writing or retrieving the company description, crafting the role overview, listing responsibilities, specifying requirements, setting up pipeline stages, configuring screening questions, selecting approval workflow participants, and setting job board distribution — spends anywhere from thirty minutes to two hours on tasks that are substantially identical to work done for the same role three months ago.
Multiply this across a team of five recruiters, each hiring for five to ten role types on a repeating cycle, and the aggregate waste is significant: hundreds of hours per year spent recreating content that already exists, in formats that are slightly different each time, with inconsistencies that affect employer brand and candidate experience quality.
The inconsistency problem is as significant as the time problem. When different recruiters create job postings for the same role type from memory or from different archived documents, the result is job descriptions that describe the same role differently to different cohorts of candidates. One posting emphasises growth opportunities; another emphasises technical depth. One includes specific compensation information; another omits it. One lists eight screening questions; another lists three. These inconsistencies mean that the candidates applying to different rounds of the same role have materially different information about what they are applying for — affecting the quality and self-selection of applicants in unpredictable ways.
Job templates solve both problems simultaneously. A well-maintained template library standardises the content of common role postings, ensures consistency across hiring rounds and across recruiters, and reduces the job creation task from a writing exercise to a review-and-customise exercise that takes ten to fifteen minutes rather than an hour or more.
What to Standardise vs What to Customise
Standardise across all hires for a role type: company description, standard benefits, department overview, pipeline stage configuration, mandatory screening questions, approval workflow routing, and core role responsibilities that are consistent across hiring rounds. Customise for each specific search: specific project context or team priorities, required experience level adjustments, compensation range for the specific budget approved, office location or remote policy details, and any role-specific requirements that differ from the template default. Clear boundaries between the standardised and customisable sections prevent templates from becoming either too rigid to be useful or too loose to produce consistency.
Job duplication vs job templates: which to use when
Job duplication and job templates serve related but distinct purposes, and understanding when to use each produces better outcomes than relying on one or the other exclusively.
Job duplication creates a copy of a specific existing job — typically a recently closed or currently active posting — as the starting point for a new search. It preserves all the content and configuration of the source job: the job description text, screening questions, pipeline stages, and approval workflow. Duplication is appropriate when you are opening the same role again quickly — a replacement hire, an additional headcount for the same function, or a re-posted role where the previous round's posting was current and accurate.
The limitation of pure duplication is that it copies whatever state the source job was in when it was duplicated, including any content that may have drifted from the organisation's current standards. If a job was posted twelve months ago, its company description may be outdated, its requirements may not reflect current tooling, and its benefits list may not include benefits added since the original posting was written. Duplication without review can propagate stale content through the system.
Job templates are purpose-built canonical versions of a role type, maintained as current and accurate representations of what the organisation looks for in that role and how it presents the role to candidates. They are not copies of specific past postings but carefully designed starting points that reflect current best practice. Templates are appropriate for role types you hire repeatedly — where the consistency benefit of a maintained template outweighs the marginal customisation time compared to duplication.
In practice, the optimal approach for most teams is a two-tier system: maintain templates for the ten to fifteen most frequently hired role types, and use duplication for all other roles where the frequency does not justify maintaining a dedicated template. The template library covers the bulk of hiring volume with maximum consistency, while duplication serves the long tail of less frequent roles efficiently.
Building a template library for your most common roles
Building a template library is a one-time investment that pays compound dividends over subsequent hiring cycles. The process has three phases: identifying which roles warrant templates, creating the templates, and establishing a governance process for maintaining them.
Identifying template candidates is straightforward: pull your hiring history for the last eighteen to twenty-four months and identify the role types you have hired for most frequently. Any role type where you have made three or more hires within this period is a strong template candidate. Roles below this threshold typically do not produce enough repetition to justify the maintenance overhead of a dedicated template — duplication serves them adequately.
Creating templates well requires involving the right stakeholders. The recruiter who most recently hired for the role brings process knowledge — which screening questions worked well, which screening question answers reliably identified good candidates, which pipeline stages were unnecessary for this role type. The hiring manager brings role knowledge — what the description should say, which requirements are genuinely essential versus aspirational, what context helps candidates self-select accurately. Together, they produce a template that reflects both process quality and role accuracy.
Plan the template creation project as a focused sprint rather than an ongoing task. Dedicating a week to building templates for your top ten role types, with structured input sessions from relevant hiring managers, produces a complete library that is ready to use immediately. Spreading the work over months risks the project stalling before it delivers value.
Job Template Library in Treegarden
Save any job posting as a reusable template in Treegarden; when launching a new search, select the template and customise only what has changed. The template library is organised by department and role type, making it easy for any recruiter to find the right starting point. Templates include all job content, pipeline configuration, screening questions and approval workflow — so starting from a template means the entire job setup is pre-configured, not just the job description text.
What job templates should include
A job template that only contains the job description text covers a fraction of the work involved in creating a new job posting. A complete template covers every component of the job setup, so that launching a new search from a template requires minimal additional configuration beyond role-specific customisation.
The job description itself should include: a company overview paragraph (standardised and current), a team or department context section (describing the function and how it fits the organisation), a role overview paragraph (the primary purpose of the role), a responsibilities section (the core duties, described at the right level of specificity), a requirements section clearly distinguishing essential from preferred qualifications, and a benefits and working arrangements section (standardised for the role level, location and employment type).
Beyond the description, templates should include the screening question set for the role — the specific questions that candidates answer when applying, calibrated to screen for the most important initial filters. For a software engineering role, this might include questions about specific programming languages, experience with relevant system types, or a brief technical problem. For a sales role, it might include questions about quota attainment history or preferred sales methodology. These questions are role-specific and should be part of the template so they are not recreated each time.
Templates should also capture the pipeline stage configuration — the specific stages candidates move through for this role type, which may differ from the organisation's default pipeline. A role requiring a technical assessment has a different pipeline from a role that goes straight from screen to hiring manager interview. The approval workflow — who needs to sign off on the job before it is posted — should also be templated, as this typically follows a consistent pattern for each role level and department.
Customising templates for specific hiring rounds
The value of a template is not to eliminate customisation but to make it targeted and intentional rather than exhaustive. Starting from a template, a recruiter should complete a specific customisation checklist for each new search — a defined set of fields and decisions that require review and possible modification, while everything else remains as the template specifies.
A typical customisation checklist covers: the role-specific context section of the job description (what is this particular team working on right now, what is the immediate priority for the hire); the approved compensation range for this specific headcount (which may differ from the template's default range); any adjustments to required experience level (is this a junior, mid or senior instance of the role type); any temporary modifications to pipeline stages (is a technical assessment required for this round, or waived because internal candidates are being considered); and any changes to the approval workflow (new manager, interim coverage, exception to standard routing).
This customisation checklist should be embedded in the template as a set of clearly flagged fields rather than left to the recruiter's judgement about what needs updating. Fields that should not change are locked; fields that require review are flagged. This structure ensures that customisation happens intentionally and that nothing important is overlooked or left as a stale template default when it should have been updated for the specific search.
One-Click Job Duplication
Duplicate an existing live or closed job in Treegarden with all settings intact — pipeline stages, screening questions, approval workflow, job board configuration — for immediate editing and launch. Duplication is ideal for replacement hires or additional headcount where the recent posting is current and accurate. The duplicated job opens in edit mode so the recruiter can make necessary updates before publication, rather than launching a carbon copy without review.
Keeping templates current and consistent
A job template library that is not maintained is worse than no library at all — it creates the false confidence of having a standard while propagating content that has silently become outdated. Template maintenance is the governance practice that determines whether the library delivers lasting value or becomes a liability.
The minimum maintenance commitment is an annual review of every template in the library. This review checks: does the company overview still accurately describe the organisation? Has the role's technology stack, tooling or methodology changed in ways that affect the requirements? Have benefit offerings changed — new wellbeing benefits, changes to pension contributions, updated remote working policy — that should be reflected? Have the screening questions proven effective in identifying good candidates, or have they been generating false positives or false negatives that suggest recalibration?
Templates should also be updated reactively when specific events occur: when the approval workflow for a role type changes because of an organisational restructure; when legal or compliance requirements change the mandatory fields or disclosures that must appear in the job posting; when a significant hire quality problem — a pattern of underperforming hires for a specific role type — suggests the job description requirements may be pointing in the wrong direction.
Establishing clear ownership for each template prevents the tragedy of the commons where templates belong to everyone and therefore no one. Each template should have a named owner — typically the senior recruiter or HR business partner most closely associated with that function — who is accountable for keeping it current. Template ownership should be included in role descriptions and performance objectives for senior recruiting staff.
Create Templates After Your Second Hire, Not Your First
The first time you run a search for a role, your requirements are still forming — you are learning what good looks like, which screening questions surface the right signals, and which pipeline stages are necessary for this role type. After the second hire, you have enough experience with the role to understand what works. Create the template at this point, when your knowledge of the role is concrete and tested, rather than after the first hire when it is still largely theoretical. A template built on two hiring cycles is significantly more accurate and useful than one built before you have hired the role successfully.
Collaborative template management across the recruiting team
In teams of more than two or three recruiters, job templates require explicit governance to prevent version control problems and ownership ambiguity. Without clear rules about who can edit templates, under what conditions, and with what notification to the team, templates become fragmented — different recruiters work from different versions, edits made for one search inadvertently affect future searches using the same template, and the consistency benefit of having templates is undermined.
The core governance principle is separating template editing from job creation. Creating a new job from a template should never modify the template itself — the new job is a fresh copy that the recruiter can edit freely without affecting the master template. Modifying the master template should be a separate, deliberate action available only to template owners, and it should be logged with the reason for the change, who made it and when.
For teams where multiple people have legitimate input into template content — recruiting leads, HR business partners, departmental heads with strong views on how their roles are described — a review and approval process for template changes prevents unilateral modifications that others are not aware of. A simple process where template change proposals go to a small review group (the template owner plus one other senior stakeholder) before being applied provides adequate governance without creating bureaucratic friction.
Transparency about template versions matters for organisations that operate in regulated industries or have specific equal opportunity reporting requirements. Knowing which version of a job template was used for each posting — and therefore what requirements and screening questions candidates were evaluated against — is important for demonstrating consistency across applications and for audit purposes if a hiring decision is challenged.
Template Version History
Treegarden tracks changes to job templates over time, records who modified each template and when, and allows template owners to revert to previous versions if a change is identified as problematic. The version history is available for every template in the library, giving HR leaders confidence that template edits are transparent and recoverable. Jobs created from a template record which version was used, creating a complete audit trail from template to posting to hire.
Frequently asked questions about job templates and duplication
What is the difference between job duplication and job templates in an ATS?
Job duplication creates an exact copy of an existing job posting — including all settings, pipeline stages, screening questions and approval workflow — as a starting point for a new search. It is used when you are opening the same role again or a very similar one with only minor differences. Job templates are pre-designed frameworks for common role types that serve as canonical starting points for new searches rather than copies of specific past postings. Templates are maintained as living documents and updated periodically; duplicated jobs are snapshots of a specific past posting that may need more significant updating.
What should a job template include?
A well-designed job template should include: the full job description with company overview, team context, responsibilities and requirements; screening questions specific to the role type; the pipeline stage configuration; the approval workflow; any mandatory compliance fields; the job board posting configuration; and a notes section documenting what to customise for each new search. Templates should not pre-fill compensation ranges, specific team context or role-specific requirements that change each time — those should be completed during customisation.
How many job templates does a typical organisation need?
Most organisations need templates for their top five to ten most frequently hired role types, covering 70-80% of their hiring volume. Beyond that, the return on template creation diminishes because roles are too infrequent to justify the maintenance overhead. A useful threshold: create a template for any role type you have hired for three or more times. Below that threshold, job duplication — copying the most recent posting for that role — is usually sufficient.
How often should job templates be updated?
Job templates should be reviewed at least annually and updated whenever a significant change occurs to the role, its requirements or the organisation's standard practices. Specific triggers for update: changes to mandatory screening questions (legal compliance updates, new role requirements), changes to the approval workflow (new sign-off requirements or removed approvers), market feedback that the job description is attracting the wrong candidates, changes to standard benefits or compensation positioning, and feedback from hiring managers that the template requirements no longer accurately describe the role.