Manatal ATS Setup & Logic Configuration
Budget: $250 – $750 USD
I have a fresh Manatal instance that needs to be structured correctly before we bulk-import roughly 300,000 candidate records. My immediate priorities are:
• Field architecture – designing the custom and default fields so every profile, job, and placement record is future-proof and reports cleanly.
• Matching logic – fine-tuning job title, sector, department, and location rules so relevant candidates surface instantly.
• ATS workflows – mapping each recruitment stage, trigger, and status to match our real-world process while keeping it lean.
Once you complete this foundation, another team member will handle the CSV import, so your configuration must be solid enough to absorb that volume without rework. I’ll provide admin access, our current process maps, and naming conventions; you bring proven, hands-on Manatal (or comparable ATS) experience.
Deliverables
1. Fully configured Manatal account reflecting the field, logic, and workflow requirements above.
2. Short Loom or written walkthrough explaining key settings so my team can maintain them.
3. One round of tweaks after internal review.
If you’ve rolled out Manatal at scale before, I’d love to see an example. Let’s lock in the setup and set the stage for a smooth data import.
• Field architecture – designing the custom and default fields so every profile, job, and placement record is future-proof and reports cleanly.
• Matching logic – fine-tuning job title, sector, department, and location rules so relevant candidates surface instantly.
• ATS workflows – mapping each recruitment stage, trigger, and status to match our real-world process while keeping it lean.
Once you complete this foundation, another team member will handle the CSV import, so your configuration must be solid enough to absorb that volume without rework. I’ll provide admin access, our current process maps, and naming conventions; you bring proven, hands-on Manatal (or comparable ATS) experience.
Deliverables
1. Fully configured Manatal account reflecting the field, logic, and workflow requirements above.
2. Short Loom or written walkthrough explaining key settings so my team can maintain them.
3. One round of tweaks after internal review.
If you’ve rolled out Manatal at scale before, I’d love to see an example. Let’s lock in the setup and set the stage for a smooth data import.