Harris Matrix Software for Stratigraphic Excavation

The Harris Matrix has been the standard for representing archaeological stratigraphy since Edward Harris introduced it in 1973. Building one by hand on graph paper still works for small excavations. For anything larger — multi-season urban excavations, deeply stratified sites, projects with multiple recorders — the matrix becomes hard to maintain on paper, and harder to keep synchronized with the underlying context records.

This guide walks through what's available for digital Harris Matrix support in 2026, where each tool fits, and the workflow that keeps stratigraphy and field records aligned.

What a good Harris Matrix workflow looks like

In an ideal workflow:

Each context (cut, fill, layer, structure) is recorded as a discrete record in the field
Each context's stratigraphic relationships (above, below, equal-to, cut-by, fills, abuts) are recorded as part of the context record, not in a separate matrix tool
The matrix is generated from the relationship data, not drawn separately
Updates to the underlying context data flow into the matrix automatically

The pain in most current workflows is that the matrix is drawn separately from the context records, which means it drifts. Someone updates a context's relationships in the matrix without updating the context record, or vice versa, and by the end of the season the matrix and the records disagree.

Tools that exist in 2026

The Harris Matrix software landscape is small. The main options:

Stratify (and ArchEd)

Specialized matrix-drawing tools. Powerful for large matrices, with automatic layout. Lacks integration with field recording tools — you maintain the matrix as a separate dataset, with the synchronization burden on the user.

Best for: Site directors building a finalized matrix from a complete dataset, post-fieldwork.

Hand-drawn (still common)

For excavations with under ~50 contexts. Quick, no software learning curve. Falls apart fast as the matrix grows.

Best for: Small excavations, pedagogical use, initial sketching.

Spreadsheet-based matrix construction

Some firms build their matrix as a relationship table in Excel and export to a graphing tool. Tedious but flexible.

Best for: Firms with strong data-management practices, willing to maintain the relationship table.

Field-tool-integrated approaches

Some archaeology field tools (FieldTap, certain custom university platforms) capture stratigraphic relationships as part of the context record itself. The matrix is generated from the relationship data, eliminating the synchronization problem.

Best for: Long-running excavations, firms running multiple deep-stratified sites.

What to look for in a digital matrix workflow

If you're evaluating a digital approach:

Relationship capture at the context record level. Stratigraphic relationships should be a property of the context, not a separate tool's responsibility.
Bidirectional consistency. If context A is "above" context B, the system should know context B is "below" context A — automatically.
Validation. Cycles (a context above itself), missing terminators, and orphan contexts should be flagged.
Export to a standard format. Matrix data should be exportable for use in Stratify or similar tools when needed for publication or final analysis.
Integration with photographs and finds. Each context's photos, samples, and finds should be linked, so the matrix view also gives access to the supporting record.

Common pitfalls

The mistakes that cost firms time:

Recording stratigraphic relationships in field notebooks but not in the digital record. Notebook gets lost or unreadable; relationships are gone.
Drawing the matrix in a separate tool without a synchronization process. By end of season, the matrix and the records don't agree.
Inconsistent terminology between recorders. "Cuts" vs "is cut by" — the relationships have to be canonical or the matrix breaks.
Not validating the matrix during the dig. Errors caught after fieldwork are much more expensive to fix than errors caught the next day.

A practical workflow for a multi-season urban excavation

For a deeply stratified site running over multiple seasons:

Every context is recorded digitally at exposure, with a context-type designation (cut, fill, layer, structure, etc.) and a relationship list.
Relationships are entered using the canonical terms — "above," "below," "equal-to," "cut-by," "fills," "abuts."
At end of day, a matrix preview is auto-generated and reviewed by the site director. Anomalies (cycles, missing terminators, contexts with no relationships) are flagged for follow-up the next morning.
At end of season, the relationship dataset is exported to Stratify or a similar tool for publication-quality matrix layout.
Throughout, photos and finds are linked to context records, so anyone navigating the matrix can immediately access the supporting evidence.

This workflow scales. The "draw the matrix on graph paper" workflow does not.

Where this fits in a broader CRM tech stack

For most CRM firms, deeply stratified excavations are a small fraction of total work — most projects are Phase I surveys, isolated finds, and shallow Phase II testing. But for firms that do excavate, having a digital workflow that handles stratigraphy as part of the field recording (rather than as a separate post-process) is the difference between a clean dataset and a season of reconciliation.

Related guides

If you're running deeply stratified excavations and want to evaluate FieldTap's stratigraphy support, start a free 30-day trial — no credit card required.