Editing Openai/69480e10-17a8-8002-ad04-2108190299a2 (section)

=== Assistant: Absolutely — I can help break down the RRECS manual-entry activities by their time value impact so you can prioritize t… ===
Absolutely — I can help break down the RRECS manual-entry activities by their ''time value impact'' so you can prioritize the ones that matter most for accurate route credit. Unlike the base scans (clock in/out, breaks), some scans drive ''actual'' time capture or add meaningful evaluated time, and others simply count occurrences for standard time calculation.

Here’s a prioritized breakdown based on how RRECS uses the scan data in the evaluation calculations (using official RRECS logic and carrier guides):

==== These scans directly capture time durations that are used in the evaluated time calculation — meaning the system tracks the actual elapsed time between two scan events and uses that value rather than just a count × standard. ====

===== - STARTLOADVEH → ENDLOADVEH Time between these scans = actual loading time credit. This can add significant evaluated time on heavy mail days. RRECSulator<ref>{{cite web|title=RRECSulator|url=https://rrecsulator.com/collection_howto|publisher=rrecsulator.com|access-date=2025-12-22}}</ref> =====
* RETURN2DU → PMCASING (or CLOCKOUT) Time between Return to Delivery Unit and either PM Casing or Clock Out = End-of-Shift time. Important: If you scan CLOCKOUT before casing, END OF SHIFT stops sooner. Many carriers miss PMCASING to maximize actual time credit here, so this one has real impact. RRECSulator<ref>{{cite web|title=RRECSulator|url=https://rrecsulator.com/collection_howto|publisher=rrecsulator.com|access-date=2025-12-22}}</ref>

===== - STARTDEVIATION → ENDDEVIATION Time on actual deviation for Express deliveries — captured in actual time, not just counted. Deviation time isn’t always huge, but on Express days it can add up quickly. GovInfo<ref>{{cite web|title=GovInfo|url=https://www.govinfo.gov/content/pkg/FR-2023-12-01/html/2023-26393.htm|publisher=govinfo.gov|access-date=2025-12-22}}</ref> =====

==== These entries don’t capture actual time intervals but instead produce counts that are multiplied by an engineered time standard — and if you do them frequently, they can accumulate significant evaluated time. ====

===== These matter because each instance adds standard minutes: =====
* TRIP2DOOR – multiple trips to a door Often overlooked credit on multi-parcel stops.
* AUTHDISMOUNT – extra dismount(s) at cluster/CBU locations
* UNSCANPARCEL – parcels without barcodes These all generate evaluated time based on a standard for each occurrence. NYRLCA<ref>{{cite web|title=NYRLCA|url=https://nyrlca.net/forms-and-information/rrecs-resources/|publisher=nyrlca.net|access-date=2025-12-22}}</ref>

===== Although they generate limited time credit, don’t ignore them: =====
* RURALREACHCUSTOMER (M)
* STAMPSTOCKSALES (N) These get standard time credit and show actual work performed, which otherwise could be lost in automated logic. NYRLCA<ref>{{cite web|title=NYRLCA|url=https://nyrlca.net/forms-and-information/rrecs-resources/|publisher=nyrlca.net|access-date=2025-12-22}}</ref>

===== - DOORMISC – misc door delivery movements This can add up when you have miscellaneous door handling that doesn’t fit normal scans. NYRLCA<ref>{{cite web|title=NYRLCA|url=https://nyrlca.net/forms-and-information/rrecs-resources/|publisher=nyrlca.net|access-date=2025-12-22}}</ref> =====

==== These don’t themselves add evaluated time but are necessary for accurate time sequences: ====

|     |     |
| --- | --- |
|     |     |
|     |     |

These don’t directly add credit but ensure your actual day is measured correctly. NYRLCA<ref>{{cite web|title=NYRLCA|url=https://nyrlca.net/forms-and-information/rrecs-resources/|publisher=nyrlca.net|access-date=2025-12-22}}</ref>

==== USPS’s RRECS methodology combines: ====
* Standard Time = count × standard for most delivery actions
* Actual Time = actual elapsed time between defined scan pairs (e.g., loading, deviation, end of shift)
* Automated Data = drive times & walking distances from route mapping GovInfo<ref>{{cite web|title=GovInfo|url=https://www.govinfo.gov/content/pkg/FR-2023-12-01/html/2023-26393.htm|publisher=govinfo.gov|access-date=2025-12-22}}</ref>

So the higher the count of high-value events and the accurate capture of actual time events, the better your evaluated time reflects real work done.

==== Priority 1 — Actual Time Capture ====
* STARTLOADVEH → ENDLOADVEH
* RETURN2DU → PMCASING (or CLOCKOUT)
* STARTDEVIATION → ENDDEVIATION

Priority 2 — High-Value Counts
* TRIP2DOOR
* AUTHDISMOUNT
* UNSCANPARCEL
* DOORMISC
* Rural Reach & Stamp Sales

Priority 3 — Time Sequencing
* OUTLUNCH / RETURNLUNCH
* CLOCKIN / CLOCKOUT

==== - Always enter every occurrence of door actions, parcels, and pickups — even small ones add standard time. RRECSulator<ref>{{cite web|title=RRECSulator|url=https://rrecsulator.com/|publisher=rrecsulator.com|access-date=2025-12-22}}</ref> ====
* Don’t mis-order PMCASING/CLOCKOUT — as that directly affects end-of-shift actual time. RRECSulator<ref>{{cite web|title=RRECSulator|url=https://rrecsulator.com/collection_howto|publisher=rrecsulator.com|access-date=2025-12-22}}</ref>
* Accurately capture loading and deviation times — they can add up more than most carriers expect. GovInfo<ref>{{cite web|title=GovInfo|url=https://www.govinfo.gov/content/pkg/FR-2023-12-01/html/2023-26393.htm|publisher=govinfo.gov|access-date=2025-12-22}}</ref>

If you want, I can go even deeper and provide per-scan standard time values (e.g., minutes credited per TRIP2DOOR or AUTHDISMOUNT), which good carriers use to estimate which activities are “worth it” relative to their route profile. Just let me know!