Human Resource Cost$86,400 · approved time
Menu
TEAMS
COMPANIES
INDUSTRIES
AI Assist
Pricing
{{ rndFrame }}
{{ marketingFrame }}
{{ smallBusinessFrame }}
{{ healthcareFrame }}
{{ miningFrame }}
{{ manufacturingFrame }}
{{ financeFrame }}
{{ constructionFrame }}
{{ softwareDevFrame }}
{{ nonprofitFrame }}
{{ resourceCostFrame }}
{{ automationFrame }}
{{ dashboardFrame }}
{{ costIntelFrame }}
{{ salesFrame }}
{{ projectManagementFrame }}
{{ consultingFrame }}
Command your projects andControl your costs. Live.
Cost Intelligence monitors budgets and actual costs. Earned Value analyses planned versus earned value, CPI and SPI. Resource Management tracks availability and utilisation live, while AI surfaces anomalies, allocation opportunities and the next signal that needs attention.
Project Health
{{ zHealth }}
Healthy
Budget Variance
{{ zVariance }}
Under Budget
CPI
{{ zCpi }}
On Track
SPI
{{ zSpi }}
On Track
◈
Material Cost{{ zMaterial }}
◍
Resource Utilization{{ zResource }}
⛨
AI Risk Alert
Unusual cost deviation detected in fabrication activities.
Cost Intelligence, The Differentiator.
Connect every project cost—human resources, materials, equipment and facilities—to the work it belongs to, then see actuals, forecast and earned value update while the project is still moving.
COST INTELLIGENCE · ATLAS LAUNCHEvery project cost, connected
HUMAN RESOURCE COST
PROJECT COST INPUTS
HR
MA
EQ
OF
Material Cost$41,700 · invoices
Equipment Cost$32,200 · utilisation
Office & Facility Cost$20,700 · allocation
LIVE ENGINECost
IntelligenceReconciling time
IntelligenceReconciling time
OUTPUTS & ANALYSIS
ACTUAL COST$181,00075% incurred
CPI1.07Cost efficient
FORECAST$231,000At completion
PROJECT HEALTH84Strong
LIVE INSIGHTApproved time is now reflected in actual cost.
Everything that is expected in project management, but very advanced.
While seamlessly managing daily execution fundamentals, nAct layers advanced intelligence on top to give the PMO absolute project visibility.
Tasks & milestonesPrototype review moved to Thursday
People & capacityJamie reaches 88% allocation
Time & actuals46 approved hours posted
Decisions & riskLaunch dependency accepted
ATLAS LAUNCHLive Project
Model{{ zaLink }}
Model{{ zaLink }}
Delivery health76 · Watch
Portfolio forecast11 of 14 on track
Cost performanceCPI 1.07 · SPI .98
AI insight1 action surfaced
The pivotal capabilities, screen by screen.
Move from planning and task management through resources, time, cost, earned value, project health and AI insight without rebuilding the project in separate systems.
Daily execution fundamentals. Advanced intelligence on top.
Plan and deliver the work, manage people and capacity, control time and cost, and keep every decision connected — all supercharged by our advanced AI agents.
Turn strategy into work
Structure the work, run iterative delivery, and keep dates visible from the task level through the portfolio.
AGENTS IN THIS WORKSPACE
TasksSprintOpsCalendarPortfolio
Plan against real availability
See who can take the work, where teams are stretched, and what resource decisions do to delivery and cost.
AGENTS IN THIS WORKSPACE
WorkloadTeamsSchedulingResource Cost
Know what is happening now
Bring time, progress, health, budget and earned value into the same operating view for delivery and leadership.
AGENTS IN THIS WORKSPACE
DashboardsTime TrackingCost IntelProject Health
Keep the why beside the what
Decisions, notes, discussions and AI stay grounded in the actual work instead of becoming another disconnected layer.
AGENTS IN THIS WORKSPACE
NotesDiscussionsDataSummary
Integrates with the tools you already use.
nAct plugs into your existing stack, so time, cost and communication stay in sync across the tools your team already runs on.
{{ i.name }}
Some of the early adopters of nAct
EARLY ADOPTER SPOTLIGHTTeams are bringing project execution and financial visibility into the same operating view.One platform for the work, its cost, and the decisions behind it.
Trusted by teams who used to run PM and finance separately.
{{ t.quote }}
Become an nAct early adopter.
Bring execution and executive teams into the same operating view—with live work, live cost and the context behind every project signal.
Features
One connected system for every way work moves.
Plan, deliver, staff, track, cost and understand the work from one project record—then let nAct connect every change across the system.
nAATLAS PLATFORM · LIVEConnected project workspace Live project
PROJECT DELIVERY
ON TRACKLaunch readiness
✓Prototype reviewPriya · approved todayDone
!Vendor approvalCost impact needs reviewToday
3Release validation6 linked tasks · 2 ownersThu
PLATFORM CAPABILITIES
IN DETAIL
The pivotal capabilities, screen by screen.
{{ f.headline }}
{{ f.desc }}
{{ f.desc2 }}
{{ b.text }}ADVANCED
{{ im.el }}
Become an nAct early adopter.
Bring execution, intelligence, and executive visibility into one connected workspace.
Sign up for early access
Everything a timesheet should do — plus the part it usually skips
Logging time is easy. Getting it approved without friction is the hard part.
⏱
Log time in seconds
Search a task, drop in billable and non-billable hours, add a note. Fill in a single day or a whole week at once, then submit whenever you're ready.
✓
Approve without the noise
See exactly what's waiting on you, filtered by teammate, project, or date. One click approves; nothing slips through unless you say so.
EMDesign review4.5 hours · TodayAPPROVE
🔒
Guardrails, not gotchas
A 24-hour daily cap catches mistakes before they're ever submitted. Once an entry is approved, it locks, the record stays clean.
DAILY TOTAL8.5 / 24h
The details that make time tracking useful
{{ daily.name }}
{{ daily.desc }}
TASK NOTE
ATTACHEDDesign review · Client Portal
Updated the responsive states and documented the approver feedback before submitting 3.5 hours.
# design-review3.5hBillable
TODAY
of 8h planned3.5h
Billable3.0h
Non-billable0.5h
ChronologicalBy taskBy memberProject
TodayClient Portal · UI review3.5h
YesterdayAPI rollout · QA5.0h
TASK TOTAL24.5h
RESOURCE31.0h
ESTIMATE40h
77% of estimate logged
1Elena submitted 4.5h9:12
2David proposed 3.5h9:18
✓Approved at 3.5h · history retained
LOGGED36.5h
BILLABLE32h
PENDING4.5h
UTILIZATION87%
ONE RECORD · TWO USEFUL PERSPECTIVES
Built for whoever's looking at it.
The person logging time and the person reviewing it need different answers. nAct gives each of them a purpose-built view of the same record.
WEEK LOGGED36.5hof 40h
91% complete
3.5h remainingNavigation refreshDesign review · 9:00–12:303.5h
Platform coreAPI mapping · 1:00–4:303.5h
Navigation refreshPrototype pass · 8:30–1:004.5h
Mobile QARegression tests · draft2.0h
TEAM MEMBERElena MorrisPROJECTAll projectsPERIODSep 12–16
SUBMITTED36.5hBILLABLE32.0hNEEDS REVIEW4.5h
Navigation refreshElena · Prototype pass4.5hReview
Platform coreElena · API mapping3.5hReady
Mobile QAElena · Regression tests2.0hReview
MY LOGS ANSWERSWhat did I log—and what can I still change?APPROVALS ANSWERSWhat needs my decision—and why?
Fewer chases, cleaner timesheets
{{ q.text }}
{{ q.initials }}
{{ q.name }}
{{ q.role }}
CONTROL WITHOUT THE CHASE
Rules that protect the record, not slow you down.
The guardrails follow an entry from the moment it is typed to the moment it becomes an approved record.
The 24-hour cap checks the day while Elena types.
EDITABLEElena can submit or revise only her own time.
OWNER CONTROLDavid proposes 3.5h; the original 4.5h remains visible.
TRACE KEPTBoth people can still read the full path to 3.5h.
RECORD LOCKEDPrototype review · billable
4.5hReason: meeting ended at 12:30
−1.0hOriginal and proposed values retained
✓Five kinds of entry, one cell
A day in your working life isn't just meetings. Calendar treats every kind of commitment as a first-class entry, so the cell you look at is the whole truth.
A five-day task looks like five days
Tasks aren't pinned to a single square. They render as bars that span their real start and end dates, carrying the estimate with them, so a 24-hour refactor across a week reads as exactly that, not as a mystery dot on Monday.
- ✓Bars span the task's actual date range across the week
- ✓The estimate rides on the bar, so you see commitment and duration together
- ✓Days without an estimate show an add-estimate affordance rather than a blank
- ✓Hover any task to see everyone else assigned to it and their own estimates
Need to reshape it? Open Hours split and move estimated hours between days in a grid, totals update as you type.
8–12 Jun
MON
8
TUE
9
WED
10
THU
11
FRI
12
WEEK
TOTAL
Auth service refactor
Daily allocation
Client reporting dashboard
Daily allocation
Release validation
Daily allocation
Edit any daily value to see that task's weekly total update immediately.
SYNCING
G
Google Calendar
1 event
09:30 · Design review
O
Outlook
1 event
14:00 · Client call
nAct · WednesdayUNIFIED
09:30 · Design review14:00 · Client call
Your other calendars, already in this one
Nobody abandons the calendar their whole company runs on. So instead of asking you to migrate, Calendar connects to Google and Microsoft and pulls their events and tasks in alongside your work, one connection, then it just stays current.
- ✓Connect Google Calendar, Microsoft/Outlook, or both at once
- ✓External events and to-dos appear on the day they belong to
- ✓Completed synced tasks show struck through, matching the source app
- ✓The connected account's address is shown in the header, so you always know which inbox you're seeing
🔌
Disconnect whenever you like, nothing internal depends on the link, and your tasks, leave and holidays stay exactly as they were.
Overloaded days flag themselves
Calendar knows your working hours per day. When the estimates you've committed on a given day add up past that, the cell marks itself, while there's still time to move something, rather than at the end of the week when there isn't.
- ✓Every day compares committed estimates against your working-day length
- ✓The overloaded day is highlighted directly in the grid, with the total shown
- ✓Weekends come from your own configuration, not a hardcoded Sat/Sun
- ✓Turn on Highlight week offs when you want non-working days to stand out
In the grid above, Wed 24 Jun is flagged at 11h, three hours past an eight-hour day, visible two days ahead of time.
Committed vs capacity · week of 22 Jun
8h/day
Mon
Tue
Wed
Thu
Fri
Wed is 3h past an 8h day, flagged before the week starts
Rebalanced · every day now inside capacity
the marker is your 8h working day
Three views, because three questions
"What am I doing right now", "what does my working week look like", and "how does the month shape up" are different questions. Switch between them without losing your filters.
The details you'd otherwise have to remember
Four kinds of membership.
Membership is not just a title. Move from the outer edge toward the team center to see how each role opens a more complete view of projects, documents, people, and settings.
TEAMProduct
Engineering
Engineering
01 · OWNER
The whole team, including its keys.
Owners see every project and document, manage people and settings, and can transfer ownership.
Product EngineeringOwner view
6PROJECTS42DOCUMENTS5PEOPLE
Navigation refreshOpenPlatform briefPrivateTeam settingsManage
02 · ADMIN
Everything needed to run the team.
Admins manage projects, documents, members, and settings. The owner’s transfer key stays protected.
Product EngineeringAdmin view
6PROJECTS42DOCUMENTS5PEOPLE
Navigation refreshOpenPlatform briefEditMember accessManage
03 · MEMBER
The work, without the administration.
Members see the projects they join, their assigned tasks, and the documents shared with the team.
My team workMember view
3PROJECTS18DOCUMENTS7MY TASKS
Navigation refreshAssignedLaunch checklistEditMember accessHidden
04 · EXTERNAL
Only the doorway you intentionally open.
External collaborators see one invited project and its shared documents—not the team behind them.
Client portalExternal view
1SHARED PROJECT2SHARED DOCS0TEAM PEOPLE
Navigation refreshCommentReview briefViewProduct EngineeringHidden
Who's here, what they're carrying, what's slipping.
The Overview brings headcount, projects, task load, and deadlines together—then makes the person who needs attention impossible to miss.
One team header. Three useful views.
The team stays fixed while each tab answers a genuinely different question: overall health, who has room, and when the work happens.
Four projects, one useful team pulse.
See delivery progress and team health together before deciding where to look next.
82TEAM HEALTH
HealthyNavigation refresh12 of 16 milestones complete
76%
On trackPlatform core7 of 13 milestones complete
54%
At riskMobile QA5 of 12 milestones complete
42%
On trackWORKLOAD · SEP 12–16
David needs relief on Wednesday.
11h of 8hEMElena6h7h8h6h4h
DKDavid8h10h11h8h7h
PSPriya4h6h3h7h8h
CALENDAR · TEAM SCHEDULE
September 12–18
Work Leave
Design system audit Elena + DavidMobile QA Product EngineeringAPI handoff PriyaLaunch reviewJordan · Leave
Three states, so nothing has to be deleted.
Pause a squad or archive a finished team without erasing its members, history, or delivered work.
The details that keep a team’s boundary real.
The team can be discoverable without exposing its work. One clear gate separates what the organization may see from what members can open.
Visible footprint
Anyone in the organization can find the team and understand where it contributes.
PEProduct Engineering5 members · 4 projectsView profile
Project namesVisibleTasks and filesLocked
◆OWNER KEYTransferable
⌁PERMISSION GATEMembership required
AREXTERNAL LANESeparate invite + removalProtected workspace
Members see the live work their role and permissions allow.
▦68 tasksOwners + due dates▤12 notesDecisions + context◌7 discussionsTeam conversation
Become an nAct early adopter.
Set the boundary once, then let every view use the same people, permissions, and history.
Sign up for early accessThe conversation stays beside the work
A decision starts on the task, reaches the right team, and appears in notifications without being copied into another app.
One workspace. Two conversation types.
Quick coordination and lasting decisions sit side by side. The shared record connects them without making anyone chase context.
nActRenovation Design workspaceONE SHARED RECORD
Approve the procurement revision
DECISION SAVED WITH TASK #184Use Fixture Schedule v4 for procurement
# vendor-coordination
LINKED FROM TASK #184Use Fixture Schedule v4 for procurement
Task discussion keeps the reason with the work.DECISION BRIDGELive channel keeps the team moving.
One rail. Every conversation.
Projects, channels, groups, and direct messages share one recency-ordered view—so the conversation that needs attention naturally comes forward.
LIVE CONVERSATION RAIL● Updating now
#
procurement
5
#
site-updates
1
RD
Renovation Design
PROJECT
PS
Priya Shah
Newest activity rises automatically
Start the conversation before the first comment
Every top-level task already has a place in Discussions. Open a quiet task, write the first message, and its conversation becomes part of the project record.
Small details that keep work moving
Mentions, files, unread state, delivery status, and ownership stay visible on the message instead of hiding in settings.
In six weeks,
someone will ask why.
Keep the decision, its owner, and the work it created on the same page—not scattered across chat threads, inboxes, and someone’s laptop.
NSPRINT 42
Design System / NavigationSaved
SPRINT 42 KICKOFF
Tab bar rewrite
Ship the navigation rewrite this sprint. Hold search until the research review is complete.
#decisions#mobile#sprint-42
✓Confirm the feature flagAK · Tue
✓Link the two blocker tasksPR · Wed
✓Send the client summaryMT · Thu
2 projects4 linked tasks6 comments
A document, not a comment field.
Use the notes tab to see how one page moves from an unstructured thought to a decision the whole project can act on.
SPRINT DECISION · SEPT 14
Navigation rewrite
The mobile tab bar will ship behind the existing navigation flag. Search remains unchanged until the research review.
Why now
Support requests show the current navigation costs people time on every project visit. The rewrite removes one level without changing permissions.
PRESS / TO BUILD THE PAGE
Give the decision a shape
OptionOwnerStatusBottom tabsDavidApprovedSide railElenaHeld
THE DECISION AND THE WORK AGREE
Everything points back here
Link the note to the project, the tasks it created, and the next review.
◆Navigation refreshProject · Product EngineeringOPEN
✓Build responsive tab barTask · Priya ShahIN PROGRESS
↗Research reviewFollow-up · September 21SCHEDULED
TWO PEOPLE, ONE CURRENT PAGE
Review without version three-final-final
The mobile tab bar will ship behind the existing navigation flag.ELENA
Search remains unchanged until the research review.DAVID
Every note stays tied to the work it created.
The reasoning, the ticket, and the follow-up all point at one another. No one has to reconstruct the chain six weeks later.
01DECISION NOTENavigation rewriteWhy the work exists
02PROJECTNavigation refreshWhere it belongs
03LINKED TASKS4 action itemsWho owns the work
04FOLLOW-UPResearch reviewWhat happens next
The argument belongs next to the answer.
Anchor the question to an exact sentence, resolve it where everyone can see the reasoning, and carry the result into the work without rewriting it.
01ANCHOR THE QUESTION02RESOLVE IT TOGETHER03CREATE THE NEXT STEP
RESEARCH REVIEW
EMElena Morris10:28 AM · Product PSPriya Shah10:41 AM · Engineering
What changes after usability testing
Move primary navigation to the lower rail on screens below 760px. Keep project-level actions in the top bar.
The new rail must preserve keyboard order and expose unread work without adding another badge system.2 COMMENTS ON THIS SENTENCE
Can we keep unread work visible without bringing the numeric badge back?
Yes. The dot-only prototype preserves the state and keeps keyboard order intact.
✓ RESOLVED INTO THE DOCUMENT
The page changes with the work.
A note does not become six separate tools. It carries one decision forward—from the first planning conversation to the work and update that follow.
Follow one decision from idea to delivery.
Live thread · 4 connected stagesPlanning records the decision.
Ship the lower navigation rail behind the existing feature flag.
The original choice and its reason stay at the top of the thread.
SPRINT PLANNING · SEP 12The decision becomes a rule.
REQ-04Keyboard focus follows visual order below 760px.REQUIRED
Requirements make “done” specific without leaving the page.
1 ACCEPTANCE RULE ADDEDFeedback changes the answer.
“I still miss unread updates.”
Unread indicatorAPPROVED
The question and its resolution remain readable together.
CLIENT REVIEW → SCOPE DECISIONThe answer becomes visible work.
✓Build unread indicatorTASK-142 · DAVID68%
The linked task and executive update point back to the same decision.
TASK + STATUS UPDATEIt is already in your sidebar.
Notes inherits the people, projects, and permissions already inside nAct. Open the workspace you know and begin with one useful page.
Become an nAct early adopter.
Give every decision a page, an owner, and a next step.
Sign up for early accessOne task. Every useful view.
Build the work once, then meet it as a list, a board, or a timeline. Owners, dates, estimates, and progress stay attached wherever the project takes you.
Wire the payment callback
Ship the new callback behind a feature flag, beginning with a 10% rollout and a monitored retry path.
OWNERPNPriya NairDUESep 9ESTIMATE6 hoursPRIORITYHigh
✓Map callback response✓Add signature verificationMonitor retry failures
DEPENDENCYVendor sandbox credentialsWaiting on Rahul · due today
THE SAME TASK, ALREADY PLACEDNo rebuilding between views
LISTPayment callbackPN · Sep 9
BOARDATL-218Payment callbackPN
TIMELINESep 7–9 · 6h
A working project in four clear moves.
Create the structure, add the work, give it owners, and begin. No implementation project required.
01Create the project
Name the outcome, owner, and working dates.
02Group the work
Use phases, workstreams, or deliverables.
03Add the tasks
Bring in descriptions, estimates, and dependencies.
04Assign and go
Owners see the same work in the view they need.
Change the view. Never change the truth.
One task record projects into four genuinely different working surfaces. Update the owner, estimate, date, or status once—and every view redraws around the same facts.
Live record · ATL-218 · synced just nowOWNERPNPriya NairESTIMATE6 hoursDUESep 9PROJECTAtlas Payments
TASKOWNERDUESTATUS
Verify signature handlingRetry-path coverageRVReview
Wire the payment callback10% rollout firstPNIn progress
Invoice template rebuildMulti-currency layoutsESTo do
Due Sep 9
PNTASK789101112
Signature handlingRV · 4h
Payment callbackPN · 6h · Sep 9
Invoice templateES · 8h
MON 7TUE 8WED 9THU 10FRI 11
Design syncSignature reviewATL-218Payment callbackPriya · 6hRelease check
No schedule collisionPriya has 2 hours remaining on Sep 9.SAFE
The work stays put. The answer changes.
Move from delivery detail to project health without rebuilding the story in another tool. Every answer below is drawn from the same Atlas Payments tasks.
APLIVE PROJECT LENSAtlas Payments · Checkout BillingSame 7 tasks
WEEKLY ANSWER
Seven tasks moved forward.
+18%MONResearch closed2 tasks completed
TUECallback startedPriya · 6h estimate
WEDTokens in reviewDan · due Sep 9
THUBeta scheduled500 merchants · Jun 10
PROJECT TREND
Completion is rising on plan.
68%75% TARGET
CAPACITY ANSWER
Two people need relief.
2PNPriya NairPayment callback96%RVRahul VermaVendor cutover91%ESElena S.Invoice templates72%TNTara N.Merchant beta54%
PLAN EXPOSURE
Three open items could alter delivery.
3RVendor sandbox unavailableHigh likelihood · high impactRahulEscalate today
DPayment callback contractExternal approval requiredPriyaDue Sep 9
A500 merchants join betaRecruitment remains on paceTaraWatch weekly
Become an nAct early adopter.
Load real tasks, people, and dates—then judge every view against the way your team already works.
Sign up for early accessPlan it. Run it. Close it honestly.
The agile workspace appears when a project needs it. Commit the sprint, record the day, own the blockers, and carry unfinished points forward with the reason still attached.
COMMITTED34pointsCOMPLETED2161.8%OPEN13pointsBLOCKERS1owned
Actual Ideal
3 points above idealThe vendor blocker explains the gap.13 pts remain
The board is the middle. The edges make it honest.
nAct makes the decision points visible before commitment and again before anything closes.
CHECKPOINT 01 · BEFORE COMMITMENT
Size and order the work before it enters the sprint.
Story points are attached in the backlog, so the sprint commits to effort rather than an arbitrary task count.
34 points readyORDERED BACKLOG
1ATL/218 · HIGH PRIORITYWire the payment callback8 pts
2ATL/224 · MEDIUMRate card import spec5 pts
3ATL/196 · DEPENDENCYVendor API cutover18 pts
CHECKPOINT 02 · THE START GATE
Unresolved work appears before the new promise.
The team can still start, but nAct requires the previous sprint’s open work to be seen and acknowledged first.
1 open item foundQA SPRINT 141 item still openATL/196 · 5 pts completeNeeds a decision
!START CHECKCarry over or close?Acknowledgement is recorded.
QA SPRINT 1534 pts ready10 working daysCommit after review →
CHECKPOINT 03 · THE WORKING DAYS
The sprint gains a record one day at a time.
Outcomes, confidence, capacity, and blockers land beside the work instead of disappearing after standup.
18 updates recordedDAY 7 OF 10Tuesday · QA Sprint 153 days left
M4updatesT3updatesW4updatesT3updatesF4updatesM—nextT—next
CHECKPOINT 04 · BEFORE CLOSURE
Closing begins with what is still unfinished.
Status totals remain visible before completion, so open work cannot quietly disappear when the sprint closes.
6 tasks still openCLOSE SPRINT INSPECTION
12tasks reviewedQA Sprint 15
CHECKPOINT 05 · AFTER THE DECISION
Unfinished points move with their explanation.
Destination, reason, and note stay attached to the task in both sprints, protecting the velocity record.
13 pts carrying overPLANNED34−COMPLETED21=CARRY OVER13
DESTINATIONQA Sprint 16REASON · REQUIREDVendor sandbox unavailableNOTEResume after credentials arrive
Outcomes in the open. Blockers with owners.
Daily Scrum captures what finished, what comes next, today’s capacity, confidence, and the blocker—without turning the morning into a status-performance ritual.
Tuesday’s team record · updating live4 / 5CONFIDENCE
CAPACITY8 hoursESTIMATE6 hours
2h room remainsTwo of three subtasks are closed.
Target handoff · 16:00 today
UPDATE RESOLVEDNo blocker
LINKED WORKATL/218 · Payment callback
Ready to move →3 points · QA handoff at 16:00
2 / 5CONFIDENCE
CAPACITY8 hoursESTIMATE2 hours
6h cannot be plannedWork cannot continue in staging.
Confidence drops and the issue enters Blocker Management.
ACTION REQUIREDSLA breached
1REPORTED BYRahul Verma2ACTION OWNERDaniel Ortiz3SLA DUEToday · 14:00
Escalation recorded →Turn the retrospective into a decision.
The sprint leaves evidence behind. nAct keeps the lesson beside that evidence, then carries the chosen change into the next commitment.
SPRINT 15 · EVIDENCE
01WHAT WORKEDPairing cut callback review below one day.4 team votes
02WHAT FAILEDWe committed while a known dependency was still open.5 team votes
03WHAT THE SPRINT PROVEDThirteen unfinished points need to move forward.34 planned · 21 completed
DECISION RECORDEDNEXT SPRINT GUARDRAIL26points maximum
Cap commitment until the vendor path is proven.
APPLIES TOQA Sprint 16REVIEW WHENVendor sandbox passes
Every planner sees the rule before the next sprint starts.
Unfinished points move with their explanation.
Close the sprint by reconciling all 34 points. Completed work becomes part of the record; unfinished work becomes a named manifest for the next sprint.
34TOTAL POINTS
21DONE
13UNFINISHED
61.8% completedLocks into Sprint 1538.2% unfinishedRequires a destination
Velocity reports the outcome exactly as it happened. Closing the sprint cannot erase the orange portion.
Work leaving Sprint 15
02 TASKSATL-218Payment callbackIn progress · 1 of 3 subtasks
ATL-224Vendor API cutoverBlocked · sandbox unavailable
- DESTINATION
- QA Sprint 16
- REASON · REQUIRED
- Vendor sandbox unavailable
- NEXT ACTION
- Resume after credentials arrive
Become an nAct early adopter.
Bring a backlog and a two-week window. Plan it, run the standup, and close with the carryover still accountable.
Sign up for early accessSee who’s free
before the next task lands.
One workload view shows the room left in every person’s week—with individual schedules, holidays, and approved leave already accounted for.
PERSONMONTUEWEDTHUFRITOTAL
EMElenaDesigner
6h2h free8hfull4h4h free7h1h free3h5h free28hDKDavidEngineer
8hfull6h2h free11h3h over8hfull4h4h free37hPSPriyaEngineer
5h3h free4h4h free—leave6h2h free8hfull23hAvailableFully bookedOver capacity1 person needs attention
Every cell shows how much room is left.
The colors stay consistent at team, project, and portfolio level. Read the week before reading every number.
NOT WORKINGROOM TO ASSIGNAT CAPACITYACTION NEEDED
Leave0 available hoursCalendar excluded
Available4h of 8h assigned4 hours remain
Fully booked8h of 8h assignedNo room remains
Over capacity11h of 8h assigned3 hours to move
Move the assignment.
Watch each day recover.
Wednesday shows the exact three-hour conflict and Friday shows the opening. Move the assignment between those two visible slots and both daily totals recalculate in place.
Wednesday returns to 8hFriday still keeps 1h of room
DAVID KIM · DAILY CAPACITYWednesday overloadedQA handoff selectedSchedule balanced
At capacity
Scheduled work8h
2h available
Scheduled work6h
3h overBalanced
Scheduled work11h8h
At capacity
Scheduled work8h
4h available1h available
Scheduled work4h7h
THE WORK STAYS VISIBLE
WED11 → 8h+FRI4 → 7h
37h total · unchangedLet the roster narrow itself to the people who matter.
On a portfolio of fifty people, status is the fastest route to the rows that need a decision.
SHOW6 people shown
PERSONTHIS WEEKCAPACITYSTATUS
DKDavid KimProduct Engineering
37 / 40hOverloaded WedEMElena MorrisDesign
28 / 40h12h availablePSPriya ShahEngineering
23 / 32hLeave WedJLJordan LeePlatform
42 / 40h2h over weekMCMaya ChenResearch
21 / 40h19h availableOBOwen BrooksDelivery
40 / 40hFully bookedCapacity is math, not a status.
nAct starts with each person’s working schedule, then subtracts approved time away and assigned task estimates. What remains is the time they can actually take on.
EMElena Morris5 working days × 8 hours
Weekly schedule40h5 × 8h
Approved leave8h1 day away
Assigned work23hTask estimates
Available capacity9hReady to assign
OSOmar Said5 working days × 6 hours
Weekly schedule30h5 × 6h
Approved leave6h1 day away
Assigned work18hTask estimates
Available capacity6hReady to assign
Recalculates as work changes
Available capacity = scheduled hours − approved leave − assigned work. Non-working days are excluded unless they are part of that person’s schedule.
Start with the team. Zoom out when the decision gets bigger.
Capacity keeps the same colors and rules while the view expands from five people to the entire portfolio.
TEAMProduct
Engineering5 people
Engineering5 people
01 · CLOSEST VIEW
Product Engineering
See every commitment currently assigned to the people inside one team.
32 hours availablePROJECTNavigation
refresh4 teams
refresh4 teams
02 · SHARED WORK
Navigation refresh
Isolate one project and see the contribution it requires across multiple teams.
3 people at riskPORTFOLIOProduct
portfolio8 projects
portfolio8 projects
03 · WIDEST VIEW
Product portfolio
Step back far enough to balance investment and risk across every active project.
4 overloaded teamsFrom “who is underwater?” to a balanced week.
Forty hours is the surface. When work pushes someone below it, nAct exposes the assignment and shows where it can safely move.
40H CAPACITY
See exactly what is filling the week.
A 23-hour workload is not a mystery percentage. nAct shows every task, estimate, project, and date included in that number.
EMPERSONElena MorrisProduct Engineering
ASSIGNED THIS WEEK23hacross 3 tasks
23h assignedof 40h scheduled
Navigation refreshInteraction statesDesign taskMon–TueSep 7–88h
Billing APIQA passReview taskWednesdaySep 96h
Client portalComponent buildEngineering taskThu–FriSep 10–119h
TASK ESTIMATES8h + 6h + 9h=VERIFIED TOTAL23h assigned
Only accessible work is shown
This verified 23h becomes the “assigned work” input above: 40h scheduled − 8h leave − 23h assigned = 9h available.
Become an nAct early adopter.
See capacity clearly, move work quickly, and keep every week realistic.
Sign up for early access
nAct unites the execution and executive teams.
SOLUTIONS
@ 2025 nAct. All rights reserved.
Plans are taking shape.Be first to see them.
Pricing will be announced at launch. Early access members see the plans before anyone else.
Freemium
For individuals and small teams trying nAct on real projects.
Freeforever
- Tasks and calendar
- Time tracking
Small teams
For teams getting projects, time and cost into one place.
$00per user / month At launch
- Everything in Freemium
- Baseline budget building
Growing teams
For delivery and finance working from the same live numbers.
$00per user / month At launch
- Everything in Small teams
- Cost intelligence and earned value
- AI Assist agents
Organisations
For portfolios, many teams and custom rollout needs.
Custom At launch
- Everything in Growing teams
- Portfolio and resource cost views
Plan names and features shown are placeholders until launch.
Questions? We've got answers.
The details while we get ready for launch.
What will nAct pricing include?
Final plans have not been announced yet. nAct pricing will be structured around a connected workspace for project delivery, resources, costs, and decisions. Early-access participants will receive plan details as they become available.
Who is nAct designed for?
nAct is designed for teams that need to manage project work, people, budgets, and decisions without separating delivery from cost visibility. It can support focused teams as well as organizations coordinating work across multiple functions.
Will nAct work with the tools my team already uses?
nAct is designed to bring connected project context around the tools and workflows your team already relies on. Specific integrations and availability will be confirmed as launch plans are finalized.
What happens after I request early access?
Our team will review your request and follow up about availability, your current workflow, and the best way to introduce you to the platform. You can also request a personalized demo while nAct prepares for launch.
Can we link the research session here before this goes to the client?