See how jobs and rates work together in workforce procurement
Job Classes, Job Titles, and Rate Card Classes form the foundation of workforce procurement configuration. Together, these three records define positions, organize rate structures, and support workforce requests.
In Beeline Enterprise, that relationship is commonly known as the Rate Card Trifecta. Understanding how these components work together can help you configure procurement records more effectively, prepare data imports, and avoid common dependency and validation issues.
Those three records are interrelated and should be synchronized to support procurement workflows, imports, Rate Cards, and Request Templates. Keeping them aligned helps ensure dependent records function correctly throughout Enterprise.
Use this article as a reference guide when configuring procurement structures, preparing imports, or troubleshooting procurement record relationships.
Jump to what you want
Why it matters
- Provides the foundation for procurement configuration.
- Supports consistent job and rate structures.
- Helps reduce configuration and import errors.
- Supports Rate Cards and Request Templates.
Who it's for
- Program Office users
- Procurement administrators
- System Administrators
- Data administrators
How it helps
- Understand how procurement records relate to one another.
- Identify dependencies between job and rate structures.
- Prepare for procurement imports and maintenance activities.
- Support Rate Card and Request Template configuration.
How it works
Use the Rate Card Trifecta to understand how job structures and rate structures fit together.
Rate Card Trifecta components
The Rate Card Trifecta consists of three related procurement records. Each record serves a distinct purpose, and together they help define positions, organize rate structures, and support workforce requests.
| Component | Purpose |
|---|---|
| Job Class | Group related positions into a common category. A Job Class serves as the parent classification for one or more Job Titles. |
| Job Title | Define a specific position within a Job Class. |
| Rate Card Class | Define a specific position that is procured in Beeline Enterprise. Job Titles are client-specific and are used throughout procurement configuration and Request Templates. |
How the components work together
Each component depends on and supports the others. Understanding these relationships can help you troubleshoot procurement configuration issues and plan imports more effectively.
| Relationship | Purpose |
|---|---|
| Job Class → Job Title | Use Job Classes to organize related positions. |
| Job Title → Rate Card Class | Associate similar Job Titles with the appropriate rate structure. |
| Rate Card Class → Rate Card | Use Rate Card Classes to support Rate Card configuration. |
| Rate Card Trifecta → Request Template | Use all three components when building Request Templates. |
Together, these components answer three important questions:
| Question | Component |
|---|---|
| What type of work is being requested? | Job Class |
| What specific position is being requested? | Job Title |
| Which rate structure should apply? | Rate Card Class |
Typical Trifecta relationship
For many implementations, the relationship between these records is maintained as a 1:1:1 structure.
| Component | Example |
|---|---|
| Job Class | Data Management |
| Job Title | Data Analyst I |
| Rate Card Class | Data Analyst I |
In that example:
- The Job Class defines the overall category.
- The Job Title identifies the specific position.
- The Rate Card Class connects that position to the appropriate Rate Card structure.
Import sequencing
Use the following sequence as a starting point when creating or importing related procurement records. Additional dependencies may apply for Rate Cards, Request Templates, and supplier-specific configurations.
| Order | Component |
|---|---|
| 1 | Job Class |
| 2 | Job Title |
| 3 | Rate Card Class |
| 4 | Rate Card |
| 5 | Request Template |
Procurement Type
The procurement structures supported by the Rate Card Trifecta are used with one of the following Procurement Types:
| Procurement Type | Purpose |
|---|---|
| Contingent | Used by the Resource Tracking module. |
| Project | Used by the Services Procurement module. |
If Procurement Type is not specified during import, the value defaults to Contingent.
Important behavior
| Consideration | Impact |
|---|---|
| Job Class, Job Title, and Rate Card Class records should remain synchronized. | Misaligned records can affect imports, Rate Cards, Request Templates, and related workflows. |
| Job Titles depend on Job Classes. | Create or import Job Classes before Job Titles. |
| Rate Card Classes depend on job structures. | Establish Job Classes and Job Titles before configuring Rate Card Classes. |
| Request Templates depend on all three components. | Create the Trifecta before building Request Templates. |
| Import order matters. | Importing records out of sequence can result in validation errors. |
Additional considerations
- Use consistent naming conventions across all three components.
- Review existing Job Classes, Job Titles, and Rate Card Classes before creating new records.
- Align job structures with reporting and procurement requirements.
- Consider future Rate Card and Request Template usage when defining new structures.
Availability and setup
Manage Job Classes, Job Titles, and Rate Card Classes through Admin > Procurement.
Learn more
Related articles:
- Workforce procurement configuration overview
- Add a job class
- Add a job title
- Add a rate card class
- Add a rate card category 1
- Add a rate card
- Create a request template
| Persona Program office users | Modules Administration | Documentation release Beeline Enterprise | Q3 2026 | Feedback? Email us: |