Section 1 of 1
How to Use NexusHire from Role Story to Hiring Packet
NexusHire is a structured hiring workspace, not just a document generator. It helps you define the role, gather missing context through guided questioning, choose the right compliance region and policy set, generate only the documents that matter, and then review those documents inside the same workspace.
Canvas phase
Start with the role story, business need, and what success in the role should look like.
Socratic phase
Use guided questioning to surface hidden assumptions about seniority, team fit, must-haves, and risks.
Configuration
Choose the operating region, relevant company policies, and the exact document types to generate.
Workspace review
Edit documents, run compliance views, compare earlier versions, and save the strong outputs back into the workspace.
Recruitment documents are for attracting and evaluating the candidate: job description, offer package, interview scorecard.
Safety documents matter when the role includes operational, physical, or workplace risk exposure.
Assessment documents help compare candidates and prepare onboarding, compensation, and development decisions.
Generate only the artifacts the team will truly use. Over-generation creates noise and slows review.
Step 1: Write the role story in business terms
Define what the role exists to accomplish, what failure would look like, and what the first months need to prove.
Step 2: Take the Socratic phase seriously
Answer the guided questions as if a skeptical hiring partner were in the room. This is where the brief becomes sharp enough for good document generation.
Step 3: Set region and policies
Choose the correct legal or operating region and add the company-specific policies that should constrain the packet.
Step 4: Generate the smallest useful packet
Select the documents the team actually needs right now and generate them. Save large packet generation for when the brief is stable.
Step 5: Review the most decision-critical document first
Open the job description, scorecard, or offer artifact that will shape the hiring decision most directly. Fix that before polishing the rest.
Step 6: Use compliance and history before sharing
Review confidence, warnings, and recommended actions. Reopen older versions if needed, then copy, save, or export only the approved artifacts.
Define success in the role before you describe tasks or perks.
Use the guided questions to reveal missing hiring logic, not just to speed through the phase.
Generate a focused document set first and expand only when the packet direction is correct.
Review compliance and recommended actions before treating any generated text as final.
Do not start from buzzwords and copy-pasted generic job descriptions.
Do not skip region and policy selection if the packet has legal or compensation impact.
Do not publish the whole packet just because one document looks strong.
Do not lose your process history; reuse it when the role reopens or the scope changes.