Study guide
8.1 Designing Tables & Statistical Exhibits
CAS Property & Casualty Predictive Analytics PCPA
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: PCPA Exam & Project Orientation
1.1 PCPA Exam Format, Scoring & Registration 1.2 The PCPA Project: Windows, Deliverables & Grading
2 Chapter 2: Dealing with Data — Sourcing, Importing & Assessing
2.1 Requirements Gathering & Assessing Data Relevance 2.2 Importing, Joining & Reshaping Data Sets 2.3 Exploratory Data Analysis & Evaluating a Data Set 2.4 Data Quality Under ASOP 23 & Modeling Under ASOP 56
3 Chapter 3: Dealing with Data — Conditioning P&C Data for a GLM
3.1 Exposure Bases, Weights & Data Grain 3.2 Missing Data Mechanisms & Imputation Strategies 3.3 Outlier Diagnostics, Trimming & Winsorization 3.4 Variable Transformation & Scaling
4 Chapter 4: Model Diagnostics & Selection — Building a GLM
4.1 Exponential Dispersion Family & Link Functions 4.2 Poisson Regression & Exposure Offsets 4.3 Overdispersion, Quasi-Poisson & Negative Binomial 4.4 Gamma & Inverse Gaussian Models for Claim Severity
5 Chapter 5: Model Diagnostics & Selection — Model Form & Predictors
5.1 Tweedie Compound Poisson-Gamma Modeling 5.2 Binomial & Logistic GLMs for Binary Outcomes 5.3 Categorical Predictors, Base Levels & High-Cardinality Grouping 5.4 Interaction Terms & Non-Linear Effects 5.5 Interpreting Coefficients & Multiplicative Relativities
6 Chapter 6: Model Diagnostics & Selection — Evaluating and Improving the Fit
6.1 Deviance, Likelihood Ratio Tests & Residual Diagnostics 6.2 Stepwise Selection & Information Criteria Penalties 6.3 Multicollinearity, Correlated Predictors & Aliasing 6.4 Under-fitting, Over-fitting & Cross-Validation
7 Chapter 7: Model Diagnostics & Selection — Validation & Model Choice
7.1 Actual vs. Predicted, Calibration & Loss Ratio Charts 7.2 Simple Quantile Plots & Measuring Lift 7.3 Double Lift Charts & Competing Model Evaluation 7.4 Gini Index, Lorenz Curves & ROC Curves
8 Chapter 8: Model Interpretation & Presentation — Tables, Charts & Exhibits
8.1 Designing Tables & Statistical Exhibits 8.2 Chart Selection & Graphical Perception 8.3 How Charts Mislead 8.4 One-Way, Two-Way & Partial Dependence Exhibits
9 Chapter 9: Model Interpretation & Presentation — Communicating the Analysis
9.1 Communicating Methodology & Modeling Decisions 9.2 Explaining Why a Variable Was or Was Not Included 9.3 Communicating to Non-Technical Audiences 9.4 The PCPA Technical Report: Structure & Rubric
8.1 Designing Tables & Statistical Exhibits
Key Takeaways Explain This Topic AI
Few's rule of thumb is that a table is right when the audience needs to look up individual values or compare precise numbers, and a graph is right when the message is in the shape of the data.
Numbers in a column should be right-aligned with a consistent number of decimal places so that magnitude is readable down the column.
Significant digits should reflect the precision the decision needs: a relativity of 1.0837 implies a credibility the data rarely supports.
Heavy gridlines, borders and fill compete with the data; Few's guidance is to reduce non-data ink and let white space do the grouping.
Every exhibit in the PCPA report needs a title that states the takeaway, labelled units, and an exposure or volume column so the reader can judge credibility.
Last updated: September 2026
Tables Are Part of the Assessed Content
PCPA Domain C is Model Interpretation and Presentation , worth 30% of the exam and 40% of the project rubric . Its first task is to "create and interpret statistical/tabular and graphical/visual representations of data." The assigned readings are Few's Show Me the Numbers , Cairo's How Charts Lie , Knaflic's Storytelling with Data , and Gelman and Unwin on infovis versus statistical graphics.
That means table and chart design are examinable content, not presentation polish. And on the project, with a hard cap of five tables or supporting graphics and 1,250 words including appendices , every exhibit has to earn its place.
Table or Graph?
Few's test is about what the reader must do with the numbers.
- Use a table when Use a graph when
- The reader must look up individual values The message is in the shape, trend, or comparison
- Precise values matter (a filed relativity, a fee) Approximate magnitude is enough
- Units differ across rows (counts, dollars, ratios) All values share one unit and scale
- Both summary and detail are needed at once Many data points must be compared at a glance
A fitted GLM's coefficient table is a table: the reader needs the number. A pattern of loss cost across ten deciles is a graph: the reader needs the shape.
The common failure is the table used as a graph — twenty rows of numbers where the point was simply "it rises then flattens." The reader has to do the visual work the analyst should have done.
Alignment, Precision, Order
Three mechanical choices decide whether a table can be read quickly.
Align numbers right, with a consistent number of decimals. Right alignment puts the ones digit under the ones digit, so magnitude is visible down the column without reading every value. Mixed decimal places destroy that; 1.2 , 0.85 and 12.417 in one column force the eye to parse each entry. Align text left. Align column headers with their data.
Show only the precision the decision needs. A territory relativity printed as 1.0837 claims four significant digits of accuracy from data that may contain 300 claims. Round to the precision the decision actually uses — usually three digits for a relativity, whole dollars for a pure premium, one decimal for a percentage. Over-precision is a quiet credibility claim, and a reviewer will notice.
Order rows by something meaningful. Alphabetical order is the default and almost never the most useful. Order by magnitude when the reader is looking for the biggest effect, by a natural sequence (age band, vehicle age, policy year) when the order carries meaning, and keep a consistent order across related tables so the reader can compare them.
Reduce the Non-Data Ink
Few's central design idea is that anything on the page that is not data competes with the data. In practice:
Drop vertical gridlines entirely; use white space to separate columns.
Use at most a light horizontal rule under the header and above a total row.
Avoid fill colour and shading in every other row unless the table is very wide.
Use one highlight — bold, or a single colour — and use it only on what the reader should notice.
Repeat units in the header ( Pure premium ($) ) rather than on every cell.
The goal is not minimalism for its own sake. It is that when almost everything is emphasised, nothing is.
What an Actuarial Exhibit Must Carry
Beyond formatting, an actuarial table has content obligations that a generic business table does not:
Volume. Exposure, claim count, or record count for every row. Without it, the reader cannot tell a credible relativity from noise. This single column is the most frequently omitted and the most frequently needed.
A basis statement. Policy year or accident year, paid or incurred, gross or net, evaluated as of when.
Units. Dollars, car-years, per 100 of payroll, percentage points.
A title that states the finding , not the mechanics. "Loss cost rises 3.1x from the best to the worst decile" tells the reader something; "Table 2: Model output by decile" does not.
Two Tables Worth Building for the Project
The coefficient / relativity table. This is the exhibit that satisfies the rubric criterion "candidate generates and provides technical output (e.g. indicate coefficients from the model)" .
- Level Exposure (car-yrs) Coefficient Relativity e β e^{\beta} e β Std. error p-value
- Territory 1 (base) 41,200 — 1.000 — —
- Territory 2 38,750 0.182 1.200 0.041 <0.001
- Territory 3 22,410 0.336 1.399 0.058 <0.001
- Territory 4 3,180 0.511 1.667 0.214 0.017
Everything a reviewer needs is present: the base level is identified, both the coefficient and its exponentiated relativity are shown, exposure lets the reader see that Territory 4's 1.667 rests on thin data, and the standard error confirms it.
The model comparison table. One row per candidate model, columns for the diagnostics you used to choose between them — degrees of freedom, deviance, AIC, BIC, and an out-of-sample statistic. This single table can carry the rubric criteria "describes which model they selected and why" and "explains what they did to iteratively check and build their model" in far fewer words than prose.
Warning
On the project, tables and graphics share one allowance of five. A coefficient table, a model comparison table, and a validation chart already use three. Decide the full exhibit set before you build any of them, and do not spend an allowance on a chart that merely restates a number already in the text.