A thesis in public administration - connecting law, documents and office activity

For an administration thesis, choose a specific part of an office's work and show what legislation and the available documents can tell you about it. For example, you could examine how a service information sheet, form and instructions describe the steps in the same process. Legislation helps establish responsibilities and requirements; documents show how the office presents them; interviews or other data may add an account of practice. Keep those answers separate: a written procedure does not prove that every case followed it.

A topic such as “the operation of a municipal office” can easily turn into pages describing departments and responsibilities. Before writing, choose something you can check: whether the instructions list the same attachments as the form, who passes a document to the next department, or how completion of an activity is recorded. Establish what you can access too. A public website can support analysis of its information, but will not show everything that happens at an employee's desk.

I will explain how to prepare this analysis in two situations: when you use public documents alone and when you can add information obtained from the office. In both cases, keep separate what the law establishes, what the documents say and what you have been able to check in practice. This guide concerns Public administration.

Choose the problem before polishing the title

Start with “I want to establish how…”. Add a specific activity, institution or set of documents and a period. “How does the office explain the steps involved in a selected service?” differs from “How do residents assess their contact with the office?”. Documents can partly address the first question; the second requires material from residents.

Avoid building a finding into the question. “Why does the office operate inefficiently?” assumes what you still need to establish. First specify which features you will examine and how you will assess them. Using the word “efficiency” does not create a measure. An impression from a single visit does not describe the entire institution.

Separate legal rules, organisation and actual activity

Divide your notes into three parts. First, record what the law establishes: who is responsible for the task and which requirements matter to your question. Second, check the organisational rules or procedure: which department is assigned the activity and where it should send the document. Third, record what you could establish about actual events, for example from records authorised for analysis or interviews. Organisational rules establish the adopted allocation of duties, but cannot alone prove that it was followed in every case.

In her article on administrative law scholarship and administrative science, Joanna Nowak discusses differences between examining law and understanding facts relating to the operation of administration. For a thesis project, this has a practical implication: describing a problem as “administrative” still requires you to specify whether you are examining rules, documents, behaviour or their relationship.

A thesis does not have to exhaust all these levels. A careful document analysis can be appropriate if that kind of project has been agreed. The title and conclusions must match its scope. “Service information in office documents” promises something narrower than “quality of service for residents”. Keep that distinction visible throughout the text.

Confirm access before promising a study

List your sources and mark each as publicly available, shared with permission, awaiting confirmation or unavailable. Employment or an internship at an office does not automatically authorise using its documents in a thesis. Agree the permissible scope and presentation of the material with the appropriate people, and check your university's requirements.

If the project depends on information whose availability is uncertain, prepare an alternative. You might narrow the question to public documents or change the selected process. Agree that change with your supervisor before collecting material for a different question. Do not retain an overly broad title simply because it was written down earlier.

For shared materials, establish storage, access restrictions and reporting arrangements from the outset. Remove unnecessary personal data. Removing names alone may be insufficient if the description of an individual case still identifies someone. Consider whether answering the question actually requires information at the level of an individual case.

Discuss legislation without building a chapter from quotations

Select rules connected to your question, rather than every enactment associated with administration. Identify the relevant authority, responsibility and requirements. Distinguish the administrative authority from the office supporting its work. This helps clarify accountability and the role of documents. “Nauka administracji”, edited by Zbigniew Cieślak, distinguishes these concepts and addresses forms of action and organisation.

Specify the date as at which you describe the law, and compare documents with the appropriate legislative version. Current wording may not fit a historical period. Check official texts and relevant amendments. Do not supply procedural deadlines or duties from memory.

After discussing the provisions, explain how you will use them. If you establish who is responsible for a task, say why that leads you to examine that unit's documents. If you derive a requirement from a provision, identify what you will look for in the document and why. Readers can then understand the purpose of citing that rule. If you cannot connect the paragraph to the later analysis, check whether it contains too much general background.

Build an organised document collection

Before comparing documents, ask what each is for. A service sheet may guide residents through the steps, a form may collect information and organisational rules may allocate employees' duties. Do not assess them as if they had identical purposes. If the form lacks an explanation, check the instructions; the gap does not yet mean the office has provided no explanation anywhere. A document's purpose and intended reader help you judge what to expect from it.

For every file, record its author or institution, title, date, version, source, reference period and reason for inclusion. Keep the analysed version where storage is permitted. A web page can change, and the access date is not the date on which the content was created. Both may be needed.

Specify exclusion criteria too. A draft instruction should not be presented as an adopted document. Different years or reporting scopes may prevent a simple comparison. When a document cannot be found publicly, record its absence from the examined collection. This does not automatically prove that the office does not possess it.

Turn broad concepts into analytical criteria

Instead of simply writing “I will assess completeness”, prepare questions for each service sheet: does it explain what residents should do, which documents to prepare, where to submit them and where to ask for help? Choose questions relevant to your project. For each, note whether you are checking a legal requirement established by the relevant provision or your own criterion for useful information. These are different assessments; do not present your checklist as a list of the office's legal duties.

For each question, leave space on the analysis sheet for an answer and a source passage. Under “consistent terminology”, record the name of the same action or attachment from the form and the instructions side by side. Define in advance when you will treat them as consistent. If examining language, you might note unexplained abbreviations or long sentences. These features do not establish that residents fail to understand the text – that would require research with readers.

Test the sheet on several documents. Record ambiguities and refine the categories before analysing the full collection. If the rules change later, return to earlier documents. Otherwise, similar passages may receive different assessments simply because they were analysed at different stages.

Example one: information about a single service

Suppose you plan to examine public materials concerning one service in three offices. Start by checking whether the service, period and document types are comparable. An initial ranking of the best and worst offices would be premature. Selecting three institutions should reflect the project's purpose and feasibility, without implying a representative sample of all offices.

Organise the findings around the questions you checked. For attachment names, place the wording from the form beside the wording from the instructions, give references for both and explain the difference. In the next paragraph, you could compare submission instructions in the same way. This shows where the conclusion comes from rather than summarising three websites separately. Do not add that a discrepancy causes residents to make mistakes if you have not studied their behaviour.

Example two: the organisation of a selected process

A different project could examine document transfers between office departments. Evidence might include authorised procedures, descriptions of activities and interviews with people in particular roles. First obtain permission for that scope and establish whether the documents concern the same process and period.

Separate the model described in a procedure from an employee's account and any records of actual events. An employee's report of a recurring difficulty is valuable participant evidence. It does not automatically measure frequency. Ask about the conditions in which the problem occurs and how it is resolved, instead of inviting confirmation of a predetermined claim about poor organisation.

If comparable, appropriately prepared time records are available, you can analyse them quantitatively. First check the starting event: receipt of a document, transfer to a department or the beginning of work. Define the end of the measurement, time units, pauses and treatment of unusual cases too. Comparison becomes meaningful only under shared rules. An average calculated from differently defined intervals may look correct while combining answers to different questions.

If records of practice are unavailable, limit the outcome to formal arrangements. Do not describe that outcome as a study of the actual handling of every case. Identifying the limitation before writing lets you build a coherent project without filling gaps with assumptions.

What do reports, totals and indicators show?

A count of registered cases concerns a defined recording category. It need not equal the number of people or all contacts with the office. Before comparing years, check definitions, reporting scope and organisational changes. An increase may reflect a different counting method and does not by itself establish deterioration.

Distinguish activity counts, outcomes and users' experiences. Publishing many information items does not demonstrate their completeness. A short time for one step does not describe the entire service. Match the indicator to your question. Where a suitable denominator or comparable categories are unavailable, explain the limitation instead of calculating an impressive percentage.

Not every administration thesis needs a survey or statistical tests. When the question concerns document contents or organisation, other methods may be more important. Quantitative work is useful when it follows from the evidence and purpose, rather than an assumption that numbers automatically make a text scholarly.

Also distinguish missing data from zero. An empty field may mean the category was not collected, the form changed or the information was not released. Do not replace it with zero yourself. Record how incomplete rows are handled and whether excluding them changes the picture. For small collections, give counts alongside percentages. Knowing that a finding concerns two out of a few documents may help readers more than a percentage with a decimal place. Presentation should explain the material and its scale instead of suggesting greater precision than the evidence provides.

Combine sources by examining agreement and differences

For a document transfer, check three accounts separately: what the procedure prescribes, which event the register records and how an employee describes that stage in an interview. Mark where the accounts agree and where they address different things. A register may give the transfer date without explaining the wait; an interview may help explore the reason. Also check whether a report and a summary draw on the same register. Two presentations of one record are not two independent confirmations.

A discrepancy is also a finding requiring explanation. You may be comparing different periods, levels of detail or meanings of a term. Check these possibilities before alleging an irregularity. In your writing, distinguish source information, interpretation and questions the available evidence cannot resolve.

Keep a decision log and a route back to the evidence

When you change the analysis, add a short explanation to your notes. If you combine two categories, say why the documents did not let you distinguish them. If you exclude a report, record whether it covered another year or counted cases differently. Note which instructions replaced an older version too. These notes will help you write the methodology later. You need not publish the entire log, but readers should know about decisions that changed the findings or the question you could answer.

For every important finding, keep a working reference: document, page or section and a short description of the passage. A conclusion about inconsistent information should be traceable to both versions. Check exact wording before quoting. When paraphrasing, preserve the meaning and identify the source. Keep your commentary separate so that, after several weeks, you do not mistake it for the document's contents.

Consider alternative explanations. A difference between offices may reflect different departmental responsibilities, update dates or document functions. You may be unable to confirm every possibility. Present it as a possibility and identify the missing evidence. An analysis is more convincing when it shows which alternatives were checked than when every difference leads to the same accusation.

Before drafting the full chapter, prepare a short findings section: one specific question, two or three connected documents, a finding and a limit on interpretation. Discuss it at the seminar alongside your analysis sheet. This makes it easier to assess the level of detail and whether the categories actually answer the question. Revising at this stage is simpler than rebuilding a completed chapter.

Plan a bachelor's or master's thesis around the project

When planning, write down what readers will learn from each part. You might first explain the concepts and rules needed to understand the selected service. Then describe the office and activity, explain how you chose the documents and how you examined them. Next, show the compared passages and findings, before answering the research question. This is a suggested sequence, not a compulsory chapter count. Agree the structure and level of detail with your supervisor.

A bachelor's project may have a narrower question and smaller collection. A master's project may deepen the comparison, combine sources or develop the discussion further. Requirements depend on the programme and seminar. Do not assume a master's thesis must use a survey or a bachelor's thesis must be descriptive. The Research methods for a bachelor’s or master’s thesis: examples and how to choose explains how to match the approach.

Write conclusions the evidence can support

In the conclusion, return to the question and state exactly what the comparison showed. If the form and instructions name the same attachment differently, identify both passages and explain the inconsistency. You can separately propose using a consistent name. That responds to a problem found in the documents, but without further research it does not establish that the change will shorten service times or reduce residents' mistakes. Keep the finding, its explanation and the improvement proposal distinct.

Limitations may involve one office, document selection, missing evidence from residents or a short period. Explain their effect on inference. “The conclusions concern the analysed materials” is useful when you also explain why they cannot cover every institution. The Limitations of the study in your thesis: explain what they mean for your conclusions can help.

Check coherence before submission

• Does the question concern law, organisation, practice or a clearly defined relationship?
• Is access to the evidence actually confirmed?
• Do you know each important document's date, version and function?
• Are legal requirements separate from your own evaluative criteria?
• Are units, periods and definitions comparable?
• Do conclusions distinguish established facts, interpretations and proposals?

Different stages may call for Help with your thesis outline and structure, Literature search and selection for your thesis, Bachelor’s and master’s thesis consultations or Bachelor’s and master’s thesis proofreading and editing. The choice should reflect the actual difficulty: missing evidence calls for different support from a completed chapter with an unclear argument.

Literature and methodological resources

These publications help clarify concepts and perspectives. Check the current rules relevant to the selected responsibility and the documents of the institution separately.

• Cieślak Z. (ed.), Nauka administracji, 2nd ed., Wolters Kluwer, Warszawa 2017. ISBN 978-83-8107-039-3. Publisher's details and extract: https://www.profinfo.pl/sklep/nauka-administracji,45042.html
• Nowak J., Konceptualizacja doświadczenia prawnego a konceptualizacja faktów związanych z funkcjonowaniem administracji – między nauką prawa administracyjnego a nauką administracji z badań wrocławskich i włoskich administratywistów, “Prawo” 322, 2017. DOI: 10.19195/0524-4544.322.5. https://repozytorium.uni.wroc.pl/Content/96303
• University of Warsaw, Nauka o administracji, course description 4007-L2NAAD7. https://informatorects.uw.edu.pl/pl/courses/view?prz_kod=4007-L2NAAD7