{"product_id":"build-board-forscore-combined-export","title":"Build Board: One-Tap ForScore Setlist Export","description":"\u003cp\u003e\u003cstrong\u003eNOT READY TO PUBLISH.\u003c\/strong\u003e Outstanding: confirm the build cost with the Phase 0 spike, set the launch date (which drives the spec-lock and close dates), publish theme \"Build Board - SOW page template (draft)\", and switch this product from Draft to Unlisted.\u003c\/p\u003e\n\n\u003cp\u003eEvery musician pulls their own part, in order, as one file. You do nothing.\u003c\/p\u003e\n\n\u003cp\u003eYou already build the set in Back On Stage. Every chart is there, assigned to the right role. Then somebody needs it on an iPad and the organisation stops: charts download one at a time, then import one at a time. For a twenty-song set with a horn section on different parts, that is not a two-minute job. It is the job that ends up happening at 11pm the night before, or in the car park before load-in.\u003c\/p\u003e\n\n\u003cp\u003eThis build closes that gap, and it does it without putting the bandleader in the middle. Each musician opens the gig on their own side of Back On Stage and exports their own book: one self-contained file carrying the set order \u003cem\u003eand\u003c\/em\u003e their charts, ready to open straight into forScore.\u003c\/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eA single self-contained forScore file with every chart already embedded, so nothing has to be pre-loaded into anyone's library\u003c\/li\u003e\n\u003cli\u003eMusicians export it themselves from the Gig Sheet or Performance Mode, so the bandleader is out of the loop entirely\u003c\/li\u003e\n\u003cli\u003eOne role at a time, chosen by the musician, so nobody receives parts they do not read\u003c\/li\u003e\n\u003cli\u003eSongs with no chart for that role become a visible placeholder, so the set order never silently breaks\u003c\/li\u003e\n\u003cli\u003eDelivery by download link rather than email attachment, so big sets do not bounce\u003c\/li\u003e\n\u003cli\u003eA size guard that refuses clearly and names the charts causing it, rather than producing a broken file\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003cp\u003e\u003cstrong\u003eWhat you walk away with.\u003c\/strong\u003e You build the set once in Back On Stage, and then you are finished. Every musician pulls their own book when they want it, with their own parts, in the right order, without asking you for anything. A sub added the day before the gig gets theirs the moment they are booked.\u003c\/p\u003e\n\n\u003ch3\u003eCheck this before you back it\u003c\/h3\u003e\n\n\u003cp\u003e\u003cstrong\u003eEvery musician who needs to open the file must be on forScore 14.3 or later.\u003c\/strong\u003e This is a hard requirement, not a preference, and it is the single most important thing to confirm with your band before contributing.\u003c\/p\u003e\n\n\u003cp\u003eThere is no fallback in this build. A lighter setlist-only version that would work on older forScore releases was considered and deliberately left out, because keeping the scope tight is what makes a build like this fundable at all. So if your players are on anything earlier than 14.3, this feature will not do anything for them. We would far rather you found that out now than after you paid.\u003c\/p\u003e\n\n\u003ch3\u003eWhy this is not already built\u003c\/h3\u003e\n\n\u003cp\u003eIt is not on the roadmap, and it is not on any list. Several bands have raised this same friction independently, which is what got it scoped in the first place, but it has never been enough people to outrank what the whole customer base needs next. That is precisely the gap the Build Board exists to close: a smaller group with a specific, real problem moving their thing up the list without waiting for it to become everyone's problem.\u003c\/p\u003e\n\n\u003ch3\u003eThe three hard calls, and why they went the way they did\u003c\/h3\u003e\n\n\u003cp\u003eEvery decision in this spec is published with its reasoning, including the ones we expect some people to disagree with. \u003cstrong\u003eYou have 14 days to argue with any of them before the spec locks.\u003c\/strong\u003e\u003c\/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eSongs where each player reads a different part.\u003c\/strong\u003e The musician picks which role they are exporting, and only that role's charts go in. We rejected routing parts automatically, because that quietly guesses on someone's behalf and gets it wrong for anyone doubling. We also rejected sending everyone every part, because that just recreates the pile of irrelevant PDFs this feature exists to eliminate.\u003c\/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eSetlists too big to fit.\u003c\/strong\u003e The export refuses and names the specific charts that pushed it over, then points you at the ZIP download that already exists so you can import manually. We rejected quietly compressing charts to make them fit, because nobody should discover mid-performance that their chart has been altered. We also rejected splitting across several files, because that defeats the single-tap point of the whole thing.\u003c\/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eWho gets the file.\u003c\/strong\u003e The musician, self-serve, from the Gig Sheet or the Performance Mode setlist screen. Not the bandleader generating and distributing. This is the decision that makes the feature actually save time rather than move the work around.\u003c\/p\u003e\n\n\u003ch3\u003eWhat is deliberately out of scope\u003c\/h3\u003e\n\n\u003cp\u003eNamed plainly so nobody backs this expecting something it will not do: no setlist-only mode for older forScore versions, no exporting several roles at once or a combined all-parts file, no automatic compression to squeeze under the size limit, no syncing annotations back into Back On Stage, no versions or forScore metadata round-tripping, no bookmarks, no two-way sync or reading anything back out of forScore, and no attempt to generate forScore's own proprietary export bundles. Those are separate builds and separate campaigns.\u003c\/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eThe full Statement of Work is published in the open\u003c\/strong\u003e, including the technical risks, the file-size numbers, the edge cases the dev team has to handle, and the reasoning behind every decision above. Read it before you back it.\u003c\/p\u003e","brand":"Back On Stage","offers":[{"title":"$100 Backer","offer_id":49121596375194,"sku":null,"price":100.0,"currency_code":"CAD","in_stock":true},{"title":"$250 Backer","offer_id":49121596440730,"sku":null,"price":250.0,"currency_code":"CAD","in_stock":true},{"title":"$500 Supporting Backer","offer_id":49121596473498,"sku":null,"price":500.0,"currency_code":"CAD","in_stock":true},{"title":"$1,000 Founding Backer","offer_id":49121596506266,"sku":null,"price":1000.0,"currency_code":"CAD","in_stock":true},{"title":"$1,500 Founding Backer","offer_id":49121596539034,"sku":null,"price":1500.0,"currency_code":"CAD","in_stock":true},{"title":"$2,500 Founding Backer","offer_id":49121596571802,"sku":null,"price":2500.0,"currency_code":"CAD","in_stock":true}],"url":"https:\/\/backonstageapp.com\/products\/build-board-forscore-combined-export","provider":"Back On Stage","version":"1.0","type":"link"}