Case Study Guidelines

Guide to Successful Case Study Submission

Publishing a case study on ITStartPage is free and a great way to illustrate in concrete terms the value that your product or service is delivering in the real world. We welcome informative case studies, but we review all case studies before publishing them and failure to follow these guidelines will result in your case study being rejected. Repeated abuse of the guidelines may result in all of your future submissions being ignored.

Here are the terms for publication:
  • You must be authorized to grant us permission to publish the case study. In general, this means that you own the copyright on the case study and the companies described and individuals quoted (if any) have approved the case study. By submitting a case study to us you are granting us permission to publish it and verifying that all of the necessary approvals have been received.

  • The case study must be about the use of an information technology product or service. Merely being something that was used by someone in the information technology field, but can just as easily be used anyone else, is not sufficient. For example, we will not publish a case study about health food eaten by a computer programmer.

  • We prefer exclusive publishing rights to the case study, but we do not require exclusivity. The only stipulation is that, obviously, you cannot have already granted anyone else exclusive publishing rights, nor can you grant exclusive rights to anyone else in the future.

  • The case study must be truthful in every respect.

  • Avoid superlatives when describing your product unless it is a direct quote from your customer's representative and that individual has authorized the quote.

  • We generally don't accept case studies that exceed 2,500 words. We might make exceptions for exceptional content, but those exceptions will be rare. Remember, conciseness is a virtue.

  • For bandwidth and, therefore financial, reasons we prefer text-only case studies, but if a diagram, such as a schematic, will help the reader to understand the case study we may consider including it. Embed the diagram in your case study file when you submit it.

  • We will reformat your case study to conform to a common look and feel for all case studies published on ITStartPage. (Because of this, you must submit your case study in a file that does not include security that will prevent cutting and pasting of its content.)

  • We will not edit the words in your case study. You are solely responsible for its contents. If it contains spelling, grammar or sentence structure errors, we will publish them as is. However, if a case study is written too sloppily we will reject it.

  • The case study should start with a very brief title and a brief subtitle. Both are required. If you don't provide them, we will create them, in which case the choice of the title and subtitle content will be ours. If you provide them, avoid too much hype.

  • The decision as to whether a case study is published on ITStartPage is solely ours (i.e., Klebanoff Associates, Inc., the owner of ITStartPage.) We may reject a case study for any reason, at our discretion.




AddThis Social Bookmark Button
Google

A listing on this site does not imply an endorsement by ITStartPage.com or its owner, Klebanoff Associates, Inc.
Descriptions are provided by individuals claiming to represent the owners of the related site or page.

feedback | privacy policy

© Klebanoff Associates, Inc. 2006 - 2008