3 ms·
Good question. I'm new at it as well. My policy, which I am admittedly experimenting with, is to count a 4+ hour day as one day. I also add up partials and coun
by 1123581321 14y ago
Good question. I'm new at it as well. My policy, which I am admittedly experimenting with, is to count a 4+ hour day as one day. I also add up partials and count them as a day when they hit four hours. So:
Monday: 2 hours.
Tuesday: 15 minutes.
Wednesday: 9 hours.
Thursday: 5 hours.
Friday: 3 hours.
adds up to three days plus 1.25 hours accruing. It still has issues like: should this be explained to a client because it's confusing? What do I do about accruals that never reach four? Does it encourage me to work close to four hours per day, which is not the point of it?
Another method I've thought of, which I read on some company's blog, is to assign people to ongoing projects who bill daily, and to also have a sweeper who bills hourly on questions, emergencies and miscellany. I'm not sure if clients would accept such a person's hourly exceeding the daily rate without setting that expectation upfront.
It's hard to fit because the daily method is best for a developer who works to a spec, turns the site over to someone else when done, and always leaves gaps between projects to avoid any overlap due to deployment issues and other problems like that.
And meanwhile, some freelancers I know are saying that weekly is all the rage...
- dylanhassinger 14y agothe 4+hour model is awesome. thanks for sharing