Connect the service event
Reference the originating pickup, site, service point, stream, container, and collected time so the load does not appear without context.
Keep the physical load, manifest or consignment reference, custodians, carrier, destination, receipt, rejection, and unresolved evidence in one traceable chain.
This tracker coordinates the custody chain around an official manifest or consignment reference. It does not submit statutory e-manifests to government portals.
Free for up to five users. No credit card required.
Adapt fields, workflows, and dashboards without code. Explore 1,000+ app templates and use cases
Inspect fictional custody handoffs and missing-evidence states; statutory filing remains external.
The tracker should show the evidence required to leave each state.
| Signal | What to inspect | Decision or next action |
|---|---|---|
| Preparing or awaiting pickup | Origin, material, package or container, custodian, approved destination | Confirm release readiness and carrier |
| In transit | Departure, carrier, vehicle or route, seal, expected destination | Monitor handoff without overwriting origin evidence |
| Rejected | Receiver finding, photos, material profile, current custody | Review return, redirect, re-sort, disposal, or dispute |
| Evidence incomplete | Receipt, ticket, certificate, recovery result, due owner | Escalate the missing proof before final closure |
The tracker should explain where the load came from, who accepted custody, where it was delivered, and which evidence closes the movement.
Reference the originating pickup, site, service point, stream, container, and collected time so the load does not appear without context.
Capture carrier or team, vehicle or route, manifest or consignment number, seal, origin custodian, and departure time.
Capture facility, receiving contact, received time, accepted or rejected outcome, ticket, and any missing evidence.
Changing the destination or closing a ticket should not hide the original rejection, missing evidence, or disputed responsibility.
Retain receiver evidence and route the load to disposition review before assigning charges or redirecting material.
Record who authorized the change, why, the new facility, and whether the material profile still permits it.
Let the physical movement close separately from the ticket, certificate, or final recovery evidence while the record remains visibly incomplete.
Jodoo can hold the references and evidence required by different streams and partners while keeping one operational chain.
A focused custody tracker can be configured in hours and connected to statutory or carrier systems that remain authoritative.Jodoo fits the operational handoff chain and missing-proof workflow; it is not a substitute for a mandated government e-manifest service.
Origin, carrier, vehicle or route, seal, custodian, destination, receiving decision, ticket, certificate, and evidence status.
Use required government or certified services for statutory submission, signatures, prescribed document formats, and jurisdictional validation.
Keep the official manifest identifier and submission status linked to the load so operational teams can resolve gaps without duplicating the filing.
Include origin, pickup, stream, load ID, carrier, vehicle or route, manifest or consignment number, seal, origin custodian, departure, destination, receiver, receipt time, acceptance or rejection, ticket, final outcome, and missing evidence.
No. Jodoo can coordinate the operational record, references, evidence, and reviews around a regulated movement. Use the required government or certified platform for statutory submission where applicable.
Yes. Authorized builders can add jurisdiction, carrier, stream, seal, signature, ticket, and certificate fields while keeping the official submission system authoritative.
Open the populated tracker to follow handoffs, receipts, rejections, and evidence gaps. Then copy the App and adapt the fields and review workflow to your streams and jurisdictions.
Open the manifest tracker