Successful project management relies on the ability to track multiple dates, often with different meanings. This often involves tracking and differentiating between start dates and due dates. While GQueues doesn't have different fields to set multiple dates for a task, with a few clicks you can get the same effect in GQueues.

GQueues is highly customizable and we encourage users to tailor it in the way that works best for you. Smart Queues and searches consider the task date as its due date. But all other uses for dates in GQueues can adapt to your definitions, so you can track dates using different methods for different purposes.

If you want to set multiple dates for a single task, such as start date, due date, and check-in dates, you can use subtasks to for each. When you receive the reminder to begin work (start date subtask), you know it’s time to get cracking.

For example, if you’re writing an article and you just put the due date, you miss the opportunity to make sure you start researching and writing early enough to actually meet that deadline. In addition to letting you set multiple dates, this can also be a nice way to break up your work into more digestible chunks!

If you rely on Google calendar for a visual reference for what you’re working on, then using the task duration could be a good fit to show the start and end date for a task. This way the task’s date indicates when you should start working on it, and the duration will show when it is due. Plus, it will show in Google Calendar for the whole period you’re working on it.

👉 Pro Tip: Combine this with setting multiple dates with subtasks to make sure you see the entire duration on your calendar, and get multiple reminders to continue working on it.

If dates slip or you want to follow up with someone at a later date, you can always modify your original dates, and that information is tracked in the task's activity. But for some projects, it's better to have a clear visual indicator the due date was pushed, and recording the reason for a date slip or scope creep as a new subtask will help when you debrief on how things when later on.
​