Your work and assigned requests
A Can You Just request you create for yourself retains the immediate interruption workflow. A request assigned to another resource enters that recipient's Incoming queue. This applies to people and agents. Incoming work remains floating until accepted: it reserves no capacity, splits no stages, creates no actuals and does not move project forecasts. Even Critical remains floating.
Queue and timeline
Open Incoming in navigation or select a resource's Incoming summary on Timeline. The full queue shows every floating request, its requester, requested time, age, named priority, estimated duration and suggestion. Select a request for details and actions. Accepted and completed requests remain available in the queue's history section.
The compact lane appears only for resources with floating requests. Day and Week can show up to three non-overlapping previews; Month and Quarter show the summary. The queue orders Critical, High, Normal, then Low, oldest first within each priority, with request ID breaking ties. Age never changes priority. A preview is a recommendation, not a reservation.
Suggestions
Suggestions use the recipient's working calendar, leave, commitments and committed plan. Critical suggests the first eligible working point. High looks within one working hour; Normal within four. Natural task boundaries are preferred. During long work, a suitable checkpoint may be suggested instead. Low looks for spare capacity within 24 working hours. If there is no eligible point within the bounded horizon, the queue explains that no suggestion is available. Continuous resources retain continuous availability.
Suggestions recalculate when you read the queue or timeline. They can move as time and the plan change. This does not change priority, create a commitment or generate Activity records.
Recipient actions
- Start Now accepts the request as an ordinary immediate interruption at the current local time. The scheduler reflows committed work normally. Starting a plan does not invent actual effort.
- Show in Plan uses your selected local date and time in the existing temporary What If plan. Review its impact and Apply changes to accept it. Discard leaves it floating. Future planning does not create Actual Start.
- Reassign moves a floating request to another active resource in your organisation. It stays floating, preserves the original requester and requested time, records the change and recalculates its suggestion.
- Complete records an outcome without requiring prior acceptance. Unknown actual start and effort remain unknown. Existing linked assistance blockers are released by completion.
Only the current recipient can perform these actions. Open an accepted request through its Incoming link to complete it. Self-created interruptions keep their existing editor.
External responses
A request can retain an external conversation reference and record a response or completion without fabricated actuals. Background checking of external systems is not part of this workflow.