Contract Management: Difference between revisions
Jump to navigation
Jump to search
m
→Failing an Under Collateral Contract
Xye Zaloris (talk | contribs) |
|||
| (8 intermediate revisions by 3 users not shown) | |||
| Line 6: | Line 6: | ||
#Standard contracts with less than 12 hours remaining | #Standard contracts with less than 12 hours remaining | ||
#Rush contracts | #Rush contracts | ||
# | # #1 Contract | ||
== Route Planning == | == Route Planning == | ||
# Choose the highest priority contract | # Choose the highest priority contract - this is the #1 contract in the queue, unless exceptions apply. | ||
# Find contracts that can be picked up and delivered on route to the pick up station | # Find contracts that can be picked up and delivered on route to the pick up station | ||
# Find contracts that can be picked up and delivered on route to the destination station | # Find contracts that can be picked up and delivered on route to the destination station | ||
| 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. | ||
* | * Pushers may use additional haulers to run additional freight on the same route; however, they should only accept as many contracts as can be run in a single trip. | ||
* This is accounting for volume and value limits. Pushers must always ensure when taking multiple contracts in a single ship that value limits are observed for each type of freight class. | * This is accounting for volume and value limits. Pushers must always ensure when taking multiple contracts in a single ship that value limits are observed for each type of freight class. | ||
*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 or 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 == | ||
| Line 62: | Line 67: | ||
*If a contract has a very high value of contents it could attract gankers so it needs to be checked before it is hauled. | *If a contract has a very high value of contents it could attract gankers so it needs to be checked before it is hauled. | ||
*If the collateral is high but the value is low that could indicate a gank contract. | *If the collateral is high but the value is extremely low (e.g. only empty containers or junk worth very little) that could indicate a gank contract. | ||
*To check a contract after accepting, find the contract in your Personal Assets window->Right click, View Contents->Ctrl+A, Ctrl+C->Paste the contents into https:// | *To check a contract after accepting, find the contract in your Personal Assets window->Right click, View Contents->Ctrl+A, Ctrl+C->Paste the contents into https://janice.e-351.com/. | ||
*A guide on appraising contracts can be found in the Corp Bulletins. | *A guide on appraising contracts can be found in the Corp Bulletins. | ||
| Line 131: | Line 136: | ||
=== Failing an Under Collateral Contract === | === Failing an Under Collateral Contract === | ||
#Fail the contract in-game. | |||
#Open the correct mail template in dropdown menu found on the incorrect contract in PIR. | #Open the correct mail template in dropdown menu found on the incorrect contract in PIR. | ||
#Fill in the mail template. | #Fill in the mail template. | ||
| Line 136: | Line 142: | ||
#Link the item exchange contract in the indicated place in the mail | #Link the item exchange contract in the indicated place in the mail | ||
#Send the mail and fail the incorrect courier contract. | #Send the mail and fail the incorrect courier contract. | ||
#Report your failed contract in Discord in #internal by typing /fail and filling in the contract ID# and Janice link. | |||
In some cases, such as a brand new Rush contract, it may be appropriate to also send the client a conversation request notify them of the situation. | In some cases, such as a brand new Rush contract, it may be appropriate to also send the client a conversation request notify them of the situation. | ||