KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesThe Do's and Don'ts of Social ResearchProject Delivery · Research ProjectsLesson 237/243← PrevNext →
GuidePublished 16 Aug 202616 min readBy KEVOS Editorialsocial research checklistresearch project dos and dontsresearch good practiceresearch diary
On this page

Ask about this page

KEVOS AIThe Do's and Don'ts of Social Research

KEVOS knowledge first · trusted web sources when needed

KEVOS/Project Delivery/Research Projects/Unit Review
Project DeliveryResearch ProjectsFoundationResearch Practice

The Do's and Don'ts of Social Research

The final week's whole substantive content is a checklist the subject did not write. It is a good checklist. It is also shorter than it looks, silent exactly where you most want a number, and pointed at a book you do not have.

Reading time18 minutes
LevelFoundation
Topic streamResearch Practice
Source materialUnit Review
Updated2026-08-16

In brief

  • The final week of the subject reproduces a student-researcher checklist from a methods text's companion website: twenty-three things to do and twenty-one not to do.
  • It carries a publisher's copyright line, so it is paraphrased here rather than reproduced; the thematic grouping is this library's and does not exist in the source.
  • At least four pairs say the same thing twice, once positively and once negatively, so it is not forty-four independent instructions.
  • Its nearest thing to a benchmark — do not expect a high response rate — carries no figure, and the subject's two other statements about response rates are not comparable with it or with each other.
  • Twelve items point at a chapter or an FAQ of a text that is not supplied, so a reader following the checklist as instructed cannot reach any of it.

What the checklist is and where it comes from

The last topic of the subject supplies one piece of substantive content, and it is not the subject's own. Seven consecutive slides carry images of a checklist headed "'Dos and Don'ts' of social research — How (not) to do a social research project", reproduced from a student-researcher toolkit that accompanies a methods textbook and was published on the publisher's website in 2012.

From the source

How the subject introduces it

"Do's and Don'ts' of Social research / This checklist will help to keep you on track. (It is reproduced here as from time to time the link does not connect.)"

The parenthesis is the source's own explanation for reproducing someone else's material: the link it would otherwise send you to is unreliable. That disclosure is to the source's credit and is unusual in the dataset.

Note

Why this page paraphrases

The checklist carries a commercial publisher's copyright line dated 2012. Every item below is restated in this library's own words, and neither the published wording nor the published order is reproduced.

23items on the "do" side
21items on the "don't" side
4pairs that restate one another
12items pointing at a text not supplied

The counts of twenty-three and twenty-one are this library's; the source states no total and prints the items unnumbered. The subject's own contribution in the final week is the decision to include the checklist and the sentence explaining why.

The list, regrouped by where it bites

The checklist is printed as two flat lists: everything to do, then everything not to do. That ordering separates instructions that belong together — the two supervisor items sit more than twenty apart, and the two data-storage items are exact inversions printed in different halves of the page.

Practice note

The grouping is this library's

The source presents two undifferentiated lists in no stated order and draws no themes. The eleven groups below are this library's arrangement, built so that each pair of related items sits together and each group corresponds to a point in a project where you would actually stop and check. Nothing has been added to the checklist and nothing has been dropped from it.

THE CHECKLIST REGROUPED — PARAPHRASED, NOT REPRODUCED

Where it appliesWhat the "do" side asksWhat the "don't" side warns against
Starting and framingBegin thinking about the research early; settle specific research questions; choose a strategy, quantitative or qualitative, and then a designLeaving everything to the last minute; working from vague, unfocused questions
Time, planning and realismBuild a timetable so the work does not end in a panicOverestimating the time and money you have; forgetting deadlines; expecting everything to go to plan; imagining a good dissertation can be written the night before
RecordsKeep a research diary; note bibliographic details as you go rather than reconstructing them laterFailing to record what you did and when
The literatureSearch thoroughly, and keep the search updated as the project runsAssuming nothing has been written about your topic
Access, approval and ethical conductNegotiate access, run a pilot study and obtain ethical approval before you start; make sure participants know their rights and consent; be reflexive about the ethics and politics of the workStarting before access and approval are in place; disregarding your discipline's code of ethics; risking your own safety in the field; using sexist, racist or disablist language in what you write
Sampling and fieldworkChoose a sampling technique that suits the design; stay alert to the interaction dynamics of face-to-face work and what weak rapport does to the validity of the data; keep the research questions in view while collectingExpecting a high response rate from a survey or questionnaire; being pulled off course by peripheral questions, unless the design is deliberately open-ended
Data handling and toolsAllow generous time for transcription; store data securely and keep backups, in a place only you can reach; learn your equipment and software before you need themUnderestimating how long transcription takes; storing data anywhere other people can get to it
AnalysisStart analysing as soon as data begin to arriveAssuming collection has to finish before analysis starts; believing a software package is required to analyse data
SupervisionMeet your supervisor regularly and act on the advice; show drafts earlySkipping meetings or disregarding the advice; adopting an unconventional style of analysis or writing without discussing it first
Writing and submissionStart drafting early; include every section the report requires; be realistic and honest about the limitations of your methodologyIgnoring your institution's requirements on length, format and presentation
After the work is finishedWrite to thank your participants and send them a summary of the findings, where that is appropriateForgetting to acknowledge participants, your supervisor, any funding body and anyone else who helped

Every cell is a paraphrase. The original wording and order belong to the 2012 toolkit and are not reproduced here.

It is not forty-four independent items

Four pairs state the same instruction twice, once as something to do and once as something not to do. Keeping a research diary and not failing to record what you did and when are one instruction. So are the two supervisor items. The two storage items are exact inversions of each other: store your data where only you can reach it, and do not store it where others can. Building a timetable and not writing the thing the night before are the same discipline stated from two ends.

Said twice

  • Keeping a record of the work as it happens
  • Using your supervisor and acting on what they say
  • Securing your data against other people's access
  • Working to a timetable instead of a deadline

Said once, and easy to skip

  • Your own physical safety while doing fieldwork
  • The language you use in the written work
  • What weak rapport in a face-to-face interview does to data validity
  • Keeping the literature search running after the initial search is done
  • Being honest about the limitations of your own methodology

Collapsing the four pairs leaves at most forty distinct instructions rather than forty-four. That arithmetic is this library's; the source states no count at all. The more useful observation is where the repetition falls. A checklist that says a thing twice is usually emphasising rather than padding, and all four repetitions are about process discipline — recording, supervision, storage, timing — rather than about method.

Source gap

The research diary is named and never explained

Keeping a research diary appears here as a "do", and the week's own case study makes the absence of one the cause of a crisis. No week of the subject explains what a research diary is, what goes into it, how often it is written or how it is used later.

It is named and not taught. This library records the gap and does not fill it: see what this material does not teach.

The nearest thing to a benchmark, and why it gives you no number

One item comes closer than any other to a performance expectation: do not expect a high response rate from a survey or questionnaire. It is the only item on the list about how much of something you should anticipate, and it carries no figure — no threshold, no range, and no definition of what would count as high.

The subject supplies two figures about response elsewhere, and neither can be read against this item or against the other.

THREE STATEMENTS ABOUT RESPONSE, NO TWO COMPARABLE

StatementWhat it quantifiesWhy it cannot be compared with the others
The checklist's warning not to expect a high response rateNothingNo figure of any kind, and "high" is undefined. It sets an expectation without a scale
An earlier week's slide: a return of 15% on postal surveys may be a good response, with internet methods said usually to improve the percentageA return rate on posted questionnairesUnattributed, hedged twice, with no year, country or survey type attached, and no figure at all given for the internet improvement
A set reading from another discipline: journal editors are usually happy with compliance rates of at least 70%The proportion of people contacted who end up as subjectsA recruitment rate, not a questionnaire return rate, and drawn from a field with different conventions and different study designs

The 15% and 70% figures are each that source's own, marked as illustrative in the material they come from. Neither is a standard and neither should be quoted as a target for a project management study.

Caution

Do not build a target out of three incompatible statements

The tempting move is to take the checklist's warning, attach the 15% to it, and treat that as the expectation. Nothing supports it. The two figures measure different quantities in different fields, and the checklist item that would connect them is deliberately unquantified.

What the item does give you is a planning instruction: design the study so that a low response does not destroy it. That means deciding, before you send anything, what response would still let you answer your question. See questionnaires and response rates and non-response and sampling bias.

Two items correct a belief rather than a behaviour

Forty-two of the items tell you to do something or to stop doing something. Two do neither. They tell you that something you may believe is not true: that you have to finish collecting before you can start analysing, and that you have to use a software package to analyse data. Both concern analysis, and they are the only items on the list addressed to an assumption.

The distinction matters because a false belief is not fixed by a reminder. You can be told to keep a diary and simply do it; being told that analysis need not wait for collection changes how you schedule the project months earlier.

What follows from the two belief items

IfYour data will arrive in batches over several weeks
ThenBegin analysing the first batch rather than holding it. The checklist is explicit that waiting is an assumption, not a requirement
IfYour schedule shows analysis starting only after collection finishes
ThenCheck whether that is a decision you made or a default you inherited. See the data collection and analysis sequence
IfYour schedule overlaps collection and analysis and does not say why
ThenSay why. An overlap that follows this item is good practice; an unexplained one cannot be told apart from an error — see a worked thesis schedule
IfYou are choosing analysis software before you have chosen an analysis approach
ThenStop. The checklist says the package is not required at all; decide the approach first — see computer-assisted qualitative data analysis

The only obligations that fall after the work is finished

Two items sit outside the project entirely. One asks you to write and thank your research participants and give them a summary of the findings where that is appropriate. The other warns against forgetting to acknowledge participants, your supervisor, any funding body and anyone else who supported the work. Everything else on the list is about producing the research; these two are about what you owe once it is produced.

They are worth separating from the rest because they are the items most likely to be skipped, and because one of them can become an obligation you incurred much earlier. A promise of feedback made during recruitment — often the thing that secured access in the first place — outlives the submission date. See voluntary participation and informed consent.

The closing pair, made concrete

  • Every person or organisation who gave access, time or data is on a list you kept as you went, not one you are reconstructing now.
  • Anything you promised participants during recruitment — a summary, a copy, a briefing — is scheduled as a task with a date, not left as an intention.
  • The summary you send participants is written for them, and breaches none of the confidentiality or anonymity you undertook to maintain.
  • The acknowledgement covers participants, supervision, funding and any other support, and names nobody you did not clear.

Where the checklist points, and where you cannot follow

Twelve of the forty-four items carry a cross-reference — to a numbered chapter or a numbered FAQ of the methods text the toolkit accompanies, and in one case to a professional association's equality guidelines. None of that material is in the supplied dataset.

Source gap

Every cross-reference leads out of the material

A reader following the checklist as instructed cannot reach a single referenced item from what has been supplied. The references sit on exactly the items where a one-line instruction is least sufficient: choosing a strategy, choosing a design, choosing a sampling technique, the dynamics of face-to-face interviewing, the ethics and politics of social research, building a timetable, and structuring the written report.

The checklist is therefore a complete index to a book the reader does not have — a limitation of how it was supplied rather than a fault in the checklist.

One item names running a pilot study among the preparations to make before you start. The pilot stage is named repeatedly across the subject — in the proposal's research design list, in an earlier week's reading, and here — and is explained nowhere. This is its fourth appearance as a named requirement without a definition, a procedure or a worked example. It is recorded and not filled.

Using it as a checklist rather than reading it as one

Read straight through, a forty-four item list produces agreement and no change in behaviour. The items are gates, and gates only work at boundaries. The sequence below is this library's; the source supplies no timing, no order and no instruction about when to use the list.

  1. Before you commit to a topicRun the framing group: specific questions, a strategy, a design. Vague questions are the item that costs the most later
  2. Before you approach anyoneRun access, approval and ethical conduct in full, including the pilot and your own safety. This is the group where proceeding out of order cannot be repaired
  3. Before the first data arriveRun data handling and tools: storage, backups, transcription time, and familiarity with your equipment
  4. As data arriveRun the analysis group. This is where the two belief items apply and where the schedule usually needs adjusting
  5. ThroughoutRecords and supervision — the two groups the checklist states twice, and the two most often deferred
  6. Before submissionRun writing and submission: your institution's requirements on length, format and presentation, and an honest statement of methodological limitations
  7. After submissionThe acknowledgement pair, which nothing else in the project will remind you about
Check before you proceed

One check before you file this away

Take the four repeated pairs — records, supervision, storage, timing — and ask whether each has a named owner, a place and a next date in your own project. Those four are the ones the checklist thought worth saying twice, and they are the four that fail silently: nothing goes wrong on the day you skip them.

What to carry forward

  1. The list is good practice, honestly attributed, and it is the whole substantive content of the subject's final week.
  2. It is not forty-four independent instructions. Four pairs restate one another, and all four concern process discipline rather than method.
  3. Its one near-benchmark is unquantified, and the subject's two other response-rate figures measure different things in different fields. No target can be built from them.
  4. Two items correct a belief rather than a behaviour, both about analysis, and both change how you schedule rather than what you do on the day.
  5. The acknowledgement pair is the only obligation the list places after the work is finished, and it can be an obligation you incurred at recruitment.
  6. Twelve items point into a text that is not supplied, so treat the checklist as an index of what to go and read rather than as self-contained guidance.

Frequently asked questions

Is this checklist the subject's own material?

No. It is reproduced in the final week's slides from a student-researcher toolkit accompanying a methods textbook, published on the publisher's website in 2012. The subject's contribution is the decision to include it and a sentence explaining that the link it would otherwise point to is unreliable.

Why does this page not reproduce the list as printed?

The checklist carries a commercial publisher's copyright line. Every item here is restated in this library's words, regrouped by where it applies rather than printed in the published order. If you need the original wording, it belongs to the toolkit rather than to the subject that reproduced it.

What response rate should I expect from a survey?

Nothing in the supplied material supports a figure. The checklist warns against expecting a high response rate and gives no number; an earlier week quotes an unattributed 15% return on postal surveys as something that may be a good response; and a set reading from another discipline mentions compliance rates of at least 70%, which measures the proportion of people contacted who become subjects. The three are not comparable.

What is a research diary and how do I keep one?

The checklist tells you to keep one and the subject never explains it. No week defines what goes in it, how often it is written or how it is used when you come to write up, and this library does not invent a procedure. The related instruction that is stated — record what you did and when — is the part you can act on immediately.

Does the checklist really say I can start analysing before collection finishes?

Yes, twice over. One item tells you to start analysing as soon as you collect, and a second tells you not to assume you have to collect everything first. That is one of only two items on the list that correct a belief rather than a behaviour, and it has direct consequences for how you schedule a project.

How should I use a forty-four item list in practice?

As gates at project boundaries rather than as something to read once. Group the items by the point at which they apply — before you commit to a topic, before you approach participants, before data arrive, as data arrive, before submission, after submission — and run only the relevant group at each boundary. That grouping is this library's; the source supplies no timing.

References and source attribution

  1. The supplied teaching source: the slide deck for the final topic of a master's-level research methods subject in project management. Author, institution and year are not stated in the supplied files. Seven of its slides are images and carry no extractable text.
  2. A student researcher's toolkit accompanying a methods textbook, published on the publisher's website with a copyright line dated 2012 — the origin of the checklist. Neither the text nor the publisher is identified in the supplied material, and the toolkit itself is not supplied.
  3. The chapter and FAQ cross-references carried by twelve of the checklist items refer to that same unsupplied text and cannot be followed from the supplied dataset.
  4. Bryman, A. 2016, Social Research Methods, 5th ed., Oxford University Press, Oxford — among the social research methods works cited in the supplied source's weekly reference lists. It is not identified in the material as the source of this checklist.
  5. O'Leary, Z. 2017, The Essential Guide to Doing Your Research Project, 3rd ed., Sage Publications, London — among the general research methods works cited in the supplied source's weekly reference lists.

Suggested questions for Ask KEVOS

  • Which items in the do's and don'ts checklist say the same thing twice?
  • What does the supplied material actually say about survey response rates, and why can the figures not be compared?
  • Which parts of the checklist apply before I approach participants?
  • What does the checklist say about analysing data before collection is finished?
  • Which checklist items point at material that is not supplied with the subject?

Related KEVOS knowledge

How This Material Expects to Be UsedFoundation · research practiceWhat This Material Does Not TeachCore · research practiceCommon Mistakes in Project Management ResearchAdvanced · research practiceThe Research Project Lifecycle End to EndCore · research practiceWorking With Your SupervisorCore · research practiceResearch Project Quick ReferenceFoundation · research practice
KEVOS® · Project Delivery · Research Projects Page KVS-PM-RES-0237 · v1.0.0 · content 2026.08 Last reviewed 2026-08-16

Continue learning

Scheduling a Research ProjectGuide · Research ProjectsNEXT LESSON →How This Material Expects to Be UsedGuide · Research ProjectsWhat Goes Wrong in a Thesis ScheduleGuide · Research ProjectsAnatomy of a Published Book ReviewGuide · Research Projects
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®