In some E&P organizations, the amount of data required to image the subsurface has now risen to several terabytes per survey, especially when multiple azimuths are considered. For the processing of converted-wave data, this amount of data rises even further, by twofold or threefold, depending on the components of particle velocity under consideration. The processing time also increases severalfold. In other words, petroleum seismologists are close to reaching a brick wall, if we have not already done so, in regard to the amount of data that we can realistically collect and properly process. In my recent book on coding and decoding, I introduced the concept of multishooting to address the problem. The idea is that seismic waves can be generated from several locations simultaneously (or nearly simultaneously, by introducing small time delays between the shooting points) instead of one single-source location at a time, as is currently the case. Significant savings in time and money in acquiring, processing, and even storing seismic data can be achieved by using this concept. However, the implementation of this concept in actual data acquisition and data processing may take some time, as a number of the solutions associated with multishooting acquisition and with the processing of multishot data require significant modifications of our current practices. In this series of papers, we propose some ideas which may be less effective than the multishooting concept, but can readily be implemented without significant new developments in acquisition or processing. In this first paper, we consider data collected in the standard form (i.e., from one single-source location at a time). We propose to group these data as if they were acquired with the multishooting technique and process them as multishot data. By doing so, we reduce the size of our data and processing time.