Last lesson. Your garden is drawn, planted, and audited, and it exists in exactly one place: this browser, on this device. That is a deliberate design choice and it means you could start planning without signing up for anything, but it is worth understanding properly, because clearing your browser data would take the lot. So this lesson covers three things. Editing without redrawing, which is the set of habits that make revising a plan quick rather than tedious. Where the work actually lives and what your options are for keeping it safe: automatic local saving, an optional EdQuest account that syncs across devices, and JSON files you can export and archive yourself. And getting the plan out: a scaled printable page with a plant inventory, and a read-only link you can send to somebody who does not have an account.

Three objectives. First, you will be able to revise a plan without redrawing it: select single objects or a marquee of them, drag vertex handles, nudge with the arrow keys, restack overlapping regions, use the right-click menu, and undo anything with the standard shortcut. Second, you will be able to say where your gardens live and choose how to keep them: automatic saving into this browser, an optional EdQuest account that syncs across devices and keeps a server backup, or an exported JSON file you archive yourself. Third, you will be able to get the plan out of the screen: a scaled printable page with a legend and a per-plant inventory you can take to the nursery, and a read-only share link that anybody can open without an account and that you can revoke later.

Five habits that make revision quick. First, select properly: the select tool picks one object, dragging on empty canvas marquees a group, and holding Alt while clicking cycles down through a stack when shapes overlap. Second, drag handles rather than redrawing: every vertex of a region has one, and the arrow keys nudge a whole selection with Shift for a larger step. Third, use the right-click menu, which carries delete, duplicate, and the merge and subtract operations from Lesson two. Fourth, manage the stack: control or command with the bracket keys brings a region forward or sends it back, and adding shift takes it all the way to the front or the back. Fifth, undo freely. Control or command with Z steps back and adding shift steps forward again, so experimenting costs you nothing.

Where does a garden actually live? By default, in this browser, saved automatically as you work. That is why you could start planning within seconds of arriving without an account, and it is genuinely the right default. It also means clearing your browsing data, or switching to a different device, would leave the plan behind. You have three ways to deal with that and they are not exclusive. Sign in with an EdQuest account and your gardens sync across devices with a server backup, and anything you made before signing in uploads automatically rather than being lost. Export a JSON file for anything you want archived independently, which you can import back into any browser later. Or accept the default and simply know the limitation. What is worth avoiding is assuming a cloud backup that you never actually turned on.

The printed plan deserves a slide of its own because it is the thing that actually goes outside with you. It is a scaled, to-page drawing of the garden with a legend, and alongside it a per-plant inventory table listing every species and how many of each. You can print the map and the table together, or just the table on its own, which turns it into a tick-box shopping list to take to the nursery. That is the point where a plan stops being a screen and starts being a thing you use with muddy hands, and it is worth generating even for a garden you consider unfinished. A printed plan with three question marks on it is more use in a garden centre than a perfect plan on a laptop at home.

Four last traps. People plan a whole season in one browser and lose it to a cleared cache: sign in, or export a file, or at minimum know that you have not. People redraw a bed to move one corner: drag the handle. People send a screenshot of the plan when they want someone else to look at it, which cannot be zoomed or read properly: mint a read-only share link instead, which opens live for anyone with no account and can be revoked whenever you like. And people receive a shared garden, start editing it, and discover it is read-only: use make a copy, which gives you your own editable version without touching the original that was shared with you.

Three things from this lesson, and then three for the course. From this lesson: revise rather than redraw, because handles, nudging, restacking, and undo between them mean almost nothing needs to be made twice. Decide where your work lives before you need to know, because the default is local and that is fine only if it is a choice. And get the plan out of the screen, onto paper for the nursery or into a share link for whoever is helping you. For the course: set the site first, because everything inherits it. Learn the one drawing gesture, because everything reuses it. And read the light before you commit, because that is the part a plan on paper could never do for you.

Five places to go next. The in-app tutorial is the fastest reference: press the question mark key in the editor any time and it opens beside the canvas while the app stays usable, with a keyboard shortcut sheet behind it. The GardenCAD project documentation covers the data model and the solar model in detail, including how shadows are projected and how sun hours are integrated. For the horticulture rather than the software, your regional extension service or equivalent publishes planting calendars and frost dates that will be more specific than any general catalogue. A seed supplier catalogue is worth reading for spacing and days to maturity for the varieties you actually buy, since those differ from generic entries. And the EdQuest class catalogue has the other courses in this series.

That is the course. You have set a real site with a real orientation, drawn beds and structures, traced an existing garden to true scale, chosen species and queued what you meant to grow, filled the beds by hand and automatically, audited the light across a season, and got the result onto paper and into a shareable link. Every tool in the editor has now turned up in the situation it was built for. Do one thing before you close this: open your own plot, set north, and draw one bed. Ten minutes of a real garden will teach you more than rewatching any of these lessons, and the plan is going to be wrong the first time regardless, which is exactly why it is worth having somewhere you can change it for free.