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

=== Assistant: Yes — I found a published set of RRECS time standards tied to specific activities that can serve as the basis for build… ===
Yes — I found a published set of RRECS ''time standards'' tied to specific activities that can serve as the basis for building an alphanumeric chart of evaluated time per unit. These are the *standards applied in RRECS to “counted” events (not actual time sequences such as loading, deviations, or end-of-shift). Rural Info<ref>{{cite web|title=Rural Info|url=https://www.ruralinfo.net/shared-files/104116519/?RRECS-Standard-to-Seconds.pdf=|publisher=Rural Info|access-date=2025-12-22}}</ref>

Below is a sample of the RRECS time standards in a clear table format that you can use to understand how many minutes per unit each coded activity contributes to the evaluated time (in minutes and approximate seconds). This is not all standards in RRECS — the full list is extensive — but it’s a representative portion useful for carriers prioritizing activities: Rural Info<ref>{{cite web|title=Rural Info|url=https://www.ruralinfo.net/shared-files/104116519/?RRECS-Standard-to-Seconds.pdf=|publisher=Rural Info|access-date=2025-12-22}}</ref>

==== |     |     |     |     | ====
| --- | --- | --- | --- |
|     |     |     |     |
|     |     |     |     |
|     |     |     |     |
|     |     |     |     |
|     |     |     |     |
|     |     |     |     |
|     |     |     |     |
|     |     |     |     |
|     |     |     |     |
|     |     |     |     |
|     |     |     |     |
|     |     |     |     |
|     |     |     |     |
|     |     |     |     |
|     |     |     |     |
|     |     |     |     |
|     |     |     |     |
|     |     |     |     |
|     |     |     |     |
|     |     |     |     |
|     |     |     |     |
|     |     |     |     |
|     |     |     |     |

: 

==== - Higher seconds/minutes per unit → more evaluated credit for that activity. ====
* Trip / dismount credits (e.g., S117A, S123, S129) are relatively high — these repeatedly add significant time when frequent on your route. Rural Info<ref>{{cite web|title=Rural Info|url=https://www.ruralinfo.net/shared-files/104116519/?RRECS-Standard-to-Seconds.pdf=|publisher=Rural Info|access-date=2025-12-22}}</ref>
* Box time standards vary by bundle configuration — more bundles = more box time. Rural Info<ref>{{cite web|title=Rural Info|url=https://www.ruralinfo.net/shared-files/104116519/?RRECS-Standard-to-Seconds.pdf=|publisher=Rural Info|access-date=2025-12-22}}</ref>
* Minor credits like stop signs / yield signs still contribute cumulatively when mapped — especially on long rural routes. Rural Info<ref>{{cite web|title=Rural Info|url=https://www.ruralinfo.net/shared-files/104116519/?RRECS-Standard-to-Seconds.pdf=|publisher=Rural Info|access-date=2025-12-22}}</ref>

==== - One-step vs. two-step MDD inputs: Some carrier entries (like entering parcel counts or customer contacts) have an associated scanner entry time standard (e.g., 0.0795 min/scan or 0.0928 min/scan) that contributes a small time credit for performing the entry itself. Rural Info<ref>{{cite web|title=Rural Info|url=https://www.ruralinfo.net/shared-files/131327/NRLCA-Comprehensive-Guide-to-RRECS-revised-April-2022-Final.pdf|publisher=Rural Info|access-date=2025-12-22}}</ref> ====
* This chart does not cover actual time sequences such as loading time, deviation time, or end-of-shift time — those are measured as actual elapsed time rather than standard units. Rural Info<ref>{{cite web|title=Rural Info|url=https://www.ruralinfo.net/shared-files/131327/NRLCA-Comprehensive-Guide-to-RRECS-revised-April-2022-Final.pdf|publisher=Rural Info|access-date=2025-12-22}}</ref>
* RRECS has many more standards (e.g., door delivery distances, parcel delivery distances, park points, steps) not shown above — the full “RRECS-Time-Standards.pdf” available through Ruralinfo.net contains dozens more. Rural Info<ref>{{cite web|title=Rural Info|url=https://www.ruralinfo.net/knowledgebase.html|publisher=Rural Info|access-date=2025-12-22}}</ref>

If you’d like, I can expand this into a full alphanumeric chart keyed to the actual MDD scan codes (e.g., TRIP2DOOR, AUTHDISMOUNT, DOORMISC, etc.) and pair them with their RRECS standard IDs (e.g., Sxxx) and total evaluated time per occurrence. Just let me know!