Automated conflict detection in terminal airspace is a challenging problem, in part because key information regarding flight intent is not available. Unlike en route controllers, terminal controllers currently do not enter altitude clearances when they issue them by voice, so the altitude at which a flight will level off is unavailable to the conflict detection automation. This uncertainty increases the likelihood of false alerts. Requiring terminal controllers to make entry of altitude clearances may be met with resistance due to workload concerns. A new method is studied in which a ground-based trajectory predictor predicts altitude level-offs a priori, based on altitude restrictions on published runway descent profiles and at waypoints on Nominal Interior Routes (NIRs) and Area Navigation (RNAV) Departure Procedures (DPs). The full benefit of the intent information of all altitude clearances is shown to be achievable when controllers only make entry of altitude clearances not attributable to altitude restrictions, which leads to an insignificant workload increase; an unacceptable level of workload increase may result if all altitude clearances are entered during busy hours. In addition, the integration of altitude restriction increases the average alert lead time to 43 seconds from 37 seconds without.