# Annex: electronic consignment procedure **Procedure version: maxmove-cmr-2.** This annex governs the Maxmove consignment procedure used by participating senders, carriers, fleet workspaces and consignees. A representative agrees to this procedure when confirming the authority-and-procedure statement for the identified revision. The revision and acceptance evidence retain the procedure version; later changes do not replace that recorded agreement. This procedure version applies to revisions that state it. Revisions that state maxmove-cmr-1 keep their procedure version. 1. **Scope and parties.** The preparing party identifies the sender, contractual carrier, consignee, goods, route and applicable document profile. The international profile concerns carriage within the CMR's scope; the German domestic profile concerns a freight note under ยง408 HGB. The procedure does not extend either instrument's scope or replace mandatory law. The preparing party confirms ordinary freight and that no competing agreed consignment note covers the same lot. If a subcontractor performs the carriage for the contractual carrier, the note names it, with registration numbers, as the performing carrier; the contractual carrier remains the carrier on the note. If the order allocates its goods to individual loading and delivery stops, each pair of loading and delivery place has its own note. The goods and quantities of each note follow from that allocation, and all notes of an order together never describe more goods than the order carries. The current workflow excludes removals, dangerous goods, customs-dependent carriage, successive carriers and orders with several stops but no allocation of the goods. 2. **Authentication and authority.** The authenticated order booker may sign for the sender from the order owner's workspace without a phone challenge. The assigned driver accepts for the carrier with their own signed-in Account. If a subcontractor performs the carriage, its driver accepts for the carrier after accepting the order invitation in the Maxmove driver app; for this purpose the driver becomes a member of the contractual carrier's workspace. Without a Maxmove Account, the subcontractor's driver may hand over the note in the browser through the order's execution link. To do so, the driver confirms the phone the order was sent to with a one-time code. This session lasts at most 12 hours and only while the link, the assignment and the phone number stay the same; the link ends when it is revoked or expires, or when the order is completed, reassigned or accepted by a driver in the app. In the session, the driver confirms the takeover for the carrier, and the sender and consignee sign by hand on that device. The note names these methods with the masked phone number. Location and copy are recorded as on the driver's device (sections 4 and 10). In the browser every signature needs a connection; it keeps no signature for sending later. At pickup and delivery, the representative of the sender or consignee may review the revision on the assigned driver's signed-in device and sign it there by hand; the service records the drawn signature and the driver's Account. Signing links are sent by SMS to the phone number entered for that party in the order. Opening one sends the representative a one-time code at the same number. A signing link alone cannot sign or reveal the document. Every signer supplies their name and confirms authority to represent the named party. Control of an Account, device or phone number does not itself establish corporate signing authority; the representative is responsible for that attestation. 3. **Review and acceptance.** The signer reviews the identified revision, including selected accompanying documents, and expressly accepts or refuses it. The sender's acceptance issues the electronic note. The carrier records acceptance and any reasoned reservations. At pickup, the driver checks the goods and records the carrier's reservations before the sender signs on the driver's device. The sender sees the goods and the reservations before signing and may expressly accept the reservations (for CMR notes, Art. 8(2) CMR); the sender may also sign without accepting them. The note then marks each reservation as accepted or not accepted by the sender. Reservations the sender has not expressly accepted in this way, for example because the sender signed in advance by link, are not accepted. Before signing, the consignee sees the shortages, damage and refused goods recorded at delivery, which become the consignee's reservations on the note. The consignee records delivery acknowledgment, quantities and exceptions or a reasoned refusal. If several notes are handed over at one stop, the sender or consignee signs once on the driver's device; the signature is recorded as a separate acceptance for each note. An operational order status, POD waiver, photograph or previously captured signature does not substitute for this document-specific action. Section 11 governs delivery without the consignee's signature. 4. **Integrity and evidence.** The service records the exact document hash, revision, represented role, name, authority confirmation, authentication evidence and server time. For a signature given on the driver's device, it also records the time of signing as stated by that device. For every signature given on the driver's device, including the driver's own acceptance, it also records the location reported by the device, rounded to about 10 metres, with the accuracy the device states. The location is information from the device, not verified proof of place; if the device reports no location, the signature is recorded without one. The sender's acceptance of reservations is part of the sender's evidence. Each piece of evidence states the procedure version of the accepted revision. Maxmove seals the evidence using JAdES and retains the signed bytes and validation material in its versioned archive. Where a timestamp service is configured, each seal receives an RFC 3161 timestamp from that service (JAdES Baseline-T), which is a qualified electronic timestamp when the service is a qualified trust service provider. The timestamp proves that the seal existed at that time. Without a timestamp service, the sealing time is Maxmove's statement (JAdES Baseline-B). Each piece of evidence states its seal profile, and evidence that calls for a timestamp is never sealed without one. The platform evidence seal is distinct from the participant's act of acceptance. It is not represented as a qualified signature or a qualified company seal. A pending seal or archive remains visibly pending; the service does not call an unsigned PDF a completed electronic consignment. 5. **Corrections.** A permitted editor records a reason and creates a new revision. Previously accepted contents and evidence remain available. All acceptances required for the corrected revision are collected again, and previous signing grants cannot accept the new revision. The parties use the current identified revision, while retaining earlier versions for evidence. Maxmove queues a change notice for participants who previously responded, using their verified phone or authenticated workspace identity, and for copy recipients who opened their copy with a code (section 10). The dispatcher coordinates the change with affected participants and provides the new signing link where required; delivery of a notice does not itself establish renewed acceptance. A delivered note, including one delivered without the consignee's signature, can no longer be corrected. 6. **Access and inspection.** Authorized order participants can read the permitted documents and download readable copies and evidence. A separate, phone-verified, read-only grant may provide another person access to a specified revision for 24 hours. It is revocable and cannot sign. Section 10 governs copies for the sender and consignee, section 12 roadside inspections and section 13 the authenticity check. Signing links expire after 72 hours and verified review sessions after 30 minutes. Revocation or expiry prevents future service access; it does not erase copies already downloaded. Participants provide the applicable document to competent authorities through a readable copy or this access procedure. 7. **Outages and paper replacement.** A local cached copy is marked as the last downloaded version. A signature given on the driver's device without a connection is kept there, encrypted, for up to seven days and sent once the device is online. It is recorded only if the identified revision is still current; the evidence shows the device's time of signing and the server time of receipt, and the server time is the time of recording. If the revision changed meanwhile, the signature is not recorded and the party signs the current revision again. If the electronic process cannot be completed, an authorized editor may record a reason and create a linked paper replacement. At a handover the assigned driver may do so too, for example when signing on the driver's device does not work; the driver may also replace a complete draft this way and uploads a scan of the signed paper note. The original electronic record is retained and marked as replaced. The responsible sender/carrier informs the other participants and completes the applicable paper-original and signature process. An ordinary printout alone does not perform this replacement. 8. **Paper evidence and attachments.** An uploaded executed paper scan is evidence of the specified paper revision; it neither authenticates the handwriting automatically nor becomes an electronic acceptance. Accompanying files are bound by their exact checksums when included in a reviewed revision. Files added later do not silently alter an already accepted document. 9. **Retention and recovery.** The document archive preserves exact object versions, checksums, seal material, history and the retention rule frozen for each archived revision. The applicable operational transport-evidence policy currently retains these records for six years from year-end, subject to applicable obligations and legal holds. Device caches are temporary and are not the legal archive. Participants should export the relevant PDFs, evidence and accompanying files for their own required records. Suspected unauthorized access, incorrect party data or compromised credentials must be reported to Maxmove support without delay; access may be revoked and a corrected or replacement document issued without deleting original evidence. 10. **Copies for the sender and consignee.** A representative of the sender or consignee who signs on the driver's device may give a phone number or email address for their party's copy. The field is prefilled with that party's contact in the order. The representative may change or clear it; a cleared field means no copy. If the device offers no such field, the copy goes to the party's contact in the order. A representative who signs by link with a one-time code receives the copy at the verified phone number. Maxmove sends a copy only once the signed revision is sealed and archived: to the sender after the carrier's takeover, to the consignee after delivery. If the carrier refuses the takeover, the signed revision is corrected before the takeover, or the note is cancelled or replaced by paper before then, that copy is not sent. An email copy contains the PDF as an attachment and no link. An SMS copy contains a link; opening it sends a one-time code to the same number. The link shows the latest archived revision for 90 days, marks the revision the party signed and allows downloading the PDF. It is revocable and cannot sign. SMS copies go only to numbers in the EU, the EEA, Switzerland and the United Kingdom. A recipient who has opened their copy with a code also receives notices of corrections, switches to paper and cancellation. Where a copy goes is not part of the sealed evidence. 11. **Delivery without the consignee's signature.** If the driver's proof of delivery records the goods as left, for example at the door, or a manager of the carrier declares the delivery, the note is marked as delivered without the consignee's confirmation. It contains the carrier's delivery declaration with its reason and time and, where one exists, a reference to the order's proof of delivery. This declaration comes from the carrier and is not the consignee's confirmation. The consignee may still sign afterwards by link with a one-time code (section 2). After goods are left, Maxmove sends the consignee the signing link by SMS if a phone number is entered for them; the consignee's signature marks the note as delivered, and the declaration is kept. A note delivered without the consignee's confirmation can no longer be corrected, cancelled or replaced by paper. 12. **Roadside inspection.** The assigned driver, the carrier's dispatch and the note's editors may create an inspection link, which the driver app shows as a QR code. An inspection link is valid for 12 hours; each note has at most five valid inspection links, and a new one replaces the oldest. Whoever opens the link sees, without a one-time code, the archived revision in force with its contents, signers, signature methods and reservations, and may download the PDF. The inspection view shows no phone numbers, copy recipients or evidence. The link ends early if it is revoked, the note is cancelled or replaced by paper, the order moves to another carrier, or, for a link the driver created, another driver is assigned. Each opening is logged with the revision and a hashed value of the network address and deleted after 90 days. The carrier sees the openings. 13. **Authenticity check.** Every PDF carries a QR code for the authenticity check. It opens a public page with the document number, the printed and the current revision, the status, the sealing times and the SHA-256 checksum of the printed revision, without data about goods or parties. The code cannot be derived from the document number. If the checksum printed on the PDF matches the checksum on the page, the contents match the archived revision; the page also shows whether a newer revision now applies. 14. **Photo evidence.** The driver may support reservations with photos. The photos of a reservation and the proof-of-delivery photos taken at the note's loading or delivery place are bound to the accepted revision by their SHA-256 checksums once uploaded, in a separate addendum that is sealed on its own. An addendum does not change the accepted revision and is not any party's acceptance. The PDF states the number of photos per party and per reservation.