A logistics or supply-chain thesis cohort hosted inside real companies — a distribution centre, a carrier, a manufacturer’s planning team — keeps stalling at the same point: a student secures informal access to operational data, writes most of the analysis, and only then discovers the company expects sign-off before anything specific about its operations appears in a public document. Without a standing access-agreement template, that discovery lands late, costs weeks the submission calendar does not have, and repeats itself with the next company-hosted cohort because nothing from the last stall was written down. A department that has been through this once, and still has nothing written down to show for it, is choosing to repeat the same costly discovery indefinitely.
Where the bottleneck actually sits
The friction is rarely the company’s willingness to host a student — many companies are glad to have a motivated analyst look at a real operational problem. The friction is the absence of a written agreement covering what the student can see, what they can name specifically in the thesis (facility locations, supplier names, throughput figures), and who signs off before submission. Without that agreement negotiated at the start, the company’s own legal or communications team ends up reviewing a finished thesis under deadline pressure, which is the worst possible time to discover a disagreement about what can be published.
What a workable access agreement actually needs to cover
Four elements, negotiated before data collection begins: which operational data the student can access and analyse; which specific findings can be named in the public thesis versus anonymised or aggregated; a fixed pre-submission review window, set as a specific number of days worked back from the submission calendar, during which the company can flag a concern without gaining editorial control over the thesis’s conclusions; and an explicit statement that the company owns its own underlying operational data while the student owns their own analysis and interpretation. A template covering these four elements, drafted once by the graduate school’s research-partnerships office and reused across placements, replaces a negotiation a student and a company currently have to invent from scratch each time.
Why this costs the department more than it looks like
A stalled company placement does not just cost the one student affected — it costs the department’s standing with that company for future cohorts. A company that had a bad experience with an under-specified access agreement on one placement is a harder sell for the next student who wants to work with them, and a department that loses access to its best industry partners over a solvable paperwork problem is trading a one-time fix for a recurring loss of placement capacity.
What the fix looks like once the template exists
A logistics or supply-chain faculty that adopts a standing access-agreement template moves the negotiation from “whatever the student and company work out informally” to “a known document both sides review and sign before data collection starts.” The same discipline this site covers for a different field’s agency-hosted placements — setting up a data-sharing and access agreement for a thesis hosted inside a government agency — applies directly here, with the host organisation type swapped from a government agency to a logistics or supply-chain company and the specific access tiers adjusted to operational rather than public-records data.
How this intersects with the department’s own proposal-review process
A logistics or supply-chain programme sitting inside a business school already runs some form of proposal-review committee process for every thesis topic, and the access-agreement check belongs inside that same review, not as a separate gate a student has to clear on their own initiative. Adding one question to the existing intake form — is an access agreement in place or in progress for this placement, and who is the named company contact — catches a missing agreement at the same point the committee already checks methodology and scope, rather than leaving it to surface only once a student has already started data collection.
What a supervisor should check before approving a company-hosted proposal
A short checklist, not a full legal review: does the agreement name what data the student can access, does it separate analysable data from publishable findings, does it specify a review window with a named company contact, and does it state who owns what. A supervisor confirming these four items at proposal stage catches a missing agreement before a student has invested months in analysis the company may not let them publish as written.
How this affects the thesis timeline specifically
The failure pattern without a template shows up predictably late: a student finishes a full draft, sends it to the company for the first time at the same moment it goes to the examination committee, and the company’s review either surfaces a redaction request the submission calendar cannot absorb or, in the worst case, blocks publication of the thesis’s central findings entirely. Negotiating the access terms before data collection begins, rather than after a draft exists, moves that risk to a point in the timeline where it costs a conversation rather than a missed submission deadline.
Why supply-chain theses hit this friction more than most fields
Operational data in logistics and supply chain — throughput volumes, supplier relationships, routing efficiency, warehouse layouts — sits closer to a company’s competitive position than the data a company might share for a marketing or HR thesis, which makes companies in this sector more cautious about what appears in a public document, not less willing to host students at all. A department that treats a supply-chain placement’s access negotiation the same way it treats a lower-stakes placement in a less commercially sensitive field underestimates how much specificity the company will actually want to review before publication, and ends up surprised by a review request a more sector-aware template would have anticipated.
What a company’s own reluctance usually signals
A company that hesitates over an access agreement is rarely objecting to the student’s presence — it is usually objecting to an unclear scope. A vague request to “analyse our supply chain operations” reads to a company’s legal or operations team as an open-ended commitment they cannot evaluate, while a specific request naming the exact process, dataset and time window the student needs to analyse is something they can approve or decline with confidence. A department that coaches students to bring a specific, scoped request rather than an open-ended one removes a large share of the hesitation before the access-agreement conversation even starts.
Building the template to survive staff turnover on both sides
A company’s own point of contact for a placement changes jobs; a department’s supervisor changes departments. An access agreement that lives only in the memory of the two people who originally negotiated it does not survive either change, and the next person on either side has to reconstruct the arrangement from scratch, often less favourably than the original. A written template, filed centrally by the graduate school rather than held in one supervisor’s email archive, survives both kinds of turnover and gives whoever inherits the relationship a starting point rather than a blank page.
Why a single generic non-disclosure agreement is not enough on its own
Companies sometimes offer a standard non-disclosure agreement as their entire answer to a student’s access request, and a department should recognise this as necessary but insufficient: an NDA covers confidentiality of what the student sees, but it does not by itself specify what the student can name in a public thesis, who reviews the draft before submission, or who owns the resulting analysis. A department that accepts an NDA alone, without the four additional elements a proper access agreement covers, is still exposed to the same late-stage surprise the NDA was meant to prevent — it has protected the company’s confidentiality, but not clarified the student’s publication rights.
Why this belongs to the graduate school, not each supervisor individually
A supervisor negotiating a fresh access agreement with a new company for every placement, without a standing template to start from, is solving the same problem from zero each time — and a supervisor without legal training is not well placed to spot a gap in an informal arrangement a company’s own legal team would catch immediately. A graduate school or research-partnerships office that owns the template, and logs which companies have hosted placements before and on what terms, builds institutional memory that survives a supervisor changing departments or a company contact moving roles.
Sizing this against the faculty’s other capacity pressures
A stalled access agreement compounds the same scheduling pressure covered in this site’s piece on the capacity cliff a whole cohort creates when too many dissertations land in the same narrow window: a placement that stalls for weeks over an access dispute pushes that student’s submission into the same crunch period every other student is already competing for supervisor and examiner time in, turning a one-student problem into a cohort-wide scheduling problem.
Where Tesify fits
The access agreement itself is a negotiation between the graduate school’s research-partnerships office, the company and the student’s supervisor — none of it is a writing-platform decision. Once a student has cleared access and moved into drafting, Tesify is the platform candidates use to write their own thesis chapter by chapter: more than 9,000 students have written over 15,000 chapters with it, and the thesis stays 100% written by the candidate. See how Tesify supports a logistics and supply-chain thesis cohort.
Frequently asked questions
What causes a company-hosted logistics thesis to stall?
Typically, the absence of a written access agreement covering what data the student can see, what can be named in the public thesis, and who signs off before submission — discovered late, after most of the analysis is already written.
What should the access agreement separate explicitly?
Data the student can analyse from findings the student can publish, as two distinct permissions, with a named company contact who signs off on the second before submission.
How long should the company’s pre-submission review window be?
A specific number of days, fixed against the department’s own submission calendar, so the review neither slips past the deadline nor gives the company indefinite control over the timeline.
Who owns the data analysed during a company placement?
The company retains ownership of its own underlying operational data; the student retains authorship of their own analysis and interpretation. Stating this explicitly avoids a later dispute over who controls what.
Does a stalled placement affect only the one student involved?
No. It also damages the department’s standing with that company for future placements, and it pushes the affected student’s submission into the same capacity crunch every other student in the cohort is competing for.
Who should own the access-agreement template?
The graduate school or research-partnerships office, not individual supervisors, so the template is maintained consistently and the department retains institutional memory of past company placements regardless of staff changes.
Is a standard non-disclosure agreement enough on its own?
No. An NDA covers confidentiality of what the student sees, but it does not specify what can be named in the public thesis, who reviews the draft before submission, or who owns the resulting analysis — a full access agreement needs all four elements, not confidentiality alone.
Should the access-agreement check sit inside the existing proposal-review process?
Yes. Adding one question to the department’s existing intake form — whether an agreement is in place and who the named company contact is — catches a missing agreement at proposal stage rather than leaving it to surface after data collection has started.