How to Run a Project with a Task Board and Deadlines

A project is late long before the deadline arrives; it becomes late the first time a task has no clear owner or date. The cure is not working harder but running the project in a simple, repeatable way. This guide shows a method you can use on a task board, whether you are building a website, fitting out an office, running a training programme or launching a campaign.

1. Define the finish line

Before creating tasks, write three things in plain words: what will be delivered, who accepts it and by when. For example, "A working online shop with 200 products and payment set up, accepted by the owner, live before the festival season." If the client or your boss cannot agree on this sentence, the project will drift. Also write what is not included, because unwritten extras are the main cause of overruns.

2. Break the work into tasks

Split the project into milestones, then each milestone into tasks that one person can finish in one to three days. A task that says "design" is too big; "design home page desktop layout" is just right. Smaller tasks make progress visible and problems early. Use subtasks or a checklist for the steps inside a task.

• Start from the end: what must be true for the client to sign off?
• List the tasks needed for each milestone.
• Add tasks for reviews, approvals and client feedback; these delays are often forgotten.
• Mark tasks that wait on the client or a third party, so waiting time is not blamed on your team.

3. Give every task one owner and one date

One person, not "the design team". Shared ownership means no ownership. Agree the date with the owner instead of imposing it; people keep dates they helped set. Include some buffer, and respect real Nepali calendar issues: Saturday is the usual weekly off, Dashain and Tihar can swallow weeks, and elections, bandhs or monsoon can slow site work. Put such known gaps in the plan on day one.

4. Set up the board

Keep stages simple and in the language your team uses:

Stage	Meaning
To do	Planned and assigned, not started
In progress	Someone is working on it now (limit this per person)
Waiting	Blocked by a person or event outside the owner's control
Review	Finished by the owner and waiting for check
Done	Accepted, with files attached

Limiting how many tasks each person has in progress at once prevents the common problem of ten half-finished tasks and nothing delivered. A tool such as our project management software lets you drag cards through these stages and see the whole project at a glance.

5. Run a short weekly review

Once a week, for thirty minutes, open the board and check four things:

1. What finished since last time?
2. What is overdue, and why?
3. What is blocked, and who can unblock it?
4. What are the next week's top priorities?

Do not read status aloud from memory; read it from the board. Update owners and dates in the meeting itself. Short daily check-ins of ten minutes are useful for urgent phases, but do not turn them into long reporting sessions.

6. Handle change without chaos

Clients will change their minds. Treat each change as a new task with an estimate, and tell the client what it does to the date or budget before you accept it. Writing the change on the board and getting a simple written confirmation, even by WhatsApp or email, keeps friendships intact. Many Nepali projects suffer because "small changes" are accepted verbally and the extra work is never recognised.

7. Track time if money depends on it

If you bill by the hour, or want to know if a fixed-price job is profitable, log time on tasks. Compare estimated and actual hours at the end of each project and use the difference to estimate better next time. After three or four projects, your quotations will be noticeably more accurate.

8. Close properly

• Get written acceptance from the client.
• Archive files and decisions with the project.
• Hold a short review: what went well, what went wrong, what we change.
• Save the task list as a template for similar projects.

If client updates are a burden, see how a helpdesk system separates support requests from project work after delivery.

A worked example: launching a small business website

Take a simple project: a five-page company website for a local client. The finish line is a live site accepted by the owner before a set date. Milestones might be content collected, design approved, development complete, testing done and launch. Under design approved you might have tasks such as collect logo and brand colours, prepare home page layout, send for client review, apply feedback and get written approval. Each has one owner and a date, and the client-review task is marked as waiting on the client so everyone understands that a delay on their side moves the launch.

In the weekly review the manager sees at once that the content task is two days overdue and blocking the design. A polite WhatsApp message to the client, with the task link and the new date, solves it that day instead of at the end of the project. That small difference, repeated across tasks, is what makes a project run smoothly.

Keep the board clean

Archive finished tasks regularly, delete duplicates and avoid inventing new stages for every special case. A board that looks messy will not be trusted, and a board that is not trusted will not be updated.

Your next step

Take your current biggest project and give every open task one owner and one date this week, even on paper. When you are ready to run it on a shared board with reminders and reports, message WebsNP on WhatsApp at +977 9846280400 for a demo.

Get a demo and quote for Project Management Software

Tell us about your business and we will reply the same working day with a demo and a clear quote. No obligation.

Chat on WhatsApp

Or call / WhatsApp +977 9846280400

Your name Phone / WhatsApp Email (optional) Business / organisation What do you need?

Request demo

More guides on Project Management Software