Section 0.1: Glossary and acronym reference

The terms you will meet across ABRAM and this documentation, grouped by area.

1. ABRAM and AI

• ABRAM: The assistant built into ABRAM. It answers questions about your work, makes documents, tables, charts and reports, and does work for you, with bigger changes waiting for your approval. See Section 0.3.
• Action Plan: The list of changes ABRAM lays out before a bigger job. Nothing happens until you click Approve.
• Artifact: A document, table, chart or report ABRAM makes in chat. It opens beside the chat, keeps its versions, and downloads or saves to a project.
• ABRAM Memory: What ABRAM remembers about you, managed in Settings > AI > Memory.
• Documents & brain: Your organization's shared files and the knowledge ABRAM keeps from them, in two views, Documents and Organization brain. Owners and admins find it under Organization.
• AI usage: What AI features draw on. Every plan includes some, and how much a request takes depends on how much work it does.
• Extra usage: AI usage past what a paid plan includes, billed monthly up to a spend limit an owner or admin sets.

2. People and access

• Person: Anyone ABRAM knows about, inside or outside your organization. The same person record is used for crew, team and contacts.
• Owner / Admin / Member / Guest: The four organization roles. Owners own billing and everything else; admins manage settings and members; members get the permissions switched on for them; guests are read-only and see only what they are added to. See Section 1.4.
• Access level: What someone can do on one project: Can manage, Can edit or Crew view. Separate from their organization role.
• Outside crew: People from outside your organization on a production. They take no seat, and the number per production depends on your plan.
• Crew roster: The freelancers and companies you work with from outside your organization, in Team management > Crew roster. Your organization's own members are listed under Organization. See Section 4.1.
• Open slot: A role on a project with nobody in it yet.
• Drafted: Someone added to a project who has not been sent an invitation. Nobody is contacted until you click Send invites.
• Seat: A paid place in your organization for one member.

3. Projects and production

• Project number: The number ABRAM gives each project. Click it in the project header to copy it.
• Work package: A phase of a project, such as Pre-production or Delivery, holding its own dates, budget and work. There are 12 types.
• Milestone: A checkpoint with a target date, and optionally a share of the payment.
• Deliverable: A piece of finished work you hand over. It moves through Not started, In progress, In review, Approved and Completed.
• Version: One submission of a deliverable, as an uploaded video (Pro and above), a PDF or DOCX file, or a link such as a Vimeo link.
• ABRAM Vision: Checks every uploaded video for picture and sound, tracks coverage against the plan and makes analyzed footage searchable. See Section 6.10.
• Assets: Where a project keeps its documents, pictures and video, in folders, with versions and share links. See Section 6.9.
• Review link: A link that opens a cut in the browser with no account. It can carry a passphrase and an expiry. See Section 6.6.
• Signed approval: A client types their full name to approve a version. ABRAM records who signed and a fingerprint of the exact file.
• Work order: A call: when and where, who is on it, and what gear goes.
• Shoot day: One day of production, with its own call sheet. Listed in Production > Shoot days.
• Call sheet: The document for a shoot day with call times, locations, schedule, safety and department notes, sent to everyone working that day.
• Stripboard: Scenes laid out as colour-coded strips so you can order the shooting schedule.
• Breakdown: The list of scenes and the Elements in them (cast, props, locations and so on), built by hand or with Import script.
• Day out of days (DOOD): Which days each cast or crew member works across the whole shoot.
• Run of show: A rundown of a live show or event, timed to the second, which you run live and send to screens, share links and a live data feed.
• Hard out: The time a show day must be off air. The run of show counts back from it and shows how far over or under the day will land.
• Triage: The queue of projects with no owner and project requests nobody has handled yet. Studio and above.
• Intake form: A form clients fill in to send you a project request. Studio and above.
• Calls: Call transcripts pasted or uploaded to a project under Client > Calls. ABRAM reads them into a summary, decisions, action items and scope changes. Studio and above.
• Import: Bringing projects in from a CSV file, or from Jira, Asana or Monday.
• Wrap report: Plan against actual for a project, opened from the project's menu. Before the project wraps it shows running totals. See Section 3.9.

4. Schedule, hours and gear

• Check-in: Tapping Check in on your phone when you arrive on a shoot day or work order, and Wrap when you leave. The hours come from the clock.
• Time card: Your week of hours on the phone, logged by day and task and submitted for approval.
• Hours record: The team's logged hours, a tab in Team management.
• Utilization: How much of a person's or a resource's available time is booked.
• Time off: Days someone is away. Time off reduces their available hours and never counts as work.
• Needed vs Booked: On a project's Resources > Equipment, gear the project needs sits at the top under Needed, and booked gear sits under the work order that dates it.
• Pack list: The gear list for one work order. Tick each item Packed on the way out and Returned on the way back.
• Transit buffer: Days added around a gear booking for shipping or prep, set in Settings > Workspace > General. Studio and above.

5. Dashboards

• Delivery and Money cards: The two charts on the dashboard that show a figure over time, each with a breakdown underneath. Delivery follows scope, started and done work. Money follows budget, invoiced and paid.
• Delivery forecast: The projection on the Delivery card, at the pace of the last 28 days.
• Client health: A 0 to 100 score for a client, averaged from its projects' health scores.

6. Money and plans

• Plans: Free, Pro, Studio and SMB / Enterprise. Pro and Studio are priced per seat with no seat minimum. See Section 5.3.
• Studio trial: 7 days of Studio for a new team, with AI included and no card.
• Quote: A priced proposal for a client, which can be accepted and signed in the client portal and converted to an invoice.
• Purchase order (PO): A payment the payer authorizes up front with a hold on their card. The hold lasts 7 days.
• Processing Fee: The fee on payments through ABRAM, tiered by plan and charged only above each plan's monthly allowance.
• Budget version: A saved copy of a project budget. One version is the primary.
• Cost / Client price: The two ways to read a budget: what it costs you, and what you charge.
• ROM estimate: A rough order of magnitude budget, set in project settings before the detailed budget exists.
• Client portal: The page where a client follows a project, reviews work and signs off. Pro and above.

7. Sign-in and technical terms

• SSO (single sign-on): Signing in with your company's identity provider. SMB / Enterprise.
• SAML and OIDC: The standards identity providers use for single sign-on.
• SCIM (directory sync): Keeps your ABRAM members in step with your company directory. SMB / Enterprise.
• Stripe Connect: The payout account a payee connects in Settings > Billing > Payouts to receive payments.