{
  "$comment": "Contract A4 seed items for the hiring-and-onboarding domain.",
  "track": "ashr-ops",
  "domain": "hiring-and-onboarding",
  "items": [
    {
      "id": "ashr-ops.hiring-and-onboarding.01",
      "kind": "mcq",
      "domain": "hiring-and-onboarding",
      "stem": "A candidate applies through the organisation's public career page. Where does that application appear, and with what attached?",
      "options": [
        { "key": "a", "text": "In a general inbox, from which a recruiter copies it into a pipeline by hand" },
        { "key": "b", "text": "Directly in that job opening's pipeline at the first stage, with the resume and intro video attached to the candidate" },
        { "key": "c", "text": "In the helpdesk queue, as a ticket" },
        { "key": "d", "text": "Nowhere until a recruiter accepts the application" }
      ],
      "answer_key": { "correct": ["b"] },
      "max_points": 1,
      "cites": ["https://ashr.work/help/recruitment/publishing-jobs-and-collecting-applications"]
    },
    {
      "id": "ashr-ops.hiring-and-onboarding.02",
      "kind": "mcq",
      "domain": "hiring-and-onboarding",
      "stem": "A recruiter marks an offer as Accepted. What does ASHR.work do next?",
      "options": [
        { "key": "a", "text": "Nothing further — the recruiter must also change the candidate's stage by hand" },
        { "key": "b", "text": "Marks the candidate as Hired and suggests adding them as an employee so onboarding can begin" },
        { "key": "c", "text": "Creates the employee record and payroll structure automatically" },
        { "key": "d", "text": "Closes the job opening and rejects every remaining candidate" }
      ],
      "answer_key": { "correct": ["b"] },
      "max_points": 1,
      "cites": ["https://ashr.work/help/recruitment/managing-your-hiring-pipeline"]
    },
    {
      "id": "ashr-ops.hiring-and-onboarding.03",
      "kind": "mcq",
      "domain": "hiring-and-onboarding",
      "stem": "An organisation wants its own pipeline stages, and asks whether it can remove Hired and Rejected. What is true in ASHR.work?",
      "options": [
        { "key": "a", "text": "Stages are fixed and cannot be changed at all" },
        { "key": "b", "text": "Stages can be added, renamed, reordered or archived, but Hired and Rejected are permanent outcomes and are always available" },
        { "key": "c", "text": "Every stage including Hired and Rejected can be deleted" },
        { "key": "d", "text": "Stages can only be changed on a new job opening, never on an existing one" }
      ],
      "answer_key": { "correct": ["b"] },
      "max_points": 1,
      "cites": ["https://ashr.work/help/recruitment/managing-your-hiring-pipeline"]
    },
    {
      "id": "ashr-ops.hiring-and-onboarding.04",
      "kind": "mcq",
      "domain": "hiring-and-onboarding",
      "stem": "An admin is worried that approving several onboarding submissions in quick succession could give two people the same employee ID. What does ASHR.work actually do?",
      "options": [
        { "key": "a", "text": "Duplicates are possible, so the admin should check the directory after each approval" },
        { "key": "b", "text": "The counter skips any number already taken, so duplicates are impossible; in manual mode ASHR.work uses exactly the ID entered" },
        { "key": "c", "text": "IDs are assigned nightly in a batch, which is why duplicates cannot occur" },
        { "key": "d", "text": "IDs are random strings, so a collision is merely unlikely" }
      ],
      "answer_key": { "correct": ["b"] },
      "max_points": 1,
      "cites": ["https://ashr.work/help/onboarding/assigning-an-employee-id"]
    },
    {
      "id": "ashr-ops.hiring-and-onboarding.05",
      "kind": "mcq",
      "domain": "hiring-and-onboarding",
      "stem": "A new hire's onboarding submission is complete except for one document, which is the wrong file. What is the correct action, and what does it do?",
      "options": [
        { "key": "a", "text": "Approve, then edit the record afterwards — approval is only a formality" },
        { "key": "b", "text": "Request changes, which sends the form back to the new hire with your note so they can fix it and resubmit" },
        { "key": "c", "text": "Delete the submission and ask them to start again" },
        { "key": "d", "text": "Approve, because approval does not activate the employee" }
      ],
      "answer_key": { "correct": ["b"] },
      "max_points": 1,
      "cites": ["https://ashr.work/help/onboarding/reviewing-submissions"]
    },
    {
      "id": "ashr-ops.hiring-and-onboarding.06",
      "kind": "mcq",
      "domain": "hiring-and-onboarding",
      "stem": "A candidate who applied three months ago asks for their data to be removed. What does the ASHR.work careers surface provide?",
      "options": [
        { "key": "a", "text": "Nothing — candidate data can only be removed by a support request" },
        { "key": "b", "text": "The application form carries a plain-language consent notice the candidate must accept, the organisation controls retention windows, and the candidate can withdraw and erase their data from their status page" },
        { "key": "c", "text": "Candidate data is deleted automatically after 30 days regardless of the organisation's settings" },
        { "key": "d", "text": "Only the resume can be removed; the rest of the application is permanent" }
      ],
      "answer_key": { "correct": ["b"] },
      "max_points": 1,
      "cites": ["https://ashr.work/help/recruitment/publishing-jobs-and-collecting-applications"]
    }
  ]
}