Earlier quoted context omitted.
The weird thing with consulting (in my experience) is that a customer almost never knows how capable they are of effectively using a consultant's time and output. "Okay, we signed a one month consulting engagement, starting Tuesday." Consultant(s) show up on Tuesday, no db's or credentials have been set up, everyone seems surprised they're there. It consistently amazed me how much consultant time companies waste. Whe…
Why do you think this happens?
1) The decision to hire a consultant is (in most orgs) made at a level abstracted from day to day operations. So the person hiring you may simply not know what needs to be done.
2) The consultant's patron didn't take the time to get buy-in from all necessary stakeholders. This happens a lot at the VP level. You may have absolute commitment from your project's VP, but when you need resources from another part of the organization this turns into "what's that person's VP's relationship with my VP." Which may be great, or may be terrible. Navigating office politics to aid a project's success is 10-25% of being a successful consultant (result wise).
3) Inconvenience to ongoing work. I know if someone failed to loop me in and introduced a stranger to me on Tuesday, then asked me to do something that impacted my ability to do the work I already had scheduled, I wouldn't be overly happy.
4) Poor IAM (identity and access management) discipline and IT organizational structure. Consultant access and timelines are normally very different than new hires / "business as usual". The client may not be able (technically, process wise) to successfully complete an ad hoc request on an accelerated timescale.