Glossary

This glossary says what each term in Teralo and its help articles means, industry terms included. Where an industry term doesn't name a screen in Teralo, its entry says which screen does.

• Host: the organisation that created a project and configures it. Learn more about hosts and guests.
• Guest: an organisation working on another organisation's project, such as a subcontractor, consultant or supplier. Guests add records and act on the workflow steps assigned to them. They don't configure the project.
• Organisation: a company's account in Teralo, holding its members, settings and plan.
• Project: one job. It holds the job's records and people from many organisations.
• Organisation level and project level: the two places a tool can sit. Learn more about organisation level and project level.
• Tool: one item in the sidebar, such as Inspections, Permits, Documents or Mail. A tool's types and templates are set up at organisation level and activated on each project. Learn more about the tools catalogue.
• Activation: making an organisation template available on a project, on the project's Tools page.
• Register: the table a tool opens on, with search, filters, grouping, saved views and export. Learn more about registers.
• Saved view: a register's filters, grouping, sorting and columns, saved under a name for yourself, the project or the organisation.
• My Items: the records on a project that are waiting on you. Learn more about My Items.
• Permission template: a named set of permissions given to a person, such as Site Team or Subcontractor Manager. Everyone on a project has one. Learn more about permission templates.
• Workflow: the steps a record goes through for review and approval. A template holds a workflow's structure, a run is one record's way through it, and binding attaches a template to a tool so new records use it. Learn more about what a workflow is.

• Contract sum: the agreed value of a contract, shown in Teralo as Total Contract Value. Approved variations change it.
• Schedule of values: the breakdown of a contract sum into sections and line items, each with a quantity, a rate and a Total. Progress is claimed against it. Procurement schedules and variations use the same structure.
• Cost code and cost type: the cost code is the part of the works a line belongs to, and the cost type is the kind of cost, such as labour, material or subcontract. Together they make the line's Budget Code.
• Commitment: money committed against a budget line by an awarded contract or order, shown in Teralo as Committed Costs.
• Progress claim: a claim for work done in a period, made line by line against the schedule of values. Learn more about progress claims.
• Certification: agreeing the amount to be paid against a claim, as distinct from the amount claimed. Teralo calls the agreed amount the assessed amount.
• Retention: an amount held back from each payment as security. Teralo supports a percentage, a maximum value, a bank guarantee in place of cash and tiered retention, with a separate basis for variations. When retention is released is set in Release Trigger Settings.
• Variation: a change to the scope, priced and approved, which changes the contract sum. Also called a change order. Learn more about variations.
• Provisional sum: an allowance in a contract for work not yet fully defined.
• Direct cost: a cost booked to the project budget outside a subcontract, such as a supplier invoice or plant hire.
• Cashflow: money due in and out over time. The organisation's Cashflow tool shows it month by month across the projects your organisation hosts, and each project's Program has a Cashflow tab. Learn more about cashflow.
• Tender: a priced offer for a package of work. Tenders lists the packages other organisations invite yours to price. The prices you receive for your own project's packages are in Procurement, under Tenderers. Learn more about tenders.
• Procurement package: a package of work put out to price, with its scope, the invited companies, their prices side by side and the award. Learn more about procurement.
• Take-off: measuring quantities from drawings to build up a price. Learn more about estimating.

• Program: the schedule of the works, with its tasks, durations, dependencies and dates. Learn more about Program.
• Work breakdown structure: the nested outline of a program, from the whole job down to single activities. A summary task rolls up the tasks under it.
• Dependency: a link saying one task can't start or finish until another has, with an optional Lag (working days).
• Critical path: the chain of tasks with no float. A task is critical when its float is at or below the Critical Path Threshold (days), which is 0 by default.
• Float: how long a task can slip before it delays another task.
• Baseline: a saved copy of a program's dates, for comparing with the current ones. Select Save Baseline to take one.
• Look-ahead: the next few weeks of work, for coordinating on site. A basic program is a look-ahead sheet, and an advanced program has a 4 Week Lookahead filter.
• Status date: the date progress is reported at.

• Inspection: a checklist completed at a place on the job, recording what passed and what failed. Learn more about inspections.
• ITP: an inspection and test plan, setting out what is checked, when, by whom and against what standard. In Teralo, an ITP is an inspection template plus the schedule on the Inspections Plans tab.
• Hold point: a stage that work can't pass until someone signs it off. A witness point is a stage someone may attend, where work continues if they don't. Teralo has no separate hold point setting. A workflow bound to Inspections applies to every inspection.
• Location: where work happens, held as a tree from a building down to a level, room or area. Many tools share one location tree, and each project names the levels of its tree.
• Observation: something seen on site that needs tracking to close-out, with an assignee and a due date. It can be raised from a failed inspection item. Learn more about observations.
• Defect: work not to the required standard. Defect is one of the default observation types.
• Incident and injury: an incident is an event, and an injury is a person hurt in one. Near Miss is a default incident type. An incident reported to the regulator is marked Authority Notified. Learn more about incidents and injuries.
• Permit to work: authorisation for high-risk work in a set place for a set time, given through an approval. Learn more about permits.
• Method statement: how a task will be done safely, reviewed before the work starts and signed by the workers doing it. Also called a SWMS (safe work method statement). Learn more about method statements.
• Safety data sheet: the manufacturer's document for a hazardous substance. Learn more about safety data sheets.
• Induction: the record of a worker cleared to work on site, with their details, licences, acknowledgements and expiry dates. Learn more about inductions.
• Compliance document: a document a project requires from an organisation, such as an insurance certificate or a licence, often with an expiry date. Learn more about compliance documents.
• Penetration: a hole through a fire-rated wall or floor for a service, sealed with a certified system and recorded. Learn more about passive fire.

• Revision: a numbered version of a drawing or document. Earlier revisions are marked superseded and kept. Learn more about versions and revisions.
• Document status: where a document stands. The default statuses are Draft, IFR (Issued for Review), IFC (Issued for Construction), AFC (Approved for Construction), Rejected, For Coordination and For Information.
• Transmittal: a record of documents issued to named people. Documents attached to mail are listed on the Transmittals tab in Documents.
• Markup: a drawing on top of a document, such as a cloud, a highlight, a measurement or a pin. Markups sit in a layer above the file, so the file itself doesn't change. Learn more about markups and annotations.
• Submittal: something submitted for review before it's used, such as a shop drawing, a sample or a product data sheet. Learn more about submittals.
• RFI: a request for information, a formal question about the design. In Teralo, an RFI is mail of the type Request for Information. Learn more about mail.
• Distribution group: a named group of people on a project, which mail can be sent to. Distribution groups are on the Distribution Groups tab of the project directory.
• Site diary: the daily record of a site, including who was there, the work done, the weather, deliveries and delays. Learn more about the site diary.