Skip to updates
DevLaunch home

Plan client work, manage capacity, and collect clearer approvals.

One HyperTask update brings reusable project plans, workload and budgets, client proofing, smarter requests, bulk changes and bigger spreadsheet imports.

Running client projects means more than keeping a task list. HyperTask 1.4 brings the planning, feedback and approval steps into the same workspace, so your team can start repeatable work faster and keep clients involved as it moves forward. Everything below comes in one updated download.

  • Reuse your best project plans and create fresh projects for recurring client work.
  • See team capacity and billable time alongside project budgets.
  • Collect feedback on exact design revisions, agree extra work, and send clearer client updates.
See who has room for more work. Northstar Studio, the people and all figures are fictional examples shown in the real app.

Start the next project from a plan you already trust.

Save a project as your own reusable plan, including its tasks, checklist steps, custom fields and dependencies. When you use it again, choose the new start date and the task dates move with it. The new project has its own tasks and fresh checklists.

For monthly retainers or quarterly campaigns, schedule a fresh project from the saved plan. Each period gets a separate project, so this month’s work and history do not get mixed into last month’s. You can pause the schedule when a client pauses their retainer.

Save a plan, choose the next start date and schedule repeat client projects. Fictional campaign example.

See workload before assigning more work.

The workload view brings together open assignments across the active workspace projects you can access. Compare estimated hours with weekly capacity and see overdue task counts beside each person.

Set capacity in the current project’s planning view to reflect someone’s availability. Estimates cover upcoming, undated and overdue work, helping you spot a crowded week before adding another assignment. Large reports clearly say when only part of the workspace is shown.

Keep billable work in sight of the budget.

Set a project budget, default hourly rate and the percentage where you want a warning. Choose billable or nonbillable when logging time on a task; use a different rate for an entry when needed.

The budget view compares the value of logged billable time with the project budget and warns when it reaches your chosen threshold. Each time entry keeps its recorded rate, so a later default-rate change does not rewrite the past. These figures help you manage the work; they do not charge a client or create an invoice.

Review the budget and logged time together. All amounts and work shown are fictional examples.

Invite someone to one project.

Give a freelancer or client their own project guest login. Choose whether they can read, comment, or edit, then share the invitation link with the invited person. They must sign in with the email address on the invitation, and the invitation expires after seven days.

Project access does not make them a workspace member. You can remove their project access when the work ends. Guests see the whole invited project, including internal tasks and documents; use the curated client portal when a client should see only selected client-visible work.

Choose a permission for this project and share the invitation yourself. The email address shown is an example.

Preview what a date change will move.

The timeline shows dated tasks, milestones and their dependencies. Choose a task and a shift in days, then review the affected tasks before applying the move. Downstream tasks move by the same number of days.

You can undo the latest move while the affected tasks remain unchanged. If the project changes after your preview, HyperTask asks you to review a fresh preview before applying it.

Review the proposed task and milestone dates before applying the move. Fictional campaign project.

Change several tasks together, with a way back.

Use Bulk edit to select up to 100 tasks and change their assignee, status, priority, start date or deadline together. Choose only the fields you want to change, or deliberately clear dates.

The latest bulk edit can be undone while the affected tasks stay unchanged. If newer work would be overwritten, the undo stops. Bulk changes keep project automations and recurring-task creation paused; edit those tasks individually when you need their automatic actions to run.

Apply a shared change and undo it when needed. Fictional task names are shown.

Put feedback on the exact design or PDF.

Upload a design image or PDF as a proof. Place comments where the feedback belongs, including a specific PDF page, so the next person does not have to guess which part you mean.

When the design changes, add a new revision to the same proof. Each revision keeps its own comments and decision. Through a collaboration portal link, a client can approve the latest pending revision or request changes. A newer revision needs a fresh decision.

Pin feedback to a specific location and page. This is a fictional client design uploaded to the real proofing view.

Keep earlier sign-offs attached to their revision.

The revision picker lets you return to an earlier version and see its recorded decision, name, time and comments. An approval on revision one does not approve revision two.

Portal visitors enter the name recorded with their decision. This is a project review record rather than an identity-verified digital signature.

Review the earlier approval in its own revision history. Fictional client and design example.

Agree extra work before starting it.

Draft an extra-work estimate with the additional scope, estimated hours, price and currency. Review it, then explicitly share it in the client portal.

When the client approves, HyperTask creates a task for that agreed work. A declined estimate stays in the decision history and creates no task. Estimates do not take payment or automatically increase the project budget.

Keep the scope and estimate visible while waiting for the client’s decision. Fictional example.

Ask for the details that actually matter.

Build request forms with request types, required details and questions that appear only when relevant. A design request can ask where the design will be used, while a different request type gets its own questions.

Allow or require attachments and set a first-response deadline for incoming requests. Submitted files and the response deadline appear on the resulting task. The deadline records the expectation; it does not send a reply to the client for you.

The client sees the questions for their selected request type. The attached brief and request details are fictional examples.

Review a client update before sharing it.

Create a draft from completed client-visible work, outstanding approvals and next steps. Read it, add the context your client needs, and share it in the portal when it is ready.

Drafts stay with your team until you share them. You can edit a shared update or unshare it later. Nothing emails the client automatically.

Review the wording and choose when to share the update. The text shown is an example written for this fictional project.

Keep notifications useful.

Opening the notification bell no longer marks everything read. Activity is grouped by project and type, and you can mark individual items read or unread.

Choose assignment and deadline alerts, set your timezone, and use quiet hours to delay those new alerts until you are ready to see them. These are in-app notifications. Assignment alerts use a current member or guest’s matching name or email, so an imported assignee name alone does not invite someone.

Choose the alerts and quiet hours that fit your day. Example settings are shown.

Bring over a bigger spreadsheet and reuse the mapping.

Import up to 5,000 tasks from a CSV file up to 4 MB. Save your column mapping for the next file and map columns to custom fields as well as the usual task details.

Review the rows, choose a timezone and select which tasks to bring over. HyperTask saves batches of up to 100 and reports progress. If a later batch fails, earlier batches remain saved; retry the same settings to resume without duplicating those batches. The preview shows the first 200 rows, while selection counts cover the whole file.

Map a 250-task example spreadsheet, including its Channel field. All task names and file contents are fictional.

Undo an untouched import batch.

Open CSV → Import history and undo to move an untouched batch to recoverable trash. If someone has edited the tasks or added related work, HyperTask stops the undo to preserve it.

Imports made before this update keep their existing records but do not gain undo history retroactively. Project task export continues to provide a spreadsheet of the project’s active task details.

Review the saved batches from the example import and undo an untouched batch when needed.

Try it in your own workspace.

  1. Download the single HyperTask 1.4.0 source ZIP from your portal and have your installer follow its included upgrade guide for your existing installation.
  2. Open a project and choose Agency. Start with a saved plan, workload, or budget for a familiar client project.
  3. Use Timeline or Bulk edit for shared task changes, and Form for the questions and files you need from clients.
  4. Review a proof, extra-work estimate or client update before sharing it through the client portal. Use CSV for saved mappings, bigger imports and import history.