Submitting Work for Fulfillment

When a task or trust transaction has a type that a team fulfills (see Fulfillment Configuration), you don’t do the work; you place the order. The team works it in their queue, and you watch the status change on your own screen.

Optional vs. Mandatory

The task’s properties show its fulfillment state: which team handles this type, and whether fulfillment is optional or mandatory.

Optional types give you a choice. Click Fulfill via [Team] to route the work to them, or just work it yourself. One catch: the choice window closes once the work starts. After the item leaves its starting status, the fulfill option is gone and it’s yours. Before submitting, Cancel Fulfillment backs out.

Mandatory types (trust receipts, classically) have no choice to make; the only path forward runs through the team.

Submitting

When the order is ready, click Submit Order. Three things happen:

• The order lands in the fulfilling team’s Ready queue immediately. Any future date you’d scheduled on it is cleared; submitting means “this is ready for them now,” so don’t submit until it is.
• It arrives unassigned; a team member claims it from their queue.
• If the type has an SLA, the clock starts from this moment.

From then on, the fulfilling team owns the workflow. You can watch the status but not change it, which is the deal: you traded control for not having to do it.

Tracking

The order’s status updates live on the task or transaction as the team advances it, and your submitted orders appear in your Work Items view like everything else. No status meeting, no “just checking in” email; the answer to “where’s my title search?” is on the screen.

Tips

Submit means ready. The team receives exactly what you submitted; for trust transactions, the details lock at this point. Missing information comes back as a delay, not a mind-read.

Don’t hover. If the team runs SLAs, the countdown is doing your chasing for you. Reserve the phone call for a breached SLA with a real deadline behind it.