decídalo
Documentation
Ask AI
Search Results for

    Show/Hide Table of Contents

    Glossary

    Short definitions for the terms used across these docs. Where two terms are close, the difference is called out explicitly.

    People and access

    User: anyone who can sign in to decídalo. Every user has exactly one account.

    Account: the sign-in record (email, password, permission profile). Distinct from Profile.

    Profile: a person's professional record inside decídalo: master data, projects, skills, certificates, trainings, roles. A profile may exist without an account (e.g. a freelancer you track but who doesn't log in). See Understanding Profiles, Accounts & CVs.

    Permission Profile: a named bundle of permissions. Every account gets exactly one. The five standard profiles are Restricted, Employee, Team Manager, Resource Manager and Admin; your organisation can rename them and add its own. See Permission concept.

    Delegation: a temporary hand-off of someone's responsibilities to another user (e.g. during vacation). See Delegations.

    Organization

    Tenant: your company's isolated instance of decídalo.

    Company: a top-level entity inside a tenant. Tenants can host multiple companies.

    Team: a group of consultants reporting to a team manager. Teams have a hierarchy and drive permission scoping (team data).

    Resource Group: a cross-team grouping used for staffing (e.g. "available for German-speaking projects"), and to decide who may record time directly on an order. Different from a team.

    Subgroup: a named group of people whose profiles meet a set of conditions (e.g. business unit "Consulting" and country "Germany" or "Austria"), used to set a skill goal or a certificate goal for part of the company. Skill and certificate goals share subgroups. Different from a team and from a resource group: a subgroup has no managers and grants no permissions.

    Job Family: a higher-level grouping of roles (e.g. "Engineering" containing "Frontend Developer", "Backend Developer", …).

    Role: what a consultant does on a project (e.g. "Solution Architect"). Drives the skill profile expected of them.

    Documents

    CV (also "resume"): a document tailored to a specific opportunity, generated from a profile. A profile is the source; CVs are the output. See Managing & Using CVs.

    CV Template: the company's Word or PowerPoint layout that CVs are generated into. Templates are an admin / design responsibility. See CV Templates.

    Reference: a one-pager or write-up about a past project, used in proposals to demonstrate experience. See Reference Generation.

    Quotation: a generated quotation document for an opportunity. See Quotation Generation.

    Skills

    Core Skill: a skill the company tracks deliberately as part of its taxonomy. Drives role skill profiles, the skill matrix, and matching. Curated by administrators. See Skill Overview.

    Specific Skill: a granular skill (often a specific technology, framework, or tool) added directly to a profile by the consultant. Less curated than core skills.

    Top Skill: a skill a consultant highlights as central to their profile.

    Skill Catalog: the full collection of skills known to the tenant (core + specific).

    Skill Matrix: the cross-team view of who has which skills. See Skill Matrix.

    Role Skill Profile: the set of skills expected of someone in a given role; used for matching and gap analysis. See Company Profile: Role Skill Profiles.

    Demand and staffing

    Project: an engagement that consultants get booked onto. See Projects.

    Opportunity: an as-yet-unwon project under discussion with a client.

    Resource Request: demand for one or more consultants against a project or opportunity. Has required skills, role, dates, and (often) attached candidates. See Connecting Resource Requests to Projects.

    Booking: a staffing assignment: this consultant, this project, these dates, this percentage. Its booking status (soft, reserved, confirmed or rejected) says how firm it is. See Workflows.

    Soft Booking: a tentative booking, not yet confirmed (e.g. while sales is still negotiating). If your company lets the booking workflow start on soft bookings, it is also the status in which a booking waits for approval. See Workflow start status.

    Confirmed Booking: a booking with all approvals in place; commits the consultant's time.

    Position Status: whether the position a booking is for is already won (Confirmed) or still an opportunity (Unconfirmed). Only used while the Position status data field is active for bookings (it is inactive by default); a booking on an unconfirmed position can then only be soft or rejected. See Position status.

    Bench: a consultant's unbooked capacity, and the managed list of the people who have it. decídalo suggests people whose booked work is about to end, and an authorized user confirms or removes their bench membership. The bench marker beside a person in the Resource Plan shows and sets that same membership.

    Working Time Pattern: the contractual schedule (full-time, 4-day week, …) that defines a consultant's nominal capacity. See Working Time Patterns, Absences & Availability.

    Time recording and billing (beta)

    Timesheet: where a person's working and recorded times for a period are kept and maintained. Everyone has their own; managers open other people's under Timesheets. See My Timesheet.

    Working Time: attendance. When the day started, when it ended, how long the break was.

    Recorded Time: what was worked on, as a list of entries. Deliberately independent of working time: a person can be at work for eight hours and record six. Different again from billed time, which is what a customer is charged. See Time recording concept.

    Hand In: the recorder's step of marking recorded time as final, only where the company runs time recording approval. On a project that requires approval the time then waits as Confirmation requested; everywhere else it is confirmed at once. Distinct from confirming, which is the approver's step. See Handing in your time.

    Subject: what a recording entry is booked against, shown as a path. Exactly one of: a project, a work package, an order position (each with an activity type), or a general activity. See What you record time on.

    Activity Type: the kind of work an entry was (development, consulting, travel). A company-wide catalogue; each one carries whether it is billable by default. Distinct from General Activity.

    General Activity: work that belongs to no project (internal meetings, training, vacation, sick leave). Never billable, and never on a servicesheet. Recording vacation here is not an absence and does not affect availability.

    Recording Type: a value an entry can carry beside its time, such as travel time or a travel distance, each its own column. Time itself is one and cannot be removed. Switched on per subject, priced per order position, and billed on servicesheet lines of its own. See What an entry records.

    Work Package: a part of a project that work is planned and recorded against. Who may record on it is set per project: by default only the members of its team, which is what makes membership worth maintaining, otherwise only those of them with a confirmed booking, or everyone. See Who may record against what and How somebody joins a work package's team.

    Order: what a customer actually ordered. Carries one currency, can serve several projects, and has its own customer, which need not be the projects'. See Orders & Positions.

    Order Position: one line of an order, either Fixed price or Time & material. A time & material position carries the rates, one per recording type it records, so it decides what recorded work is worth. A fixed-price position carries only its lump sum, which covers everything recorded against it.

    Framework Agreement: a commercial frame (validity, currency, agreed rates) that orders are prefilled from. Naming its customer is optional, and it can cover projects of any customer, such as a group head office's agreement covering its subsidiaries' projects. A project belongs to at most one. See Framework Agreements.

    Rate: a priced label, per Hour or per Person day, the latter always counted as eight hours. Rate Card: a named bundle of rates used as reference data. Prefilling from either copies the values, so later edits never move a price already agreed.

    Servicesheet: decídalo's record of the work delivered to a customer in a period (what, by whom, how long, at what rate). It is not an invoice: most companies invoice in another system, and a servicesheet is the proof of delivery that feeds it. Travels Draft → Accepted → Paid, or is Withdrawn. See Servicesheets.

    Servicesheet Policy: a named set of servicesheet rules that turns what was recorded into what is proposed on a servicesheet: the duration rules for the time itself (a minimum per subject and day, rounding up to a step, a daily maximum and what happens above it) and a rule set of its own for each further recording type, such as a minimum for travel time or a flat amount for a distance. It prefills, it does not fix: whoever bills has the last word. See Servicesheet policies.

    Delivery: the project tab showing its recorded time with its billing state, and what has already been put on servicesheets. Also where recorded time is confirmed. Not to be confused with a Delivery model on a resource request.

    Billable Work: the overview of what could be billed right now, by period and by order, and one of the two places a servicesheet is started from (the other is Create on the servicesheet list). See Billable Work.

    See also

    • By role: pick your role to see which terms matter most for you.
    • By task: concrete scenarios that use these terms in context.
    In This Article
    Version history Back to top Copyright © data assessment solutions · decidalo.com