Datuma
Private page for Calder and Wren
Full check · Calder and Wren

Your working file is back

This is your working file: every row that nothing stopped, each with a way to reach the person. No Datuma review is waiting on you. The Decision Brief records the rows placed by a person's review of a possible change of role or organisation, and what we decided on each.

This file was compiled on 30 September 2026.

Your file
calder_and_wren_contacts_export.csv
Rows received
2,400
Checked
24 to 29 September 2026

Start here

What came back, what is waiting on you, and which file is for which job.

What came back

Rows receivedThe rows in the file you sent us.
2,400
In your working fileThe rows that nothing stopped. Where a check went unanswered or an address was withheld, the finding is shown beside the row.
2,075
In your stopped rowsEach one marked STOPPED or PROTECTED, with the reason and the date we checked it.
325
In the Decision BriefOf the rows above, those placed by a person's review of a possible change of role or organisation, with what we decided on each.
58

Waiting on you

Nothing from Datuma is waiting on you.

Every decision Datuma made is already in your working file and your stopped rows.

What READY, STOPPED and PROTECTED mean

Your files and the Row Passports use the same three words. The update file adds flags beside them.

READY Nothing we found required this row to be stopped, and at least one way to reach the person was established. The row is in your working file.
STOPPED A check supported stopping this row, or no way to reach the person could be established. The reason is beside the row. A row marked STOPPED is in your stopped rows, and you can put it back in your own list if you know the contact.
PROTECTED The account is on your own protected accounts list. The row is in your stopped rows, and the reason is that list, not anything we found about the person.

A flag beside a row names a check that went unanswered or a finding worth knowing, such as an address we withheld. The outcome and its reason say where the row was placed and why; flags add what else we found. They never put rows in an order and ask nothing of you.

Which file is for which job

Start with
  • Your working file The rows that nothing stopped, in your own columns and order, with the columns we added. 1,984 of these rows have an address that accepted mail and was not withheld. 66 carry an address we withheld, and 25 have no address. Whether you may send marketing to any of them is not something these checks establish. We check whether a number is live. We do not screen numbers against the Telephone Preference Service (TPS) or the Corporate Telephone Preference Service (CTPS): whether a number may be called for marketing is not something this full check establishes. calder-and-wren_2026-09-30_working_v01.csv
Before you send

Before you send or call, load the withheld addresses into the tool you send from and run your own contact-preference checks: Datuma has not changed anything in your systems. If you disagree with a stopped row, you can put it back in your own list.

The withheld addresses file is a plain list of email addresses for the tool you send from. It holds every address this full check withheld: an address we could not confirm, could not check or found a problem with, an address the person on the row is no longer reached at (a work address after a confirmed move away or where the role there has an end on record, or any address where the wrong person was established), and any address on your do-not-contact list, whatever the row's outcome. Rows kept aside on your protected accounts list are not added to it for being protected. It is not a screening result against any register.

  • The withheld addresses The addresses we withheld, for loading into HubSpot. If you load them through HubSpot's opt-out import, HubSpot sets each contact it holds to unsubscribed from all email and marks any other address as ineligible for email, including addresses we withheld only because we could not confirm or check them. calder-and-wren_2026-09-30_withheld-hubspot_v01.csv
If you need to look into something
  • The stopped rows Every row we stopped or kept aside on your protected list, with the reason and the date we checked it. calder-and-wren_2026-09-30_stopped-rows_v01.csv
  • The Row Passports A card for every row: the outcome, the evidence behind it and, where there is one, the date we checked. It shows the checks and the evidence in this full check. calder-and-wren_2026-09-30_row-passport_v01.html
  • The Decision Brief The rows placed by a person's review of a possible change of role or organisation, with what we decided on each and why. calder-and-wren_2026-09-30_decision-brief_v01.html
If you need the underlying record
  • The update file One row for every row you sent: the outcome, the reason, the dates and what each channel established, keyed on your own record ID. For putting the result beside your own records. calder-and-wren_2026-09-30_datuma-update_v01.csv
  • The changelog What we changed, what we found and left alone, and the evidence for each. calder-and-wren_2026-09-30_changelog_v01.csv

Every file is under Your files, further down this page.

Optional: putting the result beside your own records

The files are usable without importing anything. Your existing CRM and sending tools have not been changed. If you send from them, load the withheld addresses first. The update file has one row for every row you sent, keyed on your own record ID where your file carried one. Import only the columns that start with Datuma, into fields you create for them, as an update to records you already have: never as new records, and never onto your own email, phone, role or organisation fields.

In your system
  • HubSpot. Create the Datuma properties on contacts. Import the update file and choose update existing contacts only. Match the update file's Customer record ID column to the HubSpot property that holds that ID (Record ID, if your file came from a HubSpot export). Set every other column that is not a Datuma property to Don't import, so nothing already in your contacts is overwritten.
  • Any other system, or a spreadsheet. The same rule: match on your own record ID where the update file carries one, bring in only the Datuma columns, and keep your own values as they are. Where the record ID is blank, check each match before importing: an email address is not a safe key on its own. If your record IDs are long numbers, open the update file through your spreadsheet's import, with the record ID column set to text. Opening it directly rounds long numbers, and the lookup then matches the wrong rows.
How to read the update file
  • One row for every row you sent us, with its record ID where your file carried one and a Datuma row ID in every case. Use it to put the result of this full check beside your own records, or to filter the list in a spreadsheet.
  • The first six columns are your own values, copied from your file so you can see who each row is. They are not a request to change anything in your systems.
  • Keep the first six columns for matching and reference. Every other column starts with Datuma: import only those, into fields you create for them. Never map them onto your own email, phone, role or organisation fields.
  • Customer record ID is copied, untouched, from the column you named as your record ID when you ordered, or else from a column named Record ID in your file. Match rows to your records on it where it is filled. Where it is blank, check each match before importing: an email address is not a safe key on its own, because an address can move between people and two records can share one.
  • Datuma row ID names the row inside this check. It is the same in every file of the pack, and the Row Passport card for the row has it as its address.
  • Datuma outcome. READY: nothing we found required this row to be stopped, and a way to reach the person was established; it is in your working file. STOPPED: a check supported stopping the row, or no way to reach the person could be established; it is in the stopped rows. PROTECTED: the row is kept out on your own instruction, because it is on your protected accounts list.
  • An outcome is not a legal judgement and not a statement about whether a person is worth contacting. STOPPED means we found a reason not to work the row as supplied; you may put it back.
  • Datuma flags. Further findings about the row, as FAMILY:CODE, several separated by a semicolon. The families are EMAIL, PHONE, IDENTITY, EMPLOYMENT, DUPLICATE, HISTORY, ROUTE and PROTECTION, and the read-me note gives the meaning of every flag. EMAIL:DO_NOT_USE means the address in the row is on the withheld list and should be kept out of sending. A row can carry several flags. Flags never put rows in an order and never recommend a contact.
  • Datuma reason code and Datuma reason. The main rule that decided where this row was placed, as a fixed code and as a sentence. Other findings are in the flags and in the channel, profile and employment columns.
  • Rows decided by a fixed rule are not in the Decision Brief, which records the rows placed by a person's review of a possible change of role or organisation: the rule is in the reason, the flags and the email status on the row. On a row that is not on your protected accounts list and does not repeat another row in this file, an address at a catch-all domain, one the mail server gave no answer for, or one that was not checked is withheld, and the row stays in your working file only where another way to reach the person was established; where your own number was the only possible way to reach the person and no network check established whether it is live, the row is stopped. Where a possible profile could not be tied to the person, none of its details were used.
  • Datuma checked on. The date this row's result was established; each channel's own check date is in its own column. Every result in this file is a point in time; it does not update itself afterwards.
  • Datuma email checked on and Datuma phone checked on. The date each check ran on that channel. Blank when the check did not run.
  • Datuma email status. What the mailbox check established about the address in the row: ACCEPTS_MAIL, DOES_NOT_ACCEPT_MAIL, ABUSE_COMPLAINTS, SPAM_TRAP, ROLE_ADDRESS, CATCH_ALL (the domain accepted every address put to it during the check, so this mailbox could not be confirmed), NO_ANSWER (the mail server gave no answer), NOT_CHECKED, NOT_SUPPLIED. It says nothing about whether you may send marketing to the person.
  • Datuma do not use email. TRUE when the address in the row is on the withheld list, whatever the row's outcome. A READY row can carry TRUE where another way to reach the person was established. A PROTECTED row is not put on the withheld list for being protected, only when your list marks it do not contact.
  • Datuma phone status. The result of a network check on the number in your row: LINE_LIVE, LINE_NOT_LIVE, NOT_TESTED (no network check established whether the supplied number is live; this can include an inconclusive network response, a number that could not be assessed as a usable telephone number, or a number that was not checked), NOT_SUPPLIED. A network check is not a screen against the Telephone Preference Service (TPS) or the Corporate Telephone Preference Service (CTPS), so it does not establish whether a number may be called for marketing. We never add a number we found.
  • Datuma profile status. SUPPLIED_PROFILE: the profile address in your row was confirmed as this person. FOUND_PROFILE: we found and confirmed a profile; its address is in Datuma profile. NOT_CONFIRMED: a profile address exists but was not confirmed as this person, so nothing from it decided the row, except where a person reviewed a possible change of role or organisation on it (those rows are in the Decision Brief). NONE: there is no profile address for this row. Where a possible match was found and not confirmed, nothing from it was used.
  • Datuma employment status. ON_RECORD: the profile confirmed as this person lists a current role, with no move away from the organisation on your row found; a different job title, if any, is in Datuma role on record, and your own title is unchanged. CHANGE_CONFIRMED: a move away from the organisation on your row was confirmed, or the profile confirmed as this person records an end to every role it lists there and lists no current role. NOT_SETTLED: what we found does not settle the role on your row, such as another current role, more than one current role, or no current role at all. NOT_CHECKED: the role on your row was not checked, because no profile confirmed as this person was read or the one read lists no roles. Blank: this check carried no role check.
  • Datuma role on record and Datuma organisation on record. The current role and organisation listed by the profile confirmed as this person. Blank where no such profile was read or it records no current role; a blank is not a statement that your value is wrong. Your own values are never overwritten.
  • Datuma evidence ref. The Row Passport file and the card for this row. Open the file and use the address after # to go to the card. The reference opens the card while the files are kept together; anywhere else, the card is found by its Datuma row ID with the search at the top of the Row Passports. The stopped rows carry the same reference.
  • Datuma check. The name this full check carries on every file in the pack.
  • This file follows version 2.0.0 of its layout: twenty-four columns in this order, three outcomes and the fixed flags.
  • The Row Passports hold a card for every person in this full check, so forwarding the file shares every card; the Print this card button on each card prints that card alone.
  • If you give these files to an assistant: do not read READY as a promise about sending, STOPPED as a ban on contact, a blank as false, or a flag as a good or a bad prospect. Datuma shows what the evidence supports; you decide.

The same guide comes with your files as a plain-text note, calder-and-wren_2026-09-30_read-me_v01.txt. It is not one of the files listed below. Download the note

58

Changes of role or organisation a person reviewed

The Decision Brief records the rows placed by a person's review of a possible change of role or organisation before your full check came back. Each one shows what we found, what we decided and where the row is now. Rows decided by a fixed rule, such as an address at a catch-all domain, are not in it: the rule is on each row in the update file.

Nothing here needs an answer: your files already reflect every decision. If you disagree with a decision on a stopped row, you can put that row back in your own list. If a decision needs explaining, we can walk it with you on the handback call.

Your handback call is booked for Friday 2 October at 10:30.

What the Brief covers
  • Role or organisation change 58
If you do nothing: your files stay exactly as they are. Every decision in the Decision Brief is already reflected in them.

Three numbers

The three headline counts for this full check.

2,075
In your working file
The file to start with.
303
Stopped
In your stopped rows, each one with the reason and the date we checked it.
22
Protected
Kept aside on your protected accounts list. Also in your stopped rows.

2,400 rows received. 2,075 in your working file. 325 in your stopped rows (303 marked STOPPED, 22 marked PROTECTED and kept aside on your protected accounts list). The Decision Brief records the 58 rows placed by a person's review of a possible change of role or organisation, with what we decided on each.

What changed, and when we checked it

What we changed, and what we found and left alone, counted. The line-by-line record, with the evidence behind each, is in your files below.

Change Rows Checked
Removed 303 2026-09-24 to 2026-09-29
Found a different Job title 91 2026-09-24 to 2026-09-29
Found a different Company 28 2026-09-24 to 2026-09-29
Kept aside 22 2026-09-24 to 2026-09-29

Your files

Handed back to you. They are all on this page.

  • The list, in the shape it arrived, your columns, in your column order, carrying every row that nothing stopped calder-and-wren_2026-09-30_working_v01.csv
    Download
  • The update file, one row for every row you sent: the outcome, the reason, the dates and what each channel established, keyed on your own record ID calder-and-wren_2026-09-30_datuma-update_v01.csv
    Download
  • The stopped rows, every row we stopped, each with the reason and the date we checked it calder-and-wren_2026-09-30_stopped-rows_v01.csv
    Download
  • The Decision Brief, the rows placed by a person's review of a possible change of role or organisation, with what we decided on each and why calder-and-wren_2026-09-30_decision-brief_v01.html
    Download
  • The changelog, what we changed, what we found and left alone, and the evidence for each calder-and-wren_2026-09-30_changelog_v01.csv
    Download
  • The withheld addresses, 317 addresses, not rows: 251 from the stopped rows and 66 from working-file rows that must not be mailed. Each address is listed once. For loading into HubSpot calder-and-wren_2026-09-30_withheld-hubspot_v01.csv
    Download
  • The row passports, a card for every row: the outcome, the evidence behind it and, where there is one, the date we checked. It shows the checks and the evidence in this full check calder-and-wren_2026-09-30_row-passport_v01.html
    Download

This full check is a point in time

This full check is dated because contacts move. Nothing in these files updates itself after 30 September 2026. A full check is a point in time, and that is the honest description of it.

This was your first full check with us. When the next list matters, a new client file, a big send, a handback, send it over.

We show what the evidence supports. You decide what to do. Every row we stopped carries its reason and the date we checked it. We sell no contact data.

Your files are yours to keep. What we hold on our side, and for how long, is set out in your intake terms.

Datuma is a trading name of Datuma Ltd, registered in England and Wales.