Broker guides

Freight Broker Appointment Change Log: A 3-Load TMS Test

freight broker appointment change log

An appointment field can tell a dispatcher what time appears on the load now. It does not necessarily show what the shipper first requested, what the facility confirmed, what changed after dispatch, or who received the update. That distinction matters when a carrier, customer, and operations team remember the same stop differently.

Before buying or implementing a freight broker TMS, test appointment changes as a controlled workflow. The goal is not to prove that software prevents detention or disputes. It is to learn whether your team can reconstruct one change without relying on a private inbox or someone’s memory.

Keep four kinds of time separate

Use precise labels before you test:

  • Requested time: the window a customer, shipper, receiver, or broker asks for.
  • Confirmed appointment: the time a facility or other authorized party accepts, with a source and confirmation time.
  • Estimated time: a forecast from a dispatcher, carrier, driver, tracking provider, or another identified source.
  • Actual time: a reported or documented event such as arrival, check-in, loading start, release, or delivery.

These are not interchangeable. A later estimate should not quietly become the confirmed appointment. An actual arrival should not erase the appointment against which performance or a detention request may be reviewed.

Current public product documentation shows that systems implement these distinctions differently. BrokerWare’s July 23, 2026 release notes describe a “Current Delivery Information” card beside “Original Shipment Information,” with pickup and delivery windows sourced from tracking and stop-level data. Its June 25, 2026 notes separately describe fixes for time-zone handling, actual-event timestamps, and appointment-window mapping. Those are attributed examples of one vendor’s implementation—not universal requirements and not claims about ServeOps.

Build one appointment-change card

For every confirmed change, capture these eight elements:

  1. load and stop identifier;
  2. prior requested and confirmed window, including time zone;
  3. proposed new window;
  4. party requesting the change and communication channel;
  5. authorized party confirming it;
  6. confirmation time and source evidence;
  7. people notified and the time of each notice; and
  8. documents or downstream records that must be revised.

Keep the evidence appropriate to the transaction: an authorized email, portal confirmation, call note under your policy, revised rate confirmation, facility reference, or another traceable source. Do not collect sensitive personal data merely to make the packet look complete.

This card is an original editorial control, not an FMCSA form or legal standard.

Run the three-load test

Use synthetic records or freight you are authorized to test. Use approved test inboxes, never a real carrier or customer address without permission. Assign one operator to make changes and a second operator to reconstruct them.

Load 1: requested time becomes confirmed

Enter a requested pickup window of 9:00–11:00 a.m. Central. Then record a facility-confirmed appointment of 10:30 a.m. Central.

The second operator should be able to answer: What was requested? What was confirmed? Who confirmed it? When? Which source supports that answer? Verify what appears on the load screen, stop record, notes or history, rate confirmation, and any export the product actually supports.

Load 2: appointment changes after carrier commitment

Create a cross-time-zone load with a confirmed delivery appointment. After the carrier has been assigned in the test record, move the appointment to a later time. Record the requester, confirmer, reason, facility-local time zone, carrier notice, customer notice, and any revised document.

Ask the second operator to find both the prior and current appointment without coaching. Check whether an older document remains distinguishable from the current version. If the system overwrites a field, test whether a disciplined note-and-attachment process creates a usable external change log.

Load 3: estimate, actual arrival, and detention review

Keep the confirmed appointment unchanged. Add a later estimated arrival, then a fictional actual arrival, check-in, loading start, and release time. Attach non-sensitive test evidence.

Truckstop’s detention article, which is vendor-authored operational guidance rather than law, recommends retaining proof of appointment, arrival time, loading or unloading times, notices, and relevant receipts or shipping documents. Use that list as a documentation prompt, not as a promise that any charge is owed. Detention terms, notice requirements, approvals, and amounts depend on the parties’ agreements and facts.

The second operator should be able to distinguish the confirmed appointment from the estimate and actual events, locate the evidence, and identify who owns the carrier-pay and customer-charge reviews. Those two commercial decisions should not be treated as automatically identical.

Score ten control surfaces

Mark each surface Pass, Manual, Fail, or Not tested:

  1. prior requested and confirmed values remain recoverable;
  2. the current confirmed appointment is unambiguous;
  3. every time includes the intended time zone;
  4. the source, actor, and recorded-at time are attributable;
  5. estimates remain labeled as estimates;
  6. actual events remain distinct from appointments;
  7. the latest and prior documents can be distinguished;
  8. carrier and customer notifications can be evidenced;
  9. detention or other exception evidence is linked without deciding entitlement automatically; and
  10. a second authorized user can retrieve the complete change packet.

A Manual result can be acceptable if the step is documented, repeatable, assigned, and survives the second-user reconstruction. A Fail means the workflow silently overwrites a critical value, loses the time zone or source, exposes data to the wrong role, or makes two versions look current. Use Not tested when you lack permission, data, or a supported feature. Do not turn missing evidence into a passing assumption.

Set the acceptance rule before the trial. A practical gate is: no Fail on prior/current values, time zone, attribution, document identity, or authorized retrieval; every Manual step has an owner and written fallback; and all other surfaces are either Pass or explicitly Not tested with a decision owner.

What federal broker records do—and do not—settle

Current 49 CFR 371.3 requires a broker to keep a record of each transaction containing listed party, document, compensation, service, freight-charge, and carrier-payment information, and to keep the required record for three years. The section does not prescribe the eight-element appointment-change card or this three-load test. Do not describe this workflow as an FMCSA-mandated appointment log.

The regulation is useful here for a narrower reason: a transaction record and an operational change history answer different questions. A brokerage should have counsel and its responsible compliance owner decide what contracts, communications, shipping documents, and other records to retain beyond the rule’s listed fields.

The ServeOps functionality boundary

This guide does not assert that ServeOps stores original and current appointment windows, converts time zones, schedules dock appointments, ingests tracking, sends notifications, preserves document versions, calculates detention, approves charges, or maintains an audit history. Those capabilities must be verified in the current product, with authorized test data and the correct user roles.

If ServeOps is on your shortlist, run this drill before relying on it for live freight. 60-day free trial; card collected upfront; no charge for 60 days; cancel anytime; then $49 per seat/month or $490 per seat/year. Card is required upfront. No charge during the trial. Record what works, what remains manual, and what is not tested.

Sources