Email Metadata
SPENCER JONES made this Official Information request to New Zealand Defence Force
Currently waiting for a response from New Zealand Defence Force, they must respond promptly and normally no later than (details and exceptions).
From: SPENCER JONES
Dear New Zealand Defence Force, Veterans Affairs (VANZ),
Official Information Act Request
I request email metadata relating to communications concerning the Veterans’ Advisory Board (VAB).
Specifically, I request the following information for emails sent or received by Veterans’ Affairs New Zealand staff, the Secretariat of Veterans’ Boards, or relevant NZDF policy teams:
1. Email subject lines.
2. Sender and recipient fields (To/From only).
3. Date and time of the email.
4. The mailbox or organisational unit associated with the email.
This request relates only to emails referencing:
• "Veterans’ Advisory Board"
• "VAB"
• "VAB advice"
• "Veterans Advisory Board recommendation"
Timeframe: 1 January 2014 to present.
For clarity, I am not requesting the content of emails at this stage—only the metadata fields listed above.
Providing metadata only should significantly reduce the scope of collation.
If the information is held in an email archive or records management system, a simple export of the relevant metadata fields would satisfy this request.
If any part of this request is considered likely to be refused under section 18(f), I am willing to discuss refining the scope.
Kind regards,
Spencer Jones
From: Ministerial Services
New Zealand Defence Force
Good morning Spencer
Your request below has been received and a decision on your request will be provided as soon as possible and no later than Thursday 16 April 2026. Responses to requests for information that are considered to be in the wider public interest will be published on the New Zealand Defence Force website (www.nzdf.mil.nz).
Regards
Corporate and Ministerial Services
Office of the Chief of Defence Force
New Zealand Defence Force | Te Ope Kātua o Aotearoa
www.nzdf.mil.nz
show quoted sections
Things to do with this request
- Add an annotation (to help the requester or others)
- Download a zip file of all correspondence (note: this contains the same information already available above).


SPENCER JONES left an annotation ()
Public Annotation – Email Metadata (Veterans’ Advisory Board Advice and Related Communications)
This request sought email metadata (rather than full email content) relating to communications involving Veterans’ Advisory Board (VAB) advice and associated policy discussions. The request focuses on identifying the existence, timing, and flow of communications across agencies, without requiring disclosure of substantive email content.
This is a targeted investigative approach designed to reveal communication patterns, decision pathways, and potential gaps in formal record-keeping.
Key observations from the response:
1. Metadata vs Content Distinction
Email metadata typically includes:
• sender and recipient fields
• dates and timestamps
• subject lines
• message identifiers or thread references
This information allows reconstruction of communication networks and timelines without accessing the full content of emails.
Where metadata is unavailable, limited, or difficult to extract, this may indicate:
• system limitations in retrieving structured metadata
• lack of centralised logging or indexing of communications
• or constraints in how searches are conducted
2. Communication Traceability
The response provides insight into whether communications relating to VAB advice can be:
• systematically identified
• traced across individuals or agencies
• reconstructed into a coherent timeline
If identification relies on keyword searches or manual review, this suggests:
• communications are not consistently tagged or categorised
• traceability depends on search assumptions rather than structured data
3. Fragmentation Across Systems
Email communications may be distributed across:
• individual inboxes (Outlook or similar systems)
• shared mailboxes
• archived systems or records management platforms
If the response indicates partial holdings or limitations, this reflects:
• decentralised storage of communication records
• potential variability in retention practices
• difficulty in producing a comprehensive dataset
4. Completeness and Search Limitations
Metadata responses are often constrained by:
• the choice of search terms
• timeframes applied
• identification of relevant custodians (staff members)
If these parameters are not clearly defined, the resulting dataset may:
• exclude relevant communications
• underrepresent the volume or scope of interaction
• reflect only a subset of actual activity
5. Governance Chain Insight
Email metadata represents a critical layer in the advisory-to-decision chain:
• VAB Advice (formal advisory input)
• Email Communications (informal and interagency coordination)
• Ministerial Briefings (formal policy advice)
• Cabinet Papers (executive decision-making)
Where formal documentation lacks traceability, email metadata can provide:
• evidence of discussions not captured in formal records
• timing of key interactions
• identification of decision-making participants
6. Transparency and Accountability Implications
The ability (or inability) to produce email metadata has implications for:
• transparency of internal communication processes
• accountability for how advisory input is discussed and developed
• confidence in the completeness of official records
Where metadata is incomplete or difficult to extract, this may limit external scrutiny.
7. Record-Keeping and System Design
The response provides indirect insight into:
• how email systems integrate (or do not integrate) with formal records management systems
• whether communications are routinely captured into official record systems
• the extent to which informal communications are preserved
This is particularly relevant where key decisions or discussions occur via email but are not formally recorded elsewhere.
8. OIA Strategy Insight
This request demonstrates an advanced investigative technique:
• requesting metadata rather than content to reduce refusal risk
• mapping communication flows across agencies
• identifying key actors and timeframes for further targeted requests
Effective follow-up strategies may include:
• requesting specific email threads once identified via metadata
• targeting named individuals or roles revealed in metadata
• aligning communication timelines with briefing and Cabinet records
9. System-Level Observation
When read alongside related OIA requests concerning:
• VAB advice generation
• ministerial briefing processes
• Cabinet-level consideration
• implementation tracking
this request contributes to a comprehensive mapping of how information moves through government systems.
A consistent pattern may emerge:
• formal records (briefings, Cabinet papers) provide structured outputs
• but underlying communication pathways are less structured and more difficult to trace
Email metadata helps bridge this gap by revealing the informal layer of governance.
This annotation is intended to assist future researchers in understanding the role of communication metadata in reconstructing decision-making processes under the Official Information Act 1982.
Link to this