Evaluation timeframe decisions determine which service episodes, records and outcomes belong in a nursing dissertation. A start date and end date are not enough when referrals cross the boundary, follow-up happens later or the service changes during collection. This guide explains how to define those boundaries so that the question, dataset and conclusion describe the same period.
This guide examines which events and episodes fall inside the observation window. Its practical output is a boundary-case timeline identifying index dates, follow-up opportunities and incomplete episodes. Begin with the how to write a focused nursing service evaluation question if you first need to establish the broader project approach. Use the timeframe decisions below once that foundation is clear.
Define the evaluation timeframe in terms of events
Begin with the event that makes a person, contact or episode relevant to the evaluation. This might be an eligible referral, an appointment or a completed service episode. The right event depends on the question. Do not use the date that happens to be easiest to export without explaining what it represents.
Write a sentence specifying the event and its permitted dates. For example, a fictional project might include eligible referrals received between two stated dates, regardless of when the first appointment occurred. That creates a referral cohort. A project including appointments delivered in that period creates a different dataset and may include referrals received earlier.
Evaluation timeframe: distinguish four key dates
The service period is when relevant activity occurs. The extraction date is when records are obtained. The follow-up window is the time allowed for a later event to be observed. The dissertation submission date is an academic deadline. These dates can overlap, but they perform different functions.
A late extraction may allow more complete follow-up for recent episodes. It may also include retrospective record updates. State which record status the extract represents. Readers should be able to tell whether the dataset describes activity as recorded at the time or activity reconstructed after a later documentation period.
Choose a cohort view or an activity view
A cohort view follows a defined group entering the service during a specified period. An activity view counts specified contacts or events delivered during that period. Neither is inherently superior. Choose the view that answers your question and explain the consequences for inclusion.
If the question concerns the path from referral to first contact, the entry event needs attention. If it concerns the volume of appointments delivered, an activity window may be appropriate. Avoid moving between the two views in the results. A count of referrals and a count of appointments cannot be treated as matching populations simply because their dates match.
Worked example: referrals crossing a boundary
This example is fictional. A service receives a referral on 28 March and delivers the first appointment on 6 April. Another referral arrives on 29 April, but its appointment occurs in May. An evaluation described only as “April activity” leaves both cases ambiguous.
If the project includes referrals received in April, the March referral is excluded from that cohort even though an appointment occurs in April. The late-April referral is included, but the researcher needs a defined follow-up window to observe its later appointment. If the project instead includes appointments delivered in April, the March referral’s appointment belongs and the May appointment does not.
Both approaches can be correct for different questions. The error is to count the April appointments as though they were the complete follow-up of April referrals. A simple boundary table can reveal this mismatch before data collection begins.
Document the evaluation timeframe in a boundary table
| Decision | What to specify | Why it matters |
|---|---|---|
| Entry event | Referral, contact or episode completion | Defines the eligible group |
| Observation period | Inclusive dates and any operating-day rules | Determines which events count |
| Follow-up | Permitted time after entry and final observation date | Prevents unequal opportunity to observe later events |
| Extraction | Date and record version | Explains retrospective updates |
| Incomplete episodes | Separate status and reporting rule | Avoids treating unobserved events as failures |
Give later entrants a defined observation opportunity
A person entering on the final day of collection has had less time to experience a later event than a person entering on the first day. Comparing their apparent completion status without considering that difference can mislead. Define how much observation is required for the particular outcome.
One option may be to restrict a descriptive outcome summary to episodes with an agreed opportunity for follow-up. Another may be to report incomplete observation separately. The appropriate choice depends on the purpose and approved plan. Do not quietly remove recent entrants after seeing their results or describe them as having failed to complete an event that could not yet be observed.
Keep incomplete episodes distinct from negative outcomes
An episode still open at extraction is not necessarily an unsuccessful episode. Its eventual result is unknown within the available window. Equally, an outcome recorded as absent is not the same as an outcome that was never collected. Define these statuses separately.
For example, use transparent categories such as completed within observation, not completed within the specified window and observation incomplete, where appropriate to the approved project. Explain exactly what each category means. Do not introduce statistical terminology you cannot support; an ordinary descriptive account of incomplete follow-up may be enough for the question.
Align the timeframe with the service pathway
A window should reflect the process being evaluated. A single consultation can be observed differently from a pathway involving referral, assessment and later review. Describe the stages relevant to your question before deciding how long records must remain observable.
Do not select a longer period merely because it sounds more rigorous. It may bring additional service changes, different recording systems or approval requirements. Conversely, a short window may exclude a meaningful part of the pathway. Explain the balance between practical access and the information needed to answer the question honestly.
Account for documentation delay
Some events are entered into a record after they occur. A field extracted immediately after a visit may appear blank and later be completed. Ask whether the service has a known recording process, and document how the extraction timing relates to it.
If the project cannot distinguish a delayed entry from an absent activity, state that limitation. Avoid assuming that all late documentation represents care delivered on time. The record may support only a statement about what was documented by the extraction date. That narrower statement can still be useful when documentation timeliness is itself the focus.
Handle service changes within the period
A new referral route, staffing model or information system can change the meaning of observations collected before and after its introduction. Record known dates and consider whether one combined description would conceal different operating conditions.
You may need to describe periods separately or limit the evaluation to a clearly defined service configuration. The choice should follow the question and available evidence. Do not split the period repeatedly until a favourable pattern appears. Explain any planned subdivision and document amendments so readers can distinguish a justified design decision from selective presentation.
Consider seasonality without claiming representativeness
A term-time clinic, holiday period or seasonal demand change may affect who attends and how the service operates. Equal numbers of weeks do not guarantee equivalent conditions. Describe relevant context rather than asserting that a convenient window is typical.
If the evaluation covers only a limited season, keep the conclusion within that season unless wider evidence supports extension. A recommendation for measurement in another period may be more useful than a broad claim about year-round performance. The aim is to make the coverage clear, not to make a short student project appear larger than it is.
Specify calendar and operating-day rules
If your measure includes elapsed time, define whether you use calendar days, working days or actual service operating days. Explain treatment of weekends, holidays and temporary closures. The same interval can produce different numbers under different rules.
Use a rule that fits the question and any verified applicable definition. If the service’s records contain dates without times, avoid reporting hours as though precise timestamps were available. Retain an explicit rule for same-day events and incomplete dates. These details prevent apparently small coding choices from becoming unexplained differences in the final findings.
Distinguish the timeframe from a baseline comparison
The overall observation window determines what can enter the evaluation. A baseline period serves a specific role as a reference position. A target date identifies an intended future milestone. These concepts may interact, but they should not be collapsed into one vague statement about project dates.
Our guide to baselines and targets addresses comparison and ambition. This article focuses on eligibility over time and the opportunity to observe events. Keeping those boundaries distinct helps avoid presenting a descriptive period as evidence that a change caused improvement.
Explain the evaluation timeframe in your methods
A strong methods paragraph identifies the entry event, inclusive dates, follow-up rule, extraction date and treatment of incomplete episodes. Add the reason each boundary fits the question. Avoid describing only the dates on which you personally worked on the dissertation.
For a record-based project, explain which approved data fields represent those dates. For interviews or feedback, distinguish when experiences occurred from when people were asked about them. A participant interviewed in June may describe an encounter from March. That recall period needs its own definition if it affects eligibility or interpretation.
Match feedback recall to the relevant encounter
A general question about “your recent care” can bring together experiences from very different periods. Decide whether feedback concerns one named encounter, a complete episode or the service more broadly. Use wording that helps participants identify the intended experience without disclosing unnecessary information.
Recall limitations should be discussed in relation to the question. A long interval may make precise timing harder to remember, while an immediate invitation may miss later consequences. There is no universal best delay for every feedback project. Explain the choice and acknowledge which part of the experience it is likely to capture.
Check the denominator at each boundary
Make sure the eligible count follows the same timing rule as the reported event. If the numerator counts outcomes from episodes beginning earlier, a denominator of only new episodes this month may be incompatible. Trace a few fictional boundary cases before applying the rule to approved records.
The guide to numerators and denominators explains the counting problem in more detail. Here, the key question is whether every counted episode has the required temporal relationship to the event. A mathematically correct fraction can still describe a poorly defined period.
Report what the window cannot capture
A project ending before later follow-up cannot establish longer-term experience or outcomes. A brief window may also miss infrequent events. State those limits in concrete terms and avoid converting “not observed” into “did not occur”.
Link any recommendation to the limitation. For example, a service might consider reviewing later outcomes through an approved process, while the dissertation reports only the initial contact stage. The focused-question guide can help narrow a question that currently requires more follow-up than the project can realistically obtain.
Test boundary cases with a small fictional timeline
Before extraction, list an episode entering just before the window, one entering on its first day, one entering on its last day and one completing after extraction. Apply the proposed rules to each case. If two readers reach different inclusion decisions, clarify the rule before handling approved records.
This exercise also exposes whether the project unintentionally mixes a cohort with an activity count. A person may legitimately contribute more than one contact to an activity review while contributing only one entry to an episode-based cohort. State which relationship the question requires. The timeline is a planning aid, not a substitute for permission to access records.
Check the final day explicitly. If the rule says “to 30 April”, explain whether the whole day is included and how records without precise times are treated. Avoid false precision. A clear date-based rule is preferable to an apparently exact timestamp boundary that the underlying data cannot support.
Timeframe decision checklist
- Identify the entry event and counting unit.
- State inclusive observation dates.
- Separate service activity from extraction and submission dates.
- Define follow-up opportunity for later events.
- Report incomplete observation separately from negative outcomes.
- Document service changes, closures and recording delays.
- Explain calendar-day or operating-day rules where relevant.
- Keep conclusions within the period and pathway stages actually observed.
Keep the abstract consistent with the observation window
The abstract often compresses a careful methods account into a broad phrase such as “current service performance”. Replace that phrase with the actual period and relevant episode boundary where space permits. A short description should not imply longer follow-up than the project obtained.
Check every headline number against the same timing rule. If different results use different eligible groups, label them rather than presenting one overall sample size as though it applies to every analysis. This final consistency review helps the reader understand why an entry count, contact count and completed-episode count may legitimately differ within one evaluation.
Frequently asked questions
Can I choose the most recent three months?
Possibly, but recency alone is not a rationale. Check whether those months cover the relevant pathway, permit sufficient observation and contain known service changes. Explain why the window fits your question and what it cannot represent. Use only data within the approved access arrangements.
Should I include episodes that started before the window?
That depends on whether your question concerns entrants, completed episodes or activity delivered during the window. Define the view before extraction. An earlier referral may belong in an appointment-based activity review while remaining outside a cohort defined by referral date.
Is an open episode an unsuccessful episode?
Not automatically. The eventual outcome may be unknown because observation ended first. Explain the follow-up rule and report incomplete episodes transparently. Avoid classifying them as failures simply because no final outcome appears in the available extract.
Must compared periods be the same length?
Equal length can help interpretation but does not guarantee comparability. Population, demand, eligibility and operating conditions also matter. If lengths differ, explain the measurement implications and avoid comparing raw counts as though observation opportunities were identical.
Can I extend the window after seeing the results?
A justified amendment may be possible through the appropriate local process, but document the reason and consequences. Do not extend or shorten collection simply to obtain a more attractive finding. Approval, access and the original question still govern what can be included.
Refine a manageable nursing dissertation plan
A realistic timeframe connects the question to events you can actually observe. Our nursing evaluation support can help you review an anonymised timing diagram or methods paragraph. Send a focused enquiry about the boundary you are struggling to define. Keep records confidential and use educational feedback to strengthen your own explanation and locally approved plan.
Reference
NHS Institute for Innovation and Improvement (n.d.) The how-to guide for measurement for improvement. Available at: NHS England (Accessed: 16 October 2026). This general measurement resource provides wider context; the boundary examples above are original teaching examples.
