Content Idea Bank and Shoot Schedule for Creators

Content Idea Bank and Shoot Schedule is an offline app (one HTML file in a zip) for a creator who films their own content. You write every idea down the moment it arrives, group ideas into series and move them along from Spark to Posted. When you decide to film, you plan a shoot day: the date, the place, the gear and a shot list linked to your ideas. You print the shot list, tick shots off on the day, and see how many are left.

The problem it removes: Ideas are lost in voice notes and screenshots, the same idea is written three times, and a shoot day ends with missing shots because nobody wrote them down in order. This app keeps one bank of ideas, tells you which to do next, and turns a shoot day into a checked list.

What is inside:

• Idea bank with series, stage, format, effort and how excited you are, with a pick-next score
• Idea board from Spark to Posted
• Shoot calendar with date, time, place, crew and gear
• Shot list per shoot, linked to ideas, with a tick for each shot
• Overview of the next shoots, the ideas ready to shoot and quick wins
• Printable shot list and idea brief
• Example data you can load in one click, a Start here guide and an Honest limits panel
• JSON backup and restore, CSV export, and CSV import with a check of every row before anything is added

Who it is for: creators, video makers, photographers and social media managers who film their own content and want ideas and shoot days in one place.

What it is NOT: It does not hold any ready-made ideas, scripts or trends: the bank starts with your own ideas. It does not edit video, store pictures or videos, or connect to any platform. Permission to film at a place is something you check yourself. It does not send reminders by itself. It is not legal, tax or accounting advice, it is not connected to any government system, bank or messaging service, and it does not file or send anything by itself. UAE e-invoicing is not part of it.

Your data stays on this device in your browser. Back it up with Export; clearing browser data loses it otherwise.

Verified by us: scripted tests in Chromium (165 checks through the real screens: adding, editing and deleting records in every table, required-field messages, backup then clear then restore, CSV export then import, keyboard order, print layouts rendered to PDF, no horizontal scrolling at 375 and 1280 pixels, no network requests) and an independent recalculation by a separately written Python evaluator of 850 calculated values (25 randomised rows plus the example data) with 0 mismatches. Safari engine (WebKit): smoke test passed; Firefox: could not be launched. Not tested: Firefox beyond what is stated here, and no real printer was used (print layouts were checked as PDF).