INDAYS
INDAYS(duration)
Turns a duration into a plain number of working days, such as a task's float as a number to round, chart or put in text. A day is a day of the task's own calendar, so 40 hours is 5 days on an 8-hour calendar and 4 on a 10-hour one; on a WBS row or the project, it's a day of the project's calendar.
Arguments
| Argument | What to give it |
|---|---|
| duration | A duration, like [Total float], [Remaining duration] or WORKDAYS(…). Blank gives blank. A plain number is refused. |
Examples
Formula=INDAYS([Total float])
The task's total float as a number of its own working days.
Formula=ROUND(INDAYS([Remaining duration]) / INDAYS([Duration]) * 100, 0)
The share of the task's duration still to go, as a whole percentage.
Formula=INDAYS(WORKDAYS(DATADATE(), [Finish date]))
The working days from the data date to the task's finish, as a number.
Formula on WBS rows=INDAYS(SUM(Tasks[Duration]))
On a WBS row: the duration of every task under the node added up, in days of the project's calendar.
Reach for something else when
| You want | Use |
|---|---|
| Hours, the same on every calendar | INHOURS |
| Calendar days between two dates | CALDAYS, already a number |
| The days shown as text with a format | TEXT: TEXT([Total float], "0.0") counts the same days |
Common questions
Why is INDAYS of a number refused?
A number has no calendar to count it in. The editor says INDAYS needs a duration. A number is already the count you want.
=INDAYS(5)
Why do two tasks with the same hours show different days?
Each counts days of its own calendar: 80 hours is 8 days on a 10-hour calendar and 10 on an 8-hour one. Compare hours with INHOURS when calendars differ. See durations.