求职申请跟踪表搭建
按所用工具设计投递记录与跟进提醒,保留申请最远进度,提供渠道转化统计和每周复盘流程。
完整提示词
<context>
A job search without a tracker leaks: follow-ups are forgotten, the same company is applied to twice, interview notes are lost, and after six weeks nobody can say whether referrals or job boards are working. A good tracker is small enough to update in two minutes a day, records the source of every application so conversion rates by channel can be compared, and turns follow-up dates into a daily to-do list. One design trap breaks most homemade trackers: a single "stage" column is overwritten when an application closes, so an application rejected after two interviews looks the same as one that never got a reply, and every response-rate figure comes out too low. Track the current stage and the furthest stage reached as separate fields. It is not a search plan (which companies, which roles); it is the instrument that tells you whether the plan is working.
Tool: {{tool}}
Applications per week: {{applications_per_week}}
{{#search_context}}
<search_context>
{{search_context}}
</search_context>
{{/search_context}}
</context>
<task>
1. Stages: define the open stages in order, each with a one-line definition and the event that moves it on: Saved, Applied, Screen, Interview, Final, Offer. Then the closed outcomes: Accepted, Rejected, Withdrawn, and No response (no reply a set number of days after applying, default 21). Number the open stages 0 to 5 so that "furthest stage reached" can be compared and counted.
2. Columns: the fields to track, each with type, allowed values and why it matters. Include at least: company, role, link, date found, date applied, source (job board, company site, referral, recruiter, networking, other), contact name and channel, current stage (an open stage or a closed outcome), furthest stage reached (open stages only; it only ever moves forward and is never overwritten when the application closes), next action, next action date, salary range if posted, notes, and date closed.
3. Build it for {{tool}}:
- spreadsheet: the header row in order, data-validation lists for stage and source, and formulas written for both common spreadsheet apps where they differ: a "follow-up due" flag (next action date on or before today and current stage not a closed outcome), days since applied, a count per current stage, and response rate by source (applications from that source whose furthest stage is Screen or later, divided by all applications from that source that were actually sent, so Saved rows are left out). Add interview rate by source the same way (furthest stage Interview or later). Name the column letters you assume and keep them consistent with the header row. Suggest conditional formatting for overdue follow-ups.
- notion: database properties with types, select options for current stage and furthest stage, a formula property for "follow-up due", a formula that marks whether the furthest stage is Screen or later, and three views (board by current stage, table filtered to due follow-ups, table grouped by source with counts of that formula).
- paper: a two-page notebook spread layout, a daily line format, symbols for each stage written left to right so the furthest one reached stays visible when the outcome is added, and a weekly tally table counting by source and furthest stage.
4. Follow-up rules: default timings to adapt - follow up on an application after about a week to ten days if there is a contact, send a thank-you within a day of an interview, check in a couple of days after a promised decision date, and move to No response after the set period. Explain how the next action date implements each.
5. Weekly targets: break {{applications_per_week}} applications into daily actions alongside other activities if the context mentions networking or recruiters, and sanity-check the number against the hours available, saying if it looks too high to do well.
6. Weekly review: a 20-minute routine with the questions to answer each week (what moved, response rate by source, which roles get screens, what to change next week) and a rule of thumb for when there is enough data to compare channels (for example at least ten applications from a source).
7. Before answering, check every formula references the correct columns from the header row, that stage names match exactly between the list and the formulas, and that no rate is calculated from the current stage alone.
</task>
<constraints>
- Keep it simple: no more columns than someone will maintain daily. Mark optional columns as optional.
- Use only standard functions that work in the major spreadsheet apps; if a function differs, give both versions.
- Do not invent application data. Example rows, if shown, are clearly labelled as examples.
- Remind the user to keep personal data of contacts minimal and private, since the tracker holds other people's names and details.
</constraints>
<output_format>
## Stages
Table: Stage | Open or closed | Means | Moves on when.
## Columns
Table: Column | Type | Allowed values | Why.
## Build it
Instructions for {{tool}}, with formulas or properties in code blocks.
## Follow-up rules
## Weekly targets
## Weekly review
Checklist of review questions.
</output_format>可替换内容
- {{tool}}
- {{applications_per_week}}
- {{#search_context}}
- {{search_context}}
- {{/search_context}}
分类与标签
职场求职、求职投递、申请跟踪、跟进提醒、渠道转化、每周复盘