Build Board: One-Tap ForScore Setlist Export

Every musician pulls their own part, in order, as one file. You do nothing. You 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. This 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 and their charts, ready to open straight into forScore. A single self-contained forScore file with every chart already embedded, so nothing has to be pre-loaded into anyone's library Musicians export it themselves from the Gig Sheet or Performance Mode, so the bandleader is out of the loop entirely One chart per song, picked automatically where it is obvious and chosen by the musician where it is not, so nobody receives parts they do not read Charts assigned to no role count as available to every musician, so your lead sheets and scores reach the whole band without being assigned role by role Songs where a musician has nothing at all become a visible placeholder, so the set order never silently breaks Delivery by download link rather than email attachment, so big sets do not bounce A size guard that refuses clearly and names the charts causing it, rather than producing a broken file What you walk away with. 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. Check this before you back it Every musician who needs to open the file must be on forScore 14.3 or later. This is a hard requirement, not a preference, and it is the single most important thing to confirm with your band before contributing. There 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. Why this is not already built It 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. The three hard calls, and why they went the way they did Every decision in this spec was published with its reasoning, including the ones we expected some people to disagree with. The spec locked on 11 September 2026 and is final. It locked two days later than planned, because a backer read it properly, found a real gap, and the design was rewritten around what he found. Songs where each player reads a different part. The export works it out song by song rather than asking you to choose a role up front. Your candidate charts for a song are everything assigned to a role you are booked for, plus everything assigned to no role, because an unassigned lead sheet or score is in practice available to everyone. One candidate and you simply get it, with no prompt. Several and you pick, and the first time you resolve a given combination you can apply that same choice to the rest of the set. None at all and you get a visible placeholder, so the set order survives and you can see the gap. This replaced an earlier design where the musician picked one role up front, after a backer pointed out it would skip every chart not assigned to a specific role. Setlists too big to fit. 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. Who gets the file. 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. What is deliberately out of scope Named 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. The full Statement of Work is published in the open, 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.