Making legends is not one of the most interesting tasks but in urban design and landscape architecture often legends need to be added to drawings. The 'Quick Legend' command is created to do the tedious work instead. In the first place as a guide for the reader but it can also help to organize calculations. The number of actions the user is asked to do are reduced to an absolute minimum. At the start of the command the user can change settings. The most interesting one is the option to export the legend to Excel. All settings have predefined values so there's no need to define anything. When everything is set the user needs to pick a point to position the legend. When the point is picked it's just a matter of selecting entities. There are three main types of entities which the user should select: blocks, hatches and linear elements. Every time an entity is selected the command will add an entry to the legend. For blocks the entry will exist out of a quantity, the block itself and the block name. When a hatch is selected the command will add an entry to the legend with the cumulative area of all the hatches with the same properties, a box with an example of the hatch and the layer name. When a linear element is selected the command will add an entry with the total length of linear elements with the same properties, a line and the layer name. With every entry all possible properties are considered. Two hatches could have all the same properties but when the color is different they are visually different. After all a legend is a guide to explain colors and so on, so every single property which could have effect on the graphic of an entity is considered. The command will keep track of the entries which are made. When an entity is selected but it's specific properties are already added to the legend the command will alert the user. This way it's impossible to make a double entry. To see what happened with every entry the command creates an overview in the command line. For every entry all considered properties are listed including any calculations. So if an entry seems to be double but it's added anyway the user can check why it was added.