文案与商业写作2019plainfreelancecontract.com
Show HN：用平实语言写成的众包自由职业合同模板
Show HN: Crowdsourced freelance contract template, written in plain language
导读
这是一个众包的自由职业合同模板项目，用大白话写成，公开放在 Google Doc 上。HN 上几位有法律背景的评论者指出它缺了独立承包人条款、费用预审批、双向赔偿、可转让限制等关键内容，还提醒各州/各国法律差异和术语未定义会带来风险。对写作者的价值在于：它是一份关于「通俗语言与精确性如何取舍」的现场案例——哪里可以简化，哪里必须定义清楚。
可以直接用的写作要点
- 01
用大白话降低阅读门槛是加分项，但省掉「独立承包人」「费用预审批」「可转让」这类边界条款，等于把风险留给读者；写说明性文本前先问：哪些边界不能省。
- 02
关键名词必须定义：「知识产权」这类词看似通用，含义却随语境变化，一旦起争议，措辞就决定一切——凡是靠读者猜的名词，都是未来的歧义源。
- 03
专业文本之所以长，往往是因为每个条款都在覆盖一种情形；「两句话的保密条款」听着简洁，但简洁不等于删掉必要细节。
- 04
合同谈判是合作的预演：模板里抄错的辖区名、对方答问的方式，都会提前暴露后续沟通的质地——文本细节是最早的信用凭证。
HN 评论精选
通俗模板对有法务的客户无效，还漏掉独立承包人、费用预审批、双向赔偿、可转让限制等关键条款。
这个点子我见过几次，最大的问题是：它也许适合小客户和临时项目，但任何有法务团队的客户要么直接拒掉，要么改得满篇法律术语，那样这份合同就帮不了你什么，因为你照样得请律师审。我们公司的一审合同基本是我做的（最终几乎都会送审，偶尔运气好能直接签），我遇到过、这份合同很可能也会踩的坑：没有确立独立承包人关系；费用支出没有预审批要求；赔偿条款不是双向的；按现在的写法合同可以转让，也就是说你签完可以立刻把它卖给第三方。普通合同里的保密条款要写一整页而不是两句话，大概也是有原因的，虽然我说不清是什么。不过我很喜欢它就是一份 Google Doc。
tptacek查看英文原文
I've seen this idea done a couple of times and it seems like the major problem with it is that while it probably works for small clients and impromptu projects, any client with a legal team is going to either reject it, or redline in so much legalese that the contract doesn't win you anything because you'll need legal review anyways. I do most of our first-round contract review (we almost always end up getting things reviewed but once in awhile you get lucky and can accept a contract without it) and snags I've hit that this contract seems likely to hit: * Doesn't establish independent contractor relationship * Asks for no pre-approval on expenses * Non-mutual indemnification * The contract as written is assignable, so you can sign it and immediately sell the contract to someone else There's probably a reason why Confidentiality agreements in normal contracts are a page long rather than just two sentences, too, but I don't know what that is. I love that it's just a Google Doc though.
辖区差异和未定义术语会让通俗模板在争议中失效，法律工作本质上是定制的。
这类东西我见过不少，理念我很喜欢，但通常问题一大堆。就像 tptacek 说的，这份文件遇到成熟的对手方根本撑不过第一轮，任何合格律师大概都会把它批得体无完肤。首先它完全没考虑使用者选择的法律辖区：填英格兰和填苏格兰，合同含义就不一样，美国各州同理。外行不知道这一点，而律师必须逐条审。文件里还有大量笼统表述，比如「知识产权」没有定义——这些不是通用词，一旦起争议，措辞就决定一切。专业合同之所以长得多，是有原因的。我不是在攻击这个想法，我极度支持法律文件开放获取，但大家得意识到法律工作大多是量身定制的——哪怕律所是批量流水作业。这是推动法律开放的一次很好的努力，但让人依赖它是危险的。来源：我是软件工程师，也是持证律师。
ruairidhwm查看英文原文
I've seen quite a few of these and whilst I love the idea, they usually have a ton of problems in them. As tptacek pointed out - there is no chance that this document would survive first contact with a sophisticated party and any qualified lawyer would likely rip this to shreds. Firstly there is no regard to the potential jurisdiction that the user chooses. If I were to put in England then that would mean there are different contractual implications to choosing Scotland. Ditto for states in the USA. A layperson won't know this, and a lawyer would need to review the provisions. There are also a ton of generalised terms in this document where things like 'intellectual property rights' aren't defined. These aren't generic terms and in the event of a dispute, language really matters. There is a reason why contracts are much longer when professionally written. This isn't to attack the idea, I'm hugely in favour of open access to legal documentation, but people need to realise that most legal work is bespoke - even if law firms do it on a 'churn' basis. This is a great effort to further open law but it's dangerous for people to rely on this. Source: I'm a software engineer and a qualified lawyer
模板里的错误会暴露专业度；合同谈判的细节往往是后续合作方式的预兆。
这份东西对双方都缺很多保护。讲个有意思的故事：我有一份常用的标准合同，对双方公平，经过多位律师审过。有次合作的律所坚持要用他们自己的版本。我一看就发现是抄的模板，漏洞一堆，我提出质疑。他们说其他承包人都用得好好的，我回答：那些人肯定没读过合同。然后我指出，合同里写的辖区「Orange County Georgia」根本不存在（显然是从加州模板抄来的），还有其他问题。我最后还是违背自己的判断，改写了他们的合同并用它。结果那是个极其难缠、基本沟通都做不好的客户——比如书面提问从不肯用是或否直接回答。合同谈判往往是后续合作状况的预兆。
lgleason查看英文原文
This is definitely missing a lot of protections for both sides. An interesting story. I have a standard contract I usually use with startups etc. that is written to be fair to both parties and vetted by multiple attorneys. One that I worked with insisted that I use theirs. When I went through it, it was clear that they took it from a template and there were numerous holes in it that I pushed back on. They stated that all of their other contractors used it successfully and I replied that these people must not have read the contract. It was at that point that I pointed out that the jurisdiction, "Orange County Georgia" does not exist (they had obviously copied it from a California template or contract) among other things. Against my better judgement I re-wrote their contract and used it. They ended up being a major pain in the ass client that was really bad at basic communication. IE: would not answer direct questions in writing with yes or no answers. Contract negotiations are often a sign of things to come with the rest of the engagement.
已有其他开源通俗合同可参考，值得在条款和标准化上协作推进。
还没来得及细看，但我会看，我强烈支持这个努力！其实我早前就写并发布过一份自己的通俗语言承包协议 Fairshake，还发布过 Switchmode——一份面向做开源与闭源混合项目的软件开发者的独立承包协议。我很乐意在条款乃至标准化上合作。关于如何启动标准商业条款，我最新最好的成果是 Canting Tribe NDA，一份自带推销功能的不披露协议。
kemitchell查看英文原文
Haven't had a chance to review yet, but I will, and I strongly support this effort! In fact, I wrote and published a plain-language contractor agreement of my own, Fairshake, some time ago. https://commonform.org/kemitchell/fairshake/current I've also published Switchmode, an independent contractor agreement for software developers doing mixes of open source and closed source projects for their clients: https://github.com/switchmode/switchmode I'd love to collaborate on terms, and potentially on standardization. For my latest and best on how to bootstrap standard commercial terms, have a look at the Canting Tribe NDA, a self-marketing nondisclosure agreement: https://nda.cantingtribe.com
同类还值得读
好文笔是一种商业优势
Good writing is a business advantage
这是广告人 George Tannenbaum 的一篇博客短文，主张清晰的写作在商业中是实打实的竞争优势——能把事情说明白的人，在会议、邮件、提案里就已经赢了一半。
文案与商业写作2020 · 449 分 · 198 评4 条写作要点编辑精选如何为落地页撰写文案
Writing copy for landing pages
这是 Stripe Atlas 关于落地页文案的写作指南，核心是把文案当成回答读者疑问的工具，而不是自我表达。
文案与商业写作2018 · 416 分 · 84 评4 条写作要点编辑精选我曾是扎克伯格的演讲稿撰写人
I was Zuckerberg’s speechwriter
这篇是第一人称回忆：作者曾为扎克伯格写演讲稿，借此复盘在剑桥分析丑闻前后，科技巨头的公开表达如何被构思、修饰和交付。
文案与商业写作2018 · 347 分 · 254 评4 条写作要点编辑精选一句话产品描述写作的艺术
The Art of Writing One-Sentence Product Descriptions
这篇文章讨论如何为产品写一句话描述，核心是把复杂产品压缩成一个能打动人的句子。
文案与商业写作2017 · 335 分 · 57 评4 条写作要点编辑精选Ask HN：为技术岗位写求职信
Ask HN: Writing cover letters for tech jobs
这篇 HN 讨论科技岗位是否需要写求职信、写给谁看、用什么语气和格式。
文案与商业写作2017 · 265 分 · 123 评4 条写作要点编辑精选