Every flag the engine can raise, as the reviewer reads it. The codes are a closed set in the
database (FlagCode): a flag that isn’t on this page doesn’t exist. Examples come from the example
world; <…> in a real message is filled from the ticket.
Bills says what an open flag does to the money: yes, the ticket bills as if the flag weren’t
there; that line no, one line bills nothing and the rest bill; no, nothing bills until the
ticket is corrected. Accepting a flag never changes what bills. Every message ends “Flagged for
review.” unless it says otherwise. See Flags, never blocks for how a reviewer
handles them.
On an ROE project, a collection, unit rate ticket or survey with no ROE
“Ticket 102002: no ROE.”
yes (on the ticket)
ROE_NOT_ON_PROJECT
Its ROE isn’t one of the project’s
“Ticket 102003: ROE R-0099 is not on this project.”
yes (on the ticket)
ROE_UNSIGNED
Its ROE isn’t signed
“Ticket 102004: ROE R-0008 is not signed.”
yes (on the ticket)
ROE_OUT_OF_SCOPE
Its ROE has a scope and the work isn’t in it: a collection’s debris type, or a unit rate ticket’s payable type, isn’t among the ROE’s scope picks. An ROE with no scope picked is never flagged for scope
“Ticket 102005: outside the scope of ROE R-0008.”
yes (on the ticket)
NO_PRE_WORK_SURVEY
A post-work survey with no pre-work survey on its ROE
A field event arrived without a detail its kind always records: a load’s or a haul-out’s debris type at either end; a disposal with no load call, no scale receipt and no count; a haul-out collection’s load call; a unit rate event’s kind of work
“Ticket 101036: collection has no debris type.”
yes, where an amount can be computed
TYPED_NUMBER_NO_REASON
The ticket number was typed instead of scanned and no reason was picked
“Ticket 101037: typed ticket number (no reason picked).”
yes
WRONG_KIND_OF_BADGE
A load or a haul-out recorded on a crew’s certification, or unit rate work on a container’s
“Ticket 101038: a load recorded on crew certification 730417.”
yes, where an amount can be computed
GPS_UNREADABLE
The phone sent a GPS fix that can’t be one (half a fix, a latitude past 90); the field event was saved without it
“Ticket 101039: GPS unreadable.”
yes
NOT_A_TICKET_NUMBER
The ticket number isn’t digits: the field event pairs with nothing until a person renumbers it
“Ticket 10A040: not a valid ticket number. Flagged for review; not billed.”
no
ENDED_BEFORE_STARTED
A field event’s end is before its start
“Ticket 101041: collection ended 09:10, before it started 09:40.”
yes
SPLIT_NOT_ALLOWED
A collection with a split suffix on a project whose Allow split loads is off
“Ticket 101042: a split load on a project that doesn’t allow split loads.”
yes
OUTSIDE_CONTROL_RANGES
On a project numbered from control tickets, a load’s or a haul-out’s number is in none of the ranges entered for its series
“Ticket 109999: number is in none of the project’s control ticket ranges.”
yes
ASSIGNMENT_ON_ANOTHER_PROJECT
A field event’s assignment belongs to a different project from the field event
“Ticket 101043: recorded under an assignment on another project.”
yes
SCALE_NET_DISAGREES
A scale receipt holds a gross, a tare and a net, and the net isn’t the gross less the tare. The weights stay as typed, never corrected
“Ticket 101054: scale receipt BCL-88251’s net (17.60 tons) is not its gross less its tare (17.10 tons).”
yes, from the net as written
TWO_QUANTITIES
A load’s disposal holds a load call and a scale weight. Which one bills is read from the paying pay item; the two are never compared
“Ticket 101055: disposal has both a load call and a scale weight.”
The worker hit an error on a ticket that was priced before: nothing of the failed run is kept, so its lines stay as its last good run wrote them until it is fixed
“Ticket 101035: could not be processed. Flagged for review; its lines are as of its last run.”
A sub it names has a name alike another sub’s on the project, once case, spaces, punctuation, a leading The, an ampersand and a company ending (LLC, Inc, Co…) are set aside: perhaps one company spelled two ways. Never which spelling is right; a person corrects the sub on the certification, or accepts the flag as two companies
“Certification 730416: sub “Rivera Trucking Co” looks like “Rivera Trucking” on this project.”
A phone’s field event names a person who, when it arrived, didn’t hold that phone over its field time (within the device clock’s own allowance), as above. A reviewer who corrects who it names clears it
“Ticket 101044: recorded under Ana Brooks, who wasn’t signed in on that phone.”
yes
ASSIGNMENT_OF_ANOTHER_PERSON
A phone’s field event was recorded under an assignment of somebody other than the person it names
“Ticket 101045: recorded under another person’s assignment.”
