Plan coverage with the calendar

Read the calendar

Calendar places each post on its intended publish date. If that is blank, it falls back to the published date, linked contest date, or creation date. Badge color follows workflow status.

Month, Week, and Day views share the same filters. Editors can add a contest layer so games and content plans are visible together.

1 2 3 4

1. 1

   Switch among Month, Week, and Day and move through dates.

2. 2

   Contest layer overlays the game schedule for planning.

3. 3

   Filter by status, type, sport, assignee, persona, tier, or search.

4. 4

   Colored cards show the workflow status on the intended date.

Plan a week

1. Show the contest layer

   Review the slate and identify rivalry games, championships, streams, features, and expected high-interest results.

2. Create planned items

   Editors can create Planned posts for coverage that needs an assignment later. Link the contest and set an intended date.

3. Assign the right format and staff

   Choose recap, preview, roundup, feature, broadcast, podcast, interview, or highlight work based on the editorial plan.

4. Balance the board

   Filter by assignee or persona and move dates before the desk becomes overloaded.

5. Use Week view for handoff

   A week view makes tomorrow’s deadlines and missing assignments easier to discuss in a desk meeting.

Maintain contests

Contests holds seasons and games used by planning and the recap pipeline. A High School Sports season has a source URL. Fetch updates matching games, flags missing upstream games as stale, and does not delete them automatically.

1. Create or select a season

   Use a clear name, sport, term, year, and High School Sports source URL when the season is feed-backed. Manual leagues may leave the source URL blank.

2. Fetch the season

   The fetch adds new games and updates existing games by their stable contest identity.

3. Review stale rows

   Stale means a previously fetched contest did not appear in the latest response. Confirm a cancellation, source change, or upstream correction before editing.

4. Fetch supplemental details for finals

   Supplemental results, statistics, rosters, and coach comments feed recap production when available.

5. Use manual contests carefully

   Manual rows are appropriate for uncovered leagues or one-off corrections. Do not duplicate a game already owned by a feed.

Work coverage gaps

A coverage gap is a final contest in the configured recent-day window with no linked, non-rejected post. A linked planned or draft item counts as planned coverage; published or archived work counts as covered.

• ✓ Confirm the contest is truly final and not a duplicate or stale feed row.
• ✓ Search Posts before creating anything.
• ✓ When coverage exists, connect the existing post to the contest.
• ✓ When coverage is still needed, create a planned or draft item from the gap.
• ✓ When no story is warranted, leave an editorial note or resolve the underlying contest data according to desk policy.

Frequently asked questions