Routes: who it goes through
The hops between your consultant and the client, and why each one is recorded.
Work rarely goes straight from your desk to the company that decides. It passes through a vendor, sometimes a prime above them, sometimes an implementation partner above that. The route is that path, recorded.
Why it matters on a Tuesday morning
- Who you are waiting on is the company at the hop it is sitting at — not simply “the vendor”.
- Lateness is judged against that company's own answering time.
- A blacklisted company blocks the route it is on, and says so at the moment somebody tries to use it rather than failing quietly later.
Duplicates are caught on the route
The same consultant reaching one client through two vendors is the mistake that costs a relationship. Because the route records where work actually went, a second attempt down a different path can be spotted rather than discovered by the client.
A consultant sees the vendor and the client on their submission only once it has really been sent — never while it is still being assembled.
Frequently asked
What if I do not know the full chain?
Record what you know. A route with one hop is honest; a guessed prime becomes a fact nobody questions later.
Does the client ever see the route?
No. It is your record of how the work travelled.
Can two routes reach the same client?
Yes, and that is exactly what the route lets you notice before somebody submits down both.
Was this helpful?
More in Vendors & clients
Still stuck? Tell us what you are trying to do — a person answers, and we would rather fix the product than explain it twice.