What this is
What counts as a bulk load rather than manual entry?
What counts as a bulk load rather than manual entry?
Any operation that writes more than a handful of records into a registry from an external file or system in one pass, rather than a person typing one record at a time through the form. A CSV import of fifty vendors, a migration from a legacy spreadsheet, or an API sync that creates two hundred asset records overnight are all bulk loads, even if no one calls them that.
Why does a load into a registry need its own record at all?
A manual entry has one author who can be asked what they meant. A load has a source file and a mapping, and often no one in the room who checked it. The record exists to reconstruct what happened when rows turn out to be wrong.
What is the difference between mapping and verification here?
Mapping is the decision, made before the load runs, about which source column becomes which registry field and value. Verification is what gets checked after: record counts, sampled rows, and whether the values mean what the mapping intended.
Scope
When is a bulk import and data load record required?
This record exists for the load itself, not for the registry entries it creates or for deciding whether those entries were the right call in the first place.
Use this template when
- A bulk import, migration or scheduled sync is about to write records into any registry rather than a person entering them one at a time
- A one-off spreadsheet migration is replacing a legacy system's export as the source of a registry
- An automated feed (API sync, nightly extract) creates or updates registry records without a person reviewing each one
- A previous load is being corrected or re-run and the correction itself needs its own trail
- The load formed part of a controlled change and needs to be traceable back to the Management of Change record
Do not use it for
- Management of Change, which covers the decision to change a process or system, not the mechanics of loading the resulting data.
- Root Cause Analysis, which investigates why something happened rather than recording how a load was mapped and checked.
- Corrective and Preventive Action, which is the general action record for any nonconformity, not a substitute for the load's own error log.
- Approval Workflow Record, which tracks a decision moving through sign-off stages, not a data load's source and verification steps.
- A single manual correction to one registry record, which is just an edit and needs no load record at all.
Compliance mapping
Which ISO 9001 cl.7.5 requirements does this satisfy?
ISO 9001 cl.7.5 treats documented information as controlled regardless of how it was created, so a bulk load meets the same bar a manual entry would.
| Clause | Requirement | Where it lands |
|---|---|---|
| cl.7.5.1 | Documented information required by the quality management system is identified and controlled, whatever its origin. | Header |
| cl.7.5.2 | Documented information is adequately identified, described and reviewed for suitability before it is used. | Source |
| cl.7.5.2 | Format and media are appropriate, which for a bulk load means the source structure has to be reconciled against the registry's own field and option definitions. | Mapping |
| cl.7.5.3.1 | Documented information is available and suitable for use where and when it is needed. | Verification after load |
| cl.7.5.3.1 | Documented information is adequately protected, including from loss of integrity, which a rollback plan exists to satisfy. | Verification after load |
| cl.7.5.3.2 | Changes to documented information are controlled, which is why a load tied to a controlled change carries the Management of Change reference forward. | Related records |
| cl.4.4 | Processes needed for the quality management system, including the inputs they rely on, are determined and their interactions understood. | Header |
What it does not cover
- Record Count Reconciled, which confirms the load didn't drop or duplicate rows but says nothing about whether the values in those rows are correct.
- Source Considered Authoritative marked Uncertain, which means the load is building the registry on a source nobody is prepared to stand behind.
- Option Values Mapped To Ours marked Partly, which means some source values are landing as blanks or as options the picklist never defined.
- Test Load Run First marked No on a load into a registry other templates link against, which skips the one step that catches mapping errors before they become inherited errors.
- Dependent Records Checked marked No, which leaves every record that already references the target registry unexamined for the errors this load may have just introduced.
Global
Bulk Import and Data Load Record requirements by country
The clause basis is ISO 9001, but what a bulk load actually puts at risk depends on which registry it lands in and what that registry holds.
ISO 9001:2015 cl.7.5
Sets the baseline: documented information is controlled the same way whether a person typed it or a file loaded it.
An auditor who finds registry entries with no traceable source or mapping treats them as uncontrolled documented information, regardless of how the data arrived.
GDPR Article 5(1)(d), accuracy principle
A bulk load into a registry holding personal data, such as the Worker Profile or Customer Register, is itself a processing activity.
Inaccurate data introduced by a load engages the controller's own accuracy obligation, not just the quality system's documentation clause.
FDA data integrity expectations (ALCOA+ principles)
Where the target registry feeds a regulated quality record, for example a Substance or Product register in a life sciences or food operation, loaded data is expected to be attributable and accurate.
A load with no verified source, no mapping record and no sampled check is the pattern regulators cite as a data integrity failure, regardless of whether the entries happen to be correct.
How to complete it
How to complete a bulk import and data load record, step by step
Filling in every field is mechanical. The judgement calls are what decide whether the record actually defends the load later.
A spreadsheet someone maintained for years is not automatically authoritative just because it's the only copy available. Marking Source Considered Authoritative Yes should mean the source is the system of record for that data, not that it was the fastest thing to export.
Sample Records Checked is a raw number, not a ratio, so a fixed figure of five means something different for a fifty-record load than a five-thousand-record one. The call is sizing the sample to the load, not repeating whatever was checked last time.
Field Mapping Documented and Option Values Mapped To Ours both allow Partly. Proceeding on Partly is defensible for a low-stakes registry and indefensible for one other templates link against, and the record should say which case this was.
Rollback Available Yes is easy to tick without a real rollback existing. The call is whether a bad load can be cheaply reversed, or whether dependent records will already exist against it by the time anyone notices.
What auditors find
Most common bulk import and data load record findings
These failure patterns show up when the load itself was rushed, not when the form was filled in carelessly.
| Finding | Clause | What fixes it |
|---|---|---|
| Record count reconciled but no sample of individual records checked, or the sample size doesn't scale with load size. | cl.7.5.3.1 | Set a minimum sample proportional to load size before the load is accepted, not a flat number. |
| Option values mapped as Partly, with no note of which options failed to map or what they landed as instead. | cl.7.5.2 | Require the unmapped source values and their landing state to be listed before Load Accepted can be set. |
| Test load skipped because the source had been used before, without re-checking the registry's option lists hadn't changed since. | cl.7.5.2 | Tie Test Load Run First to a check of the target registry's current field and option definitions, not just the source file. |
| Errors found and corrected, but Dependent Records Checked left at Partly or No, leaving downstream records unexamined. | cl.7.5.3.2 | Block Load Accepted until Dependent Records Checked is resolved whenever Errors Found is greater than zero. |
| Action Required marked No despite Errors Corrected being Partly, closing the record while known errors remain uncorrected. | cl.7.5.3.1 | Force Action Required to Yes automatically whenever Errors Corrected is anything other than Yes. |
| No rollback available and no mitigation recorded, on a load into a registry with existing dependent records. | cl.7.5.3.1 | Require a documented mitigation step whenever Rollback Available is No and the target registry already has dependent records. |
Case in point
Case in point: a vendor list migration nobody re-checked
A site migrating from a legacy spreadsheet loaded three hundred and forty vendor records in one pass. The count reconciled exactly, so the load was accepted the same afternoon. Weeks later, a procurement review found that the spreadsheet's 'Approved' and 'Pending Approval' values had both mapped onto the registry's single 'Active' option, because the source used a different label set and nobody had checked Option Values Mapped To Ours beyond a glance.
Forty vendor records tied to live purchase orders carried a status the registry had never actually verified. The fix was a corrected mapping and a re-run, but it took a dedicated review to surface, because the original load record showed every box ticked Yes and gave no reason to look again.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
5 sections
- Reference
- FDN-034
- Archetype
- Engine
- Record ID
- LOAD-2026-000
- Scoring
- Load errors
- Direction
- Low is good
- Singleton
- Yes
- Basis
- ISO 9001 cl.7.5
- Links
- Links every registry
- Tags
- Engine, Data
- Sections
- 5
- Fields
- 39
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 3
Header
10 fieldsLoad ID*
Auto sequence. Format LOAD-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Bad Data Loaded Once, Repeated Forever
Every record that references a registry inherits its errors. A bad load is far more expensive than a bad manual entry.
Target Registry*
Records In Load*
Loaded By*
Source
6 fieldsSource System Or File*
Source Owner
Source Data Verified*
- Yes3 pts
- Partly1 pt
- No0 pts
Extract Date
Source Considered Authoritative*
- Yes3 pts
- Uncertain1 pt
- No0 pts
Duplicates Removed Before Load*
- Yes3 pts
- No0 pts
Mapping
6 fieldsField Mapping Documented*
- Yes3 pts
- Partly1 pt
- No0 pts
Mandatory Fields Populated*
- All3 pts
- Most1 pt
- Many blank0 pts
Option Values Mapped To Ours*
Free text values that do not match the option list arrive as blanks or as new options nobody intended.
- Yes3 pts
- Partly1 pt
- No0 pts
Date Formats Checked*
- Yes3 pts
- No0 pts
ID Format Matches Our Convention*
- Yes3 pts
- Partly1 pt
- No0 pts
Test Load Run First*
- Yes3 pts
- No0 pts
Related records
1 fieldMOC ID
Where the load formed part of a controlled change.
Links to FDN-020 MOC ID
Verification after load
16 fieldsRecord Count Reconciled*
- Yes3 pts
- No0 pts
Sample Records Checked*
Errors Found*
Errors Corrected
- Yes3 pts
- Partly1 pt
- No0 pts
Rollback Available*
- Yes3 pts
- No0 pts
Load Accepted*
- Yes3 pts
- With corrections2 pts
- Rejected0 pts
Dependent Records Checked*
- Yes3 pts
- Partly1 pt
- No0 pts
Registry Owner Signed Off*
- Yes3 pts
- No0 pts
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Administrator*
Signature*
Registry Owner*
Second Signature*
FDN-034 · record IDs look like LOAD-2026-000 · Links every registry
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The record captures what happened during one load. Keeping registries clean across every load is what actually needs watching.
Holds the load history against every registry, flags loads with unresolved errors or missing rollback plans, and keeps the trail intact when an owner needs to trace a bad value back to its source.
Treats each accepted load as a controlled change to documented information, checking the Management of Change link is present when the load was part of a wider change.
Watches which registries take bulk loads most often and surfaces the ones running without a test load first, so mapping problems get caught before production data.
Rolls up load error counts across every registry into one trend, so a spike from one source system shows up before it's buried in forty separate records.
This template lives in General — control tower. The orchestration layer. Registries and engines every other workspace reads from.
Meet General→Glossary
Bulk Import and Data Load Record definitions and key terms
- Bulk load
- Writing many registry records in one operation from a source file or system, rather than one person entering records individually through the form.
- Field mapping
- The documented correspondence between a source column and a registry field, including how source values translate into the registry's own option lists.
- Source system
- The file or system the loaded data originated from, whether an export, a legacy database, or a live API feed.
- Rollback
- The ability to reverse a load and restore the registry to its pre-load state if the load turns out to be wrong.
- Registry
- The master data list the load writes into, such as sites, assets, workers, vendors or substances, that other templates in the library link against.
FAQ
Frequently asked questions about bulk import and data load record
Does every CSV import need one of these records?+
Any import writing more than a handful of records at once should have one, because that's the threshold where field-by-field manual checking stops and a mapping error can propagate silently. A single corrected row doesn't need one.
Who should complete this, the person who ran the load or the registry owner?+
The administrator who ran the load completes the source and mapping sections, since they know what was mapped to what. The registry owner signs off on verification, since they're accountable for what the registry now contains.
What happens if errors are found after the load has already been accepted?+
The finding belongs in this record's Errors Found and Errors Corrected fields if caught during verification, or in a fresh Corrective and Preventive Action record if it surfaces later, once dependent records already exist against the bad data.
Why does the record score load errors with low as good, rather than scoring completion?+
A fully completed record reporting twenty errors is a worse outcome than a briefer one reporting none. The score flags load quality, not how thoroughly the form was filled in.
Does a scheduled API sync need a new record every time it runs?+
A recurring sync needs a record for its initial setup and mapping, and a fresh one whenever the mapping changes, the source changes, or an error surfaces. An unchanged nightly sync doesn't need a new record every night.
Can this record be used for a load that only updates existing registry records rather than creating new ones?+
Yes. An update load carries the same mapping risks as a create load, and a mismatch is often worse, since it can silently overwrite a correct value rather than just adding a bad row.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Master Data and Foundations
Site and Location Register
Holds every site, building, area and zone your organisation operates
Asset Register
Holds every piece of equipment, machine, vehicle and tool you track
Worker Profile
Holds a record for each worker, including role, department, site and start date
Job and Task Register
Lists the jobs and tasks people perform, so risk assessments and ergonomic assessments can be tied to real work rather than job titles
Vendor and Contractor Register
Holds every supplier, contractor and service provider you work with, including their status and approval level
Chemical and Substance Register
Lists every chemical and hazardous substance held on site, with quantity, location and hazard class
More in Engines
Risk Assessment
The single risk assessment used across the whole business
Root Cause Analysis
Finds out why something happened rather than who was involved
Corrective and Preventive Action
The single action record used everywhere
Finding
Records a single deficiency picked up during an audit, inspection or check
Effectiveness Verification
Checks whether an action actually worked, some time after it was put in place
Just Culture Determination
Separates a system problem from a genuine choice to take a risk, using a consistent set of questions
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 9001:2015 cl.7.5 — Documented information
- ISO 9001:2015 cl.4.4 — Quality management system and its processes
- GDPR Article 5(1)(d) — Accuracy principle
- FDA data integrity guidance — ALCOA+ principles
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.