Structure and Focus of the Technical Guidance

1. Outcome

This Circular explains how the Technical Guidance on Ocean Accounting is organised, defines the meta-structure that each circular follows, describes the production process for circulars, and establishes the publication cadence. Authors and editors will understand the standard structure for new circulars and the conventions for versioning, stability classification, and dependency tracking.

2. Requirements

None—this Circular serves as a standalone reference for authors, editors, and users of the Technical Guidance.

3. Organisation of the Technical Guidance

3.1 Section Structure

The Technical Guidance is organised into seven sections:

3.2 Circular Numbering

Each circular is identified by: TG-[Section].[Number]

• TG-0.1: Technical Guidance, Section 0, Circular 1
• TG-3.9: Technical Guidance, Section 3, Circular 9
• TG-6.12: Technical Guidance, Section 6, Circular 12

Version numbers are appended when referencing specific versions: TG-0.1-v2.0

3.3 Stability Classification (Badges)

Each circular carries a stability badge indicating its relationship to underlying standards. See Circular 0.5 for full details. Summary:

4. Circular Meta-Structure

All circulars follow a standard structure to ensure consistency and predictability for readers. This section specifies the template for circular authors.

4.1 YAML Frontmatter Specification

Every circular begins with machine-readable YAML frontmatter:

---
id: TG-X.Y                    # Required: Circular identifier
title: "Circular Title"       # Required: Full title
badge: Applied                # Required: Core | Applied | Emerging | Pilot | null
version: "1.0"                # Required: Major.Minor version
status: Planned               # Required: Planned | Draft | Review | Completed | Priority
prerequisites:                # Required: List of prerequisite circular IDs
  - TG-0.1
  - TG-X.Z
enables:                      # Optional: List of circulars this one enables
  - TG-A.B
toc: true                     # Optional: Enable table of contents (default: true)
---

Field definitions:

Status Values:

4.2 Metadata Display Block

Immediately after the title, include a metadata table for reader reference:

<div class="circular-meta">

| Field | Value |
|-------|-------|
| **Circular ID** | TG-X.Y |
| **Version** | 1.0 |
| **Badge** | Applied |
| **Status** | Completed |
| **Last Updated** | Month Year |

</div>

4.3 Standard Section Structure

Standard Circular Template (Sections 1-4, 6)

# Circular Title

<div class="circular-meta">
[Metadata table]
</div>

## 1. Outcome
[What readers will achieve — 1-2 paragraphs]

## 2. Requirements
[Prerequisites with hyperlinks to other circulars]

## 3. Guidance Material
### 3.1 [Topic]
### 3.2 [Topic]
...
[Core methodology — bulk of content]

## 4. Limitations and Considerations (optional)
### 4.1 Data Quality Caveats
### 4.2 Methodological Limitations
### 4.3 Risks of Misapplication
[Uncertainties, caveats, edge cases — when relevant]

## 5. Acknowledgements
**Authors:** [Names and affiliations]
**Reviewers:** [Names]

## 6. References
[Footnotes or bibliography]

## Appendixes (if needed)
### A. Worked Example
### B. Sample Code
### C. Detailed Tables

Case Study Template (Section 5)

Section 5 circulars use an adapted structure for country/regional case studies:

# Case Study: [Country/Region]

<div class="circular-meta">
[Metadata table including Focus field]
</div>

## 1. Outcome
[What readers will achieve]

## 2. Requirements
[Prerequisites]

## 3. Country/Regional Context
[Geographic, institutional, policy context]

## 4. Implementation Approach
### 4.1 Institutional Arrangements
### 4.2 Data Sources
### 4.3 Methods Applied

## 5. Accounts Developed
[Description of accounts compiled]

## 6. Decision Applications
[How accounts informed policy]

## 7. Lessons Learned
### 7.1 Successes
### 7.2 Challenges
### 7.3 Recommendations

## 8. Acknowledgements

## 9. References

## Appendixes

Front Matter Template (Section 0)

Section 0 circulars have unique structures appropriate to their purpose:

• 0.1 General Introduction: Extended conceptual content with figures
• 0.5 Navigating: Primarily visual/tabular (dependency graphs, pathways)
• 0.6 Glossary: Definition list format organised alphabetically
• 0.7 QA Principles: Reference document format with standards citations

4.4 Section Content Guidelines

Section 1: Outcome

Purpose: State what readers will achieve by reading this circular.

Guidelines:

• 1-2 paragraphs maximum
• Use active voice: "Readers will understand..." or "This circular enables..."
• Be specific about the capability or knowledge gained
• Reference the policy or technical context if relevant

Example:

This Circular provides guidance on compiling asset accounts for ocean accounting, including both physical and monetary accounts for individual environmental assets (natural resources) and ecosystem assets. Readers will understand how to structure opening and closing balance sheets, record changes during the accounting period, and link asset accounts to flow accounts.

Section 2: Requirements

Purpose: List prerequisites so readers can assess their readiness.

Guidelines:

• List prerequisite circulars with hyperlinks
• Use the standard format: **[TG-X.Y Title](/path)** – brief description
• Include any non-circular prerequisites (e.g., knowledge of specific tools)
• "None" is acceptable for entry-point circulars

Example:

This Circular requires familiarity with:

- **[TG-0.1 General Introduction](/circulars/section-0/0-1-general-introduction)** – for the conceptual framework
- **[TG-0.2 Standards Overview](/circulars/section-0/0-2-standards-overview)** – for SEEA EA ecosystem condition methodology
- **[TG-3.1 Assets](/circulars/section-3/3-1-assets)** – for ecosystem extent and condition accounts that feed indicators

Section 3: Guidance Material

Purpose: The core content of the circular—methods, procedures, explanations.

Guidelines:

• Use hierarchical subsections (3.1, 3.2, 3.1.1, etc.)
• Include worked examples where applicable
• Reference international standards (SEEA, SNA) with specific paragraph numbers
• Use tables for structured information
• Include figures/diagrams for complex concepts
• Cross-reference related circulars

Section 4: Limitations and Considerations (Optional)

Purpose: Help users understand caveats, uncertainties, and risks of misapplication.

Guidelines:

• Include when the methodology has significant limitations or assumptions
• Not required for every circular—use when genuinely helpful
• Flexible length—a few paragraphs may suffice
• Cover: data quality caveats, methodological limitations, common misinterpretations, edge cases

Example topics:

• "This method assumes stable ecosystem condition; in rapidly changing systems, more frequent assessment may be needed."
• "Valuation results should not be used for cost-benefit analysis without additional adjustment for..."
• "The classification may not capture traditional use categories relevant in some Pacific Island contexts."

Section 5+: Acknowledgements and References

Acknowledgements:

• List authors with affiliations
• List reviewers
• Note any adapted content sources

References:

• Use footnote format for in-text citations
• Group references at end
• Include DOIs or stable URLs where available

5. Page Length Guidance

Circulars should be comprehensive but focused. Target lengths by section:

These are guidelines, not strict limits. Prioritize clarity and completeness over brevity.

6. Version and Revision Policy

6.1 Version Numbering

Format: v[Major].[Minor]

• Major version (v1.0 → v2.0): Substantive content changes

  • New standards incorporated (e.g., UNSC adoption of SEEA-Oceans)
  • Significant methodological corrections
  • Structural reorganisation

• Minor version (v1.0 → v1.1): Editorial improvements

  • Clarifications based on user feedback
  • Added examples or worked problems
  • Typographic corrections
  • Updated cross-references

6.2 Revision Policy

• All circulars undergo annual review to assess whether updates are needed
• Core circulars are updated only when underlying standards change
• Applied and Emerging circulars may be updated based on implementation experience
• Pilot circulars are evaluated for promotion, revision, or withdrawal after pilot period

6.3 Superseded Versions

• Superseded versions remain accessible with archival notice
• Archive URL format: /circulars/archive/TG-X.Y-v1.0
• Current version always appears at canonical URL

7. Production Process

7.1 Circular Development Workflow

1. Scoping        → Define purpose, audience, dependencies
2. Drafting       → Write content following template
3. Internal Review → GOAP Secretariat editorial review
4. Expert Review  → Technical Expert Panel review
5. Revision       → Address review comments
6. Publication    → Publish with DOI assignment
7. Maintenance    → Annual review and updates

7.2 Publication Cadence

• New circulars published on a monthly cadence following Expert Panel review
• Priority circulars may be fast-tracked
• Updates to existing circulars published as needed

7.3 Review Standards

The Technical Expert Panel reviews circulars for:

• Technical accuracy: Alignment with SNA, SEEA, and other standards
• Clarity: Accessibility to target audience
• Completeness: Coverage of essential topics
• Consistency: Alignment with other circulars in the Technical Guidance
• Practicality: Implementability with available data and resources

8. Dependency and Prerequisites

8.1 Dependency Tracking

Dependencies are tracked in two ways:

1. YAML frontmatter: prerequisites and enables fields in each circular
2. Prose requirements section: Human-readable list with hyperlinks

These must be kept synchronised.

8.2 Dependency Principles

• Explicit prerequisites: Only list circulars that are genuinely required
• Minimal dependencies: Avoid unnecessary prerequisites that create barriers
• Transitive closure: If A requires B and B requires C, A need not list C explicitly
• Bidirectional tracking: When adding a prerequisite, update the enables field of the prerequisite circular

8.3 Dependency Graph

See Circular 0.5 Navigating the Technical Guidance for the visual dependency graph showing relationships between all circulars.

9. Cross-Cutting Themes

Some topics span multiple sections and are addressed as "threads" rather than standalone circulars:

Authors should ensure consistency in treatment of cross-cutting themes and reference the primary circular for each theme.

10. Acknowledgements

Authors: GOAP Secretariat

Reviewers: GOAP Technical Expert Panel

11. References

1. GOAP. (2024). Discussion Paper: Modular Structure for GOAP Technical Guidance. Global Ocean Accounts Partnership.

2. United Nations. (2025). System of National Accounts 2025. United Nations.

3. United Nations. (2021). System of Environmental-Economic Accounting—Ecosystem Accounting. United Nations.

4. UNECE. (2019). Generic Statistical Business Process Model (GSBPM), Version 5.1.