KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesThe Complete Objective AuditProject Delivery · Research ProjectsLesson 243/243← PrevNext →
GuidePublished 16 Aug 202612 min readBy KEVOS Editoriallearning objectivesobjective auditteaching materialresearch methods
On this page

Ask about this page

KEVOS AIThe Complete Objective Audit

KEVOS knowledge first · trusted web sources when needed

KEVOS/Project Delivery/Research Projects/Synthesis
Project DeliveryResearch ProjectsCoreResearch Practice

The Complete Objective Audit

Nineteen learning objectives across eight audited weeks. Two are fully delivered — both of them in the final fortnight. Here is the reconciled audit, the pattern behind the other seventeen, and what changed at the end.

Reading time13 minutes
LevelCore
Topic streamResearch Practice
Source materialSynthesis
Updated2026-08-16

In brief

  • Nineteen objectives are stated across the eight weeks this library audits. Two are fully delivered, seven partly, and ten not at all.
  • Both full deliveries are in the last two weeks. Every week before that had at least one objective it did not reach.
  • Ten of the seventeen shortfalls are the same failure: a set of things is named, and then nothing is said about any of them.
  • This audit supersedes two earlier figures in this library — nine objectives over four weeks, and fourteen over six. Those numbers were correct for what was then held and are named here rather than quietly replaced.
  • The final week says something the audit cannot: that this material was built to be returned to during a thesis, not absorbed at the time.

The standard, and why it is the fair one

Each week opens by stating what a reader will be able to do at the end of it. That statement is the material's own commitment, which makes it the only standard worth judging against — not an external syllabus, not a comparison with another course, and not anybody's opinion about what should have been covered.

One question is asked of each objective: could a reader who worked through the week do the thing the week said they would be able to do? Where the answer is yes for part of it and no for the rest, the objective is recorded as partly delivered and the split is stated.

Note

What this audit covers, and what it does not

It covers the eight weeks whose slide decks state objectives in a form that can be checked — research design; the nature of quantitative research; the nature of qualitative research; gathering your data; quantitative analysis and presentation; analysing qualitative data and results; the challenge of writing up; and the unit review.

The earlier weeks — introduction to research, developing a topic, the literature review, ethics and the proposal — are audited on their own pages and are, on the whole, in better condition than the middle of the sequence.

The audit

19objectives stated across eight weeks
2fully delivered
7partly delivered
10not delivered

OBJECTIVE DELIVERY, WEEK BY WEEK

WeekStatedDeliveredPartlyNot delivered
Research design3012
The nature of quantitative research3012
The nature of qualitative research2002
Gathering your data1001
Quantitative analysis and presentation3012
Analysing qualitative data and results2011
The challenge of writing up3120
The unit review2110
Total192710

Assessed against each week's own stated objectives, quoted from its opening slides.

Caution

Three totals exist in this library. Only this one is current.

An earlier page audited four weeks and reported nine objectives, none fully delivered. A later one audited six and reported fourteen. Two independently produced source extracts, neither able to see the other, reported running totals of twelve and eleven.

Every one of those was correct for the set of weeks it covered. All are superseded by the nineteen above, and no page in this library should cite any other figure.

They are named rather than quietly overwritten because a reader who acted on an earlier number deserves to know it changed, and because arithmetic that propagates unchecked is exactly the failure this library exists to avoid.

The pattern behind ten of the shortfalls

Ten undelivered objectives across eight weeks is not ten unrelated oversights. The same failure recurs, and learning to spot it is worth more than memorising the cases, because it is a test you can run on any material anybody hands you.

From the source

The failure, in one sentence

A set of things is named — correctly, and often comprehensively — and then nothing is said about any of them.

The naming reads as coverage. It is not coverage. The test that separates the two is whether you could act on it. If the only thing you could do with a list is repeat the list, the topic has been named and not taught, however complete the list looks.

THE SAME FAILURE, SIX TIMES

Objective promisedWhat is namedWhat is never said
Compare types of methodsTen methods, in a gridNo comparison of any two, on any dimension
Determine benefits and disadvantages of typesThe same ten methodsNo benefit and no disadvantage for any of them
Design appropriate research toolsFive qualitative methods, describedNo interview guide, observation schedule, coding frame or instrument of any kind, in fourteen weeks
Evaluate methods of data collectionSix techniques, three of them wellSampling, observation and focus groups get about a sentence each; no two methods are ever compared
Assess categorising, coding, analysingCoding, in real detailNo analysis procedure; sixteen analysis issues stand as bare labels
Evaluate coding optionsCoding's timing and two determinantsNot one coding option is named, so none can be evaluated

Six of the ten. The remaining four are treated below.

Source gap

Two weeks whose objectives appear to belong elsewhere

The qualitative research week promises you will design research tools and evaluate types of variables. It delivers a conceptual survey of qualitative inquiry. The word "variables" occurs exactly once in the entire week — in a quoted table, in the column describing quantitative research.

The qualitative analysis week promises you will evaluate presentation styles for qualitative data. Its analysis half never uses the words present, table, figure, chart or quote; its presentation half never uses the word qualitative. The objective falls in the gap between them.

Both read as documentation errors rather than teaching failures, and it is fairer to record them that way. Judge those weeks by what they deliver instead.

What changed in the final fortnight

For six weeks the ratio did not move. In the seventh and eighth it did, and the change is worth understanding rather than just recording.

The two full deliveries

WEEK 13

Decide on the process for writing your research proposal

Four reviewer questions, four answering claims, four sections, and component lists of eight, five and fourteen items. A reader could write a proposal from this. The internal contradictions do not prevent that — they require you to choose a structure and say which.

WEEK 14

Discuss what you have studied over previous weeks

A comprehensive forty-four-item checklist covering the whole subject, plus an honest statement of how the material expects to be used. The week does what it says it will do.

Note

One judgement on this page is contestable, and it should be visible

The unit review's second objective is to complete overview activities. What is supplied is a checklist to read. This audit records that as partly delivered, on the ground that working through the checklist genuinely does review the subject.

A stricter reading would call it undelivered, because a checklist is not an activity and the week promises "self-assessment activities" specifically. That reading is defensible and would make the totals two delivered, six partly, eleven not.

The judgement is recorded here rather than buried so a reader can take the stricter line if they prefer it. To the source's credit, it discloses the substitution itself: the checklist is reproduced because "from time to time the link does not connect".

What made the difference in Week 13 is worth naming, because it is not effort or length. It is that the week describes a thing rather than listing its parts. The proposal material tells you what a reviewer is trying to find out, what each section is for, and what goes in it. Compare the method catalogue that names ten techniques and says nothing about any of them. Same amount of page space; entirely different result.

Where the material is genuinely strong

An audit that stops at shortfalls is unfair and, worse, useless — it does not tell you where to spend your time. These parts are strong and are the reason the streams exist.

Worth your time

  • The research proposal — the fullest, most concrete treatment of anything in fourteen weeks
  • Questionnaire design and question wording — the most directly actionable guidance in the subject
  • Sampling types — six named with usable distinctions, closing the library's largest recorded gap
  • The six qualitative collection approaches — the fullest data collection treatment supplied
  • The worked inductive categorisation — thirty-one responses into six categories; the only complete worked analysis
  • The results and discussion sections — the only treatment of either anywhere in the dataset
  • The abstract, with an annotated worked example — four moves shown on a real published abstract
  • The supervision breakdown scenario — a failure with no villain, and three competencies that would have prevented it
  • The Do's and Don'ts checklist — forty-four items covering the whole subject in one place

The distinction this page will not blur

Caution

A gap in the files is not a gap in the subject

One week's study notes were listed in the upload manifest and are not present on disk. That week is represented by its slide deck alone, and it carries the entire quantitative analysis content. Its definitional gaps are exactly what you would expect when the definitional document is the one missing.

So those gaps are recorded as gaps in the supplied material. This library makes no claim about what was taught, because nothing in the files supports one.

Where you read "the supplied teaching source does not define X", that statement is accurate and checkable. You will not find a page saying "the subject never taught X".

Note

And an absence that closed

One week was recorded as missing from every delivery for several batches. It was supplied afterwards — and it turned out to be the week that teaches sampling, which had been the library's largest gap.

Naming an absence is how absences get filled. That is the argument for keeping an audit like this one at all, and it is why the four files still missing are still listed.

What the final week says that the audit cannot

From the source

The subject on itself, quoted

"Whilst it is acknowledged that you may not be applying some of this information immediately, it is expected that as you progress on your thesis journey, you will return to these resources to support your work at that time."

That sentence reframes everything above, and it should be read alongside the numbers rather than instead of them. The material was built as a reference set to revisit, not as a self-contained course — and a reference set is fairly judged on whether the right thing is there when you come back for it, not on whether you absorbed it in week nine.

On that standard it does better. The proposal material is there when you write a proposal. The questionnaire guidance is there when you build an instrument. The checklist is there at the end. What it does not survive is the other half of the same claim: many of the resources it tells you to return to are bare addresses, unnamed texts and chapter references into books that were never supplied. You cannot return to what was never reachable. The full argument is at how this material expects to be used.

Using the audit

Triage by what you are about to do

IfYou are writing a research proposal
ThenYou are in the best-served part of the material. Work from it directly.
IfYou are analysing quantitative results
ThenClose the statistics gap first. One rule is given, expressed in a unit that is never defined; no measure of dispersion and no inferential procedure appears anywhere. This is the one absence that can invalidate work already done.
IfYou are choosing between data collection methods
ThenThe comparison you need does not exist. Use the selection questions as a framework and get each method's properties elsewhere.
IfYou are building an instrument
ThenNo instrument of any kind appears in fourteen weeks. The questionnaire and wording guidance is good; get worked models from examined theses.
IfYou are writing up
ThenWell served. The results, discussion, abstract and report-structure material is the strongest run in the subject.
IfYou are planning the project
ThenOne worked schedule exists, with nine demonstrable defects, and no week teaches scheduling. See what goes wrong in a thesis schedule.

What to carry forward

  1. Nineteen objectives, two delivered in full, seven partly, ten not at all — and both full deliveries come in the last fortnight.
  2. Ten shortfalls share one failure: a list of names standing in for a treatment. Ask what you could do with a list before you accept it as coverage.
  3. What made the final weeks work was describing a thing rather than listing its parts. Same page space, different result.
  4. Three earlier totals appear in this library and are superseded. Cite nineteen and nothing else.
  5. A gap in the supplied files is not evidence about the subject as taught — and this material asked to be judged as a reference set, which is a fairer standard than it first looks.

Frequently asked questions

Is this a criticism of the teaching?

No. It assesses the supplied files against the objectives those files state, which is the only standard available. It records nine parts of the material as genuinely strong, and where a document is missing it declines to draw any conclusion about what it contained.

Why do earlier pages give different totals?

Because they audited fewer weeks. Nine objectives over four weeks, then fourteen over six, are both correct for what was then held. Nineteen over eight is current, and no page should cite anything else. The superseded figures are named rather than deleted.

How can an objective be stated and not delivered?

Most often because a set of items is named without being described. An objective to compare methods is not met by a grid of method names, and an objective to evaluate coding options is not met by material that names no coding option at all.

Which parts of the material should I actually rely on?

The research proposal material, questionnaire and question design, the six qualitative collection approaches, the worked categorisation, and the whole write-up run — results, discussion, abstract and report structure. Those are strong enough to work from directly.

What is the single most urgent gap?

Statistics, if your project involves quantitative data. You are given one rule expressed in a unit that is never defined, no measure of dispersion, and no inferential procedure. It is the one absence that can invalidate analysis you have already done.

Does the library fill any of these gaps?

No. The standard it was built to is that missing information is named rather than invented, because a reader who knows they need a second source is better served than one given a plausible definition attributed to material that does not contain it.

References and source attribution

  1. The supplied teaching source: weekly study notes, slide decks and assessment activities for a master's-level research methods subject in project management, covering fourteen topics. Author, institution and year not stated in the supplied files.
  2. Anonymised student submissions supplied with the teaching material, used as observed practice rather than as model answers.

Suggested questions for Ask KEVOS

  • Which learning objectives did this material actually deliver?
  • How do I tell whether a topic has been taught or only named?
  • What are the strongest parts of this research methods material?
  • Which gap should I close first before starting my project?
  • Why does this library refuse to define terms the source leaves undefined?

Related KEVOS knowledge

What This Material Does Not TeachCore · research practiceThe Research Project Lifecycle End to EndCore · research practiceWriting Up and Submission Quick ReferenceFoundation · reporting resultsHow This Material Expects to Be UsedFoundation · research practiceResearch Design and Data Quick ReferenceFoundation · data collectionThe Do's and Don'ts of Social ResearchFoundation · research practice
KEVOS® · Project Delivery · Research Projects Page KVS-PM-RES-0243 · v1.0.0 · content 2026.08 Last reviewed 2026-08-16

Continue learning

The Research Project Lifecycle End to EndGuide · Research ProjectsWriting Up and Submission Quick ReferenceGuide · Research ProjectsWhat a Book Review Reports About a Methods TextGuide · Research ProjectsAnatomy of a Published Book ReviewGuide · Research Projects
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®