Search Results for: DACS

Notes

We Must Check Our ‘Facts;’ Mistakes Are Piling Up Again #

Take a look at the corrections page. We’re making the same kinds of mistakes over and over. Names. Numbers. Titles. We’re getting those, and other things, wrong.

This month has been especially busy. From reporters to producers to editors, it’s clear that we aren’t always double-checking the basics.

The result is that some great stories have corrections notes attached to them. That’s a shame.

So, once again:

- Be sure about “facts” you put into DACS, scripts, promos, blog posts or basically anything that could find its way onto our website or onto our airwaves. Remember, your keyboard is a live mic.

- Double- or triple-check everything, and never assume that the next person in the process is going to do it for you. If you write it, say it or approve it, you own it.

- Use the Accuracy Checklist.

John Wooden, arguably the greatest men’s college basketball coach, would show his players how he wanted them to put on their socks and tie their sneakers. His point was that if they didn’t do those things correctly, they would get blisters — blisters that could put them on the bench and hurt the team.

We get so many things right. But we’re also getting too many blisters.

(“Memmos;” July 18, 2017)

Notes

Our Corrections Page Shows Too Many Unforced Errors; Let’s Fix That #

Misspelled names.

Wrong titles.

Math mistakes.

The list could go on.

A scroll down our corrections page makes clear that we’re not doing a good enough job checking and re-checking many basic things. Bad information is getting into story collections and DACS lines. It’s getting into captions and blog posts. It’s getting on the air.

We’ve got to do better. We can do better. Here’s how:

- Be sure about “facts” you put into DACS, scripts, promos, blog posts or basically anything that could find its way onto our website or onto our airwaves. Remember, your keyboard is a live mic.

- Double- or triple-check everything, and never assume that the next person in the process is going to do it for you. If you write it, say it or approve it, you own it.

- Use the Accuracy Checklist.

(“Memmos;” Sept. 26, 2016)

Notes

Recommended Listening: Why Not To Use The Phrase “Officer-involved Shooting” #

A check of our archives shows we’ve generally avoided the phrase “officer-involved shooting.” Thanks.

But it has crept into some DACS-only pages, online teasers, photo captions and headlines. Going forward, let’s not use it.

As On The Media explored this week, “officer-involved shooting” is among those phrases that feel like “euphemisms designed by government to change the subject.”

The better way to go is almost always to simply say “police shooting” or to use action words – basically, to describe what happened rather than try to label it.

(“Memmos;” July 7, 2016)

Notes

What Did We Say About That? A Guide To The 2015 ‘Memmos’ #

What did Mark annoy us about in 2015? Here are the year’s “Memmos,” divided into categories:

 

ANONYMITY AND SOURCING

-         An Anonymous Editor Thinks What The ‘Times’ Did Was Funny

-         Single Source Approval Process

 

BREAKING NEWS

-         When News Breaks, Keep A Couple Things In Mind

 

DACS AND OTHER STANDARD PROCEDURES

-         Your Keyboard Is A Live Mic (Or, If You Write It They May Say It)

-         NPR’s ‘Minor Consent Form’: Spanish Version

-         Guidance: On Station Reporters & News About Their Universities Or Institutions

-         Resource: Guidelines About The ‘Morning Edition’ Book Club, Fundraising & The Firewall Between Them

 

-         Ben Affleck, ‘Finding Your Roots’ And Why Our Standards Point To A Different Decision

-         On Gender Identity

-         Yes, Journalists Can Give To Charities That Are Helping People In Need

-         Guidance on: Coverage of books written by NPR staffers

-         When We’re Asked To Remove A Photo, Here’s What We Do

 

-         Proofread DACS Lines; Mistakes In Them Can End Up On Our Website

-         On Why It’s Not OK To Ask Friends, Family Or Fixers To Take Photos For Us

-         DACS Lines Are Journalism

-         Guidance On The Use Of ‘Disturbing’ Videos And Audio

-         Online News Commentaries

 

-         This Is An Important Reminder About Dealing With Those Who Are Vulnerable; Please Read It

-         When There’s No Evidence To Support A Claim, We Should Say That

-         Guidance On Music In Broadcast Pieces

-         Reminder: If The Facts Don’t Support Someone’s Claim, Say That

 

DIFFICULT DECISIONS

-         The ‘Charlie Hebdo’ Cartoons And NPR’s Decision Not To Publish Them

-         Gyrocopter Story Raises An Old Question: When Should Journalists Intervene?

-         On The Plagiarism Case And How It Was Handled

 

LANGUAGE TO USE AND LANGUAGE NOT TO USE

-         Repetitive Acronyms

-         Reminder: References To War Camps Must Be Precise

-         Don’t Be Careless With The Word ‘Countless’

-         Here’s Why We Use The Word ‘Islamist’

-         Analysts, Critics, Experts & Officials Agree: We Talk About Them An Awful Lot

 

-         Some So-called Guidance

-         Watch What You Say: It’s National Grammar Day

-         In The ‘Vast Majority’ Of Cases, Are We Sure We Should Use Those Words?

-         On The Word ‘Suicide’

-         Let’s Toss ‘Hat In The Ring’ Into The Cliché Round File

 

-         Guidance On The Words ‘Protests’ And ‘Protesters’

-         Guidance: ‘Same-Sex Marriage

-         Guidance: If ‘We’ Are Not Part Of The Story, Keep ‘Us’ Out Of It

-         No Joke: A Reminder About Writing, Courtesy Of ‘The Daily Show’

-         Guidance On Key Words That Come Up In The Planned Parenthood Stories

 

-         Save Yourself A Word And Make The Latin Teachers Happy

-         No Change In The Way We Introduce The Islamic State (later revised; see next entry in this list)

-         New Guidance On ‘ISIS’ & ‘Islamic State’

-         On ‘Migrants’ And ‘Refugees’

-         Pleonasms: Words That Don’t Need To Be Together

-         Take Care When Describing Weapons

 

-         There’s No Debate About This: We’ll Get Complaints If We Say The Candidates Are Behind Podiums

-         Take The ‘Sting’ Out Of References To The ‘Planned Parenthood Videos’

-         “Let’s Reduce Our ‘Buts’ “

-         Words We Get Wrong: The List

-         New Guidance On References To Myanmar

 

-         As Great Uncle Frederick Said, ‘More’ Or ‘Most’ Probably Don’t Belong In Front Of An Adjective With One Syllable

-         It’s ‘Boy With Autism,’ Not ‘Autistic Boy’

-         Keep Your Enemies Close And Your Antecedents Closer

-         No, Virginia, It ‘Tisn’t The Season

 

MISTAKES: HOW TO HANDLE THEM AND HOW TO AVOID THEM

-         We’re Making More Than A Few

-         Serious Mistakes Need To Be Flagged Immediately

-         The NPR Accuracy Checklist

-         Please Read The ‘CJR’ Report About ‘Rolling Stone’

-         Don’t Trust, Do Verify: The Vaping Hoax

 

-         Reminder: When Posting Corrections, The Correspondents/Bloggers/Editors Who Allegedly Committed The Errors Need To Be Involved

-         Don’t Trust Your Mother Or The Internet

-         Stories About Illinois Police Officer’s Death Underscore Need To Attribute

-         Put On-Air Corrections With The Original Stories

 

NAMES AND PRONUNCIATIONS

-         Guidance On The Name Of Argentina’s President

-         Reminders On Two Names (Ofeibea Quist-Arcton & Leila Fadel)

-         Reminders: Say ‘MURZ’ & ‘STEHF-in’

-         “It’s ‘Argentine,’ Not ‘Argentinian’ “

 

OFFENSIVE LANGUAGE

-         Bleep The Whole @#$%&*! Word

-         Resending: The ‘NPR Policy On Use Of Potentially Offensive Language’ And Related Notes

-         No Exceptions: Any Clip With Offensive Language, Bleeped Or Not, Must Be Approved Well Ahead Of Broadcast

-         Warning: This Post Contains Language That May Offend; Such Words Should Not Be Used In Podcasts Or On The Air

-         If We’ve Bleeped It, Do We Also Need To Warn Listeners? Maybe Not

 

SOCIAL MEDIA

-         For Comparison Purposes: The BBC’s Updated Guidance On Social Media

-         False Alarms About The Queen Reinforce Why We Think Before We Tweet

-         Read This If You Use Social Media; Everyone Should Know Our Thinking

-         Reporter’s Suspension For A Tweet Makes This Is A Good Time To Read Our Social Media Guidance

 

THIS IS HOW TO DO IT!

-         Encore! Encore!

-         Hey, You Should Read This: We Put The ‘Superbug’ News In Its Proper Place

-         Do Listen To This: A Walk Through Sandtown That Is Compelling And Instructive

-         A Thanks And Two Reminders On Describing Weapons And Adding Sources To ‘Reportable’ Notes

-         Kudos For Some Solid Reporting, Careful Writing & Smart Blogging

 

WHAT DID WE SAY IN 2014?

-         Click here to see that list

(“Memmos;” Dec. 22, 2015)

Notes

If We’ve Bleeped It, Do We Also Need To Warn Listeners? Maybe Not #

Is it necessary to alert listeners that there’s offensive/disturbing/troubling/etc. language in a report if we’ve already bleeped the nettlesome word or words?

The short answer is, “not always.”

Previous guidance has been too strict on this point. Let’s try this:

If it’s been decided after discussions with senior editors that a word or phrase will be bleeped, don’t assume listeners do or do not need to be alerted. Instead, consider the context.

– Is the cut still intense, graphic or disturbing even after it’s been bleeped? Then a heads up for listeners could be warranted. By the way, it may not have to be a line that sounds like a warning. The language can be conversational and informational (more on that below).

– Is the cut funny and a naughty word or two are said in jest? Then a heads up probably isn’t necessary.

– Is it one bleep in an otherwise family-friendly piece and the word wasn’t said in anger? Then, again, there could be no need for a heads up.

Basically, it’s a judgment call. Talk to the deputy managing editors (Chuck Holmes & Gerry Holmes) and/or the standards & practices editor (Mark Memmott). It will get figured out.

Two related notes:

– Here’s the part about being conversational and informational. If we think listeners should be alerted, we don’t always need to say something like “we should warn you.” On Morning Edition recently, there was a piece about the comic Chris Gethard. Two F-bombs were bleeped. In the introduction, David Greene said of Gethard that, “Chris is funny and weird. But he doesn’t shock audiences. You’ll only hear a couple of bleeps this morning.” That told listeners something about Gethard and tipped them off to what was coming without saying they needed to be on guard.

– Any time there’s bleeped language in a piece, the DACS line must tell stations what that word is, when it appears (or approximately if we’re still editing) and that it will be bleeped. Obviously, on the occasions when we don’t bleep offensive language, the DACS need to explain that.

NPR’s “Policy On Use Of Potentially Offensive Language” is posted here.

(Memmos; Aug. 18, 2015)

Notes

DACS Lines Are Journalism #

By Chuck Holmes:

DACS lines are many things. A thumbnail description of a story. A necessity. And, yes, often a pain in the backside.

But above all, they are journalism. And they reach ­a vast audience. They are the prime means to inform the network of the stories we’re telling. Shows, Digital News, Member Stations — all rely on them.

A DACS line must be brief, accurate, up to date and reflective of the story. Too often they are written in haste, not updated or simply do not exist.

Bad DACS lines can have a serious cascade effect. In recent weeks, a show billboard was incorrect because information was lifted from a dated DACS line. It was an easily avoidable mistake that was heard by listeners around the world. We too often see imprecise headlines on NPR.org, again because the DACS line doesn’t accurately reflect the content of the story. On weekends especially, member stations often read our DACS lines — word for word — on air as promotional copy to highlight upcoming stories.

DACS lines are the responsibility, first and foremost, of Desk reporters and Desk editors or, in the case of 2-ways, Show editors and Show producers. Like a story, they should be written, edited and updated. And DACS lines from Desks may be further edited by Shows and Digital News, as warranted.

Here are the rules:

– Every NewsFlex entry needs a DACS line. And every DACS line needs to be updated as the story changes. If you’re creating a NewsFlex entry, you own it and will be accountable for it.

– Keep DACS lines tight and to the point. Think tweet. DACS lines should not be more than a short sentence or two. (If a language advisory or embargo note must be included, those can run longer.)

–  The DACS line needs to say something, even on a story that is developing. Unacceptable: “lines tk.” But it shouldn’t say too much. Unacceptable: a cut and paste of the first few grafs of the piece.

–  Do not include names of reporters, hosts, contributors in the DACS lines for pieces. (A byline will appear automatically on the web rundown and the note to stations).

– In a DACS line for a 2-way, only include the name of a guest when the guest is not affiliated with NPR or a member station. (An issue expert, newsmaker, etc.)

– In our hectic daily routine, it may not be the reporter who creates the DACS line, but in the end the reporter’s name is associated with it. So, if you’re a reporter, it is in your best interest to make sure the DACS line accurately reflects the story.

– Follow-up. If a story changes, let the Show and Digital News know that the DACS line needs to change, too.

We’re putting together a more extensive style guide to DACS lines and will be working with the Shows and Digital News to codify a standard workflow.  More to come.

Related:

– Proofread DACS Lines; Mistakes In Them Can End Up On Our Website

– Your Keyboard Is A Live Mic (Or, If You Write It They May Say It)

– No Exceptions: Any Clip With Offensive Language, Bleeped Or Not, Must Be Approved Well Ahead Of Broadcast

(Memmos; July 21, 2015)

Notes

Proofread DACS Lines; Mistakes In Them Can End Up On Our Website #

Here’s a DACS line as it appears in Newsflex:

“A village of Portsoy is reviving an old seamen’s superstition by banning bananas during it’s annual boat festival. NPR’s Lynn Neary talks to festival chairman Roger Goodyear.”

Here’s the introduction to that piece, as posted on one of our transcripts pages:

“A village of Portsoy is reviving an old seamen’s superstition by banning bananas during it’s annual boat festival. NPR’s Lynn Neary talks to festival chairman Roger Goodyear.”

The DACS line was picked up and posted verbatim, including the typos.

We’ve noted before that the information in “DACS lines, scripts and Web teasers could end up as copy on our website and as language read on the air by us or a member station.”

Yes, the transcript editor should spot obvious problems and either fix or write around them. Yes, an “it’s” when it should be “its” and a confusing phrase such as “a village of Portsoy” are not the biggest mistakes we will make.

And, yes, DACS lines have to do a lot (remember to include warnings about offensive language!).

But they should be as clean and accurate as possible from the start. Remember, “your keyboard is a live mic.”

(Memmos; July 6, 2015)

Notes

No Exceptions: Any Clip With Offensive Language, Bleeped Or Not, Must Be Approved Well Ahead Of Broadcast #

There have been times in recent weeks when potentially offensive language — bleeped, thankfully — was broadcast without a discussion beforehand with senior editors. That’s disturbing given the number of reminders that have gone out concerning such language and our policy. It should not happen.

Hopefully the points that follow are clear:

1. We have a detailed “Policy On Use Of Potentially Offensive Language.” Print it and read it.

2. Any clip with offensive language must be brought to the attention of the DMEs well before air time. Basically, as soon as you think you might be using it, talk to them. They may need time to consult with Legal.

Note: It does not matter if the words have already been bleeped. Be prepared to justify their use.

a. By the way, it’s assumed show executive producers and desk chiefs will already have been consulted.
b. The standards & practices editor should also be flagged.

3. The DMEs have yea-or-nay authority.

4. DACs lines must tell stations the specific language that is in the cut, when it occurs and whether it is bleeped. Those lines must go out with as much lead time as we can give.

5. If the words are bleeped, they must be completely bleeped. No syllable can be heard.

6. We do all this because we respect our audience and know that certain language will offend many. We also know that community standards vary around the nation and that complaints to the FCC can be costly to our member stations.

7. Overall, NPR is conservative about potentially offensive language — not permissive. There’s a key line right at the top of our policy statement: “NPR has always set a high bar on use of language that may be offensive to our audience.” The words must be important to the piece.

Questions? See Chuck, Gerry or me.

(Memmos; June 16, 2015)

Notes

Resending: The ‘NPR Policy On Use Of Potentially Offensive Language’ And Related Notes #

No, we haven’t had a language mishap (that I know of).

This note is just a reminder of some things because there have been questions in recent days.

– The “NPR Policy On Use Of Potentially Offensive Language” is posted here.

– As we’ve said a few times before, “if there’s potentially offensive language in a piece intended for broadcast — even if the words have been bleeped — stations need to be alerted in the DACS line. Listeners and readers online deserve to be warned as well, of course.”

– We “Bleep The Whole @#$%&*! Word.” Yes, that means no “bull.” Not even the “b.”

– As soon as you know that you might want to use some potentially offensive language, bring it to the attention of senior editors. Here’s a recent update to our Ethics Handbook:

  • Discussions Must Happen Well Before Any Broadcast:
    • If potentially offensive language is being considered for broadcast, senior editors (typically, the Deputy Managing Editors or Standards & Practices editor) must be consulted with enough lead time to allow for a substantive discussion and enough lead time to give the General Counsel time to provide guidance. If time for discussion is running short, the language must be cut from the report or “bleeped.”
    • This rule applies to acquired programs as well. As NPR’s policy on use of potentially offensive language states:
      • “In the case of programs under the ultimate direction of the Vice President for Programming, including all acquired programs, producers shall consult NPR’s Vice President for Programming or the VP’s designee as soon as possible, but in any event before the program is delivered to NPR for distribution to stations.”

(Memmos; May 11, 2015)

Notes

Bleep The Whole @#$%&*! Word #

If a word needs to be bleeped, no part of it should be heard. We don’t try to give listeners a hint by including a bit of the word’s start or end.

What language is offensive?

– The “NPR Policy On Use Of Potentially Offensive Language” is posted here.

– A discussion of NPR’s guidelines on the subject is here.

Two related notes:

– The rules apply to foreign languages as well.

– Don’t forget that “if there’s potentially offensive language in a piece intended for broadcast — even if the words have been bleeped — stations need to be alerted in the DACS line. Listeners and readers online deserve to be warned as well, of course.”

(Memmos; Feb. 13, 2015)

Notes

Your Keyboard Is A Live Mic (Or, If You Write It They May Say It) #

(Editor’s note on July 27, 2017: Click here to go to an updated special section about the do’s and don’t's of social media.)

Reporters have always been told to never put anything in a story draft that they wouldn’t want to see in print. No jokes. No obscenities. No snotty comments. No half-formed theories. No “facts” that haven’t been double-checked.

If they need to create a file into which a story can later be pasted, that’s what “the quick brown fox jumps over the lazy dog” and “lorem ipsum” are for. (Look them up if you don’t know what I’m referring to or how they’re used.)

Sometimes things slip through. Romenesko tracks such mishaps.

Broadcast journalists know every mic may be live and that they shouldn’t say something they wouldn’t want to be recorded and replayed. This note is meant to draw a parallel.

The information that goes into DACS lines, scripts and Web teasers could end up as copy on our website and as language read on the air by us or a member station.

No, our drafts and DACS are not full of naughty words, snide remarks and errors. But what goes into them matters and may find its way into places you did not expect. It’s best to treat them accordingly. Your keyboard is something of a live mic.

(Memmos; Jan. 22, 2015)

Notes

When It Comes To Being Offensive, English Isn’t The Only Language We Need To Worry About #

Everyone should be familiar with the “NPR Policy On Use Of Potentially Offensive Language.” If you need a refresher, it is posted here: https://www.documentcloud.org/documents/1273045-potentially-offensive-language-guidance.html

There are a few things to note:

– This isn’t an “English-only” issue. The FCC’s policies and our guidance apply to offensive words or phrases in any language.

– As the NPR policy states, “there is no room for guessing. If program material depicts or describes sexual or excretory activities or organs or other potentially objectionable language, the producer must seek guidance as to its suitability. If the matter is urgent, please contact the News Duty Manager …who is available 24/7 [if you don't know the phone number, ask Chuck or Gerry]. He/she will consult with the Office of the General Counsel (OGC) and/or escalate as appropriate. In all other non-urgent instances, please work through the normal editorial process, which for these matters, should involve consultation with OGC. While all decisions on content are ultimately reserved to the editorial decision making process in the News and Programming Divisions, it would be the extremely rare case that NPR journalists would not abide by the advice of NPR legal counsel as to the use of language that may be regarded as indecent or profane.”

As we’ve said before, “if there’s potentially offensive language in a piece intended for broadcast — even if the words have been bleeped — stations need to be alerted [as soon as possible] in the DACS line. Listeners and readers online deserve to be warned as well, of course.”

(Memmos; Dec. 12, 2014)

Notes

UPDATE: The Latest ‘NPR Policy On Use Of Potentially Offensive Language’ #

A search today for NPR’s latest guidance on the use of potentially offensive language revealed that we hadn’t posted the most recent version.

So, here’s a link to where our latest language about such language can be found. It was written earlier this year:

NPR Policy On Use Of Potentially Offensive Language

The biggest change from the previous document is the addition of a lengthy section on “Entertainment and Music Programming.”

Fair warning: As we might say on the air and online, “some of the language in the document will be offensive to many readers.”

The section of the Ethics Handbook that deals with “using potentially offensive language” has been updated with the new link.

This is a good time for a reminder, because one slipped through the cracks on us last week: If there’s potentially offensive language in a piece intended for broadcast — even if the words have been bleeped — stations need to be alerted in the DACS line. Listeners and readers online deserve to be warned as well, of course.

Clarification: No offensive words were heard in the piece referred to above. The words were bleeped.

(Memmos; Aug. 11, 2014)

Guideline

Using potentially offensive language. #

There is a lengthy document (updated in January 2014) that lays out NPR’s policy on use of offensive language posted online. It is radio-centered, but the same rules apply to what we post on NPR.org.

The policy statement begins with this:

“As a responsible broadcaster, NPR has always set a high bar on use of language that may be offensive to our audience. Use of such language on the air has been strictly limited to situations where it is absolutely integral to the meaning and spirit of the story being told.”

“We follow these practices out of respect for the listener,” the policy continues, and because in the post-Janet Jackson “wardrobe malfunction” world, federal regulators “have taken a much more aggressive line on what they regard as indecent or profane content.” The 2010 decision by a federal appeals court that invalidated the FCC’s indecency policy has not prompted NPR to change its position.

That said, “there are rare instances where we will permit use of profane or indecent languages for news or programmatic reasons. Such an instance is when the use of such language is so vital to the essence of the story that to excise or bleep it would be to distort it or blunt its power and meaning.”

An example (fair warning … you’re about to see an expletive): While traveling with U.S. Army forces in Iraq, NPR’s Eric Westervelt was on the scene when the unit came under fire. At one point in his tape, an American soldier could be heard telling another man to “get the fuck under the truck.”

The NPR policy states that in this case “the use of profanity … is editorially justifiable” because it meets the test of being “vital to the essence of the story” and cutting it out or bleeping the word  would alter the power and meaning of the report.

As required by NPR’s policy, “the piece was preceded by a language advisory in the intro read by the host, in addition to the DACS notices in advance to stations. NPR policy is to do both in all such instances for both legal and editorial reasons.”

Online, if sound or text containing potentially offensive language has been approved for use by a Managing Editor or someone above that level, it too must be preceded by text (and in the case of audio, a verbal warning as well) advising the NPR.org audience that what follows contains language some may find offensive. When used in a blog, in most cases the warning should come before a “jump” to a second page. It should require a second “click” to get to the offensive material.

If used online, audio or video containing offensive material should never play automatically. To view or hear it, the user must choose to click “play.”

Update on May 4, 2015. Discussions Must Happen Well Before Any Broadcast:

If potentially offensive language is being considered for broadcast, senior editors (typically, the Deputy Managing Editors or Standards & Practices editor) must be consulted with enough lead time to allow for a substantive discussion and enough lead time to give the General Counsel time to provide guidance. If time for discussion is running short, the language must be cut from the report or “bleeped.”

This rule applies to acquired programs as well. As NPR’s policy on use of potentially offensive language states:

“In the case of programs under the ultimate direction of the Vice President for Programming, including all acquired programs, producers shall consult NPR’s Vice President for Programming or the VP’s designee as soon as possible, but in any event before the program is delivered to NPR for distribution to stations.”