Bootney,
No, Project does not have that "option" and it really isn't necessary.
If you already have a plan to accomplish some end goal, then you also
have an idea of how long you expect each task to take (Duration) and
when you intend to start the whole project, whether now or sometime in
the future. Project's underlying scheduling engine does not use "fuzzy"
logic, rather, it calculates all time related data to the nearest minute
because only then can it provide accurate time related scheduling.
Don't worry that the dates shown may not be correct once the project is
started. The whole project timeline can easily be shifted in one fell
swoop by using the "adjust dates" add-in on the Analysis toolbar.
As far as tracking/forecasting, tracking can only be validly
accomplished if a plan is firm (i.e. real dates) and a baseline has been
set. There should be no problem with tentative dates in a forecast. One
caution on forecasting, some people try to put to much detail in an
initial plan for forecasting and it soon gets to unwieldy or complex.
Depending on the forecasting timeframe (i.e. near or far), sometimes the
best approach is to keep future tasks in planning format. For example,
instead of describing all the tasks necessary to design, build and test
a widget, just lay out the major phases. This approach even works well
for projects with time spans of a year or more. Lay out tasks in the
near term (e.g. next 6 months) as detail and those in the future as
planning package groups.
By the way, if you are still dead set on having a plan with "TBD" for
Start and Finish, I suggest you substitute spare text (TBD) or date (NA)
fields in the active view. Real dates will still exist in the normal
Start and Finish fields, but you can always present what you want.
Hope this helps.
John
Project MVP