@sestrahelena wrote:
I knew you'd know!
@sestrahelena wrote:
You could only speak from your own experiences, which you stated, so that can't be wrong. It would be interesting to see if others have different info for other MSCs.
@luckygirl0100 wrote:
Sorry... should have included I was typing in sarcasm font, lol.
@joanna81 wrote:
Speaking from someone in tech and not at an MSC.
Could they track when apps are submitted, withdrawn, and how long they sat pending? yes all of that could be tracked. And it could be tracked by project, location, users, etc.
Whether the MSC cares to do any reporting or monitor those stats would be up to the company, but it is most definitely possible from a technology standpoint to have those datapoints.
At my company, similar stats are reported for cycle times on how long it takes to create a job, post it, gather responses, assign and finish the job are all things you can build a report on.
@sestrahelena wrote:
That makes sense. It would be a handy tool for MSCs to weed out schedulers who under-perform, as they do by deactivating shoppers who continuously fail or submit sub-par reports. My suspicion is that most don't use it. As some threads here have indicated, there are a few schedulers that are often problematic but have stayed in the industry for a very long time.
@shoppinalongtheriver wrote:
I know of at least one MSC who tracks shops that are assigned, then cancelled. Their schedulers take it into account when assigning shops. They don't typically let shop requests linger though.