What online newspapers should decide in editorial meetings

Online newspapers need to publish regularly, but not every story starts in the same way. Some stories begin with tips from readers. Some come from press releases. Others need a reporter to find the angle, interview sources, and build a short series over time. That is why small newsrooms need editorial meetings to work as an operating habit, not just as a time to talk.

An editorial meeting does not need to be long or formal. What matters is deciding what will be published, who owns each story, when it should go live, and what needs to be checked before publication. Without a record, useful ideas disappear quickly and the team ends up reacting only to urgent work.

This guide outlines what a one-to-five-person online newsroom should decide in a weekly editorial meeting. With a CMS such as BylineCloud, drafts, owners, scheduled publishing, homepage placement, and edit history can be checked in one workflow.

Keep the meeting focused on one purpose

Editorial meetings often become too long because several purposes are mixed together. A meeting for collecting story ideas is different from a meeting for confirming this week’s publishing schedule. A meeting for reviewing performance is different again. When the purpose is unclear, the team may talk a lot but decide very little.

For a small online newspaper, the weekly meeting should first focus on the publishing plan. Review and brainstorming are useful, but trying to do everything every time makes the meeting heavy. Start with a small list of decisions that must be made before the meeting ends.

A practical first agenda can include these items.

• Decide the stories that must publish this week
• Assign the writer and reviewer for each story
• Separate reporting-heavy stories from source-based stories
• Set target publishing dates and times
• Pick candidates for homepage and newsletter placement

When the purpose is clear, missing items are easier to recover later. The meeting has done its job if everyone leaves knowing what to do next.

Collect story candidates before the meeting

If the team starts thinking of ideas only after the meeting begins, the meeting will run long. A short candidate list prepared in advance lets the meeting focus on selection. The candidate does not need to be a finished pitch. A working title, story type, source link, reader need, and possible owner are enough.

Each candidate should include its source. A reader tip, press release, reporter idea, advertiser request, or public announcement all require different checks. If the source is missing, it becomes harder to set priority and easier to miss disclosure or conflict questions.

A pre-meeting candidate list can include the following.

• Working title
• Story type
• Source and reference links
• Why readers need it
• People or facts to check
• Target publishing date
• Possible owner

For teams using BylineCloud, an idea can become a draft early and stay in draft status until the meeting confirms it. To avoid a growing pile of unused drafts, the meeting should also separate active stories from paused ideas.

Set priority by reader need and timing

When every story looks important, the newsroom needs a standard. Small teams have limited time, so they need to separate stories that lose value if delayed from stories that can be prepared more slowly. If the team only picks the easiest work, important planned stories will keep slipping.

Start by asking whether readers need the information this week. Local event notices, policy changes, and timely industry explanations often need earlier publication. Evergreen guides, interviews, and background pieces can usually be scheduled with more preparation time.

The meeting can use these questions to set priority.

• Do readers need this information this week
• Will the story lose value if it is delayed
• Can it be written without additional reporting
• Are photos or documents needed
• Could it bring useful long-term search traffic
• Does it involve advertising, sponsorship, or disclosure

Do not use expected page views as the only standard. Some stories matter for trust even if they do not become the most-read article. A good editorial meeting balances urgent, useful, and strategic work.

Separate the owner from the reviewer

In a small newsroom, one person may plan, report, write, and publish the same article. Even so, each story should have at least one reviewer. The reviewer is not there to rewrite the article. Their job is to check facts, headline risk, legal sensitivity, disclosure, and publication timing.

If only the writer is assigned, review often piles up right before publication. If too many reviewers are assigned, responsibility becomes unclear. A simple reviewer rule by story type keeps the workflow lighter after the meeting.

Roles can be divided this way.

• The writer owns reporting and the draft
• The reviewer checks facts and risk
• The publisher checks images, links, and scheduling
• The homepage owner decides placement and replacement timing
• The distribution owner checks newsletter and social sharing

BylineCloud can support this by separating account permissions and article status. Not every team member needs direct publish permission. A draft, review, and publishing flow reduces avoidable mistakes.

Record decisions instead of every conversation

Meeting notes do not need to capture the full discussion. They should capture decisions and next actions. Who suggested which idea is usually less important than which story will move forward, what must be checked, and when it will be reviewed again.

If notes are too long, nobody reads them later. If they are too short, the team forgets why a decision was made. For small teams, one or two sentences per story is usually enough.

Useful meeting notes include these points.

• Stories moving forward and stories on hold
• Writer and reviewer
• Reporting or materials needed
• Target publishing date
• Homepage and distribution plan
• Reason for putting a story on hold
• When to revisit paused ideas

The record can live in a separate document or in CMS draft notes. What matters is that the next meeting can quickly see what was decided last time.

Leave room in the publishing schedule

A common mistake is filling the weekly schedule too tightly. Small newsrooms can receive urgent tips, event updates, correction requests, or advertiser questions at any time. If the schedule is full, urgent work can damage the quality of planned work.

The weekly plan needs open space. Even a publication that posts every day should leave room for article updates, short notices, newsletter preparation, and maintenance of older articles.

Check these points when setting the schedule.

• Mix reporting-heavy stories with source-based stories
• Avoid placing several long stories on the same day
• Leave time for photos and image preparation
• Schedule review before the day of publication
• Leave time to check the live article after scheduled publishing

The schedule is a working plan, not a pressure tool. When it needs to change, record the reason and move the story. Readers are better served by consistent quality than by a rushed calendar.

Review last week at the next meeting

An editorial meeting is part of a loop. The team should check whether last week’s planned stories were actually published, why delayed stories slipped, and what happened after publication. Without review, the same problems repeat.

The review does not need to be only a numbers report. For a small publication, important signals may include reader replies, source follow-up, newsletter response, search traffic starting to appear, or a story that needs an update.

At the next meeting, check the following.

• Stories published as planned
• Stories that slipped and why
• Stories that performed better than expected
• Articles that need corrections or updates
• Topics that should become follow-up stories
• Workflow changes worth repeating next week

With a CMS such as BylineCloud, publish dates, edit dates, article status, and traffic signals can be checked together. Over time, the meeting helps the newsroom understand which topics it handles well and which steps slow the team down.

Start small and improve the format

There is no need to design the perfect editorial meeting format on day one. A format that is too complex will stop being used. Small online newspapers should start with a meeting that finishes within 30 minutes, records decisions by story, and makes the next action clear.

For the first month, one simple table is enough. Story candidate, owner, reviewer, publishing date, and status can already improve the meeting. After a month, add missing fields and remove fields nobody uses.

Once the meeting becomes a habit, publishing depends less on individual memory. Good ideas are less likely to disappear, urgent and important stories can be balanced, and new team members can understand how the newsroom works. For a small newsroom, an editorial meeting is not extra bureaucracy. It is a way to make publishing steadier.