Execute yard and dock schedules
How execute yard and dock schedules are reshaped as AGI capability advances.
The bottom line
Only about 15% of Execute yard and dock schedules is information work today — the rest is physical, and moves slowly. The exposure is concentrated in the back office: the books, the paperwork, the scheduling, the marketing.
Why: With no child occupations seeded, the scalar is derived from the APQC process name 'Execute yard and dock schedules'. This activity aligns with the 'Deliver Physical Products' category prior (~0.15), reflecting work that primarily involves the physical movement of trucks, trailers, and goods at a loading dock, placing it firmly in the physical band.
grounded in the economy graph · digital scalar 0.15 · physical
Business-as-Code
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
Execute yard and dock schedules sits inside a larger value-flow — 1 parent structure it composes into. The hierarchy is grounding, not the story: it tells you which aggregate exposure Execute yard and dock schedules inherits.
Where Execute yard and dock schedules sits
Related articles
No articles yet for this entity.
Recent capability events
No capability events for this entity yet.
How the work flows
Trigger: A carrier arrives at the facility gate or a trailer is flagged for movement within the yard.
- Check in arriving carriers and verify appointment schedules
- Assign temporary yard parking or immediate dock doors
- Dispatch yard jockeys to move trailers to designated dock doors
- Monitor loading and unloading status at dock doors
- Release trailers from the dock and check them out at the gate
Outcome: Trailers are successfully routed to assigned dock doors, processed, and dispatched from the facility on schedule.