Write and revise
The screenplay is developed and locked in the same place production planning happens, so nothing drifts out of date.
Wajang connects the screenplay to everything a production does with it afterwards: scheduling, budgeting, locations, documents, cast and crew, right through to delivery. The script stays the source of truth instead of a PDF nobody checks again after week one.
Wajang is a working platform for screenwriting and physical production together. You write and revise the screenplay, break scenes into cast and requirements, schedule shoot days, track budgets and costs, manage locations and risk, distribute and sign documents, and review cuts. All of it is built around the same script and scene data, so it isn't a set of separate tools a production has to keep in step by hand.
The screenplay is developed and locked in the same place production planning happens, so nothing drifts out of date.
Scenes become the breakdown, the stripboard and the call sheets, not a retyped copy of them in another tool.
Budget, documents, cast, crew and locations stay connected to the scenes they belong to, right through to delivery.
Wajang is built for productions where one or two people, a producer, a production manager, sometimes the writer-director themselves, end up responsible for keeping the script, schedule, budget and paperwork in step without a large studio production office behind them. It's used across development, scheduling, physical production and delivery, by producers, 1st ADs, department heads, and the cast and crew they bring on, each with access scoped to what their role actually needs to see.
Screenwriting software writes screenplays. Production-management software plans shoots. Almost nothing treats the script itself as the source the rest of the production should be built from. So scenes get retyped into a breakdown spreadsheet, the spreadsheet becomes a stripboard in a different tool again, and by the time a call sheet goes out, three separate documents are all quietly out of step with the actual script. Wajang exists to close that gap. The screenplay stays a first-class part of the production record, not something exported once and left to drift.

A scene in the script is the same scene on the stripboard, the call sheet and the breakdown, not a copy of it that can fall out of sync.
When the script changes, Wajang compares it against what the production already has and asks a person to resolve what's changed, rather than overwriting anything automatically.
Characters in the script can become cast records without duplicating contact, contract or availability details already entered.
Moving a scene or locking a new revision shows what it affects, cast, locations, call sheets, before it's applied, not after.
Kanban boards and spreadsheets can track tasks for any kind of work, but they don't know what a scene, a call sheet, a stripboard or a cast release actually is. That's why productions end up bending generic tools around film-specific processes, or running several specialist tools that don't talk to each other. Wajang is built the other way round. The record types are scenes, shoot days, cast, crew, locations, budgets and documents, and the workflows, script revision, call sheet distribution, document signing, cost tracking, are the real ones a production runs, with role-aware access built in from the start rather than bolted on later.
Wajang is made by people who work on productions themselves: filmmakers, editors and directors based in the UK, building the tool they wished existed on their own shoots. That background shapes the product directly. Features exist because a real production needed them, not because a roadmap said so, and the platform gets judged the same way a piece of kit on set would be, does it hold up under a real shoot day, or not. It also means being straightforward about scope. What's built is documented honestly, including what it doesn't yet do, rather than oversold.
Where Wajang uses AI, reading an equipment schedule from a photograph, drafting a call sheet from the current schedule, flagging a budget or scheduling risk, it produces a suggestion or a draft for a person to review, not a change it makes on its own. The production adviser is a good example: focused, separately scoped checks with a deterministic readiness score behind them, built to surface risk and answer questions, but explicitly unable to silently change a script, a schedule, a budget, a call sheet or an approval. Every AI-assisted result stays reviewable, reversible and attributed to the person who confirmed it.
A draft, a match, a flagged risk. It's never applied automatically.
Confirms, edits or dismisses it before anything changes on the production record.
What changed and who approved it stays in the audit trail, not just what the AI suggested.
Being a small, independent team means enquiries go to people who actually work on the product, not a support queue. Whether it's a question before signing up, feedback on a feature, an education or partnership enquiry, or a privacy request, the contact page routes it appropriately, with topic-specific prompts so you don't have to guess what detail is useful to include.
Create an account or contact Wajang to discuss company and education use.