>For one of my client, I am presently working on a project where no specification is done. This is my first experience in this type of project.
>
>In the middle of the development, this has caused major reconstruction of several modules, discussion of several points we have discussed before, redesign of the same icons several times, several developers working on about the same thing and the list is long.
>
>I'm used to work with specifications as most of us are. When there is no specification coming from the client and when this is for a fix cost, I insist to receive specification or I do it and the client is charged for. However, in this case, it's on site and the consultants are paid by the hour and the client doesn't care about specification. So, if it takes 200 hours for something, the consultants are paid for 200 hours. Yes, it's true deadlines are blown away. There is no project management.
>
>I was wondering what kind of approach anyone of you who faced this situation before have taken.


You have to create the specifications, module-by-module, with reasonable timelines and have the client sign off on them. Bill them for the time to create the specs and ensure that the client understands that your need to spec out the project impacts the delivery date and cost.