Offers

1. Overview

Offer drafting, approval, extension, signature, and acceptance. Realizes OFFER-MGMT. Realizes the offer_extended state on job_applications. Requires an external sign_document tool, drops module Semantius coverage to ~83%.

2. Entity summary

Name	Description
Offers	Formal employment offer extended to a candidate. Carries compensation components, start date, terms, approval chain, and status (draft / approved / sent / accepted / declined / rescinded).
Applications	A candidate’s submission against a specific requisition. Carries pipeline stage, status (active / rejected / withdrawn / hired), source, and the full evaluation history.
Candidates	Person known to the recruiting org, with or without an active application. Carries contact details, resume, tags, GDPR consent, and source. Distinct from Employee until hired.
Salary Bands	Pay-range structure by grade and geographic zone with minimum, midpoint, maximum, and benchmarking source. Drives offer guidance, merit eligibility, and pay-equity gap analysis.
Compensation Benchmarks	Imported market salary data for a job-level-geography combination, sourced from an external compensation-survey provider. Drives salary_bands maintenance.

flowchart TD
  classDef master fill:#d4f4dd,stroke:#27ae60,color:#0b3d20;
  classDef embedded_master fill:#fff4cc,stroke:#c79100,color:#5b4500;
  classDef consumer fill:#e8def8,stroke:#7b1fa2,color:#3a155d;
  classDef platform_builtin fill:#e0e0e0,stroke:#424242,color:#1a1a1a;
  job_offers["Offers"]
  candidates["Candidates"]
  job_applications["Applications"]
  compensation_benchmarks["Compensation Benchmarks"]
  salary_bands["Salary Bands"]
  users["Users"]
  candidates -->|"submits"| job_applications
  job_applications -->|"results in"| job_offers
  job_applications -->|"has owning recruiter"| users
  job_offers -->|"has approver"| users
  class job_offers master;
  class candidates embedded_master;
  class job_applications embedded_master;
  class compensation_benchmarks consumer;
  class salary_bands embedded_master;
  class users platform_builtin;
  style salary_bands stroke-dasharray:5 5;

3. Entities catalog

#	data_object	role	mastered in	necessity	pattern flags	notes
1	`job_offers` (Offers)	master	-	required	personal_content, single_approver	-
2	`job_applications` (Applications)	embedded_master	`ats-recruitment-pipeline`	required	personal_content	-
3	`candidates` (Candidates)	embedded_master	`ats-candidate-crm`	required	personal_content	-
4	`salary_bands` (Salary Bands)	embedded_master	`comp-benchmarking`	optional	-	-
5	`compensation_benchmarks` (Compensation Benchmarks)	consumer	`comp-benchmarking`	required	-	-

4. Aliases and industry synonyms

(no industry-scoped aliases or non-synonym alias types loaded for this scope; generic synonyms are omitted as common knowledge.)

5. Relationships

5.1 Intra-scope edges

from	verb	to	cardinality	kind	necessity	owner_side	notes
`candidates`	submits	`job_applications`	one_to_many	reference	required	target	-
`job_applications`	results in	`job_offers`	one_to_many	reference	required	source	-

5.2 Built-in edges (`users` and other platform built-ins)

from	verb	to	cardinality	necessity	owner_side	notes
`job_applications`	has owning recruiter	`users`	many_to_many	required	source	-
`job_offers`	has approver	`users`	many_to_many	required	source	-

5.3 Cross-scope edges

from	verb	to	cardinality	necessity	notes
`salary_bands`	anchors	`hcm_positions`	one_to_many	optional	-
`salary_bands`	bands	`job_profiles`	one_to_many	optional	-
`skill_profiles`	feeds	`candidates`	one_to_many	optional	-
`job_requisitions`	receives	`job_applications`	one_to_many	required	-
`job_postings`	is applied to via	`job_applications`	one_to_many	required	-
`candidate_referrals`	introduces	`candidates`	one_to_many	required	-
`recruitment_sources`	attributes	`candidates`	one_to_many	required	-
`recruitment_agencies`	sources	`candidates`	one_to_many	required	-
`recruitment_events`	attracts	`candidates`	one_to_many	required	-
`talent_pools`	groups	`candidates`	many_to_many	required	-
`job_applications`	schedules	`interviews`	one_to_many	required	-
`job_applications`	requires	`candidate_assessments`	one_to_many	required	-
`job_offers`	is contingent on	`background_checks`	one_to_many	required	-
`job_offers`	spawns	`onboarding_journeys`	one_to_one	required	-
`job_offers`	triggers	`benefit_enrollments`	one_to_one	required	-
`job_offers`	seeds	`compensation_statements`	one_to_one	required	-
`candidates`	becomes	`employees`	one_to_one	required	-
`job_offers`	spawns pre-employee record	`pre_employees`	one_to_one	required	-
`candidates`	becomes pre-employee	`pre_employees`	one_to_one	required	-
`labor_market_benchmarks`	calibrates	`salary_bands`	many_to_many	optional	-

6. Cross-domain context

6.1 Master consumers (other modules / domains that embed this scope’s masters)

data_object	other module / domain	role	necessity	notes
`job_offers`	ATS-BACKGROUND-CHECKS (Background Checks) - ATS	embedded_master	required	-
`job_offers`	ATS-PRE-EMPLOYEE-RECORD (Pre-Employee Record) - ATS	embedded_master	required	-
`job_offers`	COMP-STATEMENTS (Total Rewards Statements) - COMP-MGMT	consumer	required	-
`job_offers`	HCM-LIFECYCLE-WORKFLOWS (Employee Lifecycle Workflows) - HCM	consumer	required	-
`job_offers`	HIRING-STARTER (Hiring Starter) - ATS	embedded_master	required	-

6.2 Outbound handoffs (events this scope publishes)

source module	target domain	target module	trigger_event	payload	integration	friction	description
ATS-OFFERS	HCM	HCM-LIFECYCLE-WORKFLOWS	`job_offer.accepted`	`job_offers`	event_stream	medium	Offer acceptance signals firm hiring intent; HCM creates pending-employee record.
ATS-OFFERS	COMP-MGMT	COMP-STATEMENTS	`job_offer.signed`	`job_offers`	event_stream	low	Signed offer establishes the comp baseline; COMP-MGMT incorporates into cycle history.

6.3 Inbound handoffs (events this scope reacts to)

target module	source domain	source module	trigger_event	payload	integration	friction	description
ATS-OFFERS	COMP-MGMT	COMP-BENCHMARKING	`compensation_benchmark.refreshed`	`compensation_benchmarks`	batch_sync	low	Updated benchmarks inform offer-range guardrails for recruiters and hiring managers.
ATS-OFFERS	ATS	ATS-RECRUITMENT-PIPELINE	`job_application.advanced`	`job_offers`	lifecycle_progression	low	-
ATS-OFFERS	ATS	ATS-BACKGROUND-CHECKS	`background_check.flagged`	`job_offers`	lifecycle_progression	medium	-
ATS-OFFERS	COMP-MGMT	COMP-BENCHMARKING	`salary_band.updated`	`salary_bands`	event_stream	low	Updated bands flow to ATS offer-generation.

6.4 Master providers (modules / domains that own masters this scope embeds)

data_object	role here	necessity	canonical owner(s)	slice notes
`candidates`	embedded_master	required	ATS-CANDIDATE-CRM (ATS)	-
`job_applications`	embedded_master	required	ATS-RECRUITMENT-PIPELINE (ATS)	-
`salary_bands`	embedded_master	optional	COMP-BENCHMARKING (COMP-MGMT)	-
`compensation_benchmarks`	consumer	required	COMP-BENCHMARKING (COMP-MGMT)	-

7. Lifecycle states (per touched entity)

`candidates` (Candidate)

This scope holds candidates as embedded_master; the canonical state machine is owned by ATS-CANDIDATE-CRM.

order	state_name	initial?	terminal?	requires_permission?	derived gate	description
1	`prospect`	✓	-	-	-	Person known to the recruiting org with no active application.
2	`active`	-	-	-	-	Candidate has at least one open application or is actively engaged.
3	`hired`	-	✓	✓	`ats-candidate-crm:hire_candidate`	Candidate accepted an offer and converted to employee.
4	`do_not_hire`	-	✓	✓	`ats-candidate-crm:flag_do_not_hire`	Candidate flagged as ineligible for future consideration; gated decision.
5	`archived`	-	✓	-	-	Candidate kept in the database but not active in any pipeline.

`job_applications` (Application)

This scope holds job_applications as embedded_master; the canonical state machine is owned by ATS-RECRUITMENT-PIPELINE.

order	state_name	initial?	terminal?	requires_permission?	derived gate	description
1	`applied`	✓	-	-	-	Candidate submitted an application against the requisition.
2	`screening`	-	-	-	-	Recruiter is reviewing resume and qualifications.
3	`interviewing`	-	-	-	-	Candidate is progressing through interview loops.
4	`offer_extended`	-	-	-	-	An offer has been generated and is in flight for this application.
5	`hired`	-	✓	✓	`ats-pre-employee-record:hire_candidate`	Candidate accepted the offer and was hired; gated transition.
6	`rejected`	-	✓	-	-	Application closed without progression by recruiter or hiring manager.
7	`withdrawn`	-	✓	-	-	Candidate withdrew their application.

`job_offers` (Offer)

order	state_name	initial?	terminal?	requires_permission?	derived gate	description
1	`draft`	✓	-	-	-	Recruiter is composing offer terms and compensation components.
2	`pending_approval`	-	-	-	-	Offer routed to the designated approver for sign-off.
3	`approved`	-	-	✓	`ats-offers:approve_offer`	Approver signed off; offer is ready to send.
4	`sent`	-	-	-	-	Offer delivered to the candidate.
5	`accepted`	-	✓	-	-	Candidate accepted the offer.
6	`declined`	-	✓	-	-	Candidate declined the offer.
7	`rescinded`	-	✓	✓	`ats-offers:rescind_offer`	Offer withdrawn by the employer after being sent; gated action.

8. Permissions and business rules (derived)

8.1 Permissions

permission	tier	description	included in `:admin`?
`ats-offers:read`	baseline-read	Read access to every entity in the module	✓
`ats-offers:manage`	baseline-manage	Edit operational records	✓
`ats-offers:admin`	baseline-admin	Edit reference data and inherit every workflow gate below	-
`ats-offers:approve_offer`	workflow-gate (lifecycle)	Transition `job_offers` into state `approved`	✓
`ats-offers:rescind_offer`	workflow-gate (lifecycle)	Transition `job_offers` into state `rescinded`	✓
`ats-offers:view_all_offers`	override (personal_content)	View all `job_offers` rows beyond row-scope	✓
`ats-offers:manage_all_offers`	override (personal_content)	Manage all `job_offers` rows beyond row-scope	✓

8.2 Business rules

rule_name	data_object	source flag	intent
`offer_edit_scope`	`job_offers`	has_personal_content	Row-scope by default; override via `ats-offers:view_all_offers` / `ats-offers:manage_all_offers`
`approve_offer_requires_approver`	`job_offers`	has_single_approver	Exactly one explicit approver required; uses the module’s approval gate (`ats-offers:approve_offer` if surfaced as a lifecycle workflow gate).