Our goal is to allow you to post loads and post trucks to make it easier than
other sites do for others to find them...and you!
other sites do for others to find them...and you!
DaisyChainHelp
BASICS
The Daisy Chain of Reloads™ is intended to help you to reduce or eliminate deadhead miles by providing a
horizontal "tree"-type list of database entries. You see the Daisy Chain of Reloads™ for a particular entry
by clicking on the "Reloads" button to the right of that entry on the load-list page. This information will
help enable you to arrange to pick up loads in or nearby cities to which you are already traveling or plan
to travel. Alternate possible reloads in or near each destination city is displayed as well as successive
loads in or near their destination cities.
The display is not complicated. Indentation and coloring are the keys to understanding it. Here's what you
you need to know:
* A "Reload" is the first and closest load found originating either in the destination city of the load
listed above it or within your chosen (or default: 100) radius miles from that city, if there is no load
found in that destination city.
* A "Reload" is always the first load of the next higher number found immediately after another load. It
will be indented three spaces to the right and have a different background color.
* "Alternate Reloads" are all other loads with the same number as a Reload, the same background color as
that Reload and with the same amount of indentation. Alternate Reloads are choices you can make for you
to reload your truck INSTEAD of the first "Reload".
* Therefore, if two or more entries are indented the same amount to the right of an entry above and with
the same background color, the first will be labeled "Reload x" and the rest labeled "Alternate Reload x"
and they are ALL optional reloads of the first entry above them that is indented less than they are and
that has a different background color.
* When an entry is indented LESS than the previous entry, then you know that there was no load found
originating in that previous entry's destination city or within radius miles of it and that the "branch"
of which that previous is a part has ended (or it is the highest-numbered reload allowed by the Daisy
Chain Settings form). There may be an alternate reload to that final entry of the branch farther down
that begins another sub-branch.
* The colors for the maximum 4 reload "levels" are as follows:
1) Coral/pink
2) Sage/green
3) Lavendar
4) Sky Blue
DAISY CHAIN EXAMPLE
Below is a purely fictitious daisy chain for example purposes only. The mileage listed is not accurate or
meant to be.
You select a load originating in Denver, CO, and going to Miami, FL, by clicking the "Reloads" button to
the right of the entry on the List/Manage Loads page. This will be the first load diplayed and it will be
with a black background. There is one load found originating in Miami. However, theLoadPost.com found two
other loads within the default "radius" of 100 miles from Miami and will list them when the "branch"
starting with the Miami load reaches its end.
The second "Alternate Reload 1" in the display below, originats in Palm Beach, FL, 64 miles from Miami.
This load is included in the chain and any loads originating from ITS destination city or nearby and their
are destination cities onward are also included. When you look at the example display below, please note
that the 64 miles is shown beside the city and state.
The Miami load is going to Columbus, OH. It is displayed under the Denver load entry, labeled "Reload 1"
and indented some, meaning that it is a reload from the Denver trip. There is one load found originating
in or nearby Columbus (in, actually). It is going to Chicago, is displayed under the load originating in
Miami, labeled "Reload 2", and indented a little more than the Miami ("Reload 1") load to show that it is a
reload for it.
There is one load originating in Chicago, so it is displayed under the Columbus load, labeled "Reload 3"
and indented a little more than "Reload 2".
The Chicago load is going to Eudora, KS, but no loads originating in Eudora or nearby are found.
Therefore, this is the end of this branch that started with the Miami load.
This first branch shows that a trucker can take a load from Denver to Miami, then reload in Miami and take
a load to Columbus, OH, then pick up another load there, take that load to Chicago and reload one more
time, taking yet another load to Eudora, KS. If this trucker really wanted to end up back in Denver, this
example does not show that it can be done carrying a load all the way there. However, the more loads that
are in our database, the more likely that this will be the case. There should be a point where almost any
chain of reloads can be found to start in any fair-sized city and return to that city without ever having
to deadhead more than a number of miles (radius) specified by you.
The next branch starts with a load found not in Miami, but 64 miles away. This is the first of the two
mentioned in the first paragraph of this example and was found in Palm Beach. It is listed under the
the Chicago-Eudora load, but indented the same as the first Miami load because it is another possible
reload from the initial load heading up this chain (Denver-Miami). It is labeled as "Alternate Reload 1"
for the same reason.
This second "Miami" load's (Palm Beach's) destination city is Atlanta, GA. One load is found originating in
Atlanta, and it is displayed under the Palm Beach load, indented the same as all Reload 2s and labeled as
such.
The Atlanta load entry indicates that it is destined for Phoenix, AZ, but there are no loads found
originating in Phoenix, so this "sub-branch" contains only this load.
Another reload for the Palm Beach-Atlanta trip is found originating in Macon, GA, 55 miles from Atlanta, so
it is listed under the Atlanta-Phoenix load, indented the same (another Reload 2), the 55 miles displayed
by the city and state, and labeled "Alternate Reload 2" because it is an alternate reload to the one
originating in Atlanta.
This load is going to Sacramento, CA and there is no load originating in or close enough to Sacramento.
Another load is listed under the Macon-Sacramento load entry, originating in Savannah and going to Erie,
PA. It appears where it does because, in this example, Savannah is 95 miles away from Atlanta. This is a
second alternate load and the third potential reload, from the Palm Beach-Atlanta trip. It is labeled and
indented the same as the other possibilities. No load is found originating in or nearby Erie, PA, so this
is the end of the second branch that started with the Palm Beach load.
The last reload found originating in or near Miami originates in Orlando, FL, 115 miles away from Miami.
It is listed under the Macon-Sacramento entry and indented the same as the first and second "Miami" loads
and labeled as "Alternate Reload 2". Its destination city is Saint Louis, MO. In this example, no loads
originate in Saint Louis and there are no more alternate reloads for the original Denver-Miami load, so
this is the end of the daisy chain.
8/11/09-8/27/09 Denver, CO Tom/321-321-4321
EndDump Miami, FL ABC Company
Drop Cowhides 1687 miles
Reload 1: 8/12/09-8/13/09 Miami, FL Candi/321-321-4321
Dump Columbus, OH XYZ Company
Drop Cowhides 1146
Reload 2: 8/12/09-8/13/09 Columbus,OH Mike/321-321-4321
Dump,EndDump Chicago,IL OurCompany, Inc.
Live 2" rocks 355 miles
Reload 3: 8/21/09-8/22/09 Chicago,IL George/343-232-1212
Dump Eudora, KS TheLoadPost.com
Live Cowhides 121 miles
Alternate 8/12/09-8/13/09 Palm Beach,FL(64 miles) Loren/444-677-8765
Reload 1: EndDump Atlanta,GA XYZ Company
Drop Hand tools 622 miles
Reload 2: 8/12/09-8/13/09 Atlanta,GA Mike/321-321-4321
EndDump Phoenix,AZ YourCompany, Inc.
Drop Wheat 1490 miles
Alternate 8/12/09-8/13/09 Macon,GA(55 miles) Sam/121-323-4321
Reload 2: Dump Sacramento,CA Nobody's Company
Drop Cowhides 2500 miles
Alternate 8/12/09-8/13/09 Savannah,GA(95 miles) Sam/121-323-4321
Reload 2: EndDump Erie,PA Nobody's Company
Drop Refrigerators 2500 miles
Alternate 8/13/09-8/14/09 Orlando,FL(115 miles) George/123-456-7890
Reload 1: EndDump Saint Louis,MO XYZ Company
Live Garbage 622 miles
RECOMMENDATIONS/IMPORTANT INFO/DAISY CHAIN SETTINGS
Some important characteristics of the Daisy Chain of Reloads™:
* There is a maximum of 250 load entries of any chain displayed on the Daisy Chain Page.
* All reloads of the same number and color and the load entries that make up their "branches" (i.e., the
higher-numbered reloads displayed directly below them down to the next entry of the same color) are
sorted and displayed with the closest immediately under the previous, lower-numbered load entry. That
sentence is tough. This is shown in the example above. The Miami-Columbus entry is the first "Reload
1" displayed under the Denver-Miami entry because Miami is zero miles from Miami. The Palm Beach-
Atlanta entry is listed before the Orlando-Saint Louis entry because Palm Beach is 64 miles from Miami
and Orlando is 115. Similarly, the possible reloads after the Palm Beach-Atlanta trip are listed in
their order because of how far away from Atlanta they are.
* Truck/Trailer type is taken into account in matching loads, not just the city. Therefore, if you choose
a load from the load list page that can only be carried and delivered with a Hopper, then only loads
that have Hopper as at least one of their truck types will be selected, regardless of whether or not the
load originates in the city the previous load is delivered to, close to or not. There are a couple of
exceptions:
1) If "Van" is one of the truck types of the chosen load, then "Reefer" loads will also be displayed,
but not the reverse.
2) If either "Dump", "EndDump" or "DumpTrl" is one of the truck types of the chosen load, then Dump,
EndDump AND DumpTrl loads will be included in the results.
3) If "Hopper", "HopHi" or "HopLo" is one of the truck types of the chosen load, then all of those
types will be included in the results.
4) If any of "Flatbed", "FlatTrp", "FlatSid", "Doubdrp", "HotShot" or "StepD" is one of the truck
or trailer types of the chosen load, then any entries with any of those types will be included in
the results.
As more and more loads are entered into our database, the likelihood of reaching the maximum in a chain
increases. When this happens, all of the 250 entries could be in one Reload 1 branch and, therefore, no
alternates to that load will be shown. It could also be that the 250th entry is the first Reload 2 of an
Alternate Reload 1 and you won't see any other potential Reload 2s for that Alternate Reload 1. It is good
to know that all reloads for each reload "level"/number are found, sorted and only the closest ones within
the Daisy Chain Settings form settings are displayed. However, these settings can be changed to limit the
reload levels or alternates, thereby fitting more of the Reload 1s and/or 2s on the page.
One way (the "old" way) to deal with this situation, and since the limit to Reload levels is 4 and is the
default, one option is to set Number of Reloads to 1 rather than 4. The Daisy Chain Page will find the
Reload 1s and as many Alternate Reload 1s available up to what you have set for the value of "Max Alternate
Reloads" (4 is the max there, also, and this should be more than enough). This way, you can choose one of
those alternatives, return to the List/Manage Loads page, locate that load entry and click the Reloads
button to display only its daisy chain. This will give you only a subset of the previous chain and you
already know that the beginning of this chain is the first reload you want of that chain.
Considering the above, if you choose to limit the chain via the Number of Reloads, especially Reload 1s,
then set Max Alternate Reloads to its highest value (4, at present) so that you are sure to see as many
alternates as possible. If you think a larger number of Reloads or Alternative Reloads would be better,
please use the "Contact Us" page to let us know about it.
Of course, if you reduce the Radius in Miles, fewer loads will be found because the search distance is
less. This will lessen the number of entries in the daisy chain, but will also limit potential reloads.
That may not be a problem, depending on available loads within that new Radius.
A Better way: The settings now also provide for one option (not "1", but "1 (ALL&ONLY)") that will display
ALL Reload 1s and nothing else, allowing you to see all of them at one time. They will also be sorted with
the closest to the selected load at the top.
In addition to the "all and only" Reload 1s option in Number of Reloads, each entry has a "Reloads" link
exactly like the one that got you to the Daisy Chain Page and it does exactly the same thing. If you click
one of those links, then its entry becomes the selected entry and the page is refreshed with that entry in
in black at the top and its daisy chain below. Each of the entries in its daisy chain have the same Reloads
link and this can be done over and over. The "Return to..." button becomes labeled "Previous Chain", so
when you click it, you return to the daisy chain you were on when you clicked the Reloads link.
It is our hope to some day have enough loads in the database so that a daisy chain display has only reloads
from the destination cities of the previous loads and no driver needs to deadhead more than within those
cities, and can choose how many reloads and how many days he/she wants to be on the road and always ends
ends up at wherever desired with a full truck/trailer and as close to zero deadhead miles as possible. We
are very close!