KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesPlanning Data Management for a Research ProjectProject Delivery · Research ProjectsLesson 192/216← PrevNext →
GuidePublished 16 Aug 202616 min readBy KEVOS Editorialresearch data management planmanaging data in a research proposalstoring research datadata security in research
On this page

Ask about this page

KEVOS AIPlanning Data Management for a Research Project

KEVOS knowledge first · trusted web sources when needed

KEVOS/Project Delivery/Research Projects/The Nature of Quantitative Research
Project DeliveryResearch ProjectsCoreQuantitative Research

Planning Data Management for a Research Project

Five slides turn this week from a discussion of sampling into a data-custody sequence. They contain one usable lifecycle, one quoted regulatory instrument, four unanswered questions and a definition of data management that uses the word it is defining.

Reading time17 minutes
LevelCore
Topic streamQuantitative Research
Source materialThe Nature of Quantitative Research
Updated2026-08-16

In brief

  • The source requires your proposal to say how data will be managed at three stages, and supplies the three stages. That frame is usable and is the only one in the supplied material.
  • It also supplies a third definition of data management, incompatible with the two the library already held. All three are given here and none is chosen.
  • The storage slide asks four questions — format, access, download, entry — and answers none of them.
  • Every security instruction is a bare imperative: back up, make copies, plan the move. No frequency, number, location, encryption, access control or destruction rule appears.
  • The one instrument quoted in mandatory language is a national code, reproduced by the teaching material rather than written by it. Its six obligations are the most actionable thing in the week.

The three stages your proposal has to cover

The requirement is stated plainly and is worth quoting because it is the only place in the supplied material where data management is given a shape: "In your research proposal you need to determine how you are going to manage the data: while it is being gathered; when it is gathered and stored and; when it is being analysed."

  1. While it is being gathered
  2. When it is gathered and stored
  3. When it is being analysed

Three stages, counted here from the list; the source states no count. Use them as the headings of your data management section and you will have a structure the material supports directly, which is more than can be said for most of what it asks for. The gap opens immediately afterwards.

Source gap

The lifecycle stops at analysis; the code quoted three slides later does not

The three stages end at "when it is being analysed". The national code reproduced later in the same deck requires records to be kept "during and after the research process" and requires data to be retained "in a durable, indexed and retrievable form".

The week's own instruction and the week's own quoted authority therefore disagree about where data management ends. Add a fourth stage to your own plan — what happens to the data after the project closes — and be aware that you are supplying it, not following the source. Retention is developed at Research Data Storage, Retention and Ownership.

Caution

A proposal requirement, in a subject that never shows a proposal

The slide imposes an obligation on the research proposal. No proposal, proposal template, section list or data management plan appears anywhere in the supplied material. The library has recorded proposal writing conventions as an undelivered objective since an earlier batch, and this week adds a proposal requirement without closing that gap.

For what a proposal is generally expected to contain, see Components of a Research Proposal.

Three definitions of data management, none overlapping

This week was recorded in this library as missing from every previous delivery. Its arrival closes that absence and, on this topic, makes the position worse rather than better: the library held two incompatible definitions of data management and now holds three.

EVERY DEFINITION OF DATA MANAGEMENT THE SUBJECT SUPPLIES

WeekDefinition as givenWhat it coversWhat it excludes
The data-collection week"The process of data collection and analysis"Gathering and analysingCustody, storage, security and retention entirely
The quantitative-analysis week"Becoming familiar with appropriate software, logging in, entering data and cleaning data"A set of clerical software operationsBoth collection and custody; it is a description of desk work
This week"Data management is about proper management and protection of data"Custody and protectionCollection and analysis — and it defines the term using the term

The three are set out and not adjudicated. No two of them overlap, none acknowledges the others, and nothing in the material states which governs. The library's earlier record called the disagreement between the first two the most consequential single contradiction between those weeks; the third does not resolve it.

The practical instruction that follows is short. If you use the phrase "data management" in a proposal, an ethics application or a methodology chapter, say in the same sentence what you mean by it — the activities you are undertaking, not the label. A reader who has been taught any one of the three will otherwise assume you meant that one.

From the source

The claim the week attaches to it

"Data is the evidence the researcher gathers for the research project."

"The collection of figures is a very important aspect of forecasts. A conclusion is best based on the original figures."

"Mistakes, errors or bias arising in collection will be reflected in conclusions subsequently based on such figures. Subsequent analysis will be a waste of time and may mislead, with serious consequences."

The final claim is the week's only statement about what happens when data collection goes wrong, and it is absolute: no consequence is named, no threshold of error is given at which analysis becomes worthless, and no remedy is offered. "Forecasts" appears here and nowhere else in the week.

Format, access and entry: four questions, no answers

The storage slide is where a data management plan would normally be specified. It is reproduced here with its transcription defects intact, because two of the three change what the sentence appears to say.

From the source

The storage slide, quoted with its defects marked

"You need to consider the format you are going to store data in. This also relates to the how you are collecting the data. If it comes from within your organisation you need to understand how you are going to access it (is it accessible only be password) or down load it (e.g. can you put the date into [a spreadsheet program; product name scrubbed])."

"If you are collecting it e.g. survey, how are you scaling the questions and how and who is going to enter the information into the computer system?"

Three defects: "be" for "by"; "down load" split; and "date" for "data" in a sentence that is entirely about moving data into a spreadsheet. Quoted as printed and not repaired.

Four questions are asked here — what format, how to access organisational data, how to scale the questions, who enters the information — and none is answered. No criterion, option list or recommendation follows any of them. "Scaling" appears only here in the week; response scales belong to a week two later and are not cross-referenced.

Practice note

Answering the four questions yourself

The source poses these and stops. The answers below are this page's, offered as the minimum a reader of your proposal needs, not as anything the material states.

Format — name the file format and the software that will open it in five years, not the software you happen to use now. Access — say who holds the credential, what happens when they leave, and whether the extract you take is a copy or a live connection. Entry — name the person, the double-checking rule and what happens to the paper or recording afterwards. Scaling — decide it at instrument design, because changing a response scale after collection destroys comparability.

Source gap

Analysis is simultaneous, and three weeks away

The same slide states that when you design your data-gathering methods "you develop at the same time a sense of how the data will be analysed", and then defers analysis: "this will be discussed in a later topic".

The student is told the two are simultaneous and that one of them is weeks away. The deferral is only partly honoured in the supplied material — the study notes for the quantitative analysis week were never supplied — so plan your analysis approach at design time from a source you choose. Cleaning and screening are treated at Data Screening and Cleaning.

Security: three instructions, no method

The security material is three statements and three loss modes: "electronically or digitally stored data should be backed up"; "copies should be made"; "data can be easily lost or stolen or damaged/corrupted in some way". A fourth sentence covers movement: "If moving the data is unavoidable, it is wise to make a plan for the move which anticipates any potential risks or dangers posed to the data by the move."

Read as a risk statement that is sound — data is lost, stolen or corrupted, and moving it is the risky moment. Read as an instruction it is empty: no backup frequency, no number of copies, no storage location, no encryption, no access control, no retention period and no destruction rule appears. The one item the week has an authority for, retention, is on a slide three later, and this slide does not connect to it.

Source gap

The sentence assigning responsibility does not say who holds it

"Every researcher should have a plan in place for the organisation, which provides a safe and secure storage facility for data gathered for the research project."

"For the organisation" can qualify the plan — a plan covering the organisation — or name the provider, since the relative clause "which provides" attaches to "the organisation". On the second reading the researcher's plan has no stated content at all. The one sentence in the week that assigns data-security responsibility does not say who carries it, so write it down yourself: who provides the storage, who administers access, who is accountable if it is lost.

The obligation behind the storage

The week then reproduces one clause and six sub-clauses of a national code for the responsible conduct of research. This is the only quoted regulatory instrument in the supplied material and the only place in it where an obligation is stated in mandatory language. It is quoted by the teaching material, not written by it, and it should be attributed that way.

CLAUSE 2.6 — MANAGE STORAGE OF RESEARCH DATA AND PRIMARY MATERIALS, AS QUOTED

Sub-clauseObligation, quotedWhat it asks you to produce
2.6.1"Keep clear and accurate records of the research methods and data sources, including any approvals granted, during and after the research process."A method and provenance record that outlives the project
2.6.2"Ensure that research data and primary materials are kept in safe and secure storage provided, even when not in current use."A storage arrangement that persists between working sessions
2.6.3"Provide the same level of care and protection to primary research records, such as laboratory notebooks, as to the analysed research data."Equal treatment of raw records and analysed files
2.6.4"Retain research data, including electronic data, in a durable, indexed and retrievable form."An index, and a format you can still open later
2.6.5"Maintain a catalogue of research data in an accessible form."A catalogue, separate from the data itself
2.6.6"Manage research data and primary materials according to ethical protocols and relevant legislation."A stated link to your ethics approval

Six obligations under one clause; the count is derived, the source states none. The clause numbers are citations to an external instrument, not content figures. The instrument's opening line makes the institution's own policy the governing document — and that policy is not supplied, named or summarised anywhere in the week.

Source gap

A fragment of an instrument whose scope is never stated

"Part A: Section 2 … 2.6" implies at least a Part B, at least clauses 2.1 to 2.5, and sections other than 2. None is quoted, summarised or listed. The chain of authority then ends outside the material: the deck says the awarding institution's code "is based on" the national one, and the national clause says researchers must manage data in accordance with the institution's policy.

Sub-clause 2.6.6 is also the only appearance of the word "ethical" in the entire week, and it appears inside the quotation. The protocols it requires you to follow are never named. Consent, identifiability and anonymisation are treated at Confidentiality and Anonymity.

What counts as research data you have to manage

The study notes open with the question the obligations depend on: what is research data? They answer it by quoting four institutional research-data policies from a national research-data service guide, and present the four as agreeing. They do not agree.

THE FOUR QUOTED POLICIES, COMPARED

Policy 1Policy 2Policy 3Policy 4
Forms admittednumerical, descriptive, visual, tactilenumerical, descriptive, visualprint, digital, physical, othernumbers, symbols, text, images, sounds
Processing statesraw, cleaned or processedraw or analysed; experimental or observationalincludes analysed datanot stated
Primary materialsnot mentionednot separatedexplicitly includedexplicitly distinguished
Test of inclusionNoneNoneNone"commonly accepted in the research community as necessary to validate research findings"

Institutions scrubbed. Only one of the four supplies a test, and that test is sociological: it makes the boundary of research data depend on what a research community accepts. A researcher applying the four to the same file could reach different answers. One of the four is described by the notes as a draft policy; nothing dates any of them.

The notes then spend a short section on the boundary that matters for retention: whether completed questionnaires and recordings are "primary materials" or "research data". It is the most analytically careful passage in the week — it states a distinction, attributes it, raises a counter-argument, tests the counter-argument against a stated definition, and reaches a conclusion. It is also borrowed rather than written by the subject.

Caution

The deck and the notes use the same code to opposite effect

The notes record the national code as implying that completed questionnaires and recordings are primary materials while transcripts derived from them are research data, and that "different standards for retention may apply" — that is, the code differentiates the two classes. The deck's own quoted sub-clause 2.6.3 requires the same level of care and protection for primary records as for analysed data — that is, it equalises them.

One week, one instrument, two opposite readings, and neither document refers to the other. The operative retention rule in the notes is "the recommended period", which is mentioned four times and never quantified. If a retention period matters to your project, you will not find one here.

Writing the section

The checklist below combines what the source requires with what a reader of your proposal will need anyway. Items marked as the source's are traceable to the slides or the quoted code; the rest are this page's construction and should be attributed accordingly.

A data management section that answers the material and the reader

  • Source: a statement for each of the three stages — while gathering, once stored, during analysis
  • Source: the storage format, and how organisational data will be accessed and downloaded
  • Source: who will enter the data, and how the questions are scaled
  • Source, from the quoted code: records of methods and data sources kept during and after the project
  • Source, from the quoted code: a durable, indexed, retrievable retention form and a catalogue
  • Added here: a fourth stage covering what happens after the project closes, with a period you have sourced and cited
  • Added here: named responsibility for provision, administration and accountability of storage
  • Added here: the sense in which you are using the phrase "data management", given that the material supplies three
From the source

Where this material sits against the week's objectives

It sits under none of them. The week states three objectives — on concepts and measures, on reliability, validity, generalisation and replication, and on evaluating external and internal sources — and data custody appears in no objective, despite occupying five of the deck's content slides.

The consolidated audit across the six weeks now on record shows fourteen objectives stated, none fully delivered, four partially delivered and ten not delivered at all. Those are the reconciled figures and the only ones this library cites; the reckoning is at The Six-Week Objective Audit. Content that answers no objective is not thereby worthless — this is the most directly usable material in the week — but you should know that nothing in the week's own statement of purpose asked for it.

What to carry forward

  1. Use the three stages as your section headings; they are the only lifecycle the material supplies, and add the fourth stage yourself.
  2. Three incompatible definitions of data management now sit in this subject. Say what you mean by the phrase every time you use it.
  3. The storage slide asks four questions and answers none. The answers are your work, and should be written as such.
  4. Security instructions in the material are bare imperatives. Frequency, copies, location, access control and destruction are all yours to specify.
  5. The six obligations of the quoted national code are the most actionable content in the week — attribute them to that code, not to the teaching material.

Frequently asked questions

What does this material actually require me to put in my proposal?

One thing, stated once: how you will manage the data while it is being gathered, once it is gathered and stored, and while it is being analysed. Everything else on the topic is either a question the slides ask and do not answer, or an obligation quoted from an external code. The three stages are a sound structure and the content under them is yours to supply.

Which definition of data management should I use?

The subject supplies three and no two overlap: the process of collection and analysis; a set of software operations; and the proper management and protection of data. This library sets out all three and does not choose between them. Name the activities you mean rather than relying on the label.

How long do I have to keep my research data?

The material never says. The quoted national code requires retention in a durable, indexed and retrievable form, and the study notes refer four times to "the recommended period" without ever quantifying it. Take a retention period from your own institution's policy and cite it there, because the policy the code defers to is not supplied in any of this material.

Are completed questionnaires research data or primary materials?

The material argues both ways in one week. The notes record the code as treating completed questionnaires and recordings as primary materials with possibly different retention standards, while the deck quotes a clause requiring identical care for primary records and analysed data. Record the ambiguity in your plan and treat both classes to the higher standard.

Does the source say anything about backups or encryption?

It says data should be backed up and that copies should be made, and nothing further. No frequency, number of copies, storage location, encryption method, access control or destruction rule appears anywhere in the week. Those decisions are yours and should be written into the proposal explicitly.

References and source attribution

  1. A national code for the responsible conduct of research — quoted in the supplied teaching source as the basis of the awarding institution's own code, and the source of clause 2.6 and its six sub-clauses reproduced on this page. The code's name, issuing body and address are scrubbed; the code itself is not supplied in the material.
  2. Bryman, A. 2016, Social Research Methods, 5th ed., Oxford University Press, Oxford.
  3. O'Leary, Z. 2017, The Essential Guide to Doing Your Research Project, 3rd ed., Sage Publications, London.
  4. Veal, A. J. 2005, Business Research Methods: A Managerial Approach, Longman.
  5. The supplied teaching source: the slide deck on the nature of quantitative research, in particular its five slides on managing, storing and securing data, together with both copies of the accompanying study notes and the four institutional research-data policy definitions they quote from a national research-data service guide.

Suggested questions for Ask KEVOS

  • Draft the data management section of my proposal using the three stages this material supplies.
  • Turn the six obligations of the quoted code into a checklist I can apply to my own project.
  • What retention period applies to my data, and what do I need to check that the material does not tell me?
  • Write the storage, access and data-entry paragraphs for a project drawing on my organisation's records.
  • Which parts of my data management plan come from this source and which are mine?

Related KEVOS knowledge

Research Data Storage, Retention and OwnershipCore · research ethicsPopulation, Sample, Variables and DataFoundation · quantitative researchComponents of a Research ProposalCore · research proposalSteps 9-10: Writing the Report and Storing the DataCore · research processWhat Quantitative Research IsFoundation · quantitative researchQuantitative Research Quick ReferenceFoundation · quantitative research
KEVOS® · Project Delivery · Research Projects Page KVS-PM-RES-0192 · v1.0.0 · content 2026.08 Last reviewed 2026-08-16

Continue learning

Whole Population or Sample?Guide · Research ProjectsNEXT LESSON →Descriptive and Experimental Study DesignsGuide · Research ProjectsNon-Response and Sampling BiasGuide · Research ProjectsSample Size in Quantitative StudiesGuide · Research Projects
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®