There is no standard of which I am aware. I think this would vary greatly. How much time was spent with the users when developing the requirements for each form? How well-documented are the requirements? If the specs are not well-documented, they could end-up saying "That's not what we said" and that will probably not be pleasant. I would suggest documenting the requirements clearly for both your sake and theirs. If the requirements/specs are well-documented, you just have to quote an hourly rate for changes to the specs as defined.

900 hours. Wow. I mean, I've probably worked over 5000 hours on our system, but this is a salaried position. I'd hate to have to try to estimate a project that large.

Take care,
Joe

>Is there an industry standard for the percentage of time I should allow for redevelopment of an application based on the development time?
>
>For example I am putting in 900 hours of development time creating forms and screens. What percentage of the 900 hours should I build in to allow for user feedback on how this forms and reports should be changed?