Forum Discussion
Client wants .story (unpublished files) - do they need this?
I'm new to this and have a question about what my client needs. They say that they need the .story file for their LMS. I thought that the published version is all that a client would need. Am I missing something? I want to give them what they need, but also want to protect my work so that they can't just use my files as templates. Need answer asap!
39 Replies
As a client, I always appreciated the source files. Sometimes it was just in case we had to make minor edits (such as that pesky typo no one else caught). Yes we could use the source files as templates, but if we had enough time and resources to do that in the first place, we wouldn't have contracted out.
However, if a contractor gets stingy about sharing the source files with me....the client who paid for them...I get a bad taste, and most likely will not use them again.
So, if I were in your situation (and not knowing all the details), I would use this as an opportunity to try to dig deeper and see if there are any other services you can offer. And going forward make sure you clearly spell this out in your contract.
BUT....If they had been the client from HELL (and we all know they exist)....that's different.
This discussion has only recently been revived.
Tricia, in light of your comment about "stingy" contractors and "the client who paid for them", does it say in your contract with a contractor that you, the client, own the source files? If it is not stated in the contract, why do you believe that the client has the right to the source files by default? But the fact is that if surrendering source files is not included in the contract, you are asking for something and expecting not to pay for it.
- +1. We used to tell our internal customers and Sourcing group to ALWAYS build this into contracts.
Nancy Woinoski said:
I also give the source files to my clients. As Harri says, they paid for the work. It is in the best interest of the client to get the files whether they have Storyline or not because it protects them down the road should something happen to the original developer.
YMMV, but ethically I believe this is an essential right for the client.
When you buy a painting or a book, do you buy the right to reproduce it? No. Basically, you have purchased a license to use the physical object. The copyright is still held by the artist or author. Even though a building owner may purchase the services of an architect and receive a copy of the design drawings for the purpose of maintaining the building, the owner does not have the right to sell those drawings to another owner to reproduce the same building. It is NOT an essential right of the client to own the materials created during intermediate steps towards a finished outcome. It is a business decision that you are making to surrender copyright to keep a client happy.
I disagree with those who say hand over the source files. The question is whether the contract that you signed with the client is for a service or a product. In my opinion, the .story files are similar to an "instrument of service". They are the subdeliverable of a necessary step along the way. As an example, what would preventive the client from also asking for the font files that you used, the sketchbook in which you formulate your ideas, or all of the images that you used to create the presentation. The client has not purchased the source files, they have purchased your services.
Your competitive advantage is your ability to efficiently and effectively build presentations from the resources you have built and acquired. Don't give your core competency away. If the client demands the source files, they should pay a fee for your surrender of copyright.,
There are IP implications of handing over source files eg if you use stock photography it is in their End User Licence Agreenent that you can't give the client access to these photos in a format that is easily extracted such as .story file. Let your client know upfront that you don't own all components of the module and therefore cannot hand over.
Thanks for popping in to share your thoughts as well Shiraz :)
It's a very useful discussion that keeps me up at night!!!
I think if a client wants the source file, then you should give it to them in good faith unless it is specifically written into your contract that you should not do so. There are many reasons they may wish to have the source file, not the least of which is if they want to update/modify the content later if things change. This is perfectly reasonable, in my opinion, and again in my view, a client paid you in good faith for a product that should include the source file and the published output.
We hand over source files to the client too.
Maybe it depends on whether they've engaged you for a service (to design) or for a product (the final output whether it's published or source file). I'm more concerned about breaching a licence agreement with elearning assets then having the client update the module themselves. I rather they update it themselves to be honest.
I have a stipulation in my terms and conditions that I provide a published product as well as the source file. I think it's fair enough for the client to be able to maintain and update the course.
That said, Shiraz makes an excellent, and often overlooked, point re: licensed assets in your course. Even if the client ends up never even opening up the source file, there is a risk there that I might breach a licence agreement.
Very useful discussion, and I am now going to review my terms and conditions to include something around what the client can, and cannot, do with the source file (for example, can update content, can republish, cannot use the images, audio, video anywhere else or in a template, etc.)
The other thing to consider is this: how comfortable are you with your client handing your source files over to another freelancer to modify, duplicate, repurpose and sell etc? How comfortable are you with the potential for your client to take your source files, learn your methods (e.g. how do you get the interaction to behave in a certain way) and establish their own freelance business? Don't underestimate the skills you have in using the software and the value this creates. Anyone can buy a camera but it doesnt make them a photographer, same with Storyline. If your client wants source files, i don't think it's a hard and fast rule that they can or can't, but should definitely be charged more. In graphic design land the standard is 300% more for source files.
