1. LandOffer
  2. Blog
  3. All articles
  4. Float vs. Resource Guru: Choose Resource Planning by Availability, Roles, and Booking Rules

Productivity & Workflows

Float vs. Resource Guru: Choose Resource Planning by Availability, Roles, and Booking Rules

Compare a complete specialist-scheduling conflict and a people-and-equipment cost model. This review separates working availability, confirmed work, unassigned demand, booking permissions and current subscription assumptions.

10 min readLandOffer team

Choose between Float and Resource Guru by the scheduling decision your team must make: whose working hours and existing commitments leave room for the work, what remains unassigned or unconfirmed, and who may change a booking. Float is a candidate for people and role-based capacity planning; Resource Guru is especially relevant when people and non-human resources need explicit booking rules. Neither a green calendar nor a paid planning tool creates an available specialist or proves that scheduled work was completed.

This LandOffer.ai review checks official documentation and public pricing on October 27, 2026. Its two-project scheduling case and cost model are wholly fictional. Public browser observations cover price toggles and a billing FAQ only. No account, person, time off, booking, calendar, permission, timesheet, invitation or subscription was created or changed. Local checks verify the authored daily ledger, unresolved-hour count and subscription arithmetic, not either product's scheduling engine. The proposed evaluation environment is desktop Chrome; actual application behavior remains untested.

Two project leads hold different color proofs beside one artisan inspecting a print with a loupe

Separate working hours from remaining availability

Float's allocation guide describes planned time assigned to a project, optionally a phase or task. It supports hours and specific-time allocations, but specific times use the team's time zone. Its percentage allocation is a proportion of working time, not automatically the remaining capacity after other allocations and part-day time off. That distinction matters when two projects each ask for a share of the same person's week.

The same guide explains that scheduling beyond daily capacity produces an overtime indicator. A warning is information for a planner to act on; it is not a claim that every conflicting plan is blocked. Work on non-working days also needs deliberate treatment. Do not hide a staffing gap by treating a displayed overtime allocation as newly agreed working time.

Resource Guru's clash-management guide describes choices including a Waiting List, overtime and extending availability. Waiting List bookings are unconfirmed. Total Hours bookings work differently: effort that cannot fit becomes an unallocated waiting remainder. A planner must distinguish that remainder from time successfully assigned to someone.

Choose the booking behavior you intend to test. Does the team want to see an explicit unconfirmed demand queue? Who is allowed to extend availability, and what prior agreement is required? A product option to add overtime does not authorize changing a person's working arrangement. Write those booking rules before comparing calendar presentation.

Resolve two projects competing for one specialist

The invented studio ColorWorks has eight schedulable practitioners. Noor is its color-management specialist. Project owner Rafi wants ten hours for scanner-profile validation by Thursday; Mika wants eight hours for a print-proof preset study by Friday. Both need Noor's expertise. A shared role label is not evidence that another practitioner can perform either task independently.

The case covers Monday November 2 through Friday November 6, 2026, in the agreed America/Los_Angeles team time zone. Noor's normal hours are six each Monday through Thursday and four Friday: twenty-eight hours. Approved full-day time off removes Wednesday's six hours, leaving twenty-two. Existing operations work uses two hours on each remaining workday, or eight hours. Fourteen hours remain for the two project requests, which total eighteen. The shortfall is four hours before any new commitment is made.

Day Working capacity after approved time off Existing operations Requested project plan Completed revision
Monday, November 2 6 hours 2 hours A: 4 hours Keep A: 4; total scheduled 6
Tuesday, November 3 6 hours 2 hours A: 4 hours Keep A: 4; total scheduled 6
Wednesday, November 4 0 hours 0 hours No work should be assigned Preserve approved time off; no implied overtime
Thursday, November 5 6 hours 2 hours A: 2 and B: 4, totaling 8 with operations Keep A: 2 and reduce B to 2; total scheduled 6
Friday, November 6 4 hours 2 hours B: 4, totaling 6 with operations Reduce B to 2; total scheduled 4

The completed fictional decision record preserves A's ten hours and authorizes only four hours of B's initial investigation scope that week. Dana, the resource-planning owner in the case, records Mika's acceptance of that narrower scope. B's remaining four hours are unconfirmed demand for a proposed November 9 review, not a promised booking for that date. Its next-week availability has not been established.

This is a scope and ownership decision, not a statement that both original requests fit. Rafi must still verify A's required inputs; Mika’s four-hour scope is an annotated comparison of two existing presets against the team’s approved sample list; creating and validating a replacement preset is excluded. Noor's working hours and approved time off remain the constraints. The local ledger checks daily totals and the preserved four-hour gap; no scheduling tool or real colleague accepted this plan.

The studio also needs a scanner bench and a proofing station. The human-hours revision does not establish equipment availability. Dana's packet retains separate equipment bookings as an evaluation requirement rather than assuming that a free person automatically has the necessary room or device. Access to the schedule and authority to alter someone else's allocation are likewise separate requirements.

Keep tentative work visible without counting it as supply

Float's role supply-and-demand guide distinguishes scheduled demand for assigned and unassigned roles from actual team capacity. Unassigned roles have zero capacity. A planned color-management role can expose Noor's unmet demand; it does not create another qualified person or solve the four-hour shortage.

Resource Guru's placeholder guide similarly describes placeholders as a way to park work before assigning it to a real person. Crucially, placeholders have unlimited availability and do not use ordinary clash management. A placeholder that accepts eighteen hours is therefore not evidence that eighteen hours of real specialist time exist. Included placeholder allowances and extra-placeholder charges also depend on the plan.

Check the reporting state as well as the booking label. Resource Guru's heatmap guide says Waiting List and tentative bookings do not affect its displayed hours or utilization, while pending-approval bookings do. A quiet-looking heatmap may still sit alongside unresolved demand. Blackbelt and Master include that heatmap; it is not treated here as a Grasshopper entitlement.

Do not transfer those heatmap rules to every report. The Reports guide says Scheduled Time defaults to Booked Time but can include tentative, pending-approval and Waiting List time, changing the metrics. It also says standard reports assume scheduled hours were worked when no time is logged for a scheduled day. Inspect the definition and recorded inputs before treating a report as proof of completed work.

For ColorWorks, the acceptance requirement is that a permitted reviewer can find the confirmed twenty-two scheduled hours and the separately unconfirmed four hours without confusing one for the other. A report filter that hides the latter should not be used to declare the studio fully staffed. A view that presents all eighteen project hours as confirmed without an agreed capacity change fails this case’s requirements. No product report was generated in this review.

Review time off before changing the schedule

Float's time-off guide distinguishes requests, approval settings and permissions. It also explains that full-day time off over existing allocations can present a conflict confirmation that removes affected records; the behavior differs between single-day and multi-day allocations. Review that consequence before accepting a dialog, rather than assuming that adding leave merely changes a color.

In this fictional case, approved Wednesday time off is already part of the input ledger. No conflict dialog is opened, no allocation or logged record is deleted, and no actual absence reason is stored. An authorized evaluation should verify the intended workflow using permitted sample records and preserve the initial plan before making changes. The desired outcome is an accurate constraint and a clear revision history, not removing inconvenient work until the calendar appears clean.

Count the resources you will actually pay for

Current Float pricing showed Starter at $8.50 per scheduled person monthly, or $7 per month on annual billing; Pro showed $14 or $12 respectively. The page describes free guests for people who do not need to be scheduled. These are captured USD prices, not a checkout result. Pro adds time tracking and reporting capabilities; the page marks customized access and permissions as coming soon, so that wording is not treated as a delivered entitlement.

Float's People guide also distinguishes adding someone for scheduling from granting account access. Not logging in does not make a scheduled practitioner free. For the case, eight practitioners are scheduled; Dana and another planner only need permitted guest access. The Guests guide says guests can view or edit depending on their assigned rights, but cannot have work allocated to them. The case still needs a real permission-fit check before purchase.

The public Resource Guru pricing offer showed annual monthly equivalents of $5 per person and $2.50 per other resource for Grasshopper, $8/$4 for Blackbelt, and $12/$6 for Master. Monthly billing showed $6/$3, $9.60/$4.80 and $14.40/$7.20. The billing FAQ says people added to the account are counted whether they log in or not, along with non-human resources and placeholders beyond the free allowance. Blackbelt adds reports; Master adds Approval Workflow. Taxes and account-specific terms remain unverified.

A hand sorts wooden figures beside two planner medallions and miniature printing equipment

Complete a people-and-equipment cost model

ColorWorks' comparable roster is eight practitioners, two planning-only users, one scanner bench and one proofing station. Resource Guru's model therefore uses ten people and two non-human resources. Float's people-only estimate uses eight scheduled practitioners and two proposed unscheduled guests. It does not establish a complete equipment-management replacement cost.

Captured plan and authored scope Monthly-billing calculation Annual-billing calculation
Float Starter, eight scheduled people only 8 × $8.50 = $68 per month 8 × $7 × 12 = $672 per year
Float Pro, same people scope 8 × $14 = $112 per month 8 × $12 × 12 = $1,152 per year
Resource Guru Grasshopper, ten people plus two equipment resources 10 × $6 + 2 × $3 = $66 per month (10 × $5 + 2 × $2.50) × 12 = $660 per year
Resource Guru Blackbelt, same full roster with reports required 10 × $9.60 + 2 × $4.80 = $105.60 per month (10 × $8 + 2 × $4) × 12 = $1,056 per year
Resource Guru Master, same roster with Approval Workflow required 10 × $14.40 + 2 × $7.20 = $158.40 per month (10 × $12 + 2 × $6) × 12 = $1,584 per year

These are different feature scopes, not a universal cheapest-product ranking. Grasshopper's lower price does not supply Blackbelt reports or Master's approval workflow. Float's lower people-only estimate leaves equipment fit unresolved. The figures also exclude tax, negotiated terms, implementation and any separate equipment tool still needed for the Float scope. No savings, utilization improvement or delivery outcome is inferred from subscription arithmetic.

A useful sensitivity check is Dana becoming schedulable for project work. Float would then need a ninth scheduled person rather than treating her as a free guest: Starter's monthly estimate rises by $8.50. Resource Guru's ten-person roster already includes her, so that particular change does not add another person to its authored count. Adding a third equipment resource is a different change, with its own listed other-resource charge. Keep those changes separate.

Choose the unresolved booking behavior to evaluate

For ColorWorks, Resource Guru Blackbelt is a candidate when explicit equipment resources, clash handling and reports are the priority; Master needs a separate justification if booking approvals are required. Float is a candidate for role-based people planning, with permission and equipment-fit questions retained. Neither decision authorizes overtime, guarantees the right specialist or replaces checking the work's inputs and actual completion.

Use the LandOffer.ai workplace-tool library after retaining one concrete planning packet: normal hours, approved absence, existing work, two competing requests, the revised confirmed plan and a separately owned unresolved remainder. Have the authorized owner verify the required booking states and roster costs before committing. Keep planned hours, confirmed availability and later logged actuals distinct throughout that evaluation.

Sources and Further Reading