Hi Matt,
Thanks for the detailed feedback! We love getting rich descriptions of how users use, or would like to use, InqScribe.

It would be helpful to unpack a few of these requests. (Ultimately it might help to break some of these into separate features, but for now discussing whole-cloth is fine). If it's easier to discuss this via emails, feel free to contact us at support@inqscribe.com.

a) employed speech recognition to match words to timecode after transcription.

How exactly would you like to see this work? I'm not clear exactly on what is getting matched to what, and the logic behind the matchings.

b) allowed editing of the timecode stamped words into new scripts
c) allowed playing such scripts from the original source material (assembly edit)

How exactly would you envision this editing happening? I'm assuming the gist here is that you have a parent transcript and related child transcripts, and the child retains the link to the source. But it would help to know what sort of workflow you'd envision for generating the child transcripts, and what sort of relationship it needs to maintain to the parent.

d) provided export of assembly edit to editing software for finessing

Which editing software? Is their a particular industry format you'd like to see?

e) highlighted text that'd been used in a script so that after editing one could see what's been used and not used.

I'm assuming this relates to the parent/child transcript point above, correct? You'd want to easily see what parts of the parent transcripts are being used in related child transcripts?

Forgive my ignorance of the assembly editing process, but any details you can provide would be helpful. Indeed, this does sound like a tall task, but it's always helpful to a get deep understandings of our users' needs and workflows.