How to Document a DIY Building Project: Photos, Plans, and Submission Tips

Every finished build starts as a pile of lumber and a stack of questions, and the only way another builder learns from your work is to record the answers along the way. Project documentation turns a one-off weekend build into a repeatable reference for you, your future self, and anyone who sees the finished piece. Whether the record lives in a paper notebook or a cloud folder, the rules are the same: date everything, photograph every stage, and write down the numbers before they are forgotten. The habit costs a few minutes per session and pays back every time a dimension, a joint, or a finish schedule needs to be recalled.

Why Project Documentation Matters

A build log does three jobs at once. It forces you to think through each step before cutting, it preserves decisions you will otherwise forget, and it gives other builders something concrete to learn from. Workshops and maker spaces run on shared knowledge, and a documented project is the difference between a photo of a table and a lesson in making one.

What a Good Build Log Contains

• A dated entry for each working session
• Final dimensions and the cut list
• Material choices and where each piece came from
• Joint and fastener details
• Finish products, coats, and drying times
• Problems hit and how they were solved

How Documentation Improves Your Own Work

Reviewing an old build log before starting a similar project exposes the mistakes worth avoiding. The notes also feed accurate time estimates: after two or three documented builds, you can predict how long a dado, a glue-up, or a finish schedule really takes instead of guessing. The log doubles as a shopping list for the next project, because the material quantities are already written down.

When to Write

1. Before the first cut, note the plan and the intended dimensions
2. After each working session, add photos and a short entry
3. At the first problem, describe the symptom and the attempted fix
4. At completion, record the total time, cost, and lessons learned

Four entries per project are enough to reconstruct the whole build later. The notes do not need to be polished; they need to be dated and specific.

Capturing the Build: Photography and Video

Photos are the backbone of project documentation because they capture geometry that words struggle to describe. Shoot at every stage: raw stock, layout lines, each joint as it closes, the glue-up under clamps, and the finished piece from several angles. A photo taken before the clamps come off is worth more than a dozen taken after.

Digital tools have made sharing these records easier. Cloud-based project files and the document viewer improvements found in construction software mean a plan sheet or photo set can be reviewed on any device, which matters when the build moves between workshop and job site.

Shooting Progress Photos That Teach

Keep the camera square to the work and use natural light. A shot that shows the joint, the tool, and the reference marks in one frame teaches more than a close-up of a finished surface. Shoot each step twice: one overview of the whole assembly and one detail of the critical joint.

Camera Angles and Lighting

Overhead light flattens texture, so angle a lamp from the side to reveal grain and gaps. Set the camera to manual focus and tap the screen on the joint you care about, then lock exposure so the color of the wood stays consistent across the series.

Video Walkthroughs and Digital Organization

A two-minute video per session captures motion that photos cannot: how the saw feeds, how the clamps go on, how the drawer slides seat. A time-lapse of the whole build, shot from one corner on a phone tripod, compresses a weekend into a minute and makes a strong cover image for a submission.

Store clips and photos in a folder named by project and date, and keep a naming scheme so files sort themselves. Back up the folder to a second drive or cloud service at the end of each week, because a lost phone erases a season of work in one drop.

Writing Plans, Cut Lists, and Material Notes

The written record is where accuracy lives. Record the cut list in final dimensions, note blade kerf, and list every fastener and finish product by name. An index at the top of the log makes the file useful a year later, when the details have faded.

Recording Dimensions and Cut Lists

Write dimensions on the parts themselves with a pencil as they come off the saw, then transfer them to the log at the end of the session. Number each part in the log the same way it is numbered on the shop floor so the two records stay in sync. Add the supplier and price for unusual materials, since prices change and the note saves a phone call next time.

Record nominal and actual dimensions separately. A 2×4 measures 1.5 by 3.5 inches, and a 1×6 measures 3/4 by 5.5 inches, so a cut list written from nominal sizes produces parts that do not fit. Note the saw’s kerf once at the top of the page and subtract it from every interior cut.

Mistakes belong in the log too. A line that says the first drawer face was cut 1/4 inch too wide, and that the fix was to rip it down and re-clamp, teaches more than ten pages of clean success. Future readers include you, and your memory of the failure will fade long before the note does.

Choosing File Formats That Last

Plain formats outlive proprietary ones. A cut list saved as a PDF this year still opens in ten years, and a build log in Markdown converts to a website or a forum post without reformatting.

Preparing a Submission That Gets Published

When a project goes to a community gallery or a builder’s site, the submission stands or falls on how much work the editor has to do. Complete forms, real dimensions, and captioned photos get published; blurry one-liners get skipped.

Checklist Before You Submit

• Confirm the project name and the main material
• Include at least one finished shot and two build shots
• Add a short build time and cost figure
• List the tools used
• Attach the cut list or a link to it
• Proofread the description for typos

Common Submission Mistakes

1. Submitting only finished photos with no build process
2. Leaving dimensions out of the description
3. Using watermarks that obscure the work
4. Forgetting to name the finish products used
5. Ignoring the platform’s file size and format rules

Editors work through many submissions in a sitting, so a complete package moves to the front of the line. Respond to follow-up questions quickly, and treat requested changes as part of the process rather than a rejection.

Write captions that answer three questions: what the viewer is looking at, what tool or technique made it, and what would change next time. Leave personal details out of public submissions, and check the platform’s terms for how photos may be reused.

Building a Personal Project Archive

A single submission is the start, not the goal. Builders who document every project end up with a personal archive that is a portfolio, a reference library, and a record of improvement all at once.

Organizing Past Projects for Reference

Keep one folder per project with the photos, the log, and the cut list together. Add a one-line summary at the top of each folder: what the piece was, what it taught you, and what you would change. Name folders by project and year, for example end-table-2026, so the archive sorts itself.

Sharing Beyond a Single Submission

The same documentation feeds forum threads, workshop classes, and side-by-side comparisons of techniques. Each project you publish makes the next builder’s learning curve shorter, and the habit compounds across the community of people who build things by hand. Start small: one project, one folder, one honest entry about what went wrong and what you would do differently.