What Is Specification Merging?
Specification merging combines two or more classifications into one. Over time, classifications can drift apart from organizational restructuring, separate hiring decisions, or career progressions that grew more complex than they need to be. Merging gives you a way to consolidate that sprawl into a cleaner set of specs without losing the content that matters.
Holly's merge tool doesn't just stitch documents together. It analyzes the content of each specification you select and produces a draft that reflects your stated priorities, whether that means preserving specific certifications, reconciling different experience requirements, or deciding which job title and salary structure should anchor the result.
Common Use Cases
Classifications that evolved separately but now do similar work. Two roles created years apart for different departments may have converged on nearly identical duties.
Organizational restructuring. A reorg can leave you with duplicate positions across departments that should be consolidated into one classification.
Overly complex career progressions. A series with too many narrow levels can be simplified by merging adjacent levels into clearer, more meaningful steps.
Administrative efficiency. Maintaining many near-duplicate specs increases your maintenance burden. Merging reduces that overhead.
Finding Specifications to Merge
Navigate to any specification and click the Internals tab to see merge candidates: specifications with 60% similarity or higher compared to your chosen spec.
The Internal specifications view displays:
Expansion arrow to the left of a class name — expand any row to see full comparison details
Class name — related specifications from your organization
Match % — a similarity score with a color-coded dot indicating how closely the specifications align. For more on how this score is calculated, see Understanding Similarity Analysis
Min/Mid/Max salary — salary ranges, with percentage differences from your current spec
3 Dots to right of Max salary — open to access Merge capability (shown below)
Holly automatically surfaces specifications with a 60% or higher match. If you're looking for a spec that doesn't appear automatically, use the search bar covered in Adding and Managing Comparators.
Reviewing Match Details Before You Merge
Click the ▼ arrow next to any specification to see comprehensive information across three tabs.
Details tab — any notes added, and the pay schedule with hourly, biweekly, monthly, and annual conversions.
Class specification tab — the full specification content.
Similarity analysis tab — a summary of the analysis, key similarities, key differences, and recommendations for how to use the comparison.
Use this detailed view to confirm that a high similarity score reflects a genuine merge opportunity and not just a surface-level match.
Tip: Reviewing the similarity analysis before merging saves time. It's much faster to catch a mismatch here than to discover it after the merge has already produced a draft.
How to Merge Specifications
Step 1: Open the Merge Tool
Click Merge from the Action dropdown on any comparison. Holly opens a merge interface that walks you through the decisions that shape your result.
Step 2: Select Specifications to Merge
Choose all classifications you want to combine. The specification you started from is pre-selected.
Selection tips:
Merge 2–4 specifications at a time. Merging more than that can reduce the quality of the result.
Merge roles that are similar in seniority and supervisory responsibility. Mixing very different levels makes for a messier result.
Note: Only specifications already in your comparison table can be selected here. To add others, use Explore additional comparisons from the Internals tab first.
Step 3: Choose How to Merge
Select your merge approach from the dropdown. Holly offers two strategies.
Option 1: Use a Specification as Base Template
Select "Use [Specification Name] as base template" for any of your selected specs.
How it works:
Holly uses your chosen spec as the foundation
It incorporates relevant elements from the other selected specifications
The result is a new draft that retains the base template's salary range and title structure
The original specification is preserved and can be archived later or reused in another merge
Best for: situations where one classification should remain the dominant structure, where you want continuity with an existing well-built spec, or where the salary range and title need to stay consistent. This covers most standard merge scenarios.
Example: Say you want to streamline your Account Clerk series by removing Account Clerk – Advanced Level, while making sure some of its responsibilities carry over. You could use Account Clerk – Experienced Level as the base template and instruct Holly to incorporate the KSAs from the Advanced Level. The result keeps the Experienced Level's salary range and structure, enhanced with the relevant content from the level you're removing.
Option 2: Create New Specification
Select "Create entirely new specification" to build an entirely new classification.
How it works:
Holly combines all selected specifications into a new classification
No single specification dominates. It's a balanced merge of all the content
The new spec doesn't inherit title structure from any one source
You define the salary range and naming independently
Best for: equal mergers where no specification should be dominant, cases where the existing specs are outdated or incomplete, or building something genuinely new without legacy structure.
Example: Merging several aging IT classifications into a modern, comprehensive technology specialist role that doesn't favor any one legacy structure.
Which option should you choose? Use base template when you want to build on one existing classification. Use create new when you're building something new, or when no single source spec should be privileged over the others.
Step 4: Review or Input the Salary Range
This step depends on your merge approach.
If you're using a base template, the modal displays that specification's existing salary range, and this range carries over to the merged spec.
If you're creating a new specification, you'll input the salary range directly. Consider the ranges from your source specifications as a starting point.
Warning: You cannot edit the salary range after completing the merge. Confirm it's correct before proceeding.
Step 5: Provide Additional Information (Optional but Recommended)
Use the additional information field to tell Holly how to handle your specific merge priorities. This step is optional, but it meaningfully improves your results.
Guidance helps Holly prioritize competing content from multiple sources, keep critical requirements front and center, and reflect your organization's specific needs. It also tends to produce a better result on the first attempt, which saves you regeneration cycles later.
Effective guidance examples:
Effective guidance examples:
Reconciling different experience levels: "Accountant I requires 1 year experience, Accountant II requires 3 years, and Senior Accountant requires 5 years. Create a merged spec with three grade levels that maintains these experience progressions clearly distinguished across levels."
Handling supervisory differences: "Program Manager supervises 2-3 staff while Program Director supervises 8-12 staff and oversees budget. Merge into a single classification with Grade I (no supervision), Grade II (supervises 2-5 staff), and Grade III (supervises 5+ staff with budget authority)."
Reconciling conflicting education requirements: "Position A requires Bachelor's degree, Position B accepts Associate's degree with 2 additional years experience. Use the more flexible requirement: Associate's with 4 years OR Bachelor's with 2 years."
Merging different technical focuses: "GIS Analyst focuses on spatial analysis while Data Analyst emphasizes statistical modeling. Create merged specification that requires general analytical skills with specialized knowledge in either GIS or statistical methods, not both."
Combining overlapping but distinct duties: "Parks Maintenance Worker includes grounds care and basic repairs. Facilities Technician includes HVAC and electrical work. Merged spec should cover general facilities maintenance with grounds care as supplemental duty, not primary focus."
Preserving critical certifications: "One spec requires CDL Class B, another requires First Aid certification. Both are essential and must be maintained in merged specification. CDL required at hire, First Aid must be obtained within 90 days."
Handling different reporting structures: "Assistant Director - Parks reports to Parks Director. Assistant Director - Recreation reports to Recreation Director. Merged spec should report to Director of Parks & Recreation with flexibility to assign to either division based on operational needs."
Guidance tips:
Be specific about content priorities and how to reconcile differences
Mention essential requirements that must be preserved
Note organizational context Holly wouldn't otherwise know
Clarify how to handle competing or conflicting content
Specify level distinctions if you're merging multiple grades
Don't over-specify. Leave room for Holly's AI to do the merging work
Step 6: Complete and Review Your Merged Specification
Click Merge to generate your new specification. Holly processes the merge and takes you to the resulting draft.
Understanding Your Merged Specification
Holly creates a draft specification combining your selected specs. Review the results carefully before publishing.
What you'll see:
Change chips below each section, explaining what was merged and why
Complete content drawn from all merged specifications
Use the change chips as your starting point for review. They tell you exactly what Holly drew from each source, which makes it easier to spot anything that needs adjustment without rereading every section from scratch.
Refining your merge:
Use the edit function to add organizational context or adjust any section
Click the regenerate icon on specific sections that need improvement
Make any necessary changes before publishing
Once you're satisfied with the merged specification, publish it through your normal approval workflow. Your original specifications remain available and can be archived when you're ready.



