Every function Spreadsheet offers: what each argument means, a worked example, and a real estate reason to reach for it. Click Help in the toolbar for the short version inside the app, or type = and a function's first few letters for autocomplete.
Giraffe functions
These read live numbers out of your project. filter is always optional text narrowing which geometries count. source is always optional too: "bakedSections" (the default), "rawSections" or "usages", telling the function which of the project's three data tables to read from.
Function | Parts | Example | Why |
|
|
| the total gross floor area for one usage, feeding straight into a GFA line on a pro forma. |
| identical to |
| total unit count across the whole scheme, for a unit-count summary line. |
|
|
| a blended sale rate across a mixed building, the number a valuer would actually quote rather than a plain average that treats a penthouse and a studio as equally important. |
|
|
| average building height in storeys across a masterplan, for a massing summary. |
|
|
| the tallest building on site, for a height-limit compliance check; |
| no field argument. It always reads ground coverage, one level per geometry. |
| ground floor coverage for a site-coverage or setback compliance check. |
| no arguments. |
| the site area a plot ratio (FAR) divides by. It is not the same as footprint. |
| no arguments. Returns |
| label a schedule's header correctly whichever unit system the project runs in, so a report never misstates its own units. |
| identical to |
| same as |
| no field argument, only |
| how many residential buildings exist, for a building-count line in a summary table. |
|
|
| how many distinct usages a masterplan has, a quick mixed-use diversity check. |
|
|
| a schedule row that re-filters itself to whatever usage is typed in a cell, without writing the quote-and- |
|
|
| true construction cost across a mixed scheme where the rate per m² actually differs by building. |
| same as |
| average floorplate size per level, a genuine per-building average rather than one computed from two totals. |
| same as |
| the smallest floorplate per level across the scheme, useful for spotting an inefficient tower before it reaches a report. |
|
|
| the per-geometry loop written out down a column, for when a total is not enough and the underlying working has to be visible in a report. |
|
|
| the two-field shorthand for exactly the case |
|
|
| fill down beside |
|
|
| fill down to build the row labels of a usage-by-usage schedule automatically, rather than typing each usage name by hand. |
|
|
| fill down to see every field name a project actually carries, when building a new schedule against an unfamiliar project. |
|
|
| confirm how Spreadsheet is aggregating a field before trusting a total built on it. |
|
|
| pull a single specific value, such as one usage's floor-to-floor height, into an assumption cell. |
Math functions
Function | Parts | Example | Why |
| one or more numbers or ranges. |
| add a column of hand-typed cost assumptions, or average a column of comparable sale prices you pasted in from a market report. |
| one or more numbers or ranges. |
| the highest bid in a column of offers, or the earliest handover date in a construction programme. |
| one or more values or ranges. |
| how many rows of a hand-entered unit schedule have been filled in so far. |
|
|
| total the area column only where a hand-typed usage column reads "Residential": the ordinary-spreadsheet equivalent of a filtered |
| repeating |
| total area for residential buildings that are also over four storeys, when both columns were typed in rather than read live from the project. |
| one or more numbers or ranges. |
| the median sale price in a column of comparable transactions, less skewed by one outlier sale than the average would be. |
|
|
| the ordinary-spreadsheet version of |
|
|
| round a car-parking-ratio calculation up to a whole space, since a planning condition never accepts half a space. |
|
|
| a variance figure that should read the same whether a budget line is over or under, without an extra |
Logic functions
Function | Parts | Example | Why |
|
|
| flag a schedule row automatically once a live count crosses a planning threshold. |
| repeating |
| classify a building into a height band for a summary table, without nesting several |
|
|
| show a plain note instead of a formula error on a schedule row for a usage the project does not have yet. |
|
|
| look up a car-parking ratio or a cost loading by usage name without a separate lookup table. |
|
|
| map a draw-schedule date to the financial quarter it falls in. |
| one or more true/false conditions. |
| combine two planning or cost conditions into one flag rather than nesting |
Lookup functions
Function | Parts | Example | Why |
|
|
| look a usage's parking ratio up from a separate assumptions table kept on another sheet. |
|
|
| the same lookup as |
| an optional cell reference; the current cell if left out. |
| drive the index argument of |
Text functions
Function | Parts | Example | Why |
|
|
| build a readable label, such as a level name, out of live project numbers. |
|
|
| pull a lot or parcel code's project prefix out of a longer reference number pasted from a title document. |
|
|
| strip stray spaces from an address or usage name pasted in from an external spreadsheet, so it matches the project's own spelling exactly. |
|
|
| normalise a usage name typed inconsistently by different people before comparing it against another sheet. |
Date functions
Dates are Excel serials, so every one of these reads a date cell directly.
Function | Parts | Example | Why |
|
|
| set a fixed valuation or programme start date that stays constant even as |
|
|
| group a cashflow's monthly rows into financial years for a summary total. |
|
|
| build a monthly cashflow's date column so each row lands on the actual end of that calendar month, not a fixed number of days later. |
|
|
| a construction programme's duration in days, straight from a contract date and a projected handover date. |
|
|
| the fraction of a year a construction loan is outstanding, to prorate an annual interest rate. |
Finance functions
These come from a finance library rather than the core formula engine. Their results are tested against Excel's own calculations for the same inputs, so a formula like NPV or IRR returns the same number Excel would. Money going out is always a negative number and money coming in a positive one, the same convention Excel uses.
Function | Parts | Example | Why |
|
|
| the present value of a development's future cash flows, discounted at a hurdle rate, feeding straight into a residual land value. |
|
|
| the return a development is expected to generate, the single number most feasibility studies lead with. |
| as |
| a return calculation for a draw schedule whose payments do not land on tidy month boundaries. |
|
|
| the monthly repayment on a construction or acquisition loan. |
| same as |
| split a loan payment into interest and principal for a single month, to build an amortisation schedule. |
| as |
| what a savings or reserve fund contribution grows to by a target date. |
| as |
| how many months it takes to pay off a loan at a given repayment amount. |
| as |
| back out the interest rate a loan actually carries from its known payment and balance. |
|
|
| a return figure that does not assume every cash inflow gets reinvested at the project's own high IRR, a common criticism of a plain IRR on a development deal. |
Reading a finance function's arguments
The same argument names repeat across most of these:
rate: interest or discount rate for one period.
nper: total number of periods (e.g. 360 for a 30-year monthly loan).
pv / fv: present value (now) / future value (at the end, optional, 0 if left out).
pmt: the payment made each period.
type:
0if a payment lands at the end of each period (default),1if at the start.values: a range of cash flows, one per period, negative for money out and positive for money in.
guess: an optional starting estimate for
IRR/XIRR/RATE, which solve iteratively. Leave it out unless the function errors.