Anything that you and the client agree is billable, is.
>From the POV of a client:
I would be agreeable to a contractor billing a
reasonable amount of learning curve time for an
application that I had previously paid that contractor
to research for me knowing that he/she had no
expertise in it. If the contractor had previously
presented him/herself as having expertise in the
application, then no.
If I told a contractor that his/her presence at an
on-site meeting was required, then billing travel
(time or mileage, not both) would be acceptable.
If the contractor chose to be present because it
facilitated the work being done but I did not require
it, then no.
Gene Kim-Eng
----- Original Message -----
From: "Tracey Bean" <traceybean -at- verizon -dot- net>
> What I'm unsure about:
>
> 1. Time spent learning Flare
> 2. Time spent learning CSS well enough to work with Flare
> 3. Time spent traveling to on-site meetings (over an hour each way;
> hasn't happened yet, but we've talked about the possibility)
>
> Is there a standard approach to travel time?
ComponentOne Doc-To-Help gives you everything you need to author and
publish quality Help, Web, and print content. Perfect for technical
authors, developers, and policy writers. Download a FREE trial. http://www.componentone.com/DocToHelp/
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
