HR knowledge has a distinctive property that most other professional knowledge doesn't: it's time-sensitive in a specific legal sense. The minimum wage rate that applied to a specific pay period, the accommodation guidance that was current when an interactive process was conducted, the leave law requirements that applied to a specific employee's request — these facts are not just "what the law says now" but "what the law said then." An HR manager whose knowledge base doesn't maintain dated records of regulatory requirements can't reconstruct the compliance basis for past decisions.
A searchable knowledge base for HR managers organizes four knowledge types that are specific to the profession: employment law by jurisdiction, organizational policy, HR practice and employee relations patterns, and compensation and benefits benchmarks — each organized for retrieval when it's needed for a current decision and for documentation of what was known when past decisions were made.
The Four Knowledge Types in an HR Manager's Knowledge Base
Type 1 — Employment law and regulatory knowledge:
The applicable regulatory requirements at federal, state, and local levels — what the law requires, when requirements took effect, how regulatory agencies interpret ambiguous provisions, and what has changed with each regulatory update. The time-sensitivity of this knowledge type is uniquely important: not just what the law says now, but what it said when a specific decision was made.
Type 2 — Organizational policy knowledge:
The organization's own policies — what they say, which version is current, when each version took effect, and how policies have been interpreted and applied. Policy knowledge includes both the written document and the organizational practice around it.
Type 3 — HR practice and employee relations knowledge:
The accumulated experience of handling HR situations — how specific types of situations have been handled, what the outcomes were, what approaches have worked and which have created problems, and the analytical frameworks for thinking through complex situations.
Type 4 — Compensation and benefits knowledge:
Market data for compensation benchmarking, internal compensation structures, benefits plan details and costs, and the history of compensation decisions. This knowledge type is explicitly time-stamped because compensation market data is anchored to specific survey dates.
The Knowledge Base Architecture
Layer 1 — Employment Law by Jurisdiction
EMPLOYMENT LAW KNOWLEDGE BASE
└── [JURISDICTION — Federal / State / Local]
└── [LEGAL TOPIC — e.g., "Minimum Wage"]
CURRENT REQUIREMENT:
Rate/requirement: [Current requirement]
Effective date: [When this took effect]
Source: [Official URL — with archive.org backup + capture date]
PRIOR REQUIREMENTS (history):
[Prior rate]: effective [date] through [date] — [Source URL + archive.org backup]
[Prior rate before that]: effective [date] through [date] — [Source]
COMPLIANCE NOTES:
Who this applies to: [Which employees, which employer sizes, any exceptions]
Interaction with other requirements: [How this interacts with other laws]
Common compliance issues: [Where organizations typically get this wrong]
UPDATE HISTORY:
[Date]: [What changed]
[Date]: [...]
The history layer is the legal defense layer:
The history of prior requirements is what allows the HR manager to answer the question "what was the minimum wage during the period [date] through [date]?" — a question that may be asked during a wage claim investigation years after the period in question. Without the history layer, the HR manager knows what the current rate is but can't document what it was during a prior period.
Layer 2 — Organizational Policy Knowledge Base
ORGANIZATIONAL POLICY KNOWLEDGE BASE
└── [POLICY CATEGORY — e.g., "Leave Policies"]
└── [SPECIFIC POLICY — e.g., "Family and Medical Leave"]
CURRENT VERSION:
Version: [Version number or date]
Effective date: [When this version took effect]
Document location: [Where the current version is stored]
PRIOR VERSIONS:
[Version 1.0]: effective [date] through [date] — [Document location]
[Version 1.1]: effective [date] through [date] — [Document location]
POLICY SUMMARY:
What the policy says: [Plain-language summary of key requirements]
Who it applies to: [Which employee categories]
ADMINISTRATION NOTES:
How requests are submitted: [The process]
Who approves: [Decision authority]
Documentation required: [What the employee must provide]
INTERPRETATION NOTES:
Common questions: [Questions that arise frequently + how they're answered]
Judgment calls made: [Situations where policy applied in specific ways]
LEGAL BASIS:
Federal requirement: [What federal law requires]
State requirements: [What state law requires, if different/more generous]
How policy compares: [Does the policy meet, exceed, or have gaps vs. legal minimum?]
EMPLOYEE COMMUNICATIONS:
When employees receive this policy: [Onboarding, handbook, other]
Acknowledgment required: [Yes/No; if Yes: how tracked]
Layer 3 — HR Practice and Employee Relations Knowledge
HR PRACTICE KNOWLEDGE BASE
└── [SITUATION TYPE — e.g., "Performance Improvement Plans"]
THE SITUATION TYPE:
What it is: [Description of the situation type]
When it typically arises: [Circumstances that lead to this situation]
Legal dimensions: [What legal requirements or risks attach to this situation type]
THE STANDARD PROCESS:
Step 1: [What happens first]
Step 2: [What happens next]
[...]
Documentation required at each step: [What must be documented and when]
DECISION FRAMEWORK:
Key questions to assess: [What determines how to handle a specific instance]
Factors that change the approach: [What circumstances change the standard process]
Escalation criteria: [When to involve legal counsel, senior leadership, or others]
WHAT'S WORKED:
[Effective approaches in prior situations of this type]
[What's made outcomes better]
WHAT HAS CREATED PROBLEMS:
[Approaches that have created complications]
[What to avoid]
LEGAL CONSIDERATIONS:
Protected class issues to consider: [Any EEO considerations for this situation type]
Retaliation risk: [If this situation arises in a specific context]
Documentation requirements: [What must be in the file for legal defensibility]
The case pattern layer:
The practice knowledge base captures not just procedures but case patterns — how specific types of situations typically develop, what early signals predict escalation, and what approaches have tended to resolve situations effectively vs. create additional complications. This case pattern knowledge is what makes an experienced HR manager distinctively valuable: not just knowing the policy, but knowing how situations typically unfold.
Layer 4 — Compensation and Benefits Knowledge
COMPENSATION AND BENEFITS KNOWLEDGE BASE
└── [COMPENSATION ELEMENT — e.g., "Software Engineer — Senior Level"]
MARKET DATA:
Survey source: [SHRM / Radford / PayScale / Other]
Survey date: [CRITICAL — when this data was collected]
Geographic market: [What geographic comparison set this reflects]
Percentiles:
25th percentile: [Amount]
50th percentile: [Amount]
75th percentile: [Amount]
90th percentile: [Amount]
How this was used: [What compensation decisions this data informed]
CURRENT INTERNAL COMPENSATION:
Internal range: [Current approved range]
Range effective date: [When this range was established]
Where current employees fall: [Band distribution — without individual identification where needed]
PAY EQUITY CONSIDERATIONS:
Any pay equity analysis conducted: [Yes/No — if Yes: date + findings + actions taken]
UPDATE HISTORY:
[Survey year]: [How the range or data changed from prior year]
[...]
The Pre-Decision Check
Before making any significant HR decision — disciplinary action, accommodation determination, leave approval, compensation change — a pre-decision knowledge base check retrieves the relevant compliance requirements and organizational policy:
PRE-DECISION CHECK — [Date]
SITUATION: [Brief description of the decision to be made]
REGULATORY CHECK:
Applicable federal requirements: [What federal law says about this situation]
Source: [KB entry or regulatory reference — with date of guidance checked]
Applicable state requirements: [What state law says — jurisdiction: which state]
Source: [KB entry or regulatory reference — with date]
Local requirements: [Any local ordinance requirements]
Source: [...]
POLICY CHECK:
Applicable policy: [Which policy applies]
Version: [Current version + effective date]
What it says: [Relevant policy provisions]
Any interpretation notes: [Prior application of this policy to similar situations]
CONSISTENCY CHECK:
How have similar situations been handled? [Case pattern review]
Any consistency concerns: [Would this decision be consistent with prior decisions?]
DECISION BASIS:
What the decision is: [Clear statement of the decision]
Regulatory basis: [What regulatory requirement supports this decision]
Policy basis: [What policy provision supports this decision]
Documentation plan: [What will be documented and when]
The Post-Situation Knowledge Routing
After significant employee relations situations are resolved:
POST-SITUATION KNOWLEDGE ROUTING — [Date]
SITUATION TYPE: [What type of situation this was]
Resolution: [How it was resolved]
KNOWLEDGE BASE UPDATES:
HR practice knowledge: [Any new patterns or insights from this situation]
Policy knowledge: [Did this situation reveal a policy gap or interpretation question?]
Regulatory knowledge: [Any new regulatory clarity from this situation?]
CASE FILE:
Location of full documentation: [Where the employee relations file is stored]
Key documents: [What's in the file]
Key Takeaways
-
An HR manager's knowledge base has four layers. Employment law by jurisdiction (with history layer showing prior requirements — the legal defense for past decisions); organizational policy (with version history — what policy applied at which time); HR practice and case patterns (how situations unfold + what works + what creates problems); compensation and benefits (market data with survey dates + internal ranges with effective dates).
-
The history layer in employment law knowledge is what makes past decisions defensible. When a wage claim or discrimination charge involves a prior period, the question is what the law required during that period — not what it requires now. The history layer answers that question.
-
Policy version history is how you answer "what policy applied at that time." An employment dispute may involve actions taken under a prior version of a policy. Without version history, the HR manager can't document what policy applied at the specific time.
-
Case pattern knowledge is the most expert layer of HR practice. Not just procedures, but how situations typically develop, what early signals predict escalation, and what approaches have worked vs. created complications. This knowledge comes from experience and accumulates over a career.
-
All compensation data is time-stamped with the survey date. Market data from two years ago reflects a different labor market. Survey dates on every data point prevent using outdated benchmarks for current decisions.
Conclusion
A searchable knowledge base for HR managers creates the compliance and practice infrastructure that allows HR decisions to be both legally defensible and consistently applied: employment law by jurisdiction with history layers, organizational policy with version control, HR practice knowledge with case patterns, and compensation data with survey dates. The time-sensitivity built into the knowledge base architecture — dated regulatory captures, policy version history, compensation data with survey dates — is what makes this system distinctively different from a generic information organization system. It's not just what the law says; it's what the law said, when, documented with the source — the architecture of legal defensibility.
For more on this, see Building a Personal Knowledge Base.