>This agency has always preferred to work on a flat rate basis, and I end up giving them as many things as are possible on a prioritized task list. Anything I don't complete is either added later as an extra feature, or is dropped until sometime in the future (unless forgotten).
>

I'm allergic to flar rate, primarily because most of my clients suffer from creeping featuritis, and there's always something that "y'know, it'd be neat if we could inspect the glomerfritz clause of the co-authors' royalty contract from here by clicking the heels of their shoes together while chanting 'There is no Sanity Clause, the Ether bunny told me so!'"

Of course, they really don't know what'd be involved, and are horrified when I send their manager a proposal to add the feature. "oh, you misunderstood - it's not really that important..." If I don't establish a rate, timetable and milestones, I end up bleeding away time that's tough to recover.

>This has always worked quite well in the past, and they and I were both satisfied with the results. However, I am now working with a new project leader, and am quickly noticing a difference in how they work with me.
>
>I have made them aware that delays and changes in the process may result in my delivering less work to them. And, I suggested that they might want to make sure they're all on the same track, before having me change something after I've already completed it. So, I've put the brakes on further progress on my part, for the moment.
>

A document explaining the details of deliverables and measurable goals is needed before you start working. Once established, everyone needs to be aware of and agree to changes in the understanding. Not doing this seemingly always results in someone feeling screwed over.

Stopping and getting your bearings, and setting up this document seems to be a must at this point.

>I have Whil Hentzen's Developer's Guide, and it is very good. However, the structure of the specs I have is not completely specific. They know what they want the program to do, and leave it up to me to come up with the best way of delivering it. Again, this has worked quite well in the past. However, I know that using hindsight too much can get you where it hurts.
>

I wouldn't do this, but I don't like standing outside in a puddle with the wind blowing in shorts and tee shirt in the dead of winter, either. You're inviting them to revise the requirements at the last minute...