Sunday, March 11, 2007

You ask, I respond

Sorry for posting so late. Slept until 4:15.
Yay! We finally got our first question for the blog. Actually, we got our first several questions for the blog. I'm going to string out the answers over the next few days in order to A) give more attention to each (I'm trying to limit these posts to 500 words or so. The fewer issues I cover in those 500 words, the more in depth I can go), and B) Without any issues coming out this week, I had been planning to address some of these exact questions

So without further ado, Anonymous asks: "Josh, could you talk a bit more about the editorial structure of the Spectator? As in, the division of beats?"

Certainly, Anonymous.

First, a little background. The idea of a beat system is to have one writer responsible for keeping tabs on a full coverage area. These "beat chiefs" are supposed to meet regularly with key sources within the beat, pitch ideas for stories every week and to be regularly writing these pitches into articles. In theory, this benefits everybody: our sources are better served by having a regular point person on the paper and reducing the number of calls made by random reporters on deadline; the paper has a regular stream of ideas coming in so that two or three people aren't responsible for coming up with 40 story ideas each week as was the case in the past; and the readership is better served by having stories across a broader range of issues than might otherwise happen.

The idea was first introduced at Spec three years ago by Megan Greenwell and Matt Carhart in a limited form and has grown over each successive year. Right now, we have 28 beats that are covered on the campus side and about another 15 on the city side.

The process of deciding which beats we need to cover begins in October. The outgoing set of deputy and MB-level news editors meet at their weekly deputy meeting and discuss areas during which they discuss a year's worth of coverage, analyzing what the paper covered well, what it covered poorly, where we most need to improve in the coming year, and if there are any beats that we are covering which don't necessarily need a full-time or part-time beat chief.

After we compile this list together, we announce the beginning of beat shadowing at our next news meeting. Any person on the paper who has gone through training is eligible to shadow for a beat. As a shadow, reporters spend a week as if they were covering the beat. They'll meet with sources, come up with three pitch ideas, talk to their deputy, and decide upon at least one article, which they will then write.

Traditionally, writers have been eligible to shadow for up to three beats. After the end of three weeks, the deputies reconvene and look at who ran for each beat, specifically looking at how [Crap, that's 500 words already. I'll swear I'm almost done!] passionate they appear to be about the beat, how good their pitch ideas were, and how their story came out. It takes a lot of thought, especially considering the domino effect of matching all of the writers up with something that they want when some beats are more popular than others, and at the end, we have a roster of names.

Inevitably, something is left uncovered. At this point, we go back to writers on staff--both those who shadowed and those who didn't but have done impressive work in the past--and offer them some of those beats that have been taken. This is always a tough calculus--we don't want to guilt somebody into accepting a beat that they don't have time to write, but at the same time, we want to cover all of our bases.

The finals step is to organize beat chiefs into deputy groups. The idea here is that we want similar beats that share common sources and issues in a single deputy group so that we don't repeat ourselves and so groups can expand pitch ideas into analysis pieces and deeper stories. Also, we don't want one deputy to have 12 beat chiefs while another only has six.

By the end of winter break, we have all of our beats set, though we are continuously reevaluating structural issues.

More tomorrow.

No comments: