Each queue has three columns:

  • Model Name of the model or object and its order.
  • Expected next Description of the next event that we expect to happen. Examples: Client to provide clarification on assets, Client to upload photos, etc.
  • Time Amount of time that this model has been waiting in this queue.
    The column also has the description of the past event that has been used to count the time, this is called the triggering event. For example, if the model is in the production queue because we need to upload floor plans, then the triggering event occurs when the assets are marked as received and that’s when the clock starts ticking.

Existing queues

All models and objects must appear in one of the three queues unless they’ve been approved. The three queues are described next.

Asset collection

This is the list of models for which we’re collecting assets. New models will appear here straightaway.

Status of the items in this queue is: waiting_for_assets or need_more_assets.


This screen contains the list of models or objects that are waiting for us to produce & upload something.

The system will indicate what we need to upload, it could be floor plans, visuals, a revision, etc.

Status of the items in this queue is: in_production or in_revision.

Client feedback

This is the list of models that are waiting for the client to be approved. If a model is stalling here for a long period of time we may need to get in touch with the client and see what we can do to get their approval.

This is particularily important when the production queue has a low level of items.

Status of the items in this queue is: in_client_review.