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
I have no problems with that, my clients get the source files at the end of every project. I have no reason to be protective of my content that was developed for them. As far as IP is concerned I have a contract that indemnifies me.
What the client does with the source files after they are handed over is beyond my control and I do not worry about it. I am sure I have said above that I hope I add more value to a clients business than just delivering a course/module. I would hope that same client would want to come back to me because of this, if they do not, I don't want to make it any difficult for them to use another freelancer/developer/instructional designer.
I costs include the source files being handed over, there is no reduction if they don't want them.
I think one of the issues/problems here is that people in our industry get emotionally attached to their files or are frightened that someone will come along and steal their breakfast, the key thing to look at is what value do you bring to the table, and it is that which will keep the client coming back for more.
My 2 cents, as an Architect with 30 plus years experience.
NO, I do Not turn over my files.. EVER.
Design copyright laws are to protect designers (yes, you guys are designers), They are (as stated) part of the service, but they belong to me; just as my computer, my pencils, my sketch pads. If I want to turn them over (for a fee) they will also sign a document stating that if anything goes wrong with the files, that I am in NO way responsible. And that they hold me, my family, my business 100% harmless. They do NOT have the rights to the files.
Good read here regarding Design Copyrights
http://www.onextrapixel.com/2013/09/05/10-copyright-laws-every-graphic-designer-should-be-aware-of/Speaking as another architect, Terry is 100% correct.
This forum speaks of nice customers and respectful relationships between clients and contractors. From the past 30 years as a consultant I have found that a not insignificant number of clients are not respectful of the work done by designs.
You are a designer. Your ability to create engaging, rapid e-learning solutions is your core competency and therefore your competitive advantage. If a client insists on receiving your source files and it is not stated in the contract, they are neither respectful of your effort or your work.
A number of forum contributor's who are on the client's side have expressed the views that they have bought the services and have therefore are deserving of the source files. The notion has also been expressed that without the source files you cannot edit the work at a later date or turn the files over to another developer should the original developer not be available. There is a clear solution to this problem; hire a developer/designer to work full-time. Firms hire contract developer/designers because it avoids the financial overhead burden of a full-time employee.
If you are a contract developer/designer, make no mistake. Source files you give to a client without receiving appropriate compensation for surrendering your copyright will be given to someone who is cheaper.
Hi Phil,
Let's say you hand over all project files for storyline after effects and illustrator then the client comes back and says: "how did you get this execute javascript trigger to work" or "I can't load the color swatch illustrator?"
How would you handle that? If you would charge an hourly rate, would it be more than your standard rate?
Yes, I agree Phil. Anyone wanting to become a freelancer doesn't really need my source file to do that. They can learn most of what they need to do that right here on this site!
What they can't learn from a source file is reliability, creativity, punctuality, professionalism, etc etc etc. and these are, as Phil says, the very reasons why my clients hire me, us, time and time again.
The point about the camera is valid.
Face it, if the client is good enough at design and creation, and nefarious enough in intent to want to use your design to steal your business, they are good enough and nefarious enough to steal it by looking at your finished product.
They hired you because they can't or don't want to do this sort of thing; after all, they have a business to run.
When I was much younger, I did some opinion writing for newspapers. My biggest worry starting off was that editors would change my output and maybe make it say things I didn't say. An editor who was also a friend laughed at me. His point was that the last thing the editor wanted was more of that kind of work, any editor that has that kind of time and inclination will write the pieces himself.
That said, if it is as much work for them to get a product from you, and in the end it looks like something they would have done, then yes, they probably don't need you.
There is something to be said about being good enough to make it look easy, but in the end Phil is right. When they look at your product, they need to say "We couldn't do that," or "We couldn't do that that fast," or "We couldn't do that that well." Those are the reasons they hired you in the first place, and if you prove them correct in that original assessment, your work is safe.
Excellent discussion, and I appreciate all the points of view on this.
Maybe this is a US thing, but my clients require that I sign a non-disclosure agreement. Within that agreement it states, clearly, that work product belongs to the client. I've never had a problem with that.
Lots of interesting ideas and perspectives here, which are essential to this community! Thanks so much to all participants for sharing your opinions. :)
I think in the end I agree with Phil. I think what he is not saying is that this is a competitive market, and if you wont share your source file, others will, and yes, maybe do the work cheaper. I think a company chooses the developer for their skill and expertise, and that is not something that can be replicated by someone else.
Just a thought to ponder on.... when you bought your copy of Storyline, did you expect Articulate to send you a copy of the source files with it? I would suggest that a client might want the source files, but the value in them is far higher than the content output. Storyline can be used to create some fantastic content. Are you happy to let your competitors receive your hard grafted JavaScript as a gift from your client? Of course, if you don't mind, please feel free to attach your best *.story files to this discussion forum :-)
The customer dictates the terms of the contract. These types of issues should have been worked out prior to acceptance. For my part, I would hand everything over to the customer, and if they need help making things work, or understanding javascript, then I would offer them that assistance in good faith. I think the only time that becomes an issue is in cases where it had been worked out beforehand that the customer did not get the rights to the source file, then maybe you could charge them an additional fee for that.
I do offer training :-)
Honestly depends on the client and the the nature of the relationship, something simple would be free anything else would likely be chargeable. There is always an opportunity to build goodwill. Agree with David sorting this out before starting work helps with any confusion.
