The basics What is Plint and what can it do? This is Plint Plint Core is a full-featured and highly configurable system for cloud-based media localization. Powerful tools for workflow orchestration let you define and assign all the steps needed to complete a project. But Plint also provides built-in tools to actually do the work, from normal file uploads to online editing or automated tasks.  Put another way, it makes work ... work.  For project managers it is a powerful tool for creating and maintaining workflows, and keeping tabs on project progress.  For freelancers, Plint is an easy-to-use portal for accepting, discussing and completing jobs. From a client perspective, Plint provides a bird’s eye view of project progress as well as easy access to deliverables. Plint revolves around: People Projects Jobs Files Managing projects efficiently Creating and maintaining workflows often takes time and resources that could be spent on delivering quality work. For recurring assignments, Plint uses highly configurable templates to generate interconnected workflows based on project data. Suitable resources – in-house or external – are automatically selected based on customisable criteria. Automatic notifications and built-in logic makes sure that jobs are done in the right order, but no time is wasted between them. Changes in mid-project can quickly be incorporated and all the necessary jobs automatically added for an additional language or episode. At the same time, details on job level can always be adjusted at any point in the project.  Communication tools Plint's comes with built-in tools for communicating with both internal and external parties about projects or individual tasks. System messages can be linked directly to projects or jobs to provide a clear context. Other tools include project Forums, a built-in Support area and a Help section whose articles can be targeted to selected users. This allows you to keep as much of the interaction in one system as you like, greatly reducing reliance on e-mail.  File-based or online workflows While the online editing tools are among Plint’s flagship features, some projects still revolve around delivering and receiving files. Plint can be used to streamline workflows that rely entirely on file delivery, online work, or a combination of both. "The Dashboard": Plint's home page for all user types. In this case a freelancer with some job offers plus an already accepted job, which is not yet ready for work.  People, projects and jobs People People are users/accounts in Plint. They could represent an in-house resource or an outside freelancer, a project manager or a client contact representing a company. They could also be a vendor – a company providing a service. All People can be assigned Jobs in Plint.  Accounts are divided into four types Workbench Root / admin users, with access to all projects, accounts and data Manager A customisable login type which can potentially access all the same tools and data as a Workbench user Access can be set for: Specific tools/pages Projects or People matching certain criteria A built-in limitation is that Manager users cannot edit the properties of Workbench and Manager user accounts.  A typical example would be a project manager who only sees projects and resources with certain target languages or for a certain client company. They could handle both the projects and the relevant pool of freelancers.  Another example would be a finance manager with access only to relevant tools, such as reporting and rate cards. Client Typically a person representing a client company. This account type has read access to all projects for the same company and some tools not available to Resource users.  Resource An in-house or external user or vendor responsible for specific Jobs.  Resource users do not have access to overall project information and the general progress. I nstead, all necessary information to complete a job is visible in the context of the job itself.  Projects A project in Plint is something that needs to be done: typically media in need of localization. This might be a single film or an entire series, including supplementals. The project serves as a container for all the information about the project, such as number of episodes and their running times, the source language and the target languages. Who sees what? As a Workbench or Manager user, you have full access to all information within the scope of that project, This includes general project data, files and jobs as well as notes and messages linked to individual jobs on the project. As a Client user, you can create a project by placing an order. After this point, changes to the project need to be done by a project manager but you can always follow the general progress of the project. You also have access to a client Filezone where relevant files for all parts and languages can be made available.  As a Resource user, you have no overview of the project itself, only jobs assigned to you. All information and files necessary to complete a job are made available within the scope of the job. (Some basic Project information is automatically visible to all job owners; such as project title and project manager.) Jobs A job is a step that needs to be performed in order for a Project to be completed. Typically a translation job assigned to a freelancer, or preparatory work assigned to a project manager. But it may also be an automated task represented as a job in the workflow: a process.  How a job is done in the system is decided by its Delivery method (sometimes called its Action ). A job can only have a single method, and the choice will have great impact. From the "Report" method, which simply lets a user click a button to mark it as done (for offline work, for example), to "Online editing" which opens a built-in subtitle editor, or automatic jobs such as "Auto-render subtitles".  They all have in common that on completion they are set to Done , allowing the next job (or jobs) to begin.  Joblists Jobs are linked to projects in interlinked chains called joblists. These can be created manually, or automatically using Joblist templates, based on project data.  A number of consecutive Jobs linked to a Project. Jobs are typically assigned to People, but may also represent an automated step.  Default functionality Plint is a system in constant development, and some features may be available that are outside the scope of the guaranteed toolset. The "out of the box" functionality of Plint includes, but is not limited to: Customisable system data/lists   System data can be edited in the system, such as:   Job types   Languages   Help categories   Tags/Keywords   Joblist templates   User  management   Administration  tools  for all  four   basic  login  types  and  their   details   Workflows   Chains of interdependent jobs utilising parent-child logic   With automatic notifications when previous job is completed and job visibility on user Dashboard   Project and  job  management   As  user  access  allows ,  tools  for  managing  the  following   Project data   Including tools for reusing default project target languages based on, for example, end client Job lists   Jobs   Tools to  simplify /speed  up   job / joblist  management   Joblist  templates   Including  the  ability  to  customise   these     Batch   editing   tools   Assigning jobs using criteria   Using factors such as a job types, languages and tags/keywords, users can be automatically assigned work   The same logic can be used to offer jobs to multiple users on a first come, first served basis (“The Shark Tank”)   Project progres s  view/reports   Core funct i onality includes    viewing overall progress on multiple projects   summarising and exporting (CS,XML) data about multiple projects   Inbox /  built -in  communication   tools   Ability  to  send  and  reply  to  messages ,  either  “ stand-alone ” or  linked  to  projects  or  jobs .   + “Notes to  self ”,  using  the same  logic   Notifications   about  new  messages  and  replies   through  email   Help  / Support   Built -in system for  creating  and  editing   Help   articles   Visibility on article level can be set using advanced user criteria   Built-in Helpdesk available to all logged-in users   Any user of “admin” type can be assigned Helpdesk role, on specified help categories   Online subtitle editing/creation   Uploading source media for use in online editors   Importing external subtitle files in supported formats   Creating subtitles/template from scratch based on visible video   Translating from an automatically loaded template   Reviewing subtitles and adding comments on subtitle level   Comparing changes in versions/milestones using Track changes   Returning job for adjustments     Other jobs   Any user type can perform work including, but not limited to, the following:   File uploads   Including tools for specifying required files and adding detailed information on upload   Online file review   Approvals   Several job types include option to reopen previous job to request changes   This action resulting in backup copies (“milestones”) for future reference/comparison   Job/page locking   Preventing users from editing the same file/record using built-in editing or administrative tools.  Extended   functionality  ( available  on  agreement )   Media  processing   Built -in  tools  for  converting  media and  creating   deliverables   Branding / white   label   Options for  changing   basic   graphic   properties  to  bring  system in  line   with   own   corporate   profile   Including   colour   scheme ,  custom  page  footer , logo in  header  and on login  screen   Automated   jobs   e.g .  Automatic  rendering  of   proxies  /  burnt -in  subtitles   Finance tools Fee calculation based on rate cards/templates Invoicing tools for freelancers Order profit calculations  Statistics/reports API- based project creation and access to subtitles Files in Plint Plint is built to host and handle all the files needed for media localization workflows. With the exception of attachments linked to support tickets and some other cases, files are as a rule linked to a project and available in its Filezone . More details here: Various types of files Source files for download With the right settings, the right vendor or freelancer will have access to what they need in order to start work. Audio stems, proxies for download or dialogue lists. But no one else. You are in control.  Deliverables With File upload jobs, anyone with a job with the right setting can deliver a file. It will land in the right project, linked to the right job and visible to the right people Media for online editing Plint will handle the conversion and preparations needed for playing video proxies in the online editors, with or without burnt-in timecode. All you need to do is upload the source file and select conversion type.  Subtitling work files Plint's internal file format is a structured JSON compatible with all its online editors. It contains not only the localized data but also supports reference text, comments, annotations and lots more.  On completion, automatic tools can export from these files into various deliverables, such as SRT and TTML.    Customisable properties: keywords, tags, languages and job types Most of the properties in Plint can be customised to suit your needs. This is done under Tools & Data by a user with sufficient access rights. There is an important group of properties that can be attached to both people, projects and jobs and used in vital ways: to help create and build workflows , making sure that the right person gets the job or for reporting and simple filtering . They are used to control the visibility of Help articles , making sure only the right users see a certain chapter.  Keywords These are typically used to characterise a project and the special factors needed to complete it. Adding the same keywords to users enable easy matching between requirement and skill.   Keywords come in two forms: Client keywords (Volvo, IKEA) and General keywords (for example genres or interest, such as Fishing or WWII).   Tags Think of tags as "keywords on steroids". Whatever they can do, tags can do, and more. They can be added to more data types, such as Client companies and target languages on job level. They can also be used to control workflows, not just for matching. Combining keywords and tags wisely, finding a good way to use them together, can create a highly flexible system that does a lot of the work for you. Some examples: By adding a tag to the target language of a project, you can make a joblist template add any number of additional jobs to a project. Or exclude them. If you always want to skip the extra proofing step for a certain language, it's entirely possible.  By adding the same tag to freelancers, you can use them as assignment criteria, ensuring that only the right people can be offered a job in this language, on this project. Used this way, they can complement keywords. One example would be using keywords for skills and tags for budget-related requirements. Keyword: Fishing Tag: only allow vendors with the tag "Price range 3" Tags can also be added to whole projects and used in much the same way. Pro tip: decide on a strategy for naming tags. By adding consistent prefixes or suffixes, they can more easily be accessed and added by typing part of the tag name.   Languages Focused on localisation, Plint treats languages as a separate property.  A language can also be added/used to represent a market (variations on the English text depending on where it is shown) or a special localization need, such as dual-language subtitling (French-Arabic).  Languages can also be categorized into groups .  Job types Job types are handled as a separate property type as well, but share some traits with the above. They can be attached to people and projects and used as criteria: example: the job type is Time coding . Only users with the same job type can be assigned the job. Job types are also used to automatically calculate rates and fees. Pro tip: Don't add job types needlessly. In cases where none of the above benefits apply, feel free to use a Custom job with any label. The job type does not affect how the job is done or delivered – that's where Delivery methods come in.