<h1>Group Projects Without the WhatsApp File Chaos</h1>
<a href="https://ibb.co/RpkxGr5v"><img src="https://i.ibb.co/8DLWnvhK/Picture1.jpg" alt="Picture1" border="0"></a>
<p>One shared folder at the first meeting saves the last night before the deadline.</p>
<p>Every group project follows the same arc. Enthusiasm, a WhatsApp group, a shared document that someone creates on their personal account, files sent back and forth as attachments, and then, the night before the deadline, six people trying to work out which version of the slides is the real one.</p>
<p>This is a guide to skipping that last part.</p>
<h2>Why the chat is the wrong place for files</h2>
<p>A messaging app is built for messages. Files are an afterthought. Three things go wrong when a group uses it as a filing system.</p>
<p><strong>Versions multiply.</strong> Someone edits the report and sends it back. Someone else was editing the earlier version at the same time. Now there are two, and merging them at 11pm is nobody’s idea of a good evening.</p>
<p><strong>Files expire or vanish.</strong> Chat apps compress images, drop attachments after a period, and lose everything when someone changes phone.</p>
<p><strong>Nobody can find anything.</strong> Scrolling back through three weeks of chat to find the data file is not a retrieval system.</p>
<h2>The setup that works</h2>
<p>One shared folder, created at the first meeting, before anyone has written anything.</p>
<p>Use a <a href="https://proton.me/drive">cloud storage services</a> account that lets you share a folder with the group and give everyone edit access. Inside it, a small structure agreed in the first ten minutes:</p>
<ul>
<li><strong>00 Brief and marking criteria</strong> so nobody has to ask what the task is</li>
<li><strong>01 Research</strong> for sources, notes, data</li>
<li><strong>02 Drafts</strong> with dated filenames</li>
<li><strong>03 Final</strong> which stays empty until the last week</li>
<li><strong>04 Presentation</strong> if there is one</li>
</ul>
<p>The empty Final folder is the discipline. Nothing goes in it until the group agrees it is finished.</p>
<h2>Rules the group agrees once</h2>
<p>Four rules, agreed at the first meeting and never discussed again:</p>
<p><strong>One file, edited in place.</strong> No downloading, editing and re-uploading. Work in the shared copy so there is only ever one.</p>
<p><strong>Dated filenames for drafts.</strong> Report_2026-03-02.docx. When you make major changes, save a new dated copy. Version history is a backup, not a workflow.</p>
<p><strong>Link, never attach.</strong> If you need to point someone at a file, send the link to it in the shared folder. The chat becomes conversation and the folder stays the record.</p>
<p><strong>One person owns the final submission.</strong> They compile, they check, they submit, they share the confirmation. Everyone else stops editing 24 hours before.</p>
<h2>Who owns the folder</h2>
<p>The folder should be owned by an account that will still exist after the module ends, and everyone should have a copy of the final work. If the folder lives on one person’s account and that person leaves the course, drops the module or simply stops replying, the group’s work goes with them.</p>
<p>Simplest fix: at the end, everyone downloads the final folder. Two minutes, and the work is yours regardless of what happens to the shared copy.</p>
<p><a href="https://www.jisc.ac.uk">Jisc</a>, the body that runs digital infrastructure for UK universities, publishes guidance on collaborative tools and data handling for students and staff, including what to think about when group work involves personal data from surveys or interviews.</p>
<h2>Meetings</h2>
<p>Since you have a shared folder, put a running notes document in it. One document, dated headings, three lines per meeting: what was decided, who does what, by when. The person who was not at the meeting reads it instead of asking.</p>
<h2>The point</h2>
<p>Group projects are hard for reasons that have nothing to do with files: uneven effort, different standards, someone who vanishes in week four. Those problems are real and this does not solve them.</p>
<p>What it does is remove the one problem that is entirely avoidable, so that the night before the deadline is about finishing the work rather than finding it.</p>