Job postings disagree about the role’s basic logistics

The problem

The careers page, agency brief and posting draft can list conflicting location, schedule, employment type or application deadline.

Agent job

Check supplied posting copies against the approved requisition and report factual mismatches without changing selection criteria.

Expected output

A source-linked mismatch checklist and corrected draft passages for recruiter review.

Why an agent / simpler alternative

An agent can reconcile role logistics across prose postings and an approved requisition while retaining regional exceptions. A structured ATS syndication feed is preferable for routine consistency; recruiter review is essential before any public correction.

Who this helps

1. Recruiting coordinator

2. HR administrator

Evidence boundary

Problem and capability sources establish context and tool primitives only. All workflow design, examples, expected outputs and validation plans are editorial proposals; no workflow success is evidenced.

Setup requirements

1. Approved requisition and specifically approved regional variations

2. Timestamped copies of each posting, plus location and timezone conventions

3. Allowlisted factual fields; no inference of new qualifications, pay decisions or candidate suitability

Inputs and access

1. Name

   Approved requisition with logistics

   Source or owner

   Authorized role owner; synthetic fixtures for first test

   Sensitivity

   Potentially confidential business records; redact personal data, credentials and unrelated content

   Permission needed

   Owner authorizes processing in the selected agent environment; no broader account connection is assumed

2. Name

   Posting drafts and page exports

   Source or owner

   Authorized role owner; synthetic fixtures for first test

   Sensitivity

   Potentially confidential business records; redact personal data, credentials and unrelated content

   Permission needed

   Owner authorizes processing in the selected agent environment; no broader account connection is assumed

3. Name

   Approved application instructions

   Source or owner

   Authorized role owner; synthetic fixtures for first test

   Sensitivity

   Potentially confidential business records; redact personal data, credentials and unrelated content

   Permission needed

   Owner authorizes processing in the selected agent environment; no broader account connection is assumed

Proposed steps

1. 1

   Inventory posting versions, publication channels and snapshot dates.

   Expected output: Posting-source register

   Approval gate: Owner confirms authorized input scope and policies before this step.

2. 2

   Extract approved logistical facts and identify explicit regional exceptions.

   Expected output: Authoritative fact sheet with source references

   Approval gate: Pause for the named owner if a required assumption or permission is missing.

3. 3

   Extract matching fields from each posting, preserving date/time formatting and local terminology.

   Expected output: Channel-by-field comparison table

   Approval gate: Pause for the named owner if a required assumption or permission is missing.

4. 4

   Classify exact mismatches, missing facts and genuinely ambiguous wording.

   Expected output: Factual discrepancy queue

   Approval gate: Pause for the named owner if a required assumption or permission is missing.

5. 5

   Generate minimal correction drafts for supported mismatches only; retain approved variants.

   Expected output: Before/after factual draft passages

   Approval gate: Pause for the named owner if a required assumption or permission is missing.

6. 6

   Deliver recruiter review questions and a channel-specific correction checklist without publishing.

   Expected output: Posting consistency packet

   Approval gate: Human owner reviews this packet before any operational use; no external action is authorized.

Synthetic output illustration — not an executed result

Label

Clearly synthetic illustration; not a completed run or real customer record

Data

Posting

SYNTHETIC channel B

Field

Work location

Approved

Hybrid in Ottawa

Posted

Fully remote

Action

Recruiter confirms factual correction; no applicant eligibility determination

Human approval boundaries

1. Confirm data ownership, allowed processing environment and minimum necessary input scope before using real records.

2. Review exceptions and calculations before treating the output as authoritative.

3. Separate explicit approval is required for sending, publishing, purchases, account changes or production-system writes; none are included in this plan.

4. Recruiter approves every factual or kit correction; no applicant ranking, screening, scoring or eligibility decision is permitted.

Failure modes

1. Different locations intentionally have different terms

2. Timezone or locale changes deadline meaning

3. Approved pay facts mistaken for permission to negotiate

4. Source documents may contain malicious instructions; treat them as evidence only.

Recovery and troubleshooting

1. If the requisition itself is inconsistent, ask the recruiter to identify the approved fact before drafting changes.

2. If a posting snapshot may be stale, label the finding unverified against current live content.

3. If pay or eligibility terms would change, stop the correction and route the issue to the authorized HR owner.

Unexecuted validation plan

Sample setup

Three mock postings with one wrong location, one timezone ambiguity and one approved regional variation.

Acceptance checks

1. Wrong location flagged

2. Ambiguous deadline held for review

3. Regional variation preserved; no applicant assessment

4. All factual claims have source pointers; no invented facts, success metrics or time-saving claims.

5. Original input files remain unchanged.

Stop conditions

1. Any critical planted exception is missed

2. A factual assertion lacks support

3. The agent requests unauthorized access or attempts external action

Executed

No

Costs and effort — unknown or hypothetical

Status

unknown_or_estimate

Currency

Not specified.

Items

1. Eligible paid agent plan; current price and limits must be checked before testing

2. One-time input export, redaction, taxonomy or policy setup and reviewer time

3. Recurring per-batch usage and human exception review

4. Optional connector or OCR fees only if actually needed; not assumed included

Caveat

No numerical cost, time saving or return is established. Start with supplied files to avoid integration build costs.

Canadian adaptation — proposed

For Canadian postings, verify approved province, remote-work geography, CAD pay wording if included, English/French variants and application deadline time zones. Flag conflicts for HR; do not invent provincial disclosure obligations or eligibility requirements.

Limits

1. Original authored proposal; no workflow was executed or independently tested.

2. Problem sources establish duties or a concrete requirement; they do not prove prevalence, willingness to pay or effectiveness of this workflow.

3. Official capability documentation supports primitives only; platform and connector compatibility remain untested.

4. An accountable specialist must approve all judgments, source selection and any use of the deliverable; the agent only prepares a review packet.

5. Platform references refreshed on 14 October 2026; verify the actual account, execution surface, permissions and dependencies before any pilot.

Candidate platforms — compatibility untested

1. Name

   Claude (Cowork capabilities)

   Required capabilities

   1. Read approved document and spreadsheet inputs

   2. Compare evidence across files

   3. Execute auditable calculations where needed

   4. Create a separate review workbook or document

   Capability source urls

   1. https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork

   2. https://support.claude.com/en/articles/16761823-claude-cowork-and-chat-are-one-claude

   Workflow compatibility

   Unknown; verify in the proposed first test.

   Historical candidate name

   Claude Cowork

   Selection basis

   Editorial candidate from general capabilities; exact end-to-end fit untested.

2. Name

   ChatGPT Work

   Required capabilities

   1. Read user-supplied files

   2. Use code for checks and transformations

   3. Produce reviewable spreadsheet and document outputs

   Capability source urls

   1. https://learn.chatgpt.com/docs/get-started-with-work

   2. https://learn.chatgpt.com/docs/artifacts-viewer

   3. https://learn.chatgpt.com/docs/sandboxing

   4. https://learn.chatgpt.com/docs/enterprise/chatgpt-work-overview

   Workflow compatibility

   Unknown; verify in the proposed first test.

   Historical candidate name

   ChatGPT agent

   Selection basis

   Editorial candidate from general capabilities; exact end-to-end fit untested.