How to Design a Table Layout

design-table

Use tables to help readers understand large amounts of data which otherwise may take several paragraphs to describe.

The main parts of a table are:

  • Table number – number every table and use the same numbering format throughout the document.
  • Title – provide a brief but descriptive title. You don’t need to write a complete sentence. Instead, describe the data in the most useful terms for the reader.
  • Column heads – provide a word or phrase that identifies the information in each column. Use spanner heads if column heads are in two or more levels, that is, a collective head and individual heads.
  • Stub – this is the left-most column in a table. Place numbers¸ names, and unique identifiers here.
  • Body – the body of a table consists of the columns to the right of the stub and below the column heads. Enter the main data here.
  • Footnotes – three kinds of footnotes may be included at the end of a table.
  • Source notes identify the data source or, if the table is reproduced without change, the original published work.
  • General notes apply to the table as a whole.
  • Specific notes apply to specific numbers or rows or columns in the table.
  • Rules – these lines visually separate the table into parts. In general, use horizontal rules.

Table Design Rules

A table should contain at least:

  • Two columns
  • Six cells of information: two columns and three rows, or three columns and two rows.

Thousands of templates to jump start your project

Acceptance Test Plan

Contingency Plan

Software Development Templates

Acquisition Plan

Conversion Plan

Software Requirements Specification

Action Plan

Cost Benefit Analysis

Software Testing

API Documentation

Database Design

Standard Operating Procedures (SOP)

Audience Analysis

Datasheet

Statement of Work

Availability Plan

Deployment Plan

System Administration Guide

Bill of Materials

Design Document

System Boundary

Business Case

Disaster Recovery Plan

System Design Document

Business Continuity

Disposition Plan

System Specifications

Business Plan

Documentation Plan

Technical Writing Templates

Business Process

Employee Handbook

Test Plan

Business Requirements

Error Message Guide

Training Plan

Business Rules

Expression of Interest

Transition Plan

Capacity Plan

Fact Sheet

Troubleshooting Guide

Case Study

Feasibility Study

Use Case

Change Management Plan

Functional Requirements

User Guide

Communication Plan

Grant Proposal

Verification and Validation Plan

Concept of Operations

Implementation Plan

White Papers

Concept Proposal

Installation Plan

Work Instructions

Configuration Management Plan

Interface Control Document

Software Development Templates

Acceptance Test Plan

Maintenance Plan

Software Requirements Specification

Acquisition Plan

Market Research

Software Testing

Action Plan

Marketing Plan

Standard Operating Procedures (SOP)

API Documentation

Needs Statement

Statement of Work

Audience Analysis

Operations Guide

System Administration Guide

Availability Plan

Policy Manual

System Boundary

Bill of Materials

Project Plan

System Design Document

Business Case

Proposal Manager Templates

System Specifications

Business Continuity

Proposal Template

Technical Writing Templates

Business Plan

Quality Assurance Plan

Test Plan

Business Process

Release Notes

Training Plan

Business Requirements

Request for Proposal

Transition Plan

Business Rules

Risk Management Plan

Troubleshooting Guide

Capacity Plan

Scope of Work

Use Case

Case Study

Security Plan

User Guide

Change Management Plan

Service Level Agreement (SLA)

Verification and Validation Plan

Communication Plan

Setup Guide

White Papers

Concept of Operations

Social Media Policy

Work Instructions

Concept Proposal

Contingency Plan

 

Configuration Management Plan

Conversion Plan

 

 

Want More Writing Tactics?

Over 127,000 readers rely on Klariti every month. Sign up now for Ivan’s fresh writing strategies, practical advice, and resources delivered to your inbox each week.