In part two of his look at telecommuting (here's part one) Chris Hartjes talks about accountability and how you can show your managers your progress in your development.

Telecommuting is not for misanthropes who dream of long stretches of uninterrupted work. You *will* be asked to prove that you're working, not sitting on the couch playing video games when you're supposed to be debugging that new Ajax-powered user interface. Just pushing your code into production isn't enough.

He recommends a ticketing system the managers could check in on whenever they'd want an update (as well as keeping it open to the customers so they can see the progress of their projects too).