If you're not destroying your collection over the lifetime of the router you can do it this way. Benefit is that the view isn't re-initialized every time you hit a router action, instead you can focus on triggering the right events on it.

rotas_router.js.coffee

class ShiftDock.Routers.Rotas extends Backbone.Router
  routes:
    '': 'index'

  initialize: ->
    @collection      = new ShiftDock.Collections.Rotas()
    @collection.view = new ShiftDock.Views.RotasIndex(collection: @collection, el: '#container')
 
  index: (year, week) ->
    @collection.fetch
      success: (collection, response) =>
        collection.trigger('fetched')
 
# ...