Client Project Board for Nextcloud Deck
as a free board template.
A client project board 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
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
In Progress1
Send a short progress note every week
A predictable update stops the client from asking, and it creates a written record.
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
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.
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
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 whose client disputes come from criteria and scope nobody wrote down.
02
How to run this board
Write criteria and exclusions first.
Fill in the intake checklist and list what is not included before work starts.
Send a short note every week.
Use the weekly update card. Move a card to Waiting Client the moment you are blocked.
Review internally, then deliver and invoice.
Review the work yourself before the client sees it. Close out the admin while it is fresh.
03
What this creates
6 stacks, 4 labels, and 6 starter cards with 17 checklist steps.
04
Standard Deck objects only
The result is an ordinary Deck board that you edit like any other. With a Nextcloud account, Deckloud writes it straight to your server, with no relay.
05
Safe import rules
The file holds no server IDs. Due dates count from the day you create the board, and checklists are Markdown task lists in card descriptions.
FAQ
Practical questions
Does the template include comments or attachments?
No. Comments need an author, and attachments differ between servers and Deck versions, so v1 templates hold text only.
Why is Waiting Client its own stack?
It makes client delay visible. When a deadline slips, the board 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.
Related
Nextcloud Deck templates, free to download and import.
Free Nextcloud Deck board templates with starter cards and checklists: kanban, GTD, releases, bug triage, incidents, hiring, events, study, and more.
OpenBuild a Nextcloud Deck template in your browser.
Build a simple Deckloud template JSON in your browser for a Nextcloud Deck board. No account, no upload, no server credentials.
OpenCreate templates that stay portable.
Create portable Nextcloud Deck board templates with stack keys, label keys, starter cards, and relative due dates.
Open