L-IT Console Time-entry workflow
v0.1.0 local

Time-entry workflow

Move tracked hours from Google Sheets into Coral Time in four reviewable steps.

Preview build. This page shows the intended workflow. Google Sheets import and Coral Time submission are not connected yet; every row below is sample data.

Workflow

  1. Import from Google Sheets

    Pull tracked hours from the shared timesheet.

    Not connected

  2. Review / Dry Run

    Check parsed rows and totals before anything is written.

    Available soon

  3. Compare with Coral Time

    Match rows against existing Coral Time entries.

    Not connected

  4. Submit to Coral Time

    Write the approved hours as Coral Time entries.

    Not connected

Sample time entries

Illustrative preview — not loaded from Google Sheets and not written to Coral Time.

5 sample rows marked Sample
Date Project Task Hours Status
2025-01-06 Internal Platform Sprint planning 2.5 Ready for dry run Sample
2025-01-06 Client Alpha Data migration review 4.0 Needs review Sample
2025-01-07 Client Beta API integration 6.0 Ready for dry run Sample
2025-01-07 Internal Platform Code review 1.5 Missing project code Sample
2025-01-08 Client Alpha Deployment support 3.0 Ready for dry run Sample

Totals shown for illustration only: 5 rows, 17.0 hours.

Next actions

Controls are visible for review. Nothing is sent to Google or Coral Time from this build.

Not connected. Google Sheets import and Coral Time submission are disabled until credentials and endpoints are configured.

Not connected — Google Sheets credentials are not configured.

Preview validation only; this build performs no submission.

Not connected — Coral Time API access is not configured.

Not connected — submission is disabled in this build.

Before this build can submit

  • Connect the Google Sheets source and pick the tracked-hours worksheet.
  • Map sheet columns to the fields Coral Time expects.
  • Enable Dry Run to validate rows without writing anything.
  • Compare reviewed hours against existing Coral Time entries to catch duplicates.
  • Submit only after the dry run and comparison are clean.