Keeping Project Documentation Organized Across Projects

File It Right: Documentation Tips for Quantity Surveyors 1. Maintain a clear and consistent project-based filing system. E.g., create folders like “Project_A > Tender Stage > Drawings” or “Project_B > Site Records > Payment Certificates.” 2. Use standard naming conventions for all documents. E.g.: Name files like “ABC_Hotel_Project_BOQ_V3_2025-07-20.xlsx” or “Site_Measurement_Report_BlockA_2025-07-15.pdf”. 3. Digitize physical documents and back up files in cloud storage. E.g.: Scan signed variation orders and save them on Google Drive or OneDrive with the same structure as your local folders. 4. Keep a document register to track incoming and outgoing files. E.g.: Maintain an Excel sheet listing documents like “RFI #002 – Received from Architect on 20/07/2025 – Forwarded to Contractor.” 5. Follow a standardized document control procedure. E.g : Ensure every cost estimate is reviewed, signed, dated, and marked “Final” before distribution. 6. Use templates for reports, valuations, and other formal submissions. E.g: Use a standard Excel template for monthly valuations showing approved quantities, rates, and cumulative totals. 7. Ensure all documents are traceable to their sources (e.g., invoices, drawings). E.g : Link your cost report items to supporting documents like subcontractor quotes or supplier invoices. 8. Secure confidential files with passwords and access controls. E.g: Protect final account statements and commercial contracts with document-level passwords. 9. Coordinate document updates and version control with project stakeholders. E.g : Share revised BOQs or cost plans via email with version numbers and a changelog summary. 10. Conduct regular reviews and audits of your documentation system. E.g: Set a weekly or monthly reminder to archive old files, rename incorrectly labeled documents, and remove duplicates. Remember, a well-organized filing system is essential to ensure accuracy, accountability, and efficiency across all project stages. It allows easy access to key documents such as drawings, cost plans, contracts, and valuations, which supports better decision-making and reduces the risk of errors or disputes. In a profession where detail and traceability are critical, a strong filing system is not just good practice, it’s a professional necessity.

I tried building a version of the LLM wiki idea Andrej Karpathy shared, but the motivation for it was already there. Everything I work on already exists somewhere. Notes, docs, past experiments, internal writeups. Nothing is missing. The problem is that once something is written, it stays isolated and doesn’t connect back into the rest of the system in a way that is usable later. What that turns into is repeated work. You know you’ve already thought through something, but you still have to go back, search for it, read it again, and rebuild the context to get to the same point. So instead of adding another tool or another storage layer, I changed how the existing setup behaves. All the source content stays where it is. Notion, local docs, project notes. This sits on top and maintains a structured view of it. It reads through everything once, links related pieces, keeps summaries updated, and holds that as a layer that can be queried directly. Queries are no longer operating on raw documents. They operate on something that has already been processed and organized once, which removes most of the back-and-forth needed to get to a usable answer when the context is spread across multiple places. As more gets added, it doesn’t just sit there. It gets integrated into that structure, so you’re not manually maintaining connections between pieces over time. One thing I added on top of this was a repair pass. Over time, any system like this drifts. Some parts stop being relevant, some links don’t make sense anymore, and parts of it turn into storage without contributing anything useful. So there’s a pass that goes through the entire wiki, checks what still relates, what doesn’t, and restructures it into something usable again instead of letting it become a graveyard of documents. Right now this is wired into my own Notion docs and ongoing work. Nothing new was created for it, the focus was on making what already exists easier to work with. I’m still refining how this behaves across different types of content, and once that stabilizes I’ll open source it so that you can also use it without needing to set it up from scratch. If you were setting this up, what would you plug in as a source beyond docs and notes?

𝗧𝗵𝗲𝘀𝗲 𝘁𝗼𝗼𝗹𝘀, 𝗵𝗲𝗹𝗽𝗲𝗱 𝗺𝗲 stop drowning in the chaos of managing multiple projects simultaneously while keeping C-suite stakeholders informed and cross-functional teams productive. Two years ago, I was juggling five active projects across different teams, with varying timelines and competing priorities. My inbox had 200+ unread emails, project updates were scattered across endless email threads, and I spent more time hunting for information than actually managing projects. Sound familiar? Here's what saved my sanity: → 𝗔𝘀𝗮𝗻𝗮 - Project timelines that auto-update when dependencies shift. No more manual Gantt chart nightmares when scope changes hit. → 𝗦𝗹𝗮𝗰𝗸 - Organized project channels replaced email chaos. Each project gets its own space, decisions are documented, and nothing gets buried in threads. → 𝗟𝗼𝗼𝗺 - Quick video explanations replaced status meetings. Five-minute screen recordings for complex technical updates saved hours of calendar coordination. → 𝗡𝗼𝘁𝗶𝗼𝗻 - Became my project knowledge base. Meeting notes, decisions, templates, and project artifacts are all searchable in one place. → 𝗠𝗼𝗻𝗱𝗮𝘆.𝗰𝗼𝗺 - Visual project boards that executives actually understand. Status reporting went from PowerPoint decks to real-time dashboards. → 𝗧𝗼𝗴𝗴𝗹 - Time tracking that doesn't feel like micromanagement. Finally had real data for resource planning and accurate future estimates. → 𝗠𝗶𝗿𝗼 - Virtual collaboration that actually works. Requirements gathering, process mapping, and stakeholder alignment sessions for distributed teams. → 𝗖𝗹𝗶𝗰𝗸𝗨𝗽 - Custom workflows for different project types. What works for software development doesn't work for marketing campaigns or facility upgrades. → 𝗝𝗶𝗿𝗮 - When you need serious issue and change management. Bug tracking, change requests, and technical project coordination that scales. → 𝗔𝗶𝗿𝘁𝗮𝗯𝗹𝗲 - Database power without complexity. Resource management, vendor coordination, and project portfolio tracking that makes sense. → 𝗖𝗮𝗹𝗲𝗻𝗱𝗹𝘆 - Eliminated scheduling ping-pong with busy stakeholders. Meeting coordination went from hours of back-and-forth to automatic booking. → 𝗭𝗮𝗽𝗶𝗲𝗿 - Connected everything together. Project data flows automatically between tools, eliminating manual copying and spreadsheet updates. The breakthrough wasn't using more tools. It was using the right tool for each specific challenge. Task management, stakeholder communication, time tracking, documentation, and team collaboration all require different approaches. If this sounds familiar, I put together a simple guide that shows what each tool does best and when to use them. Because the right tool at the right moment can transform project chaos into smooth execution. Follow Brian Ables, PMP, for practical tips and strategies to grow your career. ♻️ If this changed how you think about PM tools, share it with other PMs.

Lots of folks ask, “Pelin, how does Zeplin use Zeplin?”. This is something I care deeply about, so I’ll tell you all about how we organize and document our projects. 🗃️ 𝗛𝗢𝗪 𝗪𝗘 𝗢𝗥𝗚𝗔𝗡𝗜𝗭𝗘 First up, for each new feature, we create a new project in Zeplin. I’ve seen lots of people use a single project like “Mobile app” and jam all the screens in there. That will get out of control pretty quickly. We use milestones as a way to divide up the features we work on. Depending on the feature, all of the milestones might get released to production (a great way to quickly gather feedback) or some of the milestones could be internal, for planning and QA purposes. But regardless, milestones are the way we split up larger features. So naturally, we use milestones to organize screens within our Zeplin projects, as sections. At the end of the day, here’s how we set things up: - Each project is a feature, an epic that a specific team is working on - Each section in the project aligns with a milestone, a sub-feature or a story We also use screen variants a LOT to help us have a clean dashboard. When someone’s looking at the project, they won’t see many states of the same screen, cluttering up the view. Things like empty states, error states are all rolled into one. 🏷️ 𝗛𝗢𝗪 𝗪𝗘 𝗡𝗔𝗠𝗘 𝗧𝗛𝗜𝗡𝗚𝗦 We also care a lot about naming our projects, sections and screens. Whatever you see as the section title should be very clear and to the point; often folks I see use really long names that no one can read quickly. This might be a habit you get from naming frames in design tools — but in Zeplin there are multiple levels of organization, so make it easy for people to glance and know what it’s about. Here’s an example: - Project: Approvals 2.0 - Section: Milestone 1 — Project Dashboard  - Screen: Request approval dialog   - Screen variants: Default, Loading, Error 🔀 𝗛𝗢𝗪 𝗪𝗘 𝗦𝗧𝗔𝗬 𝗔𝗟𝗜𝗚𝗡𝗘𝗗 We create a bot Slack channel for all of our projects, and invite people working on the project. That’s where we keep all the notifications for new screens, new screen versions and comments.  We also link each section to its Jira ticket, so with the Jira + Zeplin integration, it lets us see the status right inside Zeplin. ~~~ Whew, this was a lot. These habits help us stay aligned here at Zeplin, and I hope they’ll help you too!

If your project folder structure is a mess, your project is already in trouble. How do I know? Because I’ve seen it happen—over and over again. Whether you’re juggling retail TIs or a data center, disorganized files aren’t just inconvenient—they’re a liability. Outdated models, lost time, and costly mistakes are the direct result of an unorganized system. Here’s the folder structure I swear by: 📂 00 Project Management: Contracts, budgets, scopes of work. 📂 01 Incoming: Every doc you receive—dated subfolders keep it tidy. 📂 02 Outgoing: Sent docs for easy tracking. 📂 03 Meeting Minutes: Dated records of decisions and action items. 📂 04 Design: Models, cut sheets, calculators—everything design-related. 📂 05 Survey: Field notes and photos. 📂 06 CA (Construction Administration): Submittals, surveys, punch lists. 📂 07 Specifications: Relevant spec sections. This structure has saved me countless hours and headaches. Whether I’m leading the project or onboarding a new team member, this system ensures we’re all on the same page. No more missing files. No more excuses. Are you using a similar system for your projects? Or do you have any tips to make this even better? Let’s hear it in the comments! 👇

I cannot stress enough how critically important it is to take the time to build out systems that allow you to spend 0 time thinking about where your files are or how to access them. I have saved countless hours by taking more time upfront to set proper workflows and storage space for all my working and personal files. Some general principles to get you started: 1️⃣ Nothing is allowed to float - EVER. Don't let files float in your downloads folder or on your desktop. It will take you twice as long (if you are lucky) to find the file you need if things are allowed to float. Here is an example: Need to pull up a text editor to take notes during a meeting? The FIRST thing you are doing after that meeting is over is saving those notes (with a proper file name!) and storing it in the correct project location. Which brings me to point number 2: 2️⃣ Have a unique project location for every project. Projects of a similar type should all follow the same storage structure, but each project needs to have its own unique working space - no overlap. Example: Have two different projects for the same client? - each of those projects needs its own distinct working space to prevent misplacing items. 3️⃣ Have a specific system for each different file type you work with. Take and store meeting minutes the same way you do across all projects. Create, edit, and store deliverables the same way you do across all projects. Consistency is Key. 4️⃣ Last but not least - don't wait until the last minute to do these things - keep up with your notes and file saving as you work on these items. In the first example above where you pulled open a text editor to take meeting minutes - don't get in that situation in the first place. You should have your meeting minutes template opened and filled out with the meeting details already entered ahead of time. Work can be hard sometimes - no reason to make it harder on yourself - stay organized out there. Happy Sunday

Your team just spent 3 weeks studying how users navigate your checkout flow. Plot twist: Someone already did this study 6 months ago. 😅 Redundant research is a silent productivity killer. Here are 5 tips to avoid it.  🔁 Check existing data first Before jumping into a new study, ask around. Someone in your org might already have the answers you need. Go into support tickets, analytics data, sales call recordings and previous research studies. 📍Map research to product areas Building your checkout flow? Tag all studies that touched on payment. Creating an onboarding? Link every study about new users. At least keep a simple spreadsheet connecting features to research. Next time someone asks, you'll know exactly where to look. 🗓️ Do 'Research Retros' quarterly Get teams in a room. Share what everyone's been studying. Spot overlaps before they happen. Bonus: Great for cross-team learning! ⚡ Build a "Frequently Asked Research Questions" list What do stakeholders keep asking about? Where are the repetitive requests coming from? Update this living doc regularly. Share it before kick-off meetings. 🏮 MOST IMPORTANTLY, build a repository. The ultimate solution to prevent duplicate work. Store everything in one place. Make it searchable. Find insights in seconds. Get started with this definitive guide to building and maintaining a research repository here: https://bit.ly/3ExoGwR Also, here’s a repository tool that lets you do Google-like search for data snippets across projects.  https://bit.ly/4aWpqI7

🧵 Bioinformaticians: Drowning in multiple projects? Here's why context switching is killing your productivity—and how to fix it. 1/ Too many projects = too little progress. When your attention is scattered, your output drops. Context switching is the silent killer. 2/ Each project has its own biology: 🧬 Different TFs 🧪 Different cell lines ⚙️ Different pipelines Switching eats mental energy. 3/ Example: Jumping from CUT&RUN on H3K27me3 in mESCs to ChIP-seq on c-Myc in HeLa = full brain reboot. 4/ You spend time recalling: • QC parameters • Genome version • Where peaks are saved • Which scripts and tools you used 5/ And if the project isn't organized, you’ll waste even more time digging through old folders, scratch files, or rerunning commands. 6/ Solution 1: Ruthless prioritization Pick ONE project each day. Focus. Finish. Ship it. Half-done science doesn’t help anyone. Multitasking is a trap. 7/ Solution 2: Use consistent folder structures Example: project_name/ ├── raw_data/ ├── fastqc/ ├── trimmed/ ├── alignment/ ├── results/ ├── scripts/ 8/ Solution 3: Add a README to each project Include: • Data source • Goals • Key results • Analysis steps • TODOs This saves hours when switching context or collaborating. document as much as possible. it may seem to be a waste of time, but it saves you time long term 9/ Solution 4: Keep a running log Markdown or plain text. Example: ## 2025-04-10 - Trimmed reads with fastp - Aligned with bowtie2 (hg38) - Called peaks with macs2 10/ Key Takeaways: • Switching projects costs time and focus • Finish one before hopping to another • Structure + notes = less rework 11/ ✅ Action items: • Choose 1 project to focus on this week • Create folder structure & README • Start a daily or weekly log 12/ Deep work leads to deep insights. Prioritize. Organize. Write it down. Make future-you thank today-you. I hope you've found this post helpful. Follow me for more. Subscribe to my FREE newsletter https://lnkd.in/erw83Svn

Rule 2 – Document as You Build Documentation isn’t paperwork. It’s continuity. Most teams only start documenting when things break. By then, context is lost, people have changed, and governance turns into guesswork. What I mean by documentation here is living documentation — the kind that evolves with the project, not after it! 🗂 Governance → RACI tables, decision logs, change trackers, ⚙️ Process → one-page SOPs, workflow diagrams, approval flows, 💡 Knowledge → quick user guides, Confluence hubs, training videos, And yes — the tools matter: SharePoint, Jira, Confluence, ServiceNow… they don’t create structure, BUT they keep it alive when used with discipline! In the new CDR Consulting carrousel below, I shared how teams document in real time: • What to capture, • Which tools make it work, • And two real project examples where it saved time and trust 💬 What’s one documentation habit your team can’t live without?

Most ops teams are deep in documentation debt. It usually gets left till the end of a project. By then, everyone's exhausted from shipping the thing and feeling pressure to move on. Spending 5–10 hours writing docs at that point is often a non-starter. And so the can gets kicked down the road…and often disappears. This leaves another system that lives only in tribal memory. If the builder leaves (or simply forgets), you're stuck with something that's hard to debug and maintain and likely to get ripped out. The ideal is to document as you go, but realistically that doesn’t always happen. I hit this point last week: at the tail end of a multi-month project, excited to see everything finally coming together, and dreading the doc work. Here’s what helped: 📁 CREATE A CHATGPT PROJECT I slept on this feature for a long time, but it’s amazing. It solves the problem of persistent memory across separate chats and files. You can move all your fragmented chats into one project space and upload related files: - prompts - code - specs - data files of workflows (e.g., I got a JSON of my Zaps using Zapier's bulk export feature) Unfortunately this can’t work with everything (no easy way to get all your Marketo smart campaigns into ChatGPT) but do as best you can. ✍️ PROMPT CHATGPT TO WRITE YOUR FIRST DRAFT Example prompt: ---------- I'm now ready to document this project in Confluence. - I’ve attached an example of an existing documentation page, so you have a reference for how our documentation is typically structured.  - I also have uploaded all the files for this project:  – x – y – z - The goal: a clear high-level overview of how the project works, without getting lost in minute detail. - It should be understandable to any competent ops or systems person. ---------- You can then give feedback and iterate until you’re 90% of the way there. It can even do simple data flow diagrams although it still tends to choke if there’s high complexity. 🕵️♂️ QA THE DRAFT Before you use it, get the LLM to perform a first pass of QA on its own work and weed out errors or hallucinations: Example prompt: ---------- Please now put on your critical fact checker persona. Review the documentation with an eye to root out any potential hallucination or inaccuracy. Maximize clarity for someone new to the project while preserving technical detail. ---------- You still need to review and put the finishing touches on, and for larger projects you may want to break it out stage by stage. But this got my own doc effort down to under 30 minutes end-to-end.