Bureaucrats, push, push-admin, push-director, push-manager, push-senior, Administrators
338
edits
Contract Management: Difference between revisions
Jump to navigation
Jump to search
→Pusher Contract Etiquette
Xye Zaloris (talk | contribs) |
Xye Zaloris (talk | contribs) |
||
| Line 17: | Line 17: | ||
==Pusher Contract Etiquette== | ==Pusher Contract Etiquette== | ||
Contracts should be prioritized from oldest to newest as much as possible: | '''Contracts should be prioritized from oldest to newest as much as possible:''' | ||
* Pushers are expected to start with the highest priority contract. This will nearly always be the top contract in the queue. | * Pushers are expected to start with the highest priority contract. This will nearly always be the top contract in the queue. | ||
* Pushers are encouraged to use the internal tools to find contracts that help make routes more efficient while following contract priority. An example of this would be to pick up a newer contract that brings you at or near the top priority contract. | * Pushers are encouraged to use the internal tools to find contracts that help make routes more efficient while following contract priority. An example of this would be to pick up a newer contract that brings you at or near the top priority contract. | ||
* Contracts to and from Thera are generally an exception to this rule, and may be completed at any time a desirable entrance is available. | * Contracts to and from Thera are generally an exception to this rule, and may be completed at any time a desirable entrance is available. | ||
Pushers should not accept more contracts at once than the Pusher can run on a single trip, either for Standard or JF freight: | '''Pushers should not accept more contracts at once than the Pusher can run on a single trip, either for Standard or JF freight:''' | ||
*This is common courtesy to other pushers and customers so contracts can be accepted and completed as quickly as possible. | *This is common courtesy to other pushers and customers so contracts can be accepted and completed as quickly as possible. | ||
* If you have one hauler, only accept one contract on a route or one round-trip series of contracts. If you have 3 haulers, you can accept three contracts on the same route or round-trip. | * If you have one hauler, only accept one contract on a route or one round-trip series of contracts. If you have 3 haulers, you can accept three contracts on the same route or round-trip. | ||
| Line 28: | Line 28: | ||
*If you are making a round trip accepting your return contract at the same time is acceptable | *If you are making a round trip accepting your return contract at the same time is acceptable | ||
'''Pushers should not accept freight they do not expect to be able to complete without significant delays.''' | |||
If an unexpected delay occurs that significantly impacts the delivery time of a contract (e.g. a delay of multiple hours such as overnight): | |||
#The Pusher should notify the Senior team. This can be done by pinging @Seniors in #internal on the PushX Discord explaining the delay and when you intend to complete the contract. | |||
#The Senior will add a note to the contract in PIR. | |||
#The Pusher should send the client the "Contract Delay" mail found in the PIR mail templates. | |||
== All Contracts Must Be Opened Via PIR == | == All Contracts Must Be Opened Via PIR == | ||