They could use a set values in one template to copy into another template. We felt it would be dangerous to allow users to define their our templates because it would not be clear what the implications would be to a proposal. We asked whether visits are a universal concept or are HST-specific. It is not clear how the ETC would handle pos-targs, since the ETC might compute counts based on the reference target, rather than the actual target in the aperture. So when the VTT positions are based on pos-targs, the ETC may not get the appropriate target that is actually intended.
Similar issues arise with targets specified by patterns or offsets.
The current state of a proposal could be summarized through a table or spread sheet. On possibility would be to have the ra and dec computed and display in a common field, independent of the means used to specify the coordinate. A user could click on this field for more details about the exact specification. A table's text can be directly updated. Timing constraints on visits could be specified graphically.