An example of how (relative) network addresses may be assigned to computers is shown in the section about system address usage.

When creating documentation, it may be useful to consider using methods to abbreviate the text. (Such details may be covered more in the network documentation section.)

A quick and easy way to create documentation may be to follow this technique: Create custom network documentation that starts out by having a reference to some readily and freely available pre-made documentation, such as the system address usage example. Then use the text-abbreviation techniques to jot down notes about how the custom network matches, or is different from, the pre-made documentation.

For instance, perhaps saying “.0 through .7 : Same as shown in the skeletal document.” As shown in that simple example, eight computer network addresses have been sufficiently documented in a single sentence.

Just be sure not to lose a copy of the skeletal document being used! As a good, standard practice, have a private copy of all of the documentation. Relying on a public resource is generally an unrecommended practice, in case the publicly available resource becomes unavailable.

The most important documentation is generally credentials (usernames and passwords). The next most useful documentation is generally some short details about how to access the computer/device/equipment/software, such as an IP address and perhaps a protocol (often conveniently combinable by mentioning a URL, such as noting a printer's configuration being accessble at Simply having that information available can be the most critical thing to save time: the next best feature of documentation is easy accessibility to information, caused by things like additional adjectives (like a printer's manufacturer/make and model number) and decent organization.