An agency resource stack should distinguish planned commitments, delivered tasks and recorded time. The same project may appear in all three views, but the records answer different questions. A planning allocation is not evidence that work occurred.

The component decision is whether an existing work platform can own these responsibilities together or whether specialist planning and time tools need defined interfaces. It is not a cost or profitability calculation.

Three component roles

ComponentRecord it should ownInterface question
Resource planningPlanned person, project and periodWhich project identifiers reach the planner?
Project executionDeliverable and task stateDoes a task change affect the plan or require review?
Time recordingPerson, project and recorded workWhich mapping determines where time belongs?

Name the authoritative employee and project records separately. Matching display names can help a person navigate, but it is not a complete rule for reconciling different records.

Candidate components with documented boundaries

Float documents projects as containers for planning context. It is a candidate resource-planning component where the agency needs a capacity view beyond its project board. Ask how the proposed integration handles project identifiers, people and changed allocations. This guide does not assert a native Float-to-Harvest synchronization.

Harvest documents Asana project and people imports and one-way project synchronization. Its Asana time-tracking guide describes choosing a Harvest project and task for tracked time. Those details make Asana plus Harvest a concrete execution-and-time route to evaluate.

Confirm current plan and participant permissions. The documented connection does not establish that every Asana task becomes an equivalent Harvest task or that recorded time updates a separate resource plan.

Two proportionate stack shapes

For a simple agency, the existing project platform plus a controlled time record may be sufficient. Capacity can remain a deliberately maintained planning view if the delivery owner can reconcile it.

A specialist planner becomes more relevant when competing project commitments are hard to see. Add it with a named plan owner, project mapping and update convention. Avoid treating three dashboards as a unified system merely because they display the same client name.

Evaluate a rescheduled project with time already recorded

Use a synthetic project with planned work and a few fictional time entries. Move the delivery dates. Inspect what changes in the planner and what remains in the historical time record.

Then rename the project and move a participant to another team. Ask the administrator to show whether identifiers and assignments remain intact. Record any manual mapping required instead of assuming that a connected integration propagates every change.

Finally, close the project while a planning allocation remains. Determine who removes or revises the allocation and who may still record late time. These are operational responsibilities even where a tool offers automation.

Keep the accounting handoff separate

Time may inform billing, but the ledger owns accounting under finance’s rules. Do not turn a recorded duration into an automatically approved invoice without a defined review owner.

See the agency CRM, delivery and accounting map for that wider boundary. Browse the Agency Operations hub for adjacent component decisions.