A proposal clears academic review — sound research question, defensible methodology, engaged supervisor — and then stalls for weeks because the student discovers, only after approval, that the commercial database or company dataset the proposal assumed access to is not actually available to them. This is the single most common reason an Accounting & Finance dissertation misses its cohort deadline, and by the time it surfaces, the student has already lost weeks of drafting time on a design that has to be reworked from the data-access question backward.
The pattern, and why it keeps recurring
Accounting and finance dissertations lean heavily on data most students cannot access independently: WRDS, Bloomberg Terminal and Refinitiv Eikon for market and financial-statement data, or a specific company’s internal records for a case-based project. This site’s own comparison of statistical and analysis software for an Accounting & Finance faculty covers the platform decision itself; the pattern this piece addresses is upstream of that — a proposal-review process that approves a research design on academic merit without first confirming the student actually has, or can realistically obtain, access to the specific data source the design depends on. A student assumes access will follow naturally once they need it; a supervisor assumes the student has already checked; and the gap surfaces only once the student is actively trying to pull data and discovers the licence does not extend to them, or the company contact who promised records access has gone quiet.
Three ways the gap typically surfaces
The pattern is not one single failure mode but three related ones, each worth naming so a proposal-review committee knows specifically what to ask about. First, a seat-licence gap: the faculty holds a WRDS or Refinitiv subscription, but individual seat access is limited and a student assumes enrolment alone grants it, discovering only later that a separate request and approval step was required. Second, a scope gap: the student has general database access but the specific dataset their proposal depends on — a particular exchange’s historical records, a specialised bond-pricing feed — sits behind an additional licence tier the faculty’s subscription does not cover. Third, and hardest to control for at proposal stage, a relationship gap: a case-based project depends on a named company’s internal records or interview access, informally promised during initial conversations but never formalised, and that access quietly evaporates once the company’s own priorities shift months later. A pre-check that only asks “do you have data access” in general terms misses the distinction between these three; a pre-check that asks the student to name the specific database, tier and confirmation source catches all three specifically.
What a well-designed pre-check form actually asks
A pre-check that catches all three gaps above is short — a single page — but specific. It asks the student to name the exact database or data source the proposal depends on, not a general category; to state which access tier that source requires and whether the student has confirmed, in writing, that they currently hold it; and, for a company-based project specifically, to name the individual contact who has agreed to provide access and attach or summarise that agreement, rather than describing it as “access has been discussed.” A committee reviewing this pre-check is not assessing the research design at this stage — that is the full proposal review’s job — it is checking only whether the data-access claim is specific and confirmed enough to be credible. A vague answer at this stage (“I will use WRDS,” with no confirmation of seat access; “the company is supportive,” with no named contact or written agreement) is itself the signal that the proposal is not yet ready for full review, regardless of how strong the underlying research question is.
Why this costs the faculty more than the individual student’s timeline
Every proposal that stalls on a late-discovered data-access gap consumes disproportionate staff time to unwind: the supervisor spends meetings re-scoping a design that should have been checked at the outset, the programme office fields an anxious student asking for a deadline extension, and in a bad case, the student switches topics entirely months into the term, losing the literature-review and methodology work already completed. Multiplied across a cohort, a data-access gap that recurs in even a modest share of proposals each intake is a genuine drag on the faculty’s overall completion-rate and time-to-defence figures — a slower, quieter version of the seasonal capacity problem this site’s piece on five hundred dissertations landing in the same eight weeks describes for supervision staffing generally.
The fix is a pre-check, not a post-mortem
The structural fix is the same one this site’s companion piece on structuring a nursing faculty’s proposal-review workflow applies to a different feasibility question in a different field: move the confirmation question upstream, before full committee review, rather than discovering the gap after approval. A one-page data-access pre-check — which specific database, tier or company relationship the proposal depends on, and written confirmation that the student currently has, or has a credible, named plan to obtain, that access — catches the same failure mode the placement-feasibility check catches for a nursing proposal: a design built around a resource that was never confirmed available, discovered only after the student has invested real drafting time in it. This is a small addition to an existing review process, not a new committee or a new software purchase, and faculties that add it report catching the gap in a matter of days rather than weeks.
What this means for enrolment momentum specifically
A prospective student comparing accounting and finance programmes increasingly asks about completion timelines directly — word travels within a cohort and between intakes when a data-access stall becomes a known, recurring pain point rather than an isolated bad-luck story. A faculty that can credibly say its proposal process checks data-access feasibility before approval, not after, has a genuine, defensible answer to that question, and a smoother, more predictable pipeline from proposal to defence supports the faculty’s own enrolment and reputation goals in a way that is easy to overlook when the fix is framed only as an administrative process change rather than connected to the momentum it actually protects.
Where a structured drafting workspace fits, once the proposal clears
Once a proposal has cleared both academic review and the data-access pre-check, the next friction point is usually supervisor visibility during drafting — not knowing whether a student is actively working, stuck, or quietly drifting from the approved scope until a chapter is overdue. Tesify for Institutions gives supervisors that visibility directly: progress against the approved proposal, drafting activity over time, and an early signal if a chapter’s direction is diverging from what was approved, rather than discovering drift only at the next scheduled supervision meeting. This does not replace the data-access pre-check or the committee’s own judgement — it addresses the separate, later-stage visibility gap that persists even once the upstream proposal-review fix above is in place.
The free departmental pilot
A faculty does not need a procurement decision to test this. A free departmental pilot puts one supervisor group or cohort on the platform for a term, with no purchase commitment, so the faculty can evaluate whether the supervisor-visibility benefit actually holds against its own students’ real drafting patterns before any wider rollout conversation. This is deliberately the same low-commitment, zero-procurement entry point this site’s other Growth Engine pieces describe — a pilot clears internal approval processes in a way a purchase order does not, and it gives the faculty its own evidence rather than a vendor’s general claim. A faculty running the pilot alongside the data-access pre-check introduced above, in the same term, gets a cleaner read on both fixes at once — fewer stalled proposals at the front of the pipeline, and better supervisor visibility once drafting is underway.
Addressing the integrity objection directly
A reasonable question from an integrity officer or programme director evaluating this: does giving students a structured drafting workspace create an academic-integrity risk of its own? The honest answer is that a writing platform used for drafting support and supervisor visibility is a different category of tool from an AI writing generator, and the faculty’s own AI-use policy — covered in more depth in this site’s piece on what a law faculty should add to a university AI policy, whose underlying disclosure-and-boundary logic applies broadly across faculties — should state explicitly what use is permitted, rather than leaving students to guess. A pilot is a low-risk way for the faculty’s own integrity office to evaluate this directly against its current policy, rather than deciding the question in the abstract before ever seeing the tool in use.
Frequently asked questions
What is the most common reason an Accounting & Finance dissertation proposal stalls?
A data-access gap: the proposal assumes access to a commercial database (WRDS, Bloomberg, Refinitiv, a specific company’s internal records) that the student does not yet have confirmed access to at the time the proposal is submitted, discovered only after academic approval.
What are the three ways this data-access gap typically surfaces?
A seat-licence gap (enrolment alone does not grant database access), a scope gap (general access does not cover the specific dataset tier the proposal needs), and a relationship gap (informally promised company data or interview access that is never formalised and later evaporates).
What does a well-designed data-access pre-check actually ask the student?
The exact database or data source the proposal depends on, the specific access tier required and written confirmation the student holds it, and for a company-based project, the named contact who has agreed to provide access rather than a vague statement that the company is supportive.
How does a data-access pre-check reduce proposal-review delay?
By moving the access-confirmation question to before full proposal review, rather than after, so a proposal built around genuinely unavailable data is caught in a one-page pre-check rather than a full committee cycle.
Does Tesify replace the faculty’s own proposal-review committee?
No. The academic and data-feasibility judgement stays entirely with the committee. Tesify supports the drafting stage once a proposal is approved, giving supervisors visibility into progress against the approved scope.
What does a free departmental pilot actually involve?
One cohort or supervisor group tests the platform for a term, with no procurement commitment, so the faculty can evaluate fit against its own proposal-review and supervision workflow before any purchasing decision.
Is student and research data hosted securely, and where?
Data residency, GDPR and FERPA posture are procurement and data-protection office questions the faculty’s IT and legal teams review directly as part of any pilot or purchase — this article does not assert a specific figure or claim not confirmed with those teams.
How is this different from the site’s Business School proposal-review piece?
That piece addresses a company-based-project and committee-capacity bottleneck for a business school generally. This piece is specific to Accounting & Finance’s own recurring failure mode — a data-source access gap discovered after approval — which is a narrower and more field-specific problem with its own fix.