<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The Business Rusch: A Tale of Two Royalty Statements</title>
	<atom:link href="http://kriswrites.com/2012/08/15/the-business-rusch-a-tale-of-two-royalty-statements/feed/" rel="self" type="application/rss+xml" />
	<link>http://kriswrites.com/2012/08/15/the-business-rusch-a-tale-of-two-royalty-statements/</link>
	<description></description>
	<lastBuildDate>Mon, 20 May 2013 19:56:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Nicole Burton</title>
		<link>http://kriswrites.com/2012/08/15/the-business-rusch-a-tale-of-two-royalty-statements/comment-page-1/#comment-16769</link>
		<dc:creator>Nicole Burton</dc:creator>
		<pubDate>Sat, 08 Sep 2012 23:18:45 +0000</pubDate>
		<guid isPermaLink="false">http://kriswrites.com/?p=9045#comment-16769</guid>
		<description><![CDATA[I would be interested in seeing a good writer&#039;s contract.]]></description>
		<content:encoded><![CDATA[<p>I would be interested in seeing a good writer&#8217;s contract.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kristine Kathryn Rusch</title>
		<link>http://kriswrites.com/2012/08/15/the-business-rusch-a-tale-of-two-royalty-statements/comment-page-1/#comment-15929</link>
		<dc:creator>Kristine Kathryn Rusch</dc:creator>
		<pubDate>Thu, 23 Aug 2012 19:52:36 +0000</pubDate>
		<guid isPermaLink="false">http://kriswrites.com/?p=9045#comment-15929</guid>
		<description><![CDATA[Wonderful post, Don. Should I see it as a conspiracy that it got caught in my spam? &lt;VBG&gt; I hope others see this and understand how important your points are. Thanks.]]></description>
		<content:encoded><![CDATA[<p>Wonderful post, Don. Should I see it as a conspiracy that it got caught in my spam? <vbg> I hope others see this and understand how important your points are. Thanks.</vbg></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kristine Kathryn Rusch</title>
		<link>http://kriswrites.com/2012/08/15/the-business-rusch-a-tale-of-two-royalty-statements/comment-page-1/#comment-15701</link>
		<dc:creator>Kristine Kathryn Rusch</dc:creator>
		<pubDate>Mon, 20 Aug 2012 04:18:50 +0000</pubDate>
		<guid isPermaLink="false">http://kriswrites.com/?p=9045#comment-15701</guid>
		<description><![CDATA[Good point, Tom. And yeah, that&#039;s often (usually) true these days.]]></description>
		<content:encoded><![CDATA[<p>Good point, Tom. And yeah, that&#8217;s often (usually) true these days.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Simon</title>
		<link>http://kriswrites.com/2012/08/15/the-business-rusch-a-tale-of-two-royalty-statements/comment-page-1/#comment-15694</link>
		<dc:creator>Tom Simon</dc:creator>
		<pubDate>Mon, 20 Aug 2012 01:03:45 +0000</pubDate>
		<guid isPermaLink="false">http://kriswrites.com/?p=9045#comment-15694</guid>
		<description><![CDATA[That’s quite true. I was only pointing out that in such cases, it is the publisher and its contract, not Apple, that is to blame.]]></description>
		<content:encoded><![CDATA[<p>That’s quite true. I was only pointing out that in such cases, it is the publisher and its contract, not Apple, that is to blame.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kristine Kathryn Rusch</title>
		<link>http://kriswrites.com/2012/08/15/the-business-rusch-a-tale-of-two-royalty-statements/comment-page-1/#comment-15588</link>
		<dc:creator>Kristine Kathryn Rusch</dc:creator>
		<pubDate>Sat, 18 Aug 2012 18:57:06 +0000</pubDate>
		<guid isPermaLink="false">http://kriswrites.com/?p=9045#comment-15588</guid>
		<description><![CDATA[Thank you, Sheila. :-)]]></description>
		<content:encoded><![CDATA[<p>Thank you, Sheila. <img src='http://kriswrites.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sheila Guthrie</title>
		<link>http://kriswrites.com/2012/08/15/the-business-rusch-a-tale-of-two-royalty-statements/comment-page-1/#comment-15559</link>
		<dc:creator>Sheila Guthrie</dc:creator>
		<pubDate>Sat, 18 Aug 2012 13:03:55 +0000</pubDate>
		<guid isPermaLink="false">http://kriswrites.com/?p=9045#comment-15559</guid>
		<description><![CDATA[Another eye-opening post, Kris. Thanks for such good explanations about these contracts, I hope new and old writers are reading and taking this information in. 

As I learn more about traditional publishing I&#039;m becoming less inclined to seek out that route and more inclined to stay indie. The only benefit there seems to be in traditional contracts is the advance, no matter how small it may be, but rights grabs like you&#039;ve written about in this and other posts take away any bright spot that may have been.

When I first starting reading about how to become published--back when I was in high school, aka in the Jurassic age ;) --I would have signed bad contracts without a thought, because I didn&#039;t know there was any other way. Now, with the Internet and so much more information available, it would be foolish for anyone to just sign their rights away like this.

Keep up the good work. You and Dean are my go-to people for writing information and advice.]]></description>
		<content:encoded><![CDATA[<p>Another eye-opening post, Kris. Thanks for such good explanations about these contracts, I hope new and old writers are reading and taking this information in. </p>
<p>As I learn more about traditional publishing I&#8217;m becoming less inclined to seek out that route and more inclined to stay indie. The only benefit there seems to be in traditional contracts is the advance, no matter how small it may be, but rights grabs like you&#8217;ve written about in this and other posts take away any bright spot that may have been.</p>
<p>When I first starting reading about how to become published&#8211;back when I was in high school, aka in the Jurassic age <img src='http://kriswrites.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  &#8211;I would have signed bad contracts without a thought, because I didn&#8217;t know there was any other way. Now, with the Internet and so much more information available, it would be foolish for anyone to just sign their rights away like this.</p>
<p>Keep up the good work. You and Dean are my go-to people for writing information and advice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Don McGowan (@LegalMinimum)</title>
		<link>http://kriswrites.com/2012/08/15/the-business-rusch-a-tale-of-two-royalty-statements/comment-page-1/#comment-15529</link>
		<dc:creator>Don McGowan (@LegalMinimum)</dc:creator>
		<pubDate>Sat, 18 Aug 2012 06:34:35 +0000</pubDate>
		<guid isPermaLink="false">http://kriswrites.com/?p=9045#comment-15529</guid>
		<description><![CDATA[The comment above from C.E. Petit is very appropriate, particularly the part noting that none of the GCs have antitrust experience. I&#039;m a GC in my day job and do have some, but I don&#039;t work at a publishing company. Most GCs of public companies are securities lawyers or deal folks, and it shows.

Anywho... why I&#039;m here is to comment on what you call the basket clause. If you&#039;re looking through your own contracts, look for something called cross-collateralization, which is the technical term for this kind of thing. It&#039;s what lawyers do when they want to protect their company from a situation where one book is a runaway hit but the other ones are duds: they can avoid paying royalties on the hit until the duds are paid off. Great for the company, crap for the author, like you&#039;ve noted.

And you&#039;ve (accidentally) noted the best way not to get screwed with one of these which is to publish your books with different companies each time, but there&#039;s possibly others. Another thought is maybe to create a separate bank account for each book you write and specify payments for each book into a each account. Even more protection: put each book into an LLC and sign the publishing contract between the publisher and the LLC. That way you&#039;ll have a quick and easy breach of contract: failure to pay the money into the right bank account or to the right LLC. After all, companies are people ever since Citizens United, so they can&#039;t cross-collateralize between different people...]]></description>
		<content:encoded><![CDATA[<p>The comment above from C.E. Petit is very appropriate, particularly the part noting that none of the GCs have antitrust experience. I&#8217;m a GC in my day job and do have some, but I don&#8217;t work at a publishing company. Most GCs of public companies are securities lawyers or deal folks, and it shows.</p>
<p>Anywho&#8230; why I&#8217;m here is to comment on what you call the basket clause. If you&#8217;re looking through your own contracts, look for something called cross-collateralization, which is the technical term for this kind of thing. It&#8217;s what lawyers do when they want to protect their company from a situation where one book is a runaway hit but the other ones are duds: they can avoid paying royalties on the hit until the duds are paid off. Great for the company, crap for the author, like you&#8217;ve noted.</p>
<p>And you&#8217;ve (accidentally) noted the best way not to get screwed with one of these which is to publish your books with different companies each time, but there&#8217;s possibly others. Another thought is maybe to create a separate bank account for each book you write and specify payments for each book into a each account. Even more protection: put each book into an LLC and sign the publishing contract between the publisher and the LLC. That way you&#8217;ll have a quick and easy breach of contract: failure to pay the money into the right bank account or to the right LLC. After all, companies are people ever since Citizens United, so they can&#8217;t cross-collateralize between different people&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kristine Kathryn Rusch</title>
		<link>http://kriswrites.com/2012/08/15/the-business-rusch-a-tale-of-two-royalty-statements/comment-page-1/#comment-15521</link>
		<dc:creator>Kristine Kathryn Rusch</dc:creator>
		<pubDate>Sat, 18 Aug 2012 04:59:48 +0000</pubDate>
		<guid isPermaLink="false">http://kriswrites.com/?p=9045#comment-15521</guid>
		<description><![CDATA[I&#039;m glad to help. It&#039;s tough out there. I know a lot of writers who signed such things with their day jobs and are now regretting it. Many have asked for addendums to their employment contracts, exempting the fictional work. I also know of a few companies that said no to such addendums. Do be careful, folks, before you sign anything. Thanks for the comment.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m glad to help. It&#8217;s tough out there. I know a lot of writers who signed such things with their day jobs and are now regretting it. Many have asked for addendums to their employment contracts, exempting the fictional work. I also know of a few companies that said no to such addendums. Do be careful, folks, before you sign anything. Thanks for the comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://kriswrites.com/2012/08/15/the-business-rusch-a-tale-of-two-royalty-statements/comment-page-1/#comment-15508</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sat, 18 Aug 2012 01:55:06 +0000</pubDate>
		<guid isPermaLink="false">http://kriswrites.com/?p=9045#comment-15508</guid>
		<description><![CDATA[It&#039;s not only publishing contracts you need to read and think about.  I have a day job, in a field that normally does not have trade secrets.  However, the powers that be developed operations manual and determined that the manual and associated resources (including additional resources, such as form letters, that might be created by any of us) are intellectual property of the company that needs to be protected by a non-disclosure agreement.  Signing the agreement, we were told, is now a condition of employment.  OK, I figured--a team of people spent more than a year creating this body of work and it is hoped it will make the company more profitable; I can see why they feel it is important to require employees to protect this intellectual property.  

Then I saw the agreement itself, which had words to the effect that &lt;i&gt;... all creations, inventions, works of authorship ... created by the employee during the term of employment ... are works of hire and the property of employer...&lt;/i&gt;

What?  Wait!

All acts of authorship starting from the the first moment of the first day I was hired (months before the agreement was presented to me) to the end of the last day I&#039;m employed here are...  Um--no.  You see the problem.

Happily, my employers were aware I am a published writer of speculative fiction before they hired me, and speculative fiction is not a part of their product.  It made the conversation wherein I said I needed protection for my own intellectual property less awkward.  

This experience underscores the importance of reading contracts and imagining how they could affect things that are--or should be--unconnected to the subject matter at hand.

Thanks, Kristine--I&#039;m sure reading your column helped me make the immediate mental leap from how these words applied in my day job to how they might be applied to my creative work.]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s not only publishing contracts you need to read and think about.  I have a day job, in a field that normally does not have trade secrets.  However, the powers that be developed operations manual and determined that the manual and associated resources (including additional resources, such as form letters, that might be created by any of us) are intellectual property of the company that needs to be protected by a non-disclosure agreement.  Signing the agreement, we were told, is now a condition of employment.  OK, I figured&#8211;a team of people spent more than a year creating this body of work and it is hoped it will make the company more profitable; I can see why they feel it is important to require employees to protect this intellectual property.  </p>
<p>Then I saw the agreement itself, which had words to the effect that <i>&#8230; all creations, inventions, works of authorship &#8230; created by the employee during the term of employment &#8230; are works of hire and the property of employer&#8230;</i></p>
<p>What?  Wait!</p>
<p>All acts of authorship starting from the the first moment of the first day I was hired (months before the agreement was presented to me) to the end of the last day I&#8217;m employed here are&#8230;  Um&#8211;no.  You see the problem.</p>
<p>Happily, my employers were aware I am a published writer of speculative fiction before they hired me, and speculative fiction is not a part of their product.  It made the conversation wherein I said I needed protection for my own intellectual property less awkward.  </p>
<p>This experience underscores the importance of reading contracts and imagining how they could affect things that are&#8211;or should be&#8211;unconnected to the subject matter at hand.</p>
<p>Thanks, Kristine&#8211;I&#8217;m sure reading your column helped me make the immediate mental leap from how these words applied in my day job to how they might be applied to my creative work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kristine Kathryn Rusch</title>
		<link>http://kriswrites.com/2012/08/15/the-business-rusch-a-tale-of-two-royalty-statements/comment-page-1/#comment-15504</link>
		<dc:creator>Kristine Kathryn Rusch</dc:creator>
		<pubDate>Sat, 18 Aug 2012 01:11:04 +0000</pubDate>
		<guid isPermaLink="false">http://kriswrites.com/?p=9045#comment-15504</guid>
		<description><![CDATA[Yes, but the point of the blog is that if you sign any clause in a traditional contract that limits DRM, you may no longer be able to put up &lt;em&gt;any&lt;/em&gt; of your works without DRM.]]></description>
		<content:encoded><![CDATA[<p>Yes, but the point of the blog is that if you sign any clause in a traditional contract that limits DRM, you may no longer be able to put up <em>any</em> of your works without DRM.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
