Different researchers have proposed techniques and models for eliciting requirements, and most described process and recommendations to capture them, but there are few details on how to document with this step.Although the community has widely recognized the importance of engineering requirements, and elicitation of an important stage of this phase of software engineering, there have been few studies to guide engineers to document this elicitation.The importance of proper documentation of this step is that it allows a better understanding of customer and the user needs, and helps engineers to best perceive the problem, and model a solution that adequately reflected in the Specification.In this work are presented the results of a literature review, aimed at discovering, analyzing and comparing the proposals to document the elicitation of requirements.73 works were consulted in the databases, of which 18 formed the final sample.The conclusion is that more work is missing on what to do with this documentation, because none of the studies analyzed directly and completely describes a proposal to do so.