Over ten thousandskills, one graph.
ABRAM keeps a living record of what every person in your crew ecosystem can do. Over 10,000 skills are tracked today, and ABRAM adds more each time a production brings work the graph has not seen before.
How ABRAM thinks
Competency isearned, not typed.
Nobody grades themselves into a higher tier. ABRAM reads finished deliverables, the hours logged against them, and the wrap report filed when the project closes, then writes what that work proves back to the person who did it.
Finished deliverables
A deliverable that reaches its final state names the person who took it there and the craft the work required. ABRAM records both.
Hours against the task
Approved timecards say how long the real work took. ABRAM compares that against what the job was scoped at and carries the difference into the graph.
The wrap report
When a project closes, ABRAM writes up how the production went and who carried which parts of it. That report is the last piece of evidence a project contributes.
Every open role,answered at once.
Open a project with its roles laid out and nobody in them yet. Ask ABRAM to match, and it reads the graph for every role on the list at the same time, names who fits each one, scores them against the skills that role asks for, and says whether they are free for the dates.
Crew and rosters
Every projectleaves evidence.
ABRAM sends a weekly read on what the workspace learned: who finished what, which skills gained evidence, and where the crew is thinner than the schedule ahead needs.
The production brain
The graph iswhy matching works.
Crew suggestions, draft call sheets, and estimated hours all read from the same graph. Because the graph grows with every finished project, the drafts ABRAM hands you next month are argued from a longer record than the ones today.
The record belongs to your workspace. ABRAM never pools it with another studio’s, and every crew member can see and correct their own profile.
Questions aboutthe graph.
Start the graph on your next job.
ABRAM begins recording competency from the first deliverable your team finishes.
ABRAM Skill Graph: Crew Skills Tracking and Competency for Creative Production
ABRAM maintains a living skill graph across the crew ecosystem, tracking over 10,000 skills spanning camera, lighting, grip, sound, art department, post production, design, and production management. Competency is derived from completed work rather than self-reported profiles: finished deliverables, approved timecards, and end-of-project wrap reports each write evidence back to the person who did the work.
[ABRAM Skill Graph] [tracks] [Over 10,000 Crew Skills]
[Competency] [isEarnedFrom] [Finished Deliverables, Logged Hours, Wrap Reports]
[Skill Graph] [powers] [Crew Matching and Draft Call Sheets]
[Skill Graph Data] [isScopedTo] [The Customer Workspace]
How ABRAM Ranks Crew for a Booking
When a role is staffed, ABRAM scores the available crew pool against the skills that specific role requires. Changing the role changes the ranking, because the ranking is computed from the role’s skill requirements rather than from a fixed seniority list. Where nobody holds the exact role, ABRAM surfaces adjacent skill sets from the graph.
Data Ownership
The skill graph built from a workspace’s projects is scoped to that organization. ABRAM does not pool competency data across customers and does not sell it. Crew members can view and correct their own profile.