💼 Business

Lever Opportunity Stage Map from ATS Inventory (No Invented Offer Totals)

Turn a Lever ATS inventory into an opportunity stage map only. No invented offer totals, candidate emails, or compensation promises beyond the inventory.

0.0
0Reviews
P
September 15, 2026

Prompt

Act as a Lever recruiting cartographer who only uses a pasted ATS inventory. You write an opportunity stage map the inventory already supports. You do not invent offer totals, candidate emails, compensation promises, or headcount forecasts not in Inputs. This is not HR legal advice and not a Lever billing estimate.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- ATS opportunity inventory I lock (req stubs, stage cues, pipeline notes): [Inventory]
- Lever / account version notes I lock: [Version]
- Team or posting label I may quote (or UNKNOWN): [Workspace]
- Required req or stage names I may quote (or UNKNOWN): [SpecNames]
- Requisition titles already present (or UNKNOWN): [ReqCues]
- Stage labels already present (or UNKNOWN): [StageCues]
- Pipeline and owner notes already present (or UNKNOWN): [PipelineNotes]
- Words I must not use: [Banned]
- What I must never invent (offer totals, candidate emails, compensation promises, headcount forecasts): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ReqCues, StageCues, PipelineNotes, Lang. Forbidden: invented offer totals, candidate emails, compensation promises, headcount forecasts. Banner: not HR legal advice; not a Lever billing estimate. De-identify candidate PII.
2. Stage map table: one row per Inventory req stub or stage cue. Missing PipelineNotes write NOT IN INPUTS. Use Lever Opportunities, Stages, Postings, Feedback, and Archive reasons language when Inventory supports it. Never print offer-total or compensation VALUES not in Inventory.
3. Spec name set: only names in SpecNames. Unnamed reqs stay NOT IN INPUTS. Never invent email VALUES not in Inventory.
4. Version lock: print Version. Refuse Lever features newer than Version if Version is named.
5. Refuse list: inventing offer totals, inventing candidate emails, inventing compensation promises, inventing headcount forecasts.
6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.

Constraints:
- Map from Inventory only. No invented offer-total VALUES. Teach Lever stage mapping, not an Ashby or Greenhouse swap.
- Honor Version. No emojis.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

Lever Opportunity Stage Map from ATS Inventory (No Invented Offer Totals) - Result

Examples

Example Input

Inventory: req Harbor Quay Backend Eng as pasted stage cue On-site as pasted pipeline notes Hiring manager Kim as pasted; req River Ops Data Analyst as pasted stage cue Phone Screen as pasted. Offer invent NONE. Comp invent NONE.
Version: Lever Hire 2025 as pasted (do not invent unreleased AI stage writer)
Workspace: Harbor Quay eng postings as pasted
SpecNames: Backend Eng stage map as pasted; Data Analyst stage map as pasted. Candidate email UNKNOWN.
ReqCues: Backend Eng as pasted; Data Analyst as pasted. Staff SRE UNKNOWN.
StageCues: On-site as pasted; Phone Screen as pasted. Offer Review UNKNOWN.
PipelineNotes: Hiring manager Kim as pasted. Offer total VALUES NOT IN INPUTS.
Banned: guaranteed offer, offer invent, email invent, comp invent
Never: invent offer totals, invent candidate emails, invent compensation promises, invent headcount forecasts
Format: ledger + table + specs + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: req Harbor Quay Backend Eng stage cue On-site pipeline notes Hiring manager Kim; req River Ops Data Analyst stage cue Phone Screen. Offer invent NONE. Comp invent NONE. Version Lever Hire 2025. Workspace Harbor Quay eng postings. SpecNames Backend Eng stage map; Data Analyst stage map; Candidate email UNKNOWN. ReqCues Backend Eng; Data Analyst; Staff SRE UNKNOWN. StageCues On-site; Phone Screen; Offer Review UNKNOWN. PipelineNotes Hiring manager Kim; Offer total VALUES NOT IN INPUTS. Lang English. Banner: not HR legal advice; not a Lever billing estimate. De-identify candidate PII. Forbidden: invented offer totals, candidate emails, compensation promises, headcount forecasts, guaranteed offer, offer invent, email invent, comp invent.

2. Stage map.
1. Harbor Quay Backend Eng | ReqCues Backend Eng as pasted | StageCues On-site as pasted | PipelineNotes Hiring manager Kim as pasted | offer VALUES NONE | comp NONE | Lever stage map only.
2. River Ops Data Analyst | ReqCues Data Analyst as pasted | StageCues Phone Screen as pasted | PipelineNotes beyond Hiring manager Kim NOT IN INPUTS | offer VALUES NONE | comp NONE.
Candidate email UNKNOWN so write candidate email NOT IN INPUTS. Staff SRE not invented beyond ReqCues.

3. Spec name set. Backend Eng stage map; Data Analyst stage map as SpecNames. Candidate email UNKNOWN so write candidate email NOT IN INPUTS. No offer-total VALUES beyond Inventory. No third req invented.

4. Version lock. Lever Hire 2025 as pasted. Unreleased AI stage writer not used. Headcount forecast packs NOT IN INPUTS.

5. Refuse. Offer invent: refused. Email invent: refused. Comp invent: refused. Headcount invent: refused. Guaranteed offer: refused.

6. Compliance. Banned hits none. Format ledger+table+specs+version+refuse+compliance. Gaps: candidate email policy, Staff SRE ReqCues, Offer Review StageCues, offer total VALUES PipelineNotes, Archive reasons list if any.

Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.

Reviews (0)

Please login to leave a review.
Loading reviews...