Skip to content
Vela
Book a call

Your project records, working together.

Vela reads your existing tools to find changes, check their impact and prepare work for your team.

Book a call

Start with the records you have.

Supplier emails and drawing revisions often disagree with the equipment register. Vela reads them together and shows where they differ.

  • Choose your sources
  • Keep your existing tools
  • Set access per workspace
  • Open the source behind a finding

Connected systems

4 reading

Read from Gmail, Google Drive, Google Sheets and Google Calendar. Proposed updates wait for approval; write access is separate.

Illustrative example with fictional project records.

Access

Choose what Vela can read.

Select the folders, mailboxes and calendars for each workspace. Check the connector directory for current availability.

  • Review access before connecting
  • Limit access to your project
  • Approve write access separately

Access scope

Per workspace
MailboxesThe three project threads you nameRead
Drive foldersDesert Ridge Storage, and nothing above itRead
Equipment registerLong-lead tabRead, write on request

You pick the scope per workspace, and you see the whole list before anything connects.

Changes

See which values changed.

Vela extracts the revised dates and requirements, with a link to the source behind each finding.

  • Compare old and new values
  • Check calculations
  • Open the cited document

One thread, read four ways

Ready to ship28 Sep 2026 → 26 Oct 2026Moved
On site26 Oct 2026 → 23 Nov 2026Moved
Float to need-by11 days → 17 days lateDerived
SourceRE: GSU-01 reserved slot — revised delivery positionGmail

Check the changed values against the supplier email.

Ownership

Get the finding to its owner.

Review who needs to act when a delivery date changes, from procurement to the engineer responsible.

  • See who owns each milestone
  • Share the relevant project view
  • Set access per person

Who sees the change

Ana DuarteProcurement ManagerOwns the decision
Priya RamanInterconnection LeadEnergization date
Hollis TrentOwner's Engineer, Saguaro Line EngineeringRead-only

An outside engineer gets the view without getting an account. Access is set per person.

Example

A supplier changes a delivery date.

In this fictional project, Vela checks the email against the register and prepares the update for review.

1

A message lands

Meridian moves the ship date from 28 Sep to 26 Oct 2026.

Gmail · 24 Jul 2026
2

Vela finds the conflict

The register still shows arrival on 26 Oct 2026. Vela flags the conflict.

Long-lead tab, row 12
3

The delay affects a milestone

Arrival on 23 Nov is 17 days after the 6 Nov need-by date in Rev 7.

Float: 17 days late
4

The owner reviews the update

Dana Whitfield reviews the register edit. Ana Duarte and Priya Raman see the delivery impact.

Awaiting approval

More about Vela

Explore the products

AI agents

Create an agent for a task and choose its access.

Explore

Project model

Keep project records with their sources and history.

Explore

Project views

See the work and decisions relevant to your role.

Explore

Get to know Vela.

Meet the team and learn what we are building. No preparation needed.

Book a call