editorial-workflow

編集ワークフロー管理

ニュースルームはシステムで運営されています。このスキルでは、記事の追跡、締め切りの管理、記者と編集者間の連携に使えるテンプレートとプロセスを提供します。

使用する場面

• 記事の追跡システムを構築するとき
• 編集カレンダーを作成するとき
• 担当割り当てと引き継ぎの手順を定めるとき
• 複数の記事と締め切りを管理するとき
• 新しい編集者にワークフローを教えるとき

記事のステータス分類

標準ステータス

ステータス	意味	担当者
企画案	アイデアが提出され、承認待ち	記者
担当決定	承認済みで、記者が作業中	記者
取材中	取材が進行中	記者
原稿	初稿が提出済み	編集者
編集	編集者が修正中	編集者
修正	記者に差し戻され、修正中	記者
校正	校正段階	校正者
最終稿	公開準備完了	編集者
公開予定	指定日に公開するためキューに登録済み	システム
公開済み	公開中	完了
保留	中断中で、取りやめではない	編集者
取りやめ	記事を取りやめ	編集者

ステータスの流れ

Pitch → Assigned → Reporting → Draft → Edit → Revision (loop) → Copy → Final → Scheduled → Published
                                         ↓
                                       Hold/Kill

記事の担当追跡

担当記録テンプレート

## Story: [Slug/working title]

### Assignment details
- **Reporter:** [name]
- **Assigning editor:** [name]
- **Date assigned:** [date]
- **Deadline:** [date/time]
- **Target publication:** [outlet/section]

### Story specs
- **Format:** [brief, feature, enterprise, etc.]
- **Word count:** [target]
- **Multimedia:** [photos, video, graphics needed]
- **Sources required:** [minimum sources]

### The assignment
[What the story is, angle, key elements to include]

### Key contacts
[Sources to interview, PR contacts, experts]

### Background/resources
[Links to previous coverage, documents, data]

### Budget line
[One sentence for editorial budget meetings]

### Status history
| Date | Status | Notes |
|------|--------|-------|
| [date] | Assigned | |
| [date] | [status] | [note] |

担当引き継ぎチェックリスト

記事を割り当てるとき：

## Assignment handoff

### From editor to reporter
- [ ] Story scope clearly defined
- [ ] Deadline confirmed
- [ ] Word count/format specified
- [ ] Key sources identified
- [ ] Background materials shared
- [ ] Multimedia needs discussed
- [ ] Questions answered

### Reporter confirms
- [ ] Deadline is realistic
- [ ] Have access to necessary sources
- [ ] Understand the angle
- [ ] Know who to ask for help

編集カレンダー

カレンダーテンプレート

## Editorial calendar: [Week/Month of Date]

### Monday [date]
| Time | Story | Reporter | Status | Notes |
|------|-------|----------|--------|-------|
| AM | [story] | [name] | [status] | |
| PM | [story] | [name] | [status] | |

### Tuesday [date]
[same format]

### Evergreen queue
| Story | Reporter | Ready date | Notes |
|-------|----------|------------|-------|
| [story] | [name] | [date] | [can run anytime after this] |

### Upcoming (next 2 weeks)
| Story | Reporter | Target date | Status |
|-------|----------|-------------|--------|
| [story] | [name] | [date] | [status] |

企画会議テンプレート

週次／日次の編集会議用：

## Editorial meeting: [date]

### Today's lineup
| Story | Reporter | Status | Publish time | Notes |
|-------|----------|--------|--------------|-------|
| [story] | [name] | [status] | [time] | |

### Tomorrow's lineup
[same format]

### In progress (due this week)
| Story | Reporter | Due | Status | Blockers |
|-------|----------|-----|--------|----------|
| [story] | [name] | [date] | [status] | [any issues] |

### Pipeline (next 2+ weeks)
| Story | Reporter | Target | Status |
|-------|----------|--------|--------|
| [story] | [name] | [date] | [status] |

### Discussion items
- [Topic 1]
- [Topic 2]

### Action items
- [ ] [Action] - [Owner] - [Deadline]

締め切り管理

締め切りの種類

締め切り	目的	通常の先行時間
取材	インタビュー／調査を完了する	初稿の2～5日前
初稿	編集者に提出する	編集の24～48時間前
最終稿	修正後の原稿	校正の12～24時間前
図版／写真	ビジュアル素材を準備する	初稿と同じ
校正	言葉遣い／スタイルを確認する	公開の4～8時間前
公開	公開する	時刻を設定

締め切り追跡テンプレート

## Story: [title]
**Final publish deadline:** [date/time]

### Working backward
| Milestone | Deadline | Status |
|-----------|----------|--------|
| Reporting complete | [date] | ☐ |
| First draft due | [date] | ☐ |
| Art/photos due | [date] | ☐ |
| Edit complete | [date] | ☐ |
| Revisions due | [date] | ☐ |
| Copy edit complete | [date] | ☐ |
| Final review | [date] | ☐ |
| Schedule/publish | [date] | ☐ |

締め切りに間に合わない場合の手順

締め切りに遅れるおそれがある場合：

1. すぐに知らせる - 締め切りを過ぎるまで待たない
2. 簡潔に説明する - 何が進行を妨げているか
3. 新しい締め切りを提案する - 現実的な見積もり
4. 代替案を提示する - 短いバージョンにするか、切り口を変えるか

## Deadline alert

**Story:** [title]
**Original deadline:** [date/time]
**Issue:** [what's blocking]
**New proposed deadline:** [date/time]
**Impact:** [what this affects]
**Alternatives:** [options if any]

編集の引き継ぎ手順

記者 → 編集者

原稿を提出するとき：

## Draft submission: [story title]

**Draft location:** [link/file]
**Word count:** [count]

### What's in the draft
- [Key points covered]

### What's still needed
- [ ] [Outstanding item]
- [ ] [Waiting for source callback]

### Questions for editor
- [Question about structure, angle, etc.]

### Source notes
[Any attribution issues, off-record info, etc.]

### Multimedia status
- Photos: [ready/pending/needed]
- Graphics: [ready/pending/needed]

編集者 → 記者

修正のために差し戻すとき：

## Edit notes: [story title]

**Overall:** [brief assessment - on track, needs work, etc.]

### Structural changes needed
- [Major reorg, missing elements, etc.]

### Specific fixes
- Line [X]: [issue/change]
- Line [X]: [issue/change]

### Questions to resolve
- [Question requiring reporter input]

### Deadline for revisions
[date/time]

### Discussion needed?
[Yes - let's talk before you revise / No - changes are clear]

公開チェックリスト

公開前チェックリスト

## Pre-publish: [story title]

### Content
- [ ] Headline is accurate and compelling
- [ ] Dek/subhead summarizes well
- [ ] Lede works
- [ ] All facts verified
- [ ] All sources attributed correctly
- [ ] Quotes are accurate
- [ ] Numbers double-checked

### Style
- [ ] AP Style applied
- [ ] Consistent voice throughout
- [ ] No typos or grammatical errors
- [ ] Appropriate length

### Legal/Ethics
- [ ] No defamation risk
- [ ] Sources of comment contacted
- [ ] Corrections from previous versions applied
- [ ] Embargoes respected

### Multimedia
- [ ] Photos have captions and credits
- [ ] Alt text added
- [ ] Video/audio plays correctly
- [ ] Graphics are accurate

### Metadata
- [ ] SEO headline filled
- [ ] Meta description written
- [ ] Tags/categories applied
- [ ] Author byline correct
- [ ] Publication date/time set

### Final sign-off
- [ ] Reporter reviewed final
- [ ] Editor approved
- [ ] Copy editor signed off

公開後チェックリスト

## Post-publish: [story title]

### Immediate (within 1 hour)
- [ ] Story displays correctly
- [ ] Links work
- [ ] Images load
- [ ] No obvious errors
- [ ] Social posts scheduled/published

### Same day
- [ ] Monitor comments/feedback
- [ ] Watch for corrections needed
- [ ] Track initial metrics
- [ ] Respond to any issues

### Follow-up
- [ ] Note any updates needed
- [ ] Document corrections made
- [ ] Capture reader response
- [ ] Plan follow-up stories if warranted

ワークフローの文書化

プロセス文書テンプレート

ニュースルームのワークフローを文書化するとき：

## Workflow: [Name of process]

### Purpose
[What this workflow accomplishes]

### When to use
[Triggers for this workflow]

### Roles involved
| Role | Responsibility |
|------|----------------|
| [Role] | [What they do] |

### Process steps

**Step 1: [Name]**
- Owner: [role]
- Action: [what happens]
- Output: [what's produced]
- Next: [what triggers next step]

**Step 2: [Name]**
[same format]

### Tools used
- [Tool]: [what it's used for]

### Templates/Forms
- [Link to templates]

### Exceptions
- [When normal process doesn't apply]
- [What to do instead]

### Escalation
- [When to escalate]
- [Who to contact]

新しいスタッフのオンボーディング

## Editorial workflow onboarding

### Day 1
- [ ] Access to CMS granted
- [ ] Added to editorial chat/channels
- [ ] Received style guide
- [ ] Introduced to direct editor

### Week 1
- [ ] Shadow experienced reporter
- [ ] Review workflow documentation
- [ ] Complete first assignment (low-stakes)
- [ ] Learn deadline expectations

### Month 1
- [ ] Independently handle standard assignments
- [ ] Know escalation paths
- [ ] Understand publication calendar
- [ ] Comfortable with all tools

### Key contacts
| Need | Contact |
|------|---------|
| Assignment questions | [name] |
| Technical issues | [name] |
| Editorial disputes | [name] |
| HR/Admin | [name] |

---

優れたワークフローは意識されません。問題が起きたときにだけ、その存在に気づきます。