Workflow template

Client Project Board for Nextcloud Deck as a normal Nextcloud Deck board.

A client project board for Nextcloud Deck with stacks for Intake, Scope, In Progress, Review, Waiting Client, and Delivered. Starter cards cover success criteria, exclusions, weekly updates, and invoicing.

Last verified

Board preview

Client Project

Intake1

Collect constraints and success criteria

Write the result, deadline, owner, and blocker list before work starts.

  • Name the one outcome the client is paying for
  • Record the hard deadline and what drives it
  • List every system or person you need access to
  • Write down the budget or day rate agreed
  • Note who signs off on the finished work
Client

Scope1

Write down what is not included

Most client disputes come from unstated exclusions, not from the work itself.

  • List the deliverables in plain language
  • List what is explicitly out of scope
  • State how many revision rounds are included
  • Agree what happens when scope changes
Clientdue in 2 days

In Progress1

Send a short progress note every week

A predictable update stops the client from asking, and it creates a written record.

Follow-updue in 7 days

Review1

Run your own review before the client sees it

Catch the obvious problems yourself so the client review is about substance.

  • Check the work against the success criteria card
  • Proofread every client-visible string
  • Test the delivery on a clean machine or account
  • Confirm nothing internal or private is included
Admin

Waiting Client1

Chase approvals after three working days

Move a card here the moment you are blocked, so waiting time is visible rather than silent.

Urgentdue in 3 days

Delivered1

Close out and invoice

Finish the administrative work while the project is still fresh.

  • Hand over files, accounts, and credentials
  • Send the final invoice with the agreed terms
  • Write two lines on what to do differently next time
  • Ask for a reference or testimonial
Admin
ClientAdminUrgentFollow-up
View the portable v1 template JSON
{
  "schema": "deckloud-template-v1",
  "schemaVersion": 1,
  "slug": "client-project-nextcloud-deck",
  "locale": "en",
  "title": "Client Project Board for Nextcloud Deck",
  "description": "A client-facing workflow for intake, scope, active work, review, waiting on client, and delivery.",
  "category": "work-teams",
  "tags": [
    "client",
    "project",
    "review"
  ],
  "quickCreateStackKey": "intake",
  "compatibility": {
    "requiresBoardCreate": true,
    "includesAttachments": false,
    "includesComments": false
  },
  "board": {
    "title": "Client Project",
    "color": "8B5CF6"
  },
  "labels": [
    {
      "key": "client",
      "title": "Client",
      "color": "8B5CF6"
    },
    {
      "key": "admin",
      "title": "Admin",
      "color": "64748B"
    },
    {
      "key": "urgent",
      "title": "Urgent",
      "color": "EF4444"
    },
    {
      "key": "follow-up",
      "title": "Follow-up",
      "color": "F59E0B"
    }
  ],
  "stacks": [
    {
      "key": "intake",
      "title": "Intake",
      "order": 1
    },
    {
      "key": "scope",
      "title": "Scope",
      "order": 2
    },
    {
      "key": "in-progress",
      "title": "In Progress",
      "order": 3
    },
    {
      "key": "review",
      "title": "Review",
      "order": 4
    },
    {
      "key": "waiting-client",
      "title": "Waiting Client",
      "order": 5
    },
    {
      "key": "delivered",
      "title": "Delivered",
      "order": 6
    }
  ],
  "cards": [
    {
      "stack": "intake",
      "title": "Collect constraints and success criteria",
      "description": "Write the result, deadline, owner, and blocker list before work starts.\n\n- [ ] Name the one outcome the client is paying for\n- [ ] Record the hard deadline and what drives it\n- [ ] List every system or person you need access to\n- [ ] Write down the budget or day rate agreed\n- [ ] Note who signs off on the finished work",
      "labels": [
        "client"
      ]
    },
    {
      "stack": "scope",
      "title": "Write down what is not included",
      "description": "Most client disputes come from unstated exclusions, not from the work itself.\n\n- [ ] List the deliverables in plain language\n- [ ] List what is explicitly out of scope\n- [ ] State how many revision rounds are included\n- [ ] Agree what happens when scope changes",
      "labels": [
        "client"
      ],
      "dueOffsetDays": 2
    },
    {
      "stack": "in-progress",
      "title": "Send a short progress note every week",
      "description": "A predictable update stops the client from asking, and it creates a written record.",
      "labels": [
        "follow-up"
      ],
      "dueOffsetDays": 7
    },
    {
      "stack": "review",
      "title": "Run your own review before the client sees it",
      "description": "Catch the obvious problems yourself so the client review is about substance.\n\n- [ ] Check the work against the success criteria card\n- [ ] Proofread every client-visible string\n- [ ] Test the delivery on a clean machine or account\n- [ ] Confirm nothing internal or private is included",
      "labels": [
        "admin"
      ]
    },
    {
      "stack": "waiting-client",
      "title": "Chase approvals after three working days",
      "description": "Move a card here the moment you are blocked, so waiting time is visible rather than silent.",
      "labels": [
        "urgent"
      ],
      "dueOffsetDays": 3
    },
    {
      "stack": "delivered",
      "title": "Close out and invoice",
      "description": "Finish the administrative work while the project is still fresh.\n\n- [ ] Hand over files, accounts, and credentials\n- [ ] Send the final invoice with the agreed terms\n- [ ] Write two lines on what to do differently next time\n- [ ] Ask for a reference or testimonial",
      "labels": [
        "admin"
      ]
    }
  ]
}

01

When to use this board

For consultants and freelancers running client work where the disagreements are almost never about the work itself. The board front-loads the two things that prevent them: written success criteria at intake, and an explicit list of what is out of scope before anything starts.

02

How to run this board

  • Write criteria and exclusions first.

    Fill in the intake checklist and list what is not included before you move any card to In Progress.

  • Send a short note every week.

    Use the weekly update card for a predictable progress note, and move cards to Waiting Client the moment you are blocked.

  • Review internally, then deliver and invoice.

    Run your own review before the client sees the work, and close out the admin while the project is fresh.

03

What this creates

6 stacks, 4 board labels, and 6 starter cards carrying 17 checklist steps. Attachments and comments are intentionally omitted so the template stays portable.

04

Why it fits Deckloud

The template is just a recipe for standard Deck objects. No hosted workflow account, no relay backend, and no Deckloud-only object model.

05

Safe import rules

IDs are not stored. Stack and label keys are remapped at creation time, due dates use relative offsets instead of stale fixed dates, and checklists are written into the card description as ordinary Markdown task lists.

FAQ

Practical questions

Does this change my Nextcloud server schema?

No. It creates ordinary boards, stacks, labels, and cards through the normal Deck model.

Does the template include comments or attachments?

No. V1 templates are text-only because comments imply authorship and attachments vary by server/version.

Can I edit the board after creating it?

Yes. After creation it is just a normal Nextcloud Deck board.

Why is Waiting Client its own stack?

It makes client-side delay visible instead of silent. When a deadline slips, the board already shows how long approval sat unanswered.

Should client-specific details go in the template?

No. Keep names, rates, and credentials on the board you create, never in a template you share. Templates are recipes, not records.

Get Deckloud

Work with your Nextcloud Deck boards natively

Get Deckloud for iPhone and iPad, or the desktop app for Mac, Windows, and Linux. Your boards, cards, and due work stay on your own server.