This template separates two distinct questions for every sending service: who approved it for business use, and what its authentication evidence shows. A service can pass DMARC and still have nobody in the business who currently approves its use. DMARC provides domain-use validation, and that validation does not establish a service’s current business approval. Keeping the two separate, and the table layout below, are workflow recommendations rather than requirements of any standard. This worksheet is an internal practice: every row gets an owner who chases its open gaps.
Before opening the first record, log the organization or client name, the register maintainer, and where evidence artifacts live. Next, gather your active service inventory, the owners for each service, and whatever reporting feeds or server logs you have access to. Where inventory has blind spots, state them openly instead of assuming complete coverage. When you know an application sends email but it never shows up in reports, keep a record marked as not observed. The wider discovery task belongs to the sender inventory procedure.
Filling in one record in evidence order
Create one record per sending account and stream. If an application uses different identities or serves multiple business purposes, give each path its own row; combining them muddies which evidence backs which decision. Long evidence stays in a note keyed to the record ID so the table stays readable.
- Record and scope: assign a local ID and record the client or organization, the vendor service, the specific account or tenant identifier, and the functional stream.
- Responsible people: document the business owner, the technical contact and, when relevant, the DNS or change contact. Include contact details in the linked evidence note. A single engineer or manager can hold multiple roles.
- Domains, selector and IPs: record the visible
Fromdomain, the SPF-evaluatedMAIL FROMidentity, the DKIM signing domaind=and selectors=, along with connecting IP addresses when available. Clearly separate intended configuration from observed traffic data. These values come directly from DMARC aggregate domain identities and DKIM domain and selector fields. An IP address on its own does not identify an account or establish sending permission. - Evidence references: link the inventory ticket and dated authorization note, or explain why either record is absent. For aggregate reports, log the reporter and report_id, the UTC reporting interval, and the specific row selector, IP and count. For raw email samples, capture the message identifier, receiving server evaluator, and the trust basis for Authentication-Results, because a header you cannot trace to a trusted evaluator proves little.
- Business and technical assessments: track business authorization as confirmed, pending, withdrawn, or unknown, noting the approval date and reference ticket. Separately, document technical findings as pass, fail, or not observed, keeping underlying authentication results distinct from DMARC alignment and disposition. The business labels are local workflow choices, not terms from a standard.
- Next action and review: write down the unresolved question, the assigned owner, the deadline, and the scheduled recheck trigger. Link previous decision logs and preserve historical evidence rather than overwriting past entries.
Fill every field deliberately. If an answer is unknown, explain why and schedule a review. Only mark a field N/A if you can state why it doesn’t apply.
| Record and scope | Responsible people | Domains, selector and IPs | Evidence references | Business and technical assessments | Next action and review |
|---|---|---|---|---|---|
| … | … | … | … | … | … |
A synthetic example: DMARC passes, business confirmation is pending
Everything in this section is invented, including the people, dates, service and evidence references. Notes A to D are illustrative notes, not existing files or checks anyone performed.
Note A, REQ-27, 2026-09-12. Example Support requests Case Notices, account tenant-42, for automated case updates sent from notify.example.com. The assigned business owner is Mira Chen, the technical lead is Leon Fox, and the DNS administrator is Noor Vale. Mira’s approval is pending, meaning no official sign-off date exists yet.
Note B, REP-27. Reporter example.org; report_id=reg-27@example.org; window 2026-09-10 00:00 UTC to 2026-09-11 00:00 UTC. The selected row lists source_ip=192.0.2.64, count=42, header_from=notify.example.com, and envelope_from=bounces.example.net. Discovered policy: domain notify.example.com, p=none, adkim=s, aspf=s, and discovery_method=treewalk. Underlying results show DKIM domain notify.example.com with selector case7 passing, while SPF domain bounces.example.net with scope mfrom passes. Evaluated policy output in policy_evaluated: DKIM pass, SPF fail, disposition none. For this exercise, assume the report’s provenance is established; the excerpt leaves out the full XML.
Note C, MSG-27, collected 2026-09-10 09:15 UTC. Visible From domain is notify.example.com; evaluating gateway is mx.example.org, assumed trusted within the receiving system. Evaluation shows DKIM pass for header.d=notify.example.com and header.s=case7, SPF pass for smtp.mailfrom=bounces.example.net, and DMARC pass for header.from=notify.example.com. This sample aligns with Note B, though it does not prove that every message counted in B was identical.
Note D, NOTE-27, 2026-09-14. Leon asks Mira to sign off on the service by 2026-09-16. Review the record on that date or earlier if she replies. These are example dates, not a required observation window.
| Record and scope | Responsible people | Domains, selector and IPs | Evidence references | Business and technical assessments | Next action and review |
|---|---|---|---|---|---|
| R-27; Example Support; Case Notices; tenant-42; case-status notifications (A) | Business: Mira Chen; technical: Leon Fox; DNS/change: Noor Vale (A) | From and DKIM d=: notify.example.com; MAIL FROM: bounces.example.net; DKIM s=: case7; IP: 192.0.2.64 (B/C) | A: request; B: REP-27 selected row, 42 messages in its stated period; C: MSG-27 sample; D: NOTE-27 | Business: pending, no approval date (A). Technical: DMARC pass through aligned DKIM in B/C; SPF passes but is unaligned (B/C) | Leon coordinates Mira’s confirmation by 2026-09-16; review on that date or earlier if she replies; history: NOTE-27 (D) |
Entry R-27 is built from the four notes. The scope and people come from Note A, the observed domains and authentication results originate from Notes B and C, and the pending task comes from Note D. The visible header domain matches the DKIM signing identity notify.example.com, fulfilling strict alignment, while bounces.example.net differs. Under standard evaluation, a single aligned authenticated identifier is sufficient for DMARC to pass. The volume of 42 messages applies solely to that specific report row and period: it does not reflect the total volume of the service, nor does it represent an inbox-delivery count. Passing authentication by itself provides no inbox guarantee. The new authorization stays on hold pending Mira’s decision; nothing here says that existing sending was stopped, and nothing here authorizes enforcement. If you want a refresher on identity matching, the guide covers what DMARC alignment means.
What happens when the owner or the evidence is missing?
When an entry lacks an identified business owner or authorization ticket, business approval remains pending and the request goes to the business owner or the domain or account administrator. Technical misconfigurations affecting legitimate traffic go to the engineering contact, and any planned policy tightening must wait until those authentication gaps are resolved. Incomplete or suspicious telemetry stays on hold: never base policy changes on malformed reports or potential forged information until you’ve verified the source.
Cross-reference unverified senders against internal inventories. If unapproved or unidentified sending traffic continues, escalate the stream to security using the DMARC investigation runbook. STOP applies to the dependent decision; it is not an automatic blanket pause of live mail. Resume the affected decision only after its specific gap is resolved and the updated evidence or approval, the reviewer and the date are recorded.
A record is usable when a colleague could reconstruct both assessments from it and find the next owner. Unverified evidence, unexplained domain identities, or a vague scope keep the decision on hold. Pay close attention to seasonal, batch, or disaster-recovery services: receivers may omit reports entirely, so match observation windows to real-world sending cadence. No static observation timeline applies to every sender. I’d recommend reviewing a record after any change of account, owner, provider, domain or selector, and before you rely on it for another change.
Frequently asked questions
Does a DMARC pass mean the business has approved the service?
No. A sending service can pass DMARC even though nobody in the business has approved it. DMARC validates domain authorization technically, but it cannot confirm whether anyone in your organization approved the tool for company use.
Does an IP address identify the sending account?
No. An IP address indicates a connecting server, not an account tenant or authorized user. Note connecting IPs when available, but always distinguish requested configuration from observed server data.
Does the message count in a DMARC report show the service’s total volume?
No. The count of 42 messages in this example reflects only that specific report row and reporting period. It represents neither total sending volume across all recipients nor inbox delivery.
Can a service that never appears in reports have a record?
Yes. A service you know about but never see in reports can still have a record, marked “not observed.” Receivers may omit reports, so note the evidence gaps for seasonal, infrequent and standby mail.
Does STOP mean pausing all live mail?
No. A STOP decision applies strictly to the pending change or promotion under review. You only resume the rollout once the specific ownership or technical gap has been formally resolved and documented.


