GuideDaily WorkflowDaily Workflow
Daily Workflow

Daily Workflow

This is where you'll spend most of your time in Shipmark. Everything here is built around one idea: capturing work should take seconds, not minutes, so you actually keep doing it.

A day with Shipmark

Log as you go

A sentence per finished task, in seconds.

Capture the rest in Notes

Anything that isn't a dated entry.

Work through your tasks

Assigned → In Progress → Review → Done.

Let reminders catch what you'd forget

Deadlines and follow-ups, handled on time.

My Logs

A dated record of what you actually worked on.

Why it exists

Status meetings exist because work is invisible by default. A log entry — title, work type, duration, optional notes and screenshots — makes it visible without anyone having to ask.

When to use it

Throughout the day, or in a short batch at the end of it.

  1. 1

    Open "+ New Log"

    From the dashboard or the My Logs page.

  2. 2

    Describe the work

    Type it naturally — quick logging fills in work type and duration for you — or fill the form manually.

  3. 3

    Tag it

    Pick a work type (15 built-in categories) and, if the project has any, a custom tag.

  4. 4

    Attach a screenshot if it helps

    Optional, but useful for anything visual.

app.shipmark.io/logs
My Work Logs
Today · 3 entries · 2h 25m logged
+ Add Log
Auth flow refactorFeature
Rewrote token refresh logic
45m
Fix race condition in queueBug Fix
Added mutex lock to job runner
1h 20m
PR #204 reviewedCode Review
Left 6 comments, approved
20m

Pro Tip

Work types like Bug Fix, Feature, Research, Blocker, and Meeting exist so your logged time rolls up into meaningful analytics, not just a wall of text.

Pro Tip

A project can define its own custom tags on top of the 15 built-in work types, for vocabulary specific to that codebase or client.

Notes

Rich-text space for anything that isn't a dated log entry.

Why it exists

Not everything worth writing down happened on a specific day for a specific duration — meeting minutes, a running list of gotchas, onboarding docs. Notes is that space, separate from the log timeline.

When to use it

Capturing knowledge you'll want to search for later, not a single day's work.

  1. 1

    Open Notes

    From the sidebar.

  2. 2

    Create a note

    Choose Private (only you) or Team visibility.

  3. 3

    Write with the rich-text editor

    Headings, lists, and formatting, not just plain text.

Pro Tip

Use Private notes for anything you're still figuring out, and switch to Team once it's worth sharing.

Tasks

Assigned work with priority, status, and comments attached.

Why it exists

A log records what already happened; a task tracks what still needs to. Keeping the conversation on the task itself — instead of scattered across chat — means nothing gets lost.

When to use it

Anything that needs an owner, a priority, or a deadline.

  1. 1

    Create a task

    From a project or the Tasks page — title, description, and priority (Low, Medium, High, or Urgent).

  2. 2

    Assign it

    One person per task — Shipmark deliberately keeps task ownership single-assignee, so accountability is never ambiguous.

  3. 3

    Set a due date

    Optional, but it's what powers overdue reminders.

  4. 4

    Track it through

    Assigned → In Progress → Review → Done (or Blocked / Cancelled along the way).

app.shipmark.io/tasks
Tasks
+ Create Task
JFix checkout redirect bugUrgentIn Progress
AWrite onboarding email copyMediumReview
MSet up staging DB backupsHighAssigned
AArchive Q1 campaign assetsLowDone

Pro Tip

@mention a teammate in a task comment to notify them directly, instead of hoping they check back.

Pro Tip

Link a task to an approved client requirement from the Scope Tracker so scope and execution stay connected.

Reminders

Time-based nudges for meetings, deadlines, and follow-ups.

Why it exists

Some things need to surface at a specific moment, not just sit in a list — a client call, a deadline, a follow-up you'd otherwise forget.

When to use it

Anything tied to a specific time rather than an ongoing task.

  1. 1

    Create a reminder

    Give it a title, a type (Meeting, Task, Deadline, Follow-up, or General), and a time.

  2. 2

    Get notified

    A notification fires 15 minutes before it's due.

  3. 3

    Snooze or dismiss

    Push it back or mark it handled once it's done.

Pro Tip

Checklist steps with a due date can create a linked reminder automatically, set for 9am the day before.

Best practices

  • Log immediately after finishing something rather than batching it — the detail you remember at 5pm about a 9am task is thinner than you think.
  • Reserve Notes for anything you'd want to search for weeks later; keep logs focused on "what happened, how long".
  • Give every task a priority honestly — a list where everything is Urgent stops meaning anything.

Frequently asked questions

The 15 work types (Feature, Bug Fix, Testing, and so on) are fixed and shared across the whole app. Custom tags are per-project labels a team defines for their own vocabulary — both can be applied to a log at once.
No — tasks are deliberately single-assignee, so there is always exactly one owner. The Build-Step Checklist, covered on the Projects & Checklist page, is the one place multiple people can be assigned to the same item.

Need more help?

Can't find what you're looking for here — try these.