Reference

Glossary

Every Srishti term you meet in the app, in alphabetical order, with a link to where it is explained in full.

Everyone

Words in bold are labels exactly as the app shows them. Follow a link for the full explanation.

A to C

Action: The page-access level that lets you change things in a module, not only look. See Page access.
Action log: The history of one activity, on the Action log tab of its side panel: what changed, who changed it and when.
Activity: One piece of work in a project, with a duration, a team, an owner, the activities it waits for and the tasks that complete it. See Activities and tasks.
Activity template: The starting plan every new project copies: activities, durations, predecessors, teams and tasks. See Activity templates.
Ahead: A project whose forecast launch is earlier than its baseline launch, with no critical-path activity delayed. An activity is Ahead when it finished before its baseline end.
Approvals & Alerts: The page, in everyone's menu, where approvals waiting on you and all your notifications are listed. See Approvals.
Approver: A person with the Approver flag, set in User Management. Only approvers can be named as baseline approvers, decide activity approvals or be someone's escalation contact.
At risk: A project whose forecast launch is not later than its baseline launch, but with at least one critical-path activity Critical, or two or more activities Near critical.
Baseline: The agreed plan a project is measured against. The first, BL0, is saved when the project is created; each approved re-baseline that changes dates saves the next one (BL1, BL2…). See Baselines.
Baseline approvers: The one to three approvers a PM names when creating a project. They decide a new project that runs over its template and every re-baseline of that project.
Baseline launch: The launch date in the project's current baseline.
Behind schedule: A project whose forecast launch is later than its baseline launch.
Calculate schedule: The button in step 4 of project creation that works out every date, the float and the critical path from Activity 1's start date.
Changes needed: A project draft an approver sent back with Request changes. The PM chooses Make changes, then Resubmit for approval.
Check / Reject, Approve / Reject: Review tasks: the owner checks or approves a document an earlier activity uploaded, or rejects it and sends the work back.
Closed: A project ended with Actions → Close project. Closing cannot be undone; everything stays viewable but nothing can change.
Completed: A project whose mandatory activities are all complete.
Conversation: A thread of messages inside a project, about the project or one activity. See Conversations.
Critical: An activity status: on the critical path, with less than 20% of its own duration left before its planned end.
Critical path: The chain of activities with no float. A delay on any of them moves the launch date. See Schedule, float and the critical path.

D to F

Delayed: An activity status: today is past its planned end and it is not complete.
Document storage: A named structure of folders, subfolders and document names that activity templates file their documents under. Draft until published, then Active. See Document storage.
Document Upload: A task type: the owner uploads one file for each document the task names.
Draft: Not finished yet. A project draft is a project still being created; a template or document storage structure in Draft cannot be used until it is published.
Duplicate: Copy an activity template or a document storage structure into a new Draft that you own. Later changes to either copy do not affect the other.
Escalation level 1 (L1): The approver a person's work escalates to first: told when their activity is due. Set in User Management.
Escalation level 2 (L2): The approver told when a person's activity is four days overdue. Without one, the L1's own L1 is told. See Notifications, reminders and escalations.
Float: How many days an activity can slip without moving the launch date. Activities with no float are on the critical path.
Forecast launch: The launch date Srishti calculates from today's plan: current dates, durations and dependencies.
FS (finish-to-start): The only kind of dependency: an activity starts after its predecessor finishes, plus any lag. Written as 3 FS or 3 FS+2.

G to O

Gate: An activity that waits for a sign-off from its approvers before work moves on. It waits under Pending Approvals, like other activity approvals.
Grant: Access to a project's documents that the PM gives a person or team, on the whole project, a folder or one document: View only or View & Download. A grant never opens a document before its visibility trigger.
Lag: Extra days between a predecessor finishing and the next activity starting.
Master team: One of the eight teams templates are built on: Marketing, F&D, Regulatory, Packaging, Quality, Operations, Finance and Management. They cannot be renamed or deleted.
Mandatory, non-mandatory: A project is Completed when all its mandatory activities are complete; non-mandatory ones do not hold it up. A non-mandatory activity can never be a predecessor.
My Activities: Everyone's home page: the activities assigned to you, grouped by project, with their tasks, documents and conversations. See My Activities.
Near critical: An activity status: not on the critical path, but with float of 5% of the project's length or less, so a small slip could move the launch date.
Needs reassignment: A card on a project's Overview listing open activities still assigned to people who were removed. The PM gives each a new owner.
On track: A project whose forecast launch is not later than its baseline launch and that is neither At risk nor Ahead.
Owner: The person an activity is assigned to (Assigned to), from the activity's team. They complete its tasks.

P to R

Page access: What a person can open: None, View or Action for each of Portfolio (None or View only), Projects, Templates and User Management; My Activities is always Action. See Page access.
Pending approval: A new project waiting for its approvers because its schedule runs over its template.
PM: The project manager: the person who created the project. Nothing in Srishti changes a project's PM.
Portfolio: The read-only dashboard of every active project's health. Needs Portfolio: View. See The Portfolio dashboard.
Predecessor: An activity that must finish before another can start.
Project duration (CPM): A template's length in days along its critical path. A new project whose schedule runs longer needs approval.
Project type: Innovation Class A or B, Renovation Class A or B, White Label or Hybrid. A project takes its type from its template. On a person, project types are only a label for filtering.
Project-wide access: On a project's Documents tab, the people who can see every document: the PM and everyone granted access to the whole project.
Re-baseline: A change to a project's baseline: the PM's Actions → Create new baseline draft, decided by a baseline approver.
Round: One pass of a new-project approval. Round 1 allows Approve or Request changes; round 2 allows Approve or Reject.

S to Z

Schedule deviation: Baseline launch minus forecast launch, in days: + is ahead, − is behind, zero is on schedule.
Slot: One document name in a document storage structure: the place for the file a Document Upload task asks for. An empty slot shows Pending.
Sub-activity: An activity inside another, numbered like 3.1. An activity can have up to 10, one level deep.
Tag: Naming a project member in a conversation. They are notified in the app and by email, and the thread shows Needs your reply for them.
Task: What an activity's owner does: Document Upload, Checkbox, Field Input, Check / Reject or Approve / Reject. Mark task complete stays off until everything mandatory is done.
Team: The group a person belongs to. An activity's owner must be on the activity's team. See Users, teams and escalation chains.
Thread: One conversation in a project: a title, a first message and replies.
Top of chain: A person with no escalation level 1, shown as — (top of chain). Their due-today alerts reach nobody.
Version: Each upload of a document: V1, V2 and so on. Only the PM sees older versions.
View: The page-access level that lets you open a module and look, without changing anything.
Visibility trigger: When a document becomes visible beyond the uploader's team: On upload, On check or On approval. Set on each Document Upload task.
Visible to: The teams, or All teams, that may see a Document Upload task's documents once the trigger fires, if they are assigned to an activity in the project.

A to C

D to F

G to O

P to R

S to Z

Related