[{"data":1,"prerenderedAt":644},["ShallowReactive",2],{"blog-post-\u002Fblog\u002Fcandidate-public-pool-guide":3,"blog-related-\u002Fblog\u002Fcandidate-public-pool-guide":152},{"id":4,"title":5,"body":6,"date":138,"description":139,"extension":140,"image":141,"meta":142,"navigation":143,"path":144,"seo":145,"stem":146,"tags":147,"__hash__":151},"blog\u002Fblog\u002Fcandidate-public-pool-guide.md","候选人公海池怎么做才有效？RPO 团队提升转化率的关键机制",{"type":7,"value":8,"toc":126},"minimark",[9,17,21,24,29,32,35,39,42,64,67,71,82,85,105,108,111,123],[10,11,12,13],"p",{},"很多 RPO 团队都遇到过同样的问题：候选人库看起来很大，但真正被跟进的很少；老寻访员手里囤着几百份简历，新寻访员却无资源可用。",[14,15,16],"strong",{},"公海池机制，就是解决这类资源沉淀问题的核心手段。",[18,19,20],"h2",{"id":20},"什么是真正有效的公海池",[10,22,23],{},"公海池不是「候选人回收站」。一个有效的公海池体系，包含三个互相咬合的机制：",[25,26,28],"h3",{"id":27},"_1-保护期给跟进设定明确节奏","1. 保护期：给跟进设定明确节奏",[10,30,31],{},"候选人被寻访员认领后进入保护期，比如 14 天。保护期内，该候选人归认领人所有；到期后如果未产生有效跟进（推荐、约面、入职），系统自动回收至公海。",[10,33,34],{},"保护期的意义在于制造「节奏感」：资源不是永久占有，而是持续经营的权益。实践中，14 天保护期配合「至少 2 次有效跟进」的规则，能显著提升首次跟进的及时率。",[25,36,38],{"id":37},"_2-回收规则让规则代替人情","2. 回收规则：让规则代替人情",[10,40,41],{},"回收规则建议覆盖三类场景：",[43,44,45,52,58],"ul",{},[46,47,48,51],"li",{},[14,49,50],{},"超期未跟进","：保护期内无任何跟进记录，自动回收；",[46,53,54,57],{},[14,55,56],{},"长期无进展","：停留在某一状态超过 N 天，提醒后回收；",[46,59,60,63],{},[14,61,62],{},"主动释放","：寻访员判断暂时无法推进，主动放回公海供他人认领。",[10,65,66],{},"规则一旦配置，系统自动执行，不需要管理者反复催促。规则代替人情，是公海池能否长期运转的关键。",[25,68,70],{"id":69},"_3-流转统计资源效率看得见","3. 流转统计：资源效率看得见",[10,72,73,74,77,78,81],{},"管理者需要关注两个数字：",[14,75,76],{},"回收量","和",[14,79,80],{},"认领率","。回收量持续偏低，说明保护期可能设置过长；认领率低，说明候选人质量或岗位匹配有问题。流转数据每周复盘一次，公海池会越用越顺。",[18,83,84],{"id":84},"公海池带来的三个改变",[43,86,87,93,99],{},[46,88,89,92],{},[14,90,91],{},"首跟及时率提升","：认领即倒计时，寻访员会第一时间跟进；",[46,94,95,98],{},[14,96,97],{},"新人上手加速","：新寻访员从公海池认领资源，而不是等老员工「施舍」；",[46,100,101,104],{},[14,102,103],{},"候选人复用","：上次不匹配的候选人，可能是下个项目的人选，历史跟进记录一目了然。",[18,106,107],{"id":107},"如何在系统中落地",[10,109,110],{},"落地公海池不需要复杂制度，核心是三步：",[112,113,114,117,120],"ol",{},[46,115,116],{},"在系统中配置保护期与回收规则；",[46,118,119],{},"明确「有效跟进」的口径（推荐、到面、入职算有效，单纯打标签不算）；",[46,121,122],{},"每周查看流转统计，持续调整参数。",[10,124,125],{},"云享智聘内置了可配置的公海池模块：保护期、回收规则、认领提醒、流转统计开箱即用，配合跟进时间线，让每一次资源流转都有记录。如果你在为候选人资源沉淀发愁，建议开通试用，先跑两周看看流转数据的变化。",{"title":127,"searchDepth":128,"depth":128,"links":129},"",2,[130,136,137],{"id":20,"depth":128,"text":20,"children":131},[132,134,135],{"id":27,"depth":133,"text":28},3,{"id":37,"depth":133,"text":38},{"id":69,"depth":133,"text":70},{"id":84,"depth":128,"text":84},{"id":107,"depth":128,"text":107},"2026-03-18","公海池不是简单的候选人回收站。本文拆解保护期设计、回收规则、流转统计三个核心机制，帮助 RPO 团队让候选人资源真正流动起来，提升寻访转化率。","md","\u002Fimages\u002Fblog\u002Fcandidate-public-pool.jpg",{},true,"\u002Fblog\u002Fcandidate-public-pool-guide",{"title":5,"description":139},"blog\u002Fcandidate-public-pool-guide",[148,149,150],"公海池","候选人管理","RPO运营","lmMsq8VxNl_J_p2cFh_tXik_T17EhshJjl_ffTgjgFU",[153,249,374,461],{"id":154,"title":155,"body":156,"date":237,"description":238,"extension":140,"image":239,"meta":240,"navigation":143,"path":241,"seo":242,"stem":243,"tags":244,"__hash__":248},"blog\u002Fblog\u002Fai-resume-parsing-efficiency.md","AI 简历解析如何提升 RPO 寻访效率？场景与落地建议",{"type":7,"value":157,"toc":227},[158,164,168,171,174,178,181,185,188,192,198,201,221,224],[10,159,160,161],{},"问一位寻访员每天时间花在哪，答案往往不是打电话，而是「处理简历」：下载、打开、复制、粘贴、打标签……一项没有创造性的工作，占掉了大量寻访时间。",[14,162,163],{},"AI 简历解析要解决的，正是这段重复劳动。",[18,165,167],{"id":166},"ai-简历解析能做什么","AI 简历解析能做什么",[10,169,170],{},"简单说，AI 解析把一份非结构化的 Word\u002FPDF 简历，变成结构化的候选人档案：姓名、联系方式、工作经历、教育背景、技能标签等关键字段自动识别、自动填入系统，寻访员只需确认而不是录入。",[18,172,173],{"id":173},"三个最见效的应用场景",[25,175,177],{"id":176},"场景一批量简历入库","场景一：批量简历入库",[10,179,180],{},"蓝领批量招聘、渠道合作等场景常常一次性收到几十上百份简历。逐份手工录入显然不现实。AI 批量解析 + 自动查重，可以把几小时的录入压缩到几分钟，寻访员直接进入筛选环节。",[25,182,184],{"id":183},"场景二建档质检","场景二：建档质检",[10,186,187],{},"手工录入不可避免出现手机号错位、公司名称五花八门等问题，直接影响后续联系和统计。AI 解析按统一字段规范建档，格式天然一致；解析结果支持人工确认，关键信息错误率大幅下降。",[25,189,191],{"id":190},"场景三快速检索与画像","场景三：快速检索与画像",[10,193,194,195],{},"结构化之后，候选人档案才真正「可算」：按技能、城市、经验年限多维筛选，历史候选人一秒调出。这也是公海池、数据统计等功能的前提——",[14,196,197],{},"没有结构化数据，一切精细化运营都无从谈起。",[18,199,200],{"id":200},"落地建议",[112,202,203,209,215],{},[46,204,205,208],{},[14,206,207],{},"从存量简历入库开始","：把团队散落的历史简历批量解析入库，立刻获得一个可检索的候选人资产库；",[46,210,211,214],{},[14,212,213],{},"把解析嵌入业务流","：邮件收简历、渠道推简历，统一走系统解析，不要让简历再散落在个人电脑里；",[46,216,217,220],{},[14,218,219],{},"保留人工确认环节","：AI 解析准确率已经很高，但关键联系信息建议保留人工复核，尤其是批量入库场景。",[18,222,223],{"id":223},"结语",[10,225,226],{},"AI 简历解析不是炫技，它把寻访员的时间从「录入」还给「寻访」。云享智聘支持 Word\u002FPDF 简历上传，自动解析关键信息结构化入库，配合批量导入与查重机制，让建档效率成倍提升。如果你的团队每天还在复制粘贴简历，欢迎开通试用感受一下差别。",{"title":127,"searchDepth":128,"depth":128,"links":228},[229,230,235,236],{"id":166,"depth":128,"text":167},{"id":173,"depth":128,"text":173,"children":231},[232,233,234],{"id":176,"depth":133,"text":177},{"id":183,"depth":133,"text":184},{"id":190,"depth":133,"text":191},{"id":200,"depth":128,"text":200},{"id":223,"depth":128,"text":223},"2026-04-02","简历录入是寻访员最耗时的重复劳动。本文拆解 AI 简历解析在批量导入、建档质检、快速检索三个场景的应用方式，并给出 RPO 团队的落地建议。","\u002Fimages\u002Fblog\u002Fai-resume-parsing.jpg",{},"\u002Fblog\u002Fai-resume-parsing-efficiency",{"title":155,"description":238},"blog\u002Fai-resume-parsing-efficiency",[245,246,247],"AI简历解析","寻访效率","RPO工具","efrNIV9jtlSqNiCZPaQcl8da5IO5Fu3hqRAVNoTrCyU",{"id":250,"title":251,"body":252,"date":362,"description":363,"extension":140,"image":364,"meta":365,"navigation":143,"path":366,"seo":367,"stem":368,"tags":369,"__hash__":373},"blog\u002Fblog\u002Frpo-commission-settlement-automation.md","告别 Excel：RPO 团队提成结算自动化实践",{"type":7,"value":253,"toc":353},[254,260,263,266,286,289,293,296,316,319,323,330,334,337,339,350],[10,255,256,257],{},"对很多 RPO 团队负责人来说，每个月底最痛苦的不是业务，而是算提成：几十条入职记录、多套提成规则、Excel 里来回核对，算完还要跟寻访员一个个确认。",[14,258,259],{},"算错了伤感情，算慢了伤士气。",[18,261,262],{"id":262},"手工结算为什么总是出问题",[10,264,265],{},"复盘一下手工模式的典型链路：入职数据分散在各处 → 人工汇总到 Excel → 按规则套算 → 逐条核对 → 发放。这条链路的问题：",[43,267,268,274,280],{},[46,269,270,273],{},[14,271,272],{},"口径不统一","：推荐、到面、入职分别由谁算？入职当月还是次月计奖？口头约定终有分歧；",[46,275,276,279],{},[14,277,278],{},"过程不可追溯","：算错的数字找不到源头，只能重新来一遍；",[46,281,282,285],{},[14,283,284],{},"激励延迟","：月初发上月提成还算正常，拖到月中，激励效果大打折扣。",[18,287,288],{"id":288},"提成结算自动化三步走",[25,290,292],{"id":291},"第一步规则配置化","第一步：规则配置化",[10,294,295],{},"把提成规则从「脑子里的约定」变成「系统里的配置」：",[43,297,298,304,310],{},[46,299,300,303],{},[14,301,302],{},"计奖节点","：按推荐、到面、入职或回款触发；",[46,305,306,309],{},[14,307,308],{},"计算方式","：固定金额、比例分成、阶梯加成自由组合；",[46,311,312,315],{},[14,313,314],{},"适用范围","：不同项目、不同岗位可以套用不同规则。",[10,317,318],{},"规则一次配置，长期生效。调整规则时有记录可查，避免「说好的规则」变了又说不清。",[25,320,322],{"id":321},"第二步业绩数据自动核算","第二步：业绩数据自动核算",[10,324,325,326,329],{},"提成自动化的前提是业务数据本身在系统里：推荐记录、面试反馈、入职状态都在候选人管理中流转，提成核算直接引用这些数据，",[14,327,328],{},"不需要任何人手工二次录入","。数据同源，口径自然统一。",[25,331,333],{"id":332},"第三步结算单生成与留痕","第三步：结算单生成与留痕",[10,335,336],{},"月底一键生成结算单：每个人的计奖依据（哪笔入职、哪条记录）、计算过程、合计金额清晰列出。寻访员自查、管理者复核、财务导出对账，三个环节看的是同一份数据。有疑问，点开依据就能定位，争议自然减少。",[18,338,200],{"id":200},[43,340,341,344,347],{},[46,342,343],{},"先把现有提成规则原样翻译进系统，跑 1-2 个月与手工结果并行核对；",[46,345,346],{},"核对无误后，手工 Excel 即可退役；",[46,348,349],{},"每季度回顾一次规则合理性，激励导向要跟着业务阶段调整。",[10,351,352],{},"云享智聘的提成结算模块支持阶梯、固定、比例等规则的灵活组合，业绩数据从推荐到入职全链路自动核算，结算单一键生成、导出留痕。如果你的团队还在 Excel 里算提成，不妨开通试用，用这个月的机会把流程理顺。",{"title":127,"searchDepth":128,"depth":128,"links":354},[355,356,361],{"id":262,"depth":128,"text":262},{"id":288,"depth":128,"text":288,"children":357},[358,359,360],{"id":291,"depth":133,"text":292},{"id":321,"depth":133,"text":322},{"id":332,"depth":133,"text":333},{"id":200,"depth":128,"text":200},"2026-03-26","手工算提成慢、错、扯皮多。本文介绍 RPO 团队如何用规则配置化 + 业绩自动核算 + 结算单留痕三步，把月底提成结算从两天压缩到半小时。","\u002Fimages\u002Fblog\u002Fcommission-automation.jpg",{},"\u002Fblog\u002Frpo-commission-settlement-automation",{"title":251,"description":363},"blog\u002Frpo-commission-settlement-automation",[370,371,372],"提成结算","RPO管理","效率提升","3kXvn5IzKDHbmV1pam36UWVOjkTj90dwarrLheLYQ4g",{"id":4,"title":5,"body":375,"date":138,"description":139,"extension":140,"image":141,"meta":458,"navigation":143,"path":144,"seo":459,"stem":146,"tags":460,"__hash__":151},{"type":7,"value":376,"toc":449},[377,381,383,385,387,389,391,393,395,409,411,413,419,421,435,437,439,447],[10,378,12,379],{},[14,380,16],{},[18,382,20],{"id":20},[10,384,23],{},[25,386,28],{"id":27},[10,388,31],{},[10,390,34],{},[25,392,38],{"id":37},[10,394,41],{},[43,396,397,401,405],{},[46,398,399,51],{},[14,400,50],{},[46,402,403,57],{},[14,404,56],{},[46,406,407,63],{},[14,408,62],{},[10,410,66],{},[25,412,70],{"id":69},[10,414,73,415,77,417,81],{},[14,416,76],{},[14,418,80],{},[18,420,84],{"id":84},[43,422,423,427,431],{},[46,424,425,92],{},[14,426,91],{},[46,428,429,98],{},[14,430,97],{},[46,432,433,104],{},[14,434,103],{},[18,436,107],{"id":107},[10,438,110],{},[112,440,441,443,445],{},[46,442,116],{},[46,444,119],{},[46,446,122],{},[10,448,125],{},{"title":127,"searchDepth":128,"depth":128,"links":450},[451,456,457],{"id":20,"depth":128,"text":20,"children":452},[453,454,455],{"id":27,"depth":133,"text":28},{"id":37,"depth":133,"text":38},{"id":69,"depth":133,"text":70},{"id":84,"depth":128,"text":84},{"id":107,"depth":128,"text":107},{},{"title":5,"description":139},[148,149,150],{"id":462,"title":463,"body":464,"date":632,"description":633,"extension":140,"image":634,"meta":635,"navigation":143,"path":636,"seo":637,"stem":638,"tags":639,"__hash__":643},"blog\u002Fblog\u002Frpo-system-selection-guide.md","中小 RPO 团队如何选择招聘管理系统？一份务实选型指南",{"type":7,"value":465,"toc":623},[466,469,473,476,495,498,502,509,523,526,530,533,553,556,560,563,578,581,585,592,596,599,610,613,616],[10,467,468],{},"市面上招聘系统很多，功能介绍一个比一个宏大。但对中小 RPO 寻访团队来说，选系统的逻辑和大厂完全不同：**你要的不是功能最多，而是团队用得起来。**这篇文章从六个维度，帮你把选型这件事想清楚。",[18,470,472],{"id":471},"一先看团队规模与上手成本","一、先看团队规模与上手成本",[10,474,475],{},"中小 RPO 团队通常 5 到 30 人，没有专门的系统管理员。这意味着：",[43,477,478,485,492],{},[46,479,480,481,484],{},"系统必须",[14,482,483],{},"开箱即用","，实施周期以「天」而不是「月」计；",[46,486,487,488,491],{},"一线寻访员必须",[14,489,490],{},"当天上手","，培训成本接近零；",[46,493,494],{},"界面流程要贴合寻访动作：录简历、推候选人、约面试、记反馈。",[10,496,497],{},"判断方法很简单：让最不熟悉系统的寻访员试用半小时，看她能不能独立完成一次完整的候选人跟进。如果做不到，说明系统太重。",[18,499,501],{"id":500},"二核心流程是否完整闭环","二、核心流程是否完整闭环",[10,503,504,505,508],{},"RPO 业务的典型链路是：",[14,506,507],{},"岗位需求 → 简历寻访 → 推荐客户 → 面试协调 → 入职跟踪 → 提成结算","。选型时逐环节核对：",[112,510,511,514,517,520],{},[46,512,513],{},"岗位管理能否绑定项目与客户？",[46,515,516],{},"候选人推荐是否支持状态流转与跟进记录？",[46,518,519],{},"面试反馈能否现场录入？",[46,521,522],{},"入职数据能否直接驱动提成计算？",[10,524,525],{},"链路断一环，团队就会退回 Excel 补洞，最终系统沦为摆设。",[18,527,529],{"id":528},"三公海池机制是不是真公海池","三、公海池机制是不是「真」公海池",[10,531,532],{},"很多系统只有「候选人列表」，没有真正的公海池。有效的公海池机制应该包含：",[43,534,535,541,547],{},[46,536,537,540],{},[14,538,539],{},"保护期","：候选人被认领后有一定保护期，到期未跟进自动回收；",[46,542,543,546],{},[14,544,545],{},"回收规则","：超期未跟进、主动释放等规则可配置；",[46,548,549,552],{},[14,550,551],{},"流转统计","：回收多少、认领多少、流转率多少，数据可见。",[10,554,555],{},"公海池的价值在于让候选人资源在公司内流动起来，而不是沉淀在某个人的表格里。这是 RPO 团队提升转化率最直接的杠杆。",[18,557,559],{"id":558},"四提成结算能不能自动算","四、提成结算能不能自动算",[10,561,562],{},"提成是寻访员最关心的数字，也是管理者最容易出错的地方。问三个问题：",[43,564,565,568,575],{},[46,566,567],{},"提成规则（阶梯、固定、比例）能否自由配置？",[46,569,570,571,574],{},"业绩数据能否从推荐、到面、入职记录中",[14,572,573],{},"自动核算","，而不是手工录入？",[46,576,577],{},"结算单能否一键生成、导出、留痕？",[10,579,580],{},"如果答案都是「能」，月底对账可以从两天缩短到半小时，提成争议也会大幅减少。",[18,582,584],{"id":583},"五成本与付费模式","五、成本与付费模式",[10,586,587,588,591],{},"除了 License 价格，还要考虑隐性成本：实施费、培训费、账号加购费、按简历量或模块解锁的付费。建议优先选择",[14,589,590],{},"按团队规模的透明套餐","，并且先充分试用再决定付费。",[18,593,595],{"id":594},"六数据安全与隔离","六、数据安全与隔离",[10,597,598],{},"如果你的团队同时服务多个客户项目，务必确认：",[43,600,601,604,607],{},[46,602,603],{},"不同项目\u002F租户的数据是否完全隔离；",[46,605,606],{},"角色权限能否精细化到模块和字段；",[46,608,609],{},"关键操作是否留痕可审计。",[10,611,612],{},"候选人数据是人力公司的核心资产，这一点怎么强调都不为过。",[18,614,615],{"id":615},"总结",[10,617,618,619,622],{},"中小 RPO 团队选系统的标准排序应该是：",[14,620,621],{},"用得起来 > 流程闭环 > 公海池有效 > 提成自动 > 成本透明 > 数据安全","。云享智聘正是按照这个优先级设计的轻量化招聘管理 SaaS——先让团队跑起来，再谈其他。如果你正在选型，欢迎开通 7 天免费试用，用上面这份清单逐条对照。",{"title":127,"searchDepth":128,"depth":128,"links":624},[625,626,627,628,629,630,631],{"id":471,"depth":128,"text":472},{"id":500,"depth":128,"text":501},{"id":528,"depth":128,"text":529},{"id":558,"depth":128,"text":559},{"id":583,"depth":128,"text":584},{"id":594,"depth":128,"text":595},{"id":615,"depth":128,"text":615},"2026-03-10","从团队规模、核心流程、公海池机制、提成结算、成本与数据安全六个维度，帮助中小 RPO 寻访团队务实选择招聘管理系统，避免为用不到的重型功能买单。","\u002Fimages\u002Fblog\u002Frpo-system-selection.jpg",{},"\u002Fblog\u002Frpo-system-selection-guide",{"title":463,"description":633},"blog\u002Frpo-system-selection-guide",[640,641,642],"RPO选型","招聘管理系统","中小团队","d3ca4sBTv75oz0TEgxNk9fCZ5-1l05sPKzU31FQRZoU",1791284253828]