My advisor demands precise online citations yet the style guide is vague—how should I systematically organize and format them?
I’m drafting a literature review for my dissertation and need to include dozens of web articles, datasets, and blog posts, but the citation rules seem contradictory. I’ve tried using a spreadsheet to track URLs and access dates, yet I still lose track of which format each source requires.
1 Answer
It sounds incredibly frustrating to feel like you’re chasing a moving target, especially when you’re already deep in the weeds of a dissertation. To get a handle on this, stop trying to format as you go and instead treat your spreadsheet like a master database. Create columns for the author, title, publication date, URL, and the specific style requirements your advisor mentioned. Think of it like building a kitchen pantry; if you label every jar before you start cooking, you won’t be scrambling for ingredients when the heat is on. Once you have your master list, pick one reliable style guide—even if your advisor is vague, choose the most common one for your field—and apply those rules to your entire list at once rather than doing it piece by piece. If you’re worried about the contradictions, just pick a consistent logic and stick to it across your whole document. Advisors usually care more about your consistency than the specific placement of a comma, because a uniform system shows you’ve put in the work to be organized. If you’re still unsure, draft a single sample page with a few tricky sources and ask your advisor to confirm if that specific layout works for them. It’s much easier for them to approve a template than to critique a finished draft that’s formatted incorrectly. You’ve clearly put a lot of effort into gathering these sources, so take a deep breath and trust that a little bit of upfront structure will save you hours of headache later on. You’ve got this, and once you have a rhythm, the rest of your literature review will fall into place much faster than you think.
In-depth guide available
Why a Capture‑Classify‑Format Workflow Beats Vague Style Rules →Have a similar question?
Ask the community →